review(2): cryptpad F2-9 + F2-13 CLOSED — re-verify after fix b44d75b (poll-all-frames). create-pad roundtrip test_cryptpad_pad_content_survives_fresh_session PASSED (46s, was 340s timeout), all 5 tiers green, deploy-count=1, clean teardown. Fix non-vacuous (still asserts marker surfaces in fresh context = server-side encrypted persistence). §4.3 create-pad floor demonstrated; conditional sign-off satisfied

machine-docs/BACKLOG-2.md

@@ -373,7 +373,7 @@ Phase plan: `/srv/cc-ci/cc-ci-plan/plan-phase2-recipe-tests.md`
       specific tests were API-shape liveness, not create-and-read-back. F2-8 was the
       gate-blocker that drove the F2-X-pattern callout.
 
-- [ ] **F2-9 [adversary] — cryptpad (Q3.4) create-pad deferral: CONDITIONAL sign-off** —
+- [x] **F2-9 [adversary] — CLOSED @2026-05-29** (create-pad lift demonstrated green; was CONDITIONAL sign-off) —
       Plan §4.3: "cryptpad — create a pad and confirm it persists (note client-side-encryption:
       page is JS-rendered, so use Playwright, not bare curl)." DECISIONS.md §"Phase 2 Q3.4"
       documents three failed attempts (contenteditable+iframe, no fragment, no stable app-launch
@@ -594,7 +594,7 @@ Phase plan: `/srv/cc-ci/cc-ci-plan/plan-phase2-recipe-tests.md`
         wait proven non-vacuous (5 P7-negative unit tests pass + code-read of services_converged/
         wait_healthy/wait_ready_probes RAISE on stuck convergence). Verdict: REVIEW-2 "## Q3.2 … PASS".
 
-- [ ] **F2-13 [adversary] — cryptpad create-pad roundtrip FLAKY: read-back leg fails cold** — blocks
+- [x] **F2-13 [adversary] — CLOSED @2026-05-29** (was: cryptpad roundtrip read-back flaky) — blocks
       closing F2-9. Cold-verify @2026-05-29 (clean env, git==host d4eae4e, log
       `/root/adv-f29-cryptpad-135552.log`): `RECIPE=cryptpad PR=0 cc-ci-run runner/run_recipe_ci.py` →
       custom tier **FAIL**. `tests/cryptpad/playwright/test_pad_content_roundtrip.py::
@@ -616,3 +616,9 @@ Phase plan: `/srv/cc-ci/cc-ci-plan/plan-phase2-recipe-tests.md`
         maximal-subset basis stands. F2-9 was a CONDITIONAL sign-off → stays OPEN; this is not a VETO,
         not a passed-gate regression. Full detail: REVIEW-2 "## cryptpad F2-9 — NOT CLOSING".
       - Filed by Adversary @2026-05-29.
+      - **CLOSED @2026-05-29 (also closes F2-9):** fix `b44d75b` (poll-all-frames read-back) —
+        re-verify cold (log `/root/adv-f29-cryptpad-r2-143211.log`) `test_cryptpad_pad_content_survives_fresh_session`
+        **PASSED** (1 passed in 46.72s, was 340s timeout), all 5 tiers green, deploy-count=1, clean
+        teardown. Fix is non-vacuous (still asserts the unique marker surfaces in a FRESH context →
+        proves server-side encrypted persistence; returns False/fails if it doesn't). Verdict: REVIEW-2
+        "## cryptpad F2-9 + F2-13 — CLOSED".