amadan
copy: MV-N510-513 approved, MV-N21 withdrawal approved (Paul, 2026-10-15)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 file changed,
+5
−5
docs/superpowers/plans/2026-10-06-moves-phase1-copy.md+5 −5
diff --git a/docs/superpowers/plans/2026-10-06-moves-phase1-copy.md b/docs/superpowers/plans/2026-10-06-moves-phase1-copy.md| index 3a239bc5b..c6f42a60b 100644 |
| --- a/docs/superpowers/plans/2026-10-06-moves-phase1-copy.md |
| +++ b/docs/superpowers/plans/2026-10-06-moves-phase1-copy.md |
| @@ -468,19 +468,19 @@ Plan `docs/superpowers/plans/2026-10-15-moves-home-region-part2.md` (amadan #236 |
| | id | file | text | status | |
| |---|---|---|---| |
| -| MV-N512 | internal/moves/envreport.go (a T3 kind inside MV-N129's list) | region-present | pending | |
| +| MV-N512 | internal/moves/envreport.go (a T3 kind inside MV-N129's list) | region-present | approved | |
| Task 2b's row (fix round 3) is T3's refusal of a version 1 env report. A v1 report carries no instance layer names, so it cannot say whether a box variable such as HOSTNAME came from the instance's files or the box: a target on this release refuses it before comparing anything, fail closed, until the source runs this release too. |
| | id | file | text | status | |
| |---|---|---|---| |
| -| MV-N513 | internal/host/movesreport.go | the source reported its launch environment in an older format | pending | |
| +| MV-N513 | internal/host/movesreport.go | the source reported its launch environment in an older format | approved | |
| Task 5's rows are the Phase 1 request door's two new refusals of a home target. MV-N510 is Ruling R1: only a host-claim console admits a move into home, so the plain path refuses it before any read or write. MV-N511 is a box that sets `CARLOS_REGION` to the home's name. The console reads that box as home but the box does not, so it cannot take the move; the door names it before the staging check, which would otherwise answer MV-N20 for a bucket the box may well publish. |
| -Task 5 withdraws MV-N21 ("moves to the home region are not supported yet. the home publishes no staging lane"). The Phase 1 door no longer speaks it: MV-N510 replaces it on the plain path, and a host-claim console admits the move. The legacy door (switch off) keeps main's em-dash sentence, which the gate exempts as main's own (`movesLegacyFuncs`) until Plan 6 Task 8 retires that door. MV-N2, MV-N5, MV-N20, MV-N23, MV-N30 and MV-N177 keep their approved text. Only their fills change: `<to>` (and MV-N20's `<list>`) now name the home by its configured name instead of the empty code. MV-N16 already did. |
| +Task 5 withdraws MV-N21 ("moves to the home region are not supported yet. the home publishes no staging lane"), withdrawal approved by Paul 2026-10-15. The Phase 1 door no longer speaks it: MV-N510 replaces it on the plain path, and a host-claim console admits the move. The legacy door (switch off) keeps main's em-dash sentence, which the gate exempts as main's own (`movesLegacyFuncs`) until Plan 6 Task 8 retires that door. MV-N2, MV-N5, MV-N20, MV-N23, MV-N30 and MV-N177 keep their approved text. Only their fills change: `<to>` (and MV-N20's `<list>`) now name the home by its configured name instead of the empty code. MV-N16 already did. |
| | id | file | text | status | |
| |---|---|---|---| |
| -| MV-N510 | internal/console/apiinstancemove.go | moves into the home region need host claims. this console runs without them | pending | |
| -| MV-N511 | internal/console/apiinstancemove.go | <box> sets CARLOS_REGION, so it cannot take a move into the home region | pending | |
| +| MV-N510 | internal/console/apiinstancemove.go | moves into the home region need host claims. this console runs without them | approved | |
| +| MV-N511 | internal/console/apiinstancemove.go | <box> sets CARLOS_REGION, so it cannot take a move into the home region | approved | |