amadan
Paul ruled 2026-10-24, taking every recommendation: (1) census rows accepted as proposed, Edge.Reload kept as a read-free hint; (2) copy MV-O259..O263 approved with the N = 1 case pluralised to "approximately 1 minute"; MV-O263 is a refusal fragment outside copy scope; (3) the known transients accepted as documented; (4) self-serve moves stay off until every edge runs plan 3. Being applied on self-serve-moves-3 after plan 2's merge; then CI and the inert merge.
Plan 3 (holding page, alias rule, probe mode) is built and Astra-READY: rulings owed open
On branch self-serve-moves-3
Plan 3 is built on self-serve-moves-3 (stacked on plan 2's 5992af09), all seven tasks review-clean, and Astra's whole-branch review reached READY at 0c33ee54 after three rounds (the ledger and reports are under .superpowers/sdd/2026-10-22-self-serve-moves-3-holding-page/ on DOCS-T1). Inert behind CARLOSSELFSERVEMOVES=offline and plan 1's lifetimes cutover: the schema column routealiases.explicit, alias provenance, the edges-file offline_moves field (every reader inventoried and audited) and probe mode are additive. What needs you:
- Census: PROPOSED-self-serve-moves-3 rows (plan14-root-reads-self-serve-moves-3.tsv; note docs/superpowers/notes/census-proposal-self-serve-moves-3.md). One reclassification to rule on: Edge.Reload now reads nothing itself (listRegistry does, once per tick) and is recorded as a read-free hint rather than removed, since the census rejects a legacy row with no reads.
- Copy: the holding page's rows MV-O259..O262 in docs/superpowers/plans/2026-10-06-moves-phase1-copy.md and MV-O263 "not served here" (a refusal fragment, perhaps outside the human-text scope). At N = 1 the page reads "approximately 1 minutes": say whether to pluralise.
- Known transients, accepted by review, for your eyes: a held row's first edges-file publication carries no offline time, so a remote edge shows the no-estimate sentence for up to about 30 s; a custom domain's first landing hold omits the domain until the target's DNS stamp lands, while the source's hold still pages it; after the open a custom domain has no publisher until that stamp (existing alias behaviour, not new).
- Rollout: a mixed-version fleet cannot give the holding-page guarantee (a pre-plan-3 edge ignores offlinemoves and routes to the stale publication); fine as an upgrade interval with admission off, not with active self-serve moves. Every edges-file reader on this branch ignores offlinemoves; Astra checked older readers by source only, not the oldest binary actually running on flagship.
- CI: the host-side kills (#359) continue intermittently; this branch has three green runs (5992af09, d88aaf31, and plan 3's own earlier tip) when a run survives.
Merge: inert, with you present, after plans 1 and 2 (stacked). Plan 4 (cleanup) is next: its rev 4 and an Astra round, then the build.