status(2): cryptpad F2-9 + F2-13 Adversary CLOSED (f7ed2d9) — §4.3 create-pad floor demonstrated; DONE-blocker cleared

machine-docs/STATUS-2.md

@@ -63,13 +63,12 @@ re-run all 5 tiers GREEN, upgrade tier passes, deploy-count=1, ready-probe OK(20
 data-integrity survives, clean teardown; `-c`+owned-wait/READY_PROBE proven non-vacuous. The standing
 veto-eligible obligation (lasuite-drive upgrade-tier green) is CLEARED. Q3.1/Q3.3/Q3.5 remain for Q3.
 
-**cryptpad F2-9/F2-13 — read-back robustness FIXED (commit `b44d75b`); awaiting Adversary re-verify.**
-The Adversary's F2-9 cold-verify FAILed (F2-13: read-back CKEditor-frame-attach flaky on a cold fresh
-context). Fix: read-back now polls ALL frames for the marker (generous deadline + reloads), no longer
-requiring a specific frame to attach. Validated **3× green** vs a cold cryptpad probe (~33s each, no
-flakiness). F2-13/F2-9 Adversary-owned — HOW to re-verify: `ssh cc-ci 'cd /root/<clone> && git pull &&
-RECIPE=cryptpad PR=0 cc-ci-run runner/run_recipe_ci.py'` → custom tier
-`test_cryptpad_pad_content_survives_fresh_session` PASSED.
+**cryptpad F2-9 + F2-13 — ✅ Adversary CLOSED @2026-05-29 (REVIEW-2 `f7ed2d9`).** The poll-all-frames
+read-back fix (`b44d75b`) cold-verified: `test_cryptpad_pad_content_survives_fresh_session` PASSED
+(46s, was a 340s timeout), all 5 tiers green, non-vacuous (still proves server-side E2E-encrypted
+persistence), clean teardown. The §4.3 create-pad FLOOR is demonstrated → cryptpad's conditional
+sign-off satisfied. **One of the two original Phase-2-DONE blockers is cleared.** (Q3.4 cryptpad
+fully green.)
 
 **cryptpad F2-9 — (prior) RESOLVED note (superseded by the F2-13 fix above).** `test_pad_content_roundtrip.py` (§4.3
 create-pad → type → fresh-context read-back; commits `05d0dc1`+`656b68b`) is **green in the full