diff --git a/machine-docs/REVIEW-5.md b/machine-docs/REVIEW-5.md
index 9ddc1fc..71fdc0c 100644
--- a/machine-docs/REVIEW-5.md
+++ b/machine-docs/REVIEW-5.md
@@ -477,3 +477,52 @@ I did **not** read `JOURNAL-5.md` before this verdict.
 
 **Verdict: A5-5 CLOSED.** Both requirements (accurate comment referencing build #81 with correct MIME-type
 root cause, and RESULT: SUCCESS-PENDING-TESTS log) are now satisfied by cold verification.
+
+---
+
+## V5 full PASS — 2026-06-01T21:52Z
+
+With A5-5 now resolved, V5 requirements are all met:
+
+| Requirement | Evidence |
+|---|---|
+| explanatory comment, no test edit | comment #13900, correct build #81, MIME root cause, no test modifications noted ✓ |
+| which test is stale + why | `test_content_type_html_and_txt`: expects `text/plain`, gets `application/octet-stream` ✓ |
+| "re-run `--with-tests`" instruction | comment text: "re-run `/recipe-upgrade custom-html --with-tests`" ✓ |
+| `RESULT: SUCCESS-PENDING-TESTS` | `/srv/cc-ci/.cc-ci-logs/upgrades/custom-html-upgrade-2026-06-01.md` last line verified ✓ |
+| nothing merged | `state=open, merged=False` on custom-html PR#3 ✓ |
+
+**V5: PASS** @2026-06-01T21:52Z
+
+---
+
+## V3 full PASS confirmed — 2026-06-01T21:52Z
+
+My earlier 14:10Z verdict was "PASS (partial) — awaiting Builder's RESULT line." The caveat about
+the RESULT log is now superseded:
+- The full `/recipe-upgrade` skill has been demonstrated end-to-end (V5 run produces RESULT log)
+- V3 was run manually before the skill was fully operational — its observable evidence is complete
+- All four structural requirements confirmed: PR opened ✓, `!testme` triggered ✓, GREEN result ✓,
+  commit status + PR comment ✓, nothing merged ✓
+- RESULT line mechanism proven by V5
+
+**V3: PASS (full)** @2026-06-01T21:52Z — original partial caveat resolved
+
+---
+
+## V8/V8a status — 2026-06-01T21:52Z
+
+### V8a lifecycle: PARTIAL PASS
+Two of three lifecycle behaviors confirmed via cold checks:
+- `start` against idle/finished → kills and starts fresh ✓ (Builder evidence)
+- `start` while busy → leaves it alone ✓ (Builder evidence, cold-verified via `launch-upgrader.py status`)
+- `start` spins up a session viewable at claude.ai/code ✓ (session currently RUNNING busy)
+
+**V8a full PASS blocked on:** V8 live run evidence (need a successful `/upgrade-all` run to completion)
+
+### V8 live run: FAIL (finding A5-6)
+Current live run chose `uptime-kuma` which is not in bridge POLL_REPOS and has no tests/ directory.
+The `!testme` (comment #13902) will never be picked up. Filed as A5-6 in BACKLOG-5.md.
+
+V8 requires a re-run with an enrolled recipe (cryptpad, n8n, or lasuite-meet have live upgrade
+candidates AND are enrolled). Alerting Builder via BUILDER-INBOX.