| index 0d785b5b0..56eaba0c4 100644 |
| --- a/docs/superpowers/plans/2026-10-06-moves-phase1-copy.md |
| +++ b/docs/superpowers/plans/2026-10-06-moves-phase1-copy.md |
| @@ -710,10 +710,10 @@ MV-O181 is the usage line with `stage` added. It replaces MV-O56, whose withdraw |
| | MV-O188 | move.go | The staged copy of <host> is removed. Run carlos move offline finish --host <host> to end the move. | approved | |
| | MV-O189 | docs/site/cli.md | `stage` is optional and comes before `start`. It copies the instance's data to the region it moves to while the instance keeps serving, and each time it runs it copies only what is new. The more it has copied, the less is left to copy while the instance is offline. Until `start`, `abort` removes the staged copy and the instance is never offline. | approved | |
| |
| -Three more console door refusals for a staged move (`internal/console/apiinstancemove_offline.go`, Astra round 2), pending Luna's review. MV-O190 is what `start` and `seal` answer when the box that staged the instance (the stager, pinned on the record at the stage) no longer publishes an edges file in the source region: its absence is not proof that it stopped copying, so the step waits for it or the operator aborts. `<box>` is the stager, `<from>` the source region's name. MV-O191 is the stage door's refusal of a target whose data bucket is a source box's own, where a staged copy would replace the serving replica. MV-O192 is what `stage`, `start` and `seal` answer once the target publishes another data bucket or region than the one the stage fixed on the record: the staged copy is in the stored bucket and is never followed elsewhere. |
| +Three more console door refusals for a staged move (`internal/console/apiinstancemove_offline.go`, Astra round 2), approved by Luna 2026-10-21 (MV-O192 as Luna rewrote it). MV-O190 is what `start` and `seal` answer when the box that staged the instance (the stager, pinned on the record at the stage) no longer publishes an edges file in the source region: its absence is not proof that it stopped copying, so the step waits for it or the operator aborts. `<box>` is the stager, `<from>` the source region's name. MV-O191 is the stage door's refusal of a target whose data bucket is a source box's own, where a staged copy would replace the serving replica. MV-O192 is what `stage`, `start` and `seal` answer once the target publishes another data bucket or region than the one the stage fixed on the record: the staged copy is in the stored bucket and is never followed elsewhere. |
| |
| | id | file | text | status | |
| |---|---|---|---| |
| -| MV-O190 | internal/console/apiinstancemove_offline.go | <box>, which staged <host>, no longer publishes an edges file in <from>. bring it back or abort the move | pending | |
| -| MV-O191 | internal/console/apiinstancemove_offline.go | <to> publishes the same data bucket as <from>. a staged copy there would replace the serving one | pending | |
| -| MV-O192 | internal/console/apiinstancemove_offline.go | <to> now publishes a different data bucket than the one <host> was staged in. abort the move and stage it again | pending | |
| +| MV-O190 | internal/console/apiinstancemove_offline.go | <box>, which staged <host>, no longer publishes an edges file in <from>. bring it back or abort the move | approved | |
| +| MV-O191 | internal/console/apiinstancemove_offline.go | <to> publishes the same data bucket as <from>. a staged copy there would replace the serving one | approved | |
| +| MV-O192 | internal/console/apiinstancemove_offline.go | <to> now publishes a different data bucket or region from what was recorded when <host> was staged. abort the move and stage it again | approved | |