R-224..R-228 CLOSED: registers, capability map, campaign annotation, STATUS

Five closed in controller v0.202.0 + agent v0.126.0, each with its live or
red-proof evidence in the row. Five explicitly still open and named as such
rather than left to inference: R-214, R-220, R-221, R-213, R-202 — and R-220 is
flagged as currently worked around BY HAND on the campaign venue, which is the
only reason an app could be deployed there.

The capability map's recovery row STAYS FAIL and says why: fixes are not a
re-walk, nothing walked a customer end to end, and the customer-facing messages
were NOT re-driven live because /recovery correctly retires itself once the old
data is set aside — restoring that state is the reconfiguration the task forbade.

The campaign document is ANNOTATED, not rewritten: it records what was true when
it ran, and that is its value.

workspace-CLAUDE.md gains comment-vs-code entry 9 — the escrow header said the
errors were 'DISTINCT on purpose' and named THREE situations while a fourth was
folded into one of them, and a green test named the defect and did not prevent
it because it asserted a STRING one layer below the merge.

ROADMAP needed no collapse — it carries no rows for these IDs.

documentation/audits/CAMPAIGN-11-recovery-journey-2026-08-05.md

@@ -20,6 +20,21 @@ Evidence: `../tests/campaign11-evidence-2026-08-05/` — `journal.md` (Phases 0,
 
 ---
 
+> **ANNOTATION 2026-08-06 — what has since been fixed. The body below is NOT rewritten.** This
+> document records what was true when the campaign ran, and that is its value; the fixes are recorded
+> here and in `felhom-controller/REPORT.md`.
+>
+> **R-224, R-226, R-225, R-227, R-228 are CLOSED** in controller **v0.202.0** + agent **v0.126.0**.
+> The unlock path now classifies why it failed — from the value, never the text — and the message
+> that mentions typing is reachable only after a real refusal; anything unclassifiable renders a
+> neutral message rather than an accusation. Proven live on this venue: same wrong code, hub up →
+> `400`, hub REJECTed → `502` naming the connection and stating the code was **not used**, hub
+> restored → `400`.
+>
+> **Unchanged by that work:** the campaign's verdict, the RTO, and the capability map's recovery row,
+> which stays **FAIL** until a re-walk passes. **R-214, R-220, R-221 remain open**, and R-220 is still
+> worked around by hand on this venue.
+
 ## 1. Venue and baselines
 
 | | |