From da1325c8a1dce1a17a46e0967a6a1fca413cb300 Mon Sep 17 00:00:00 2001 From: Matt Mabrey Date: Thu, 24 Sep 2026 16:40:03 -0700 Subject: [PATCH] T11.7: full verification pass - wave 11 closed out --- docs/waves/wave-11.md | 43 +++++++++++++++++++++++++++++++++---------- 1 file changed, 33 insertions(+), 10 deletions(-) diff --git a/docs/waves/wave-11.md b/docs/waves/wave-11.md index 2e0b91b..4cd4929 100644 --- a/docs/waves/wave-11.md +++ b/docs/waves/wave-11.md @@ -240,18 +240,41 @@ test and `seed_demo.py`, run the full suite. **Done when:** -- [ ] all `CR-019` acceptance criteria in `decisions-2026-09-17.md` are met or - a failure is stated with a reason -- [ ] screenshots committed -- [ ] smoke test and `seed_demo.py` both still pass -- [ ] full test suite passes +- [x] all `CR-019` acceptance criteria in `decisions-2026-09-17.md` are met or + a failure is stated with a reason — all met +- [x] screenshots committed — `admin-390.png`/`admin-1440.png` (and + `creator`/`sop` at both widths, touched by T11.6's script-tag removal) +- [x] smoke test and `seed_demo.py` both still pass — 27/27, verified + 2026-09-24 against the exact branch state about to be considered + deployable +- [x] full test suite passes — verified 2026-09-24: ran all 39 + `tests/*_check.py` scripts plus the `usage_events` migration + round-trip. Result: 38/39 exit 0. + - `token_check.py` exits 2 with no arguments by design (needs `--out` + or `--compare`) — a CLI-invocation detail, not a test failure; + already confirmed non-regression in wave 10. + - `generalinfo_check.py` has one pre-existing failure (a raw colour + literal in `html/wp-creation-styles.css`, a file no wave 11/13 task + touched) — already diagnosed as pre-existing in wave 10. + - `autosave_check.py` **did** regress from T11.6 (it asserted the + retired analytics tracker still wrote to localStorage) — found by + this run, fixed same day (commit `4f3a94b`), now 33/33. + - Migration (T11.1): SQLite upgrade → downgrade → upgrade round-trip + clean; `alembic upgrade ... --sql` against the `postgresql` dialect + renders valid DDL (`TIMESTAMP WITH TIME ZONE`, `JSON`, no + SQLite-only syntax) — no `BL-027`-class defect. --- ## Wave 11 exit criteria -- [ ] real, server-side activity data exists per user, indefinitely retained -- [ ] the admin console shows it, filterable by date/project/user/tool -- [ ] export works in both raw and sanitized form -- [ ] the old per-browser report is gone, not duplicated -- [ ] `CR-019` fully accounted for, no open acceptance criteria +- [x] real, server-side activity data exists per user, indefinitely retained +- [x] the admin console shows it, filterable by date/project/user/tool +- [x] export works in both raw and sanitized form +- [x] the old per-browser report is gone, not duplicated +- [x] `CR-019` fully accounted for, no open acceptance criteria + +Wave 11 is closed out as of 2026-09-24. `CR-020` (wave 12) remains reserved +and unstarted. `D18`/wave 13 (`T13.2` onward) remains paused pending an Okta +API credential, per standing instruction — `T13.1`'s session changes were +included in this same verification pass and did not regress anything above.