commit bbcc1acd2bb342722b0e7c78913d9d1ba18d050d
parent 46ec18ed7b9fe9098b23952d22816b04e079a6a6
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date: Thu, 24 Sep 2026 17:24:28 -0400
plans: release 3 final suites on edd9fb3b (editor 621, export 188); why-3a-first is the plan's rule
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Diffstat:
2 files changed, 3 insertions(+), 8 deletions(-)
diff --git a/plans/STATE.md b/plans/STATE.md
@@ -39,7 +39,7 @@ Previous: 2026-09-23 — slices 2 and 4a on `main` @ `ae2fa5a9`, gate B done
**Gates on `ef88ac4d`:** tsc clean; common 1723; editor unit 67; scripts 156 + 1 skip; mcp
219; editor and export builds green (on `7dfd7508`, code-identical). Full e2e:
-`<final-suite-counts>` (3a's branch: 280/280 over 41 spec files; 4b's merged tip: the plan's
+`editor **621 passed, 0 failed, 36.3 min**; export **188 passed, 0 failed, 5.9 min** (run from a worktree detached at `ef88ac4d`, ports 3311/3310, log `final-e2e-r3.log`)` (3a's branch: 280/280 over 41 spec files; 4b's merged tip: the plan's
34 specs, 190/190).
**Next:** the release-3 rollout to :3001 (editor only — `git diff 1e27f7c3..ef88ac4d -- umtool`
diff --git a/plans/one-core-phase-3.md b/plans/one-core-phase-3.md
@@ -588,12 +588,7 @@ lanes were meant to resume. Sharp fails to load in the primary and every worktre
`c6d955ac`, `main` (`3241fed2`) merged in as `7dfd7508`, and the follow-up `b3cebcf8` (the
merged-tip gates). `ef88ac4d`'s code is byte-identical to `7dfd7508`'s.
-**Why 3a first:** the two branches share no code file — only `editor/CHANGELOG.md` and this
-record, the two files the `7dfd7508` merge conflicted on — so either order was safe, and 3a
-was ready first (review fixes in, post-review e2e green). Merging it first let 4b, the slice
-still being gated, re-run its whole gate set on a tip that already carried 3a
-(`7dfd7508`), so the release's end state was measured once, as a whole, rather than each
-slice only on a base without the other.
+**Why 3a first:** the plan's rule, decided before the worktrees were cut — merge the UI slice first, then let 4b merge `main` and re-run its whole gate set, so a schema regression shows through the NEW tables (`ChannelsTable`, `JobRow`), not through components about to be deleted. The two branches share no code file (only `editor/CHANGELOG.md` and this record, the two files the `7dfd7508` merge conflicted on), so the order cost nothing; 3a was also ready first (review fixes in, post-review e2e green), and the release's end state was then measured once, as a whole, on `7dfd7508`.
**Scope, decided with the operator 2026-09-24.** Release 2 goes live first, as a prelude, so
both branches start from the code the operator runs (the live editor had served a
@@ -612,7 +607,7 @@ diff empty. 4b on the merged tip `7dfd7508` (code-identical to `ef88ac4d`): tsc
editor and export `next build` green, `ƒ /api/view/[name]`, no zod in either `.next/static`;
numbers tool diff empty over 3,832 lines; e2e the plan's 34 specs **190/190** (12.7 min).
-Final full suites on `ef88ac4d`: <final-suite-counts — filled after the run>
+Final full suites on `ef88ac4d`: editor **621 passed, 0 failed, 36.3 min**; export **188 passed, 0 failed, 5.9 min** (run from a worktree detached at `ef88ac4d`, ports 3311/3310, log `final-e2e-r3.log`)
**Record corrections made while checking the two records against the code** (2026-09-24;
where a record and the code disagreed, the code won):
