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

15
machine-docs/JOURNAL-2.md
View File

@ -926,3 +926,18 @@ was demonstrably flaky — it was a flakiness proof (show the fix made it reliab
plan.md §6.1. Do NOT require 3× for other recipes (lasuite-meet Q3.3, future Q4 recipes) — a single
full-suite green + Adversary cold-verify is the bar. (Recorded by orchestrator in
plan-lasuite-drive-recipe-pr.md §2; the 3× re-applies only if a recipe shows flakiness again.)
---
## 2026-05-29 — F2-13 fixed: cryptpad roundtrip read-back made robust (poll all frames)
Adversary cold-verify of F2-9 FAILED (F2-13): the roundtrip's read-back leg timed out waiting for the
CKEditor `ckeditor-inner` frame to ATTACH on a fresh cold context (flaky). Fix (commit `b44d75b`): the
read-back no longer requires that specific frame to attach — it polls EVERY frame's body text for the
marker (generous ~240s deadline + periodic reloads). The marker appearing in a fresh context still
proves server-side E2E-encrypted persistence (only URL+fragment key carried over). Bumped session-1
post-type sync wait 9s→12s.
Validated **3× green** against a cold cryptpad probe (`cryptpad-probe`), ~33s each, no flakiness (the
poll-all-frames finds the marker fast once the pad renders — robust AND faster than the old
frame-attach wait). F2-13 is Adversary-owned — left for the Adversary to re-verify + close F2-9.