13.3.0 shipped on 2026-10-21 (#19652). The next day a short manual exploration of apps/workstation found a batch of dock and Workstation defects (#19982–#19993) that the team fixed and merged the same day, with follow-ups still landing (#20004, #20006, #20017, #20018). The operator's call (2026-10-22): the current state is a patch, not a feature release, and it ships once the recent tickets are done and the team is confident Workstation is stable. Three feat commits ride the patch by that call (#20010, a fix in substance; #19960 and #20011, small opt-in enhancements).
This ticket is the cut's record, on the #19652 precedent. It is not the release PR's close target: the release PR resolves a preparation leaf filed at cut time, so this record stays open until finish, npm and the Portal are verified. What "confident" means for this cut is the gate on D#19994 (the gate text, folded with Sophie's disposition); its ticks live here so the steward can tick them against receipts. The board is milestone v13.3.1.
The Cut
The milestone's open fixes land, or get an explicit disposition on this record (#20009's unknown trigger may stay open, since #19998 bounds the symptom; the operator accepts that or not).
Bump package.json to 13.3.1 and author .github/RELEASE_NOTES/v13.3.1.md on a cut-prep PR (the #19765/#19784 shape), one changelog row per merged PR since the 13.3.0 tag, reconciled against the live list. prepare drops v13.3.0.md itself.
Qualify the cut candidate (the header below) and run the gate on it.
File the preparation leaf, the release PR for v13.3.1. Then node buildScripts/release/publish.mjs prepare --rehearse --ticket <leaf> --body-file <body> prints every gate as ✅, and node buildScripts/release/publish.mjs prepare --ticket <leaf> --body-file <body> opens the release PR.
The operator merges it after its required checks and CodeQL pass. This is the cut's one human step.
node buildScripts/release/publish.mjs finish.
Brain-side post-release sync; Pages deploy; create-app publish, per their runbooks.
If a phase stops, re-running the same command continues it.
Qualification header (filled at the cut)
Engine revision · test and driver revision · Brain revision · browser/OS and worker mode · selected/executed/skipped/quarantined inventory · retained run links. Every gate tick below is bound to that candidate; a later source change re-qualifies on the new one.
Acceptance Criteria
Gate (from D#19994):
AC-1: Hosted Brain-gated NL tier green on the cut candidate with completed full-tier receipts for all shards; the single-test reds seen on dev this week (PremeasureRowsNL:77 at 058e374357, WorkstationMaximizeTabReorderNL:168 at 998f35a3bf) have a diagnosis, not a retry. (Ticked 2026-10-23 22:2xZ: run 40031596312 on dev 36a74c743c; the week's reds in the AC-1 ledger comment.)
AC-2: Three consecutive full e2e/workstation + e2e/dashboard runs on the candidate's tree, one worker, own Bridge, no new quarantine; every red re-run alone and dispositioned with its cause named; a run counts toward the three when every red in it is dispositioned as the harness, the infrastructure or a known test defect, none the engine; an engine red fails the gate until fixed on a new candidate. (Amended 2026-10-23 22:3xZ by the steward under the operator's delegation, with the amendment comment of 22:33Z as its record; the original wording, "runs green on the candidate … every 'green alone, red in the run' specimen (#20017, #20020, TearOutMatrix row 7, MaximizeOverflowMenu docked arm) fixed or dispositioned with its cause named", left what a dispositioned red does to a run's count unsaid. Ticked 22:4xZ: on the candidate's tree f9ffdca2c4 = dev 36a74c743c, runs 242/1/3, 241/2/3, 243/0/3; the three reds the known reload arm twice and one Memory Core ingress stall, each green alone; receipts in the census comment.)
AC-3: A 20-minute chartered walk of apps/workstation on the candidate by a named seat that authored none of the fixes, receipts retained, no unresolved release-blocking defect observed. (Ticked 22:2xZ: the operator's walk on 0ab667195e; findings #20081 (open, minor by his word) and #20082 (fixed by #20083 on the candidate); receipts in the qualification header.)
AC-4: No open release-blocking Workstation defect in the milestone; each residual has a ticket, an owner and a disposition recorded here. (Ticked 22:2xZ: residuals #20081, #20009, #19515, each with owner and disposition in the "no open row" comment.)
AC-5: The release PR ran dev's required checks and CodeQL, and nothing reached dev except through it; no ruleset bypass. (Ticked 23:2xZ: PR #20085, 51 checks green incl. CodeQL on 98fac97e43; merged by the operator at 23:26:44Z as dcae85851f; dev rules … bypass: never.)
AC-6: finish's squash push to main succeeded for the account that ran it, and the GitHub release body ends with the atomic-commit line. (Ticked 23:27Z: as neo-opus-vega, main 282e7ef452 → 24d865eb06, tree = the merge's; release 13.3.1 on dcae85851f ends with "All changes delivered in 1 atomic commit: 24d865e".)
AC-7: npm-publish.yml published 13.3.1 through Trusted Publishing (OIDC), with no token. (Ticked 23:33Z: run 40039753731 on the release event, + neo.mjs@13.3.1; npm view neo.mjs@latest version → 13.3.1 at 23:32:52Z.)
AC-8 (post-merge): the Portal's 13.3.1 notes route shows the atomic-commit line once the content sync archives the release; the Pages refresh from the published package needs no hand overlay. (Ticked 2026-10-24 00:1xZ: pages#52 (Grace, approved by Julia) merged by the operator at 00:14:21Z, deploy 40043974054 green 00:16:28Z; https://neomjs.com/#/news/releases/13.3.1 ends with "All changes delivered in 1 atomic commit: 24d865e"; the served releases.json lists 13.3.1 at 2026-10-23T23:27:07Z; update-neo-version from the published package, no hand overlay; Grace's receipt issuecomment-6377405202. The Knowledge Base asset and the corpus archive are in the AC-7/AC-8 receipt comment.)
Out of Scope
The contents of the patch (the milestone), the gate's design (D#19994), and the release notes' prose beyond the changelog rows.
Related
#19652 (the 13.3.0 cut record, the precedent) · #19637 (the two-phase release path) · D#19994 (the gate) · milestone v13.3.1
Live latest-open sweep: checked latest 20 open issues at 2026-10-22T22:58:40Z; no cut ticket for 13.3.1.
Keyword sweep ("Cut Engine v13.3.1", "release PR 13.3.1"): none.
A2A claim sweep: latest 30 messages, all read-states, at 22:58Z; no claim on the cut; open lane 5 in my 21:24Z posture broadcast had no taker.
MC sweep: the 13.3.0 cut records (Grace's cut-prep and prepare turns, Emmy's #19784 review): the cut-prep PR must carry the bump and the note together, and PublishReleaseNoteOrphan.spec fails CI if an older released note is retained after the bump, so step 2 keeps v13.3.0.md until prepare drops it only if that spec allows; verify before pushing.
Own-assignment sweep: #20009, #17918, #17416, #16212; none overlapping.
Lead-role convergence artifact: milestone v13.3.1 and the D#19994 gate.
Steward: me, unless Grace, who ran the 13.3.0 cut, claims it; the merge stays the operator's.
Context
13.3.0 shipped on 2026-10-21 (#19652). The next day a short manual exploration of
apps/workstationfound a batch of dock and Workstation defects (#19982–#19993) that the team fixed and merged the same day, with follow-ups still landing (#20004, #20006, #20017, #20018). The operator's call (2026-10-22): the current state is a patch, not a feature release, and it ships once the recent tickets are done and the team is confident Workstation is stable. Threefeatcommits ride the patch by that call (#20010, a fix in substance; #19960 and #20011, small opt-in enhancements).This ticket is the cut's record, on the #19652 precedent. It is not the release PR's close target: the release PR resolves a preparation leaf filed at cut time, so this record stays open until
finish, npm and the Portal are verified. What "confident" means for this cut is the gate on D#19994 (the gate text, folded with Sophie's disposition); its ticks live here so the steward can tick them against receipts. The board is milestone v13.3.1.The Cut
package.jsonto 13.3.1 and author.github/RELEASE_NOTES/v13.3.1.mdon a cut-prep PR (the #19765/#19784 shape), one changelog row per merged PR since the 13.3.0 tag, reconciled against the live list.preparedropsv13.3.0.mditself.node buildScripts/release/publish.mjs prepare --rehearse --ticket <leaf> --body-file <body>prints every gate as ✅, andnode buildScripts/release/publish.mjs prepare --ticket <leaf> --body-file <body>opens the release PR.node buildScripts/release/publish.mjs finish.If a phase stops, re-running the same command continues it.
Qualification header (filled at the cut)
Engine revision · test and driver revision · Brain revision · browser/OS and worker mode · selected/executed/skipped/quarantined inventory · retained run links. Every gate tick below is bound to that candidate; a later source change re-qualifies on the new one.
Acceptance Criteria
Gate (from D#19994):
devthis week (PremeasureRowsNL:77at 058e374357,WorkstationMaximizeTabReorderNL:168at 998f35a3bf) have a diagnosis, not a retry. (Ticked 2026-10-23 22:2xZ: run 40031596312 ondev36a74c743c; the week's reds in the AC-1 ledger comment.)e2e/workstation+e2e/dashboardruns on the candidate's tree, one worker, own Bridge, no new quarantine; every red re-run alone and dispositioned with its cause named; a run counts toward the three when every red in it is dispositioned as the harness, the infrastructure or a known test defect, none the engine; an engine red fails the gate until fixed on a new candidate. (Amended 2026-10-23 22:3xZ by the steward under the operator's delegation, with the amendment comment of 22:33Z as its record; the original wording, "runs green on the candidate … every 'green alone, red in the run' specimen (#20017, #20020, TearOutMatrix row 7, MaximizeOverflowMenu docked arm) fixed or dispositioned with its cause named", left what a dispositioned red does to a run's count unsaid. Ticked 22:4xZ: on the candidate's tree f9ffdca2c4 =dev36a74c743c, runs 242/1/3, 241/2/3, 243/0/3; the three reds the known reload arm twice and one Memory Core ingress stall, each green alone; receipts in the census comment.)apps/workstationon the candidate by a named seat that authored none of the fixes, receipts retained, no unresolved release-blocking defect observed. (Ticked 22:2xZ: the operator's walk on 0ab667195e; findings #20081 (open, minor by his word) and #20082 (fixed by #20083 on the candidate); receipts in the qualification header.)Cut mechanics (from #19652):
dev's required checks and CodeQL, and nothing reacheddevexcept through it; no ruleset bypass. (Ticked 23:2xZ: PR #20085, 51 checks green incl. CodeQL on 98fac97e43; merged by the operator at 23:26:44Z as dcae85851f;dev rules … bypass: never.)finish's squash push tomainsucceeded for the account that ran it, and the GitHub release body ends with the atomic-commit line. (Ticked 23:27Z: as neo-opus-vega,main282e7ef452 → 24d865eb06, tree = the merge's; release 13.3.1 on dcae85851f ends with "All changes delivered in 1 atomic commit: 24d865e".)npm-publish.ymlpublished 13.3.1 through Trusted Publishing (OIDC), with no token. (Ticked 23:33Z: run 40039753731 on the release event,+ neo.mjs@13.3.1;npm view neo.mjs@latest version→ 13.3.1 at 23:32:52Z.)https://neomjs.com/#/news/releases/13.3.1ends with "All changes delivered in 1 atomic commit: 24d865e"; the servedreleases.jsonlists 13.3.1 at 2026-10-23T23:27:07Z;update-neo-versionfrom the published package, no hand overlay; Grace's receipt issuecomment-6377405202. The Knowledge Base asset and the corpus archive are in the AC-7/AC-8 receipt comment.)Out of Scope
The contents of the patch (the milestone), the gate's design (D#19994), and the release notes' prose beyond the changelog rows.
Related
#19652 (the 13.3.0 cut record, the precedent) · #19637 (the two-phase release path) · D#19994 (the gate) · milestone v13.3.1
Live latest-open sweep: checked latest 20 open issues at 2026-10-22T22:58:40Z; no cut ticket for 13.3.1. Keyword sweep ("Cut Engine v13.3.1", "release PR 13.3.1"): none. A2A claim sweep: latest 30 messages, all read-states, at 22:58Z; no claim on the cut; open lane 5 in my 21:24Z posture broadcast had no taker. MC sweep: the 13.3.0 cut records (Grace's cut-prep and prepare turns, Emmy's #19784 review): the cut-prep PR must carry the bump and the note together, and
PublishReleaseNoteOrphan.specfails CI if an older released note is retained after the bump, so step 2 keepsv13.3.0.mduntilpreparedrops it only if that spec allows; verify before pushing. Own-assignment sweep: #20009, #17918, #17416, #16212; none overlapping. Lead-role convergence artifact: milestone v13.3.1 and the D#19994 gate.Steward: me, unless Grace, who ran the 13.3.0 cut, claims it; the merge stays the operator's.
Origin Session ID: 020c66cb-f735-4d6b-bb13-34f35a4b90ec Retrieval Hint: "cut record 13.3.1 Workstation patch release gate ticks publish.mjs prepare finish"