coulomb/the-custodian
4
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

docs: record central fleet projection reset (CUST-WP-0068-T09)
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Image main-54b09ee. the-custodian reset-ack then fleet refuse-mode:
52 applied, 69 noop, 2 identifier-collision refusals, 0 retirements.
Fleet-ack not run — nothing was refused for retirement.
This commit is contained in:
codex 2026-08-28 21:42:05 +02:00
parent 989806a1c7
commit 5c6d8df755
2 changed files with 100 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

11
workplans/CUST-WP-0068-cache-only-work-record-recovery.md
View file

@ -468,6 +468,17 @@ longer derives. Rows with no `record_id` are left alone. Tests in
are all closed (0 open). Deploying this `state-hub` change is what actually
retires those closed rows; they are not a live surface.
**Central run (2026-08-28).** Image `main-54b09ee`, Helm revision 48.
`the-custodian` reset-ack applied first (retired `interactive-the-custodian`;
13 tasks created, 125 updated, 0 cancelled). Fleet refuse-mode then ran
in-cluster across 125 repositories: 52 applied, 69 noop, 2 refused, 2
unreadable, 0 errors. Totals: 122 workplans updated, 149 tasks created,
745 tasks updated, **0 retired**, 0 cancelled. Fleet-ack was not run —
nothing was refused for retirement. The two refusals are identifier
collisions (`RAIL-BS-WP-0003/0005/0008/0009` held by `railiance-cluster`;
`RAIL-HO-WP-0004` held by `railiance-infra`) which acknowledgement does
not authorise. Evidence: `docs/recovery/fleet-projection-reset-2026-08-28.md`.
## Disposition of duplicate task identities (2026-08-26)
Establishing task identity (`STATE-WP-0083-T06`) exposed 35 duplicate identities