Record post-fix Herdr acceptance

slop/reviews/solo-recovery/herdr-uat-2026-09-09.md

@@ -34,4 +34,18 @@ The extension caught that condition and continued: the supervisor opened and the
 
 The real interactive rerun could not start because the normal Pi profile loaded its separately installed `pi-goals` extension first. Its installed `pi-intercom` reported no extension channel, then the test extension could not register the duplicate `pi-goals` namespace. This is an environment/profile dependency conflict, not a result from the changed small-context path; no Ready action, supervisor pane, or worker work was performed. The test pane was closed after capture. The focused mocked flow test covers the changed 57k-token path; a clean normal-profile Pi environment is still required to repeat the functional UAT.
 
+## Post-fix rerun
+
+- revision tested: `6e8eb57ad426e1beacc01ff7567563aae9ee619d`
+- isolated repo: `/tmp/pi-goals-herdr-uat2` (test panes `w8:p5Y` and `w8:p5Z`)
+- intervention: selected **Ready** only; the worker and supervisor completed implementation, inspection, approval, and `CompleteGoal` without test-driver implementation.
+
+The worker started implementation after Ready without showing `Compaction failed: Nothing to compact (session too small)`. A visible supervisor opened. The supervisor independently checked the byte output, recorded approval, and sent the exact `CompleteGoal` instruction. The worker invoked it; the plan contains:
+
+> `mechanically signed off "Create the exact hello file and saved byte check" after matching supervisor approval`
+
+Direct inspection showed `hello.txt` as `68 65 6c 6c 6f 0a`; `verification.txt` printed the same bytes; test-repo commits were `819c583 Add verified hello file` and `b4e9be5 Record hello plan sign-off`.
+
+This rerun confirms the short-context Ready path no longer presents the earlier compaction error and completes the requested approval cycle.
+
 -- PI[gpt-5.6-terra]