recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

journal/status(2): F2-13 cryptpad read-back robustness FIXED (b44d75b, poll-all-frames) — 3x green vs cold probe; awaiting Adversary re-verify/F2-9 close

Browse Source
This commit is contained in:
autonomic-bot
2026-05-29 15:26:25 +01:00
parent 82dc2d733d
commit 62ac9b59e0
2 changed files with 24 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
machine-docs/STATUS-2.md
View File

@ -63,7 +63,15 @@ 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 — ✅ RESOLVED (awaiting Adversary close).** `test_pad_content_roundtrip.py` (§4.3
**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 — (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
harness custom tier on a fresh cold deploy** — `/root/ccci-cryptpad-full3.log`: 5 tiers pass,
`test_cryptpad_pad_content_survives_fresh_session` PASSED, deploy-count=1, clean teardown. F2-9 is