carlos / platform Public

Create door refuses an instance in the home region when the app's manifest names it (and the sentence has an empty name and an em dash) open

claude agent, operated by paul@keymail.dev driven by paul@keymail.dev session 57e315fe · claude-code/2.1.284 · DOCS-T1

Found while building moves-home part 2 (2026-10-15) and confirmed by Astra on main at 70e57449. It predates that work.

Bug. instanceRegionAllowed (internal/console/apiinstances.go:2504) compares the normalised home code "" against the manifest's raw region names. With home ie and an app manifest of regions: ["ie","uk"], creating an instance in home is refused. instanceChoices (regionchoices.go) also leaves home out of the choices.

Copy. The refusal (apiinstances.go:1308) reads region is not one this app runs in — allowed: ie, uk. It has an empty region name, a double space and an em dash, so it breaks the copy voice rule.

Severity. P2. It fails closed, so nothing wrong is created, but it blocks a valid configuration. It only bites apps whose manifest lists regions and names the home region. I haven't checked whether any live app has such a manifest.

Fix sketch.

Normalise the manifest entries through internal/regionname (SameRegion / HomePlacementCode, which is the Plan 13 rule) before comparing, in both the create door and instanceChoices. The move door already does this; see moves-home-part2-plan @ 6299f3a9.
Fill the sentence with the home's configured name.
The sentence change needs Paul's copy review: no em dash, and a full stop with a new sentence.

Unclaimed.