docs(STATE-WP-0083-T04): record central fleet refuse-mode run
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

125 repos on main-54b09ee: 52 applied, 69 noop, 2 refused
(identifier collisions), 2 unreadable, 0 errors, 0 retirements.

Assistant: grok
Assistant-Session: 01a04996-76e8-7f53-b971-1885cfbed436
This commit is contained in:
tegwick 2026-08-28 21:42:05 +02:00
parent 70dddf56f8
commit 0020286bab

View file

@ -219,6 +219,15 @@ Its behaviour on failure is the part that matters, and all three are tested:
694 tests pass. Needs deployment before it can run against central.
**Ran against central (2026-08-28).** Image `main-54b09ee`. Fleet
refuse-mode over 125 repositories: 52 applied, 69 noop, 2 refused
(identifier collisions on `railiance-bootstrap` and `railiance-hosts`;
acknowledgement does not authorise those), 2 unreadable
(`vergabe_teilnahme`, `markitect-project`), 0 errors. Zero workplans
retired, zero tasks cancelled. `the-custodian` had already been
reset-acked and reported `noop` on the fleet pass. Evidence lives in
`the-custodian/docs/recovery/fleet-projection-reset-2026-08-28.md`.
## Retire what the reset replaces
```task