Purpose and current status
The newer source includes narrow installer/amendment/recovery lanes. They reconcile a specific reviewed interrupted installation or owned layout. They are not universal upgrade commands, broad permission repair, a takeover installer or a production recovery guarantee. Use only the release-specific diagnosis and qualified exact before/after bundle. Keep the original failure and private journals.
Every protected recovery lane
| Source command family | Parsed options | Required review |
|---|---|---|
| `amend-prebootstrap-coordinator plan | apply --from-bundle OLD --to-bundle NEW` | --from-bundle, --to-bundle, --disposable-vm, --authorize, --plan |
| `recover-core-directories plan | apply` | --disposable-vm, --authorize, --plan |
| `recover-core-ipc plan | apply` | --disposable-vm, --authorize, --plan |
| `recover-core-startup plan | apply` | --disposable-vm, --authorize, --plan |
| `amend-empty-layout plan | apply --from-bundle OLD --to-bundle NEW` | --from-bundle, --to-bundle, --disposable-vm, --authorize, --plan |
| `recover-mariadb-bootstrap plan | apply --from-bundle OLD --to-bundle NEW` | --from-bundle, --to-bundle, --disposable-vm, --authorize, --plan |
| `recover-mariadb-partial-bootstrap plan | apply --from-bundle OLD --to-bundle NEW` | --from-bundle, --to-bundle, --disposable-vm, --authorize, --plan |
| `amend-post-services-verifier plan | apply --from-bundle OLD --to-bundle NEW` | --from-bundle, --to-bundle, --disposable-vm, --authorize, --plan |
| `amend-prepayload plan | apply --from-bundle OLD --to-bundle NEW` | --from-bundle, --to-bundle, --disposable-vm, --authorize, --plan |
| `recover-agent-registration plan | apply` | --disposable-vm, --authorize, --plan |
| `recover-install-runtime plan | apply --from-bundle OLD --to-bundle NEW` | --from-bundle, --to-bundle, --disposable-vm, --authorize, --plan |
| `recover-service-identities plan | probe | apply --bundle CURRENT` |
| `recover-website-runtime plan | apply` | --disposable-vm, --authorize, --plan |
Plan, apply and verification
These lanes commonly require the current and successor protected bundles, a separately reviewed plan digest, explicit disposable-VM designation and exact authorization phrase printed by that release. Some observation-only overlays use only the existing protected installation state. A CLI family name is not permission to choose arbitrary files or process identities. Inspect read-only output first; do not infer flags not printed by the matching executable.
Preserve recovery
Retain original package/signature evidence, Root-owned witnesses, ordinary worker operation/generation and native receipt state. A one-agent or CREATE-only compatibility repair does not imply a full schema/renderer upgrade. Independent readiness must bind exact executable digest, current invocation and loaded confinement. Do not manually remove activation gates, requeue SQL, delete a migration ledger or downgrade an old binary after newer journal admission. Full hosting, DNS/TLS/mail and cross-machine reconstruction remain separately qualified.