Wave 7 exit - the creator is a page, the hold clears, QA is in the loop

Nine of nine exit criteria verified, eight ticked. The ninth is recorded
open, deliberately: at rest the creator reads 1,954px / 900px = 2.17 screens
against the strict 2.0 encoding of D3's "roughly two screen heights" (down
from 5,399px). The criterion was amended once already; whether 2.17 satisfies
"roughly" is a product judgment - BL-022 carries the number, the remaining
~154px of chrome, and the question. form_structure_check keeps the strict
check red until it is answered.

Wave totals: 10 tasks (T7.1-T7.10), 8 new probe suites (frame, form
structure, hold, warning, triage, QA gate + capture sink, files + offline,
sticky bar, creator dialogs, usage - 305 new checks), one Alembic migration
(wp_files), no real email sent anywhere on this branch.

Items: B7, F6, D1-D10, CR-015, A1, A2, A6, CR-014, CR-007, B6, S1(creator), D5

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
2026-08-19 11:47:23 -07:00
parent 7f712b7e00
commit b1a7fe04bc
2 changed files with 28 additions and 9 deletions

View File

@@ -474,3 +474,22 @@ deliberately deferred.
line, but it deserves its own verification against the capture sink.
- **Suggested wave or follow-up:** wave 9 backlog sweep (`T9.9`), verified with
the `tests/qa_gate_check.py` sink pattern.
### BL-022 — F6's "roughly two screen heights": 2.17 against a strict 2.0
- **Found during:** T7.2, re-measured at the wave 7 exit
- **Where:** `html/wp-creation-index.html` page chrome; `tests/form_structure_check.py`
- **What:** the creator at rest measures **1,954px against a 900px viewport at
1440px** — 2.17 screens. `D3` amended `F6`'s criterion to "no single view
exceeds roughly two screen heights at rest"; the probe encodes "roughly two"
strictly as 2.0 and is red by ~154px. The remainder is page chrome, not form:
the context bar (~67px), the release banner (~45px + margin), and header/
toolbar spacing. The form itself went from 5,399px to this.
- **Why not now:** the criterion was amended once already, in writing (`D3`).
Deciding that 2.17 "is roughly 2" — or trimming chrome that other items placed
deliberately (`A2` made the banner the ONE warning; the context bar is the
SOP identity strip) — is a product call, not an implementation detail.
- **Suggested wave or follow-up:** needs Nick. Either bless 2.17 (one-line probe
change, criterion satisfied as written) or name the chrome to compress and it
becomes a small T9 task. The strict check stays red so the question cannot be
forgotten.