Keep the runtime ready after a repeated retirement catalog #1267
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/retirement-repeat-check-20260909"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
After a catalog retires projects, the next runtime sync compares the empty removal set with the original retirement declaration. It rejects the already applied catalog and makes every replica unready.
Skip the retirement transition check when both revision and digest match the applied catalog. Reconciliation still runs so it can restart stopped workers. New catalogs must still declare the exact removed projects.
Validation: the existing retirement test now repeats sync and checks readiness. It failed with project_retirement_mismatch before the fix. All 12 runtime tests and strict compilation pass afterward.
This fault currently blocks the normal API and the mobile layout release in #1266.
c5125b8a7b327ce1f67b