commit eea0500c33c263cd20736945f5db023ad6bb9bee
parent 73fb48fdc8fde39fec0d8f65480fd7a10d4aaf5b
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date: Mon, 27 Jul 2026 02:30:08 -0400
Record the Stage B2 verification sweep
Editor e2e in default dev mode: 369 passed / 21 failed of 390. The suite
grew by the 5 new digest specs and all 5 pass. The 21 failures are the
known-on-base set, with two differences: cut-release failed once rather
than twice, and undownloaded.spec:53 appeared in its place — verified
passing in isolation (all 4 in 22.6 s), which is the CPU-contention flake
already recorded. Export suite 141/141. common: 346 unit tests, tsc clean
in all three packages.
Note: running the suite let cut-release.spec rewrite editor/CHANGELOG.md
and make a real "Release editor 9.9.10" commit, exactly as FACTS.md warns.
Both were undone — the changelog content here is unchanged from before the
run.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Diffstat:
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/plans/FACTS.md b/plans/FACTS.md
@@ -683,6 +683,13 @@ every one of the 21 is accounted for below. Do not chase these.
| `site-scope.spec` dashboard stats | 1 | fails on base |
| `cut-release.spec` (both) | 2 | expected with a dirty working tree — the spec rewrites the real `editor/CHANGELOG.md` and makes a git commit |
| `sync-break-on-existing-tree.spec` | 1 | **passes in isolation** — order-dependent flake, not a base failure |
+| `undownloaded.spec:53` | 1 | **passes in isolation** (all 4 in 22.6 s) — the CPU-contention flake already recorded below, seen again 2026-07-27 |
+
+**Re-verified again 2026-07-27** after Stage B2: **369 passed / 21 failed of 390** (the suite
+grew by the 5 new digest specs, all passing). The 21 are the same set, with two differences
+worth noting: `cut-release` failed **once** rather than twice, and `undownloaded.spec:53`
+appeared in place of the second `cut-release` — it passes in isolation. Export suite:
+**141/141**.
The `deploy-page` (×3), `new-channel-onboarding` (×5) and `site-scope` failures — **9 specs**
— are all *strict-mode locator violations* ("resolved to N elements"): specs written against
@@ -695,7 +702,11 @@ because 9 permanently-red specs train everyone to ignore the suite's exit code.
`widget.spec`'s "no buttons" assertion fails under `dev:test` because `next dev` injects a
Dev Tools button; it passes under `E2E_MODE=start`. (It passed in this run.)
-The 9 `digest.spec.ts` tests all pass.
+The `digest.spec.ts` tests all pass — now **12**, the original 9 plus three for the per-video
+review panel (renders provenance + warnings, flips to stale after an identity change,
+corrections land in the overrides sidecar with the machine file untouched). `settings.spec`
+gains two more that also pass: the Digest fieldset round-trips, and an unrelated save does
+not reset `timestampMode`/`promptVariant`.
Run `pnpm e2e` in **default dev mode** — `E2E_MODE=start` serves a stale build. Kill stale
dev servers by port between runs.
