diff --git a/workplans/STATE-WP-0083-forge-derived-projection-reset.md b/workplans/STATE-WP-0083-forge-derived-projection-reset.md
index 8f99c08..66dfc44 100644
--- a/workplans/STATE-WP-0083-forge-derived-projection-reset.md
+++ b/workplans/STATE-WP-0083-forge-derived-projection-reset.md
@@ -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