Engine 13.2.0 shipped on 2026-10-11 (tag 13.2.0, npm latest, neomjs.com deployed). ROADMAP.md still opens with ## Next: Engine 13.2 and points session intake at milestone #9, which has closed 141 items and still holds 9 open ones. The operator's direction on 2026-10-12:
a release every 1–2 weeks from now on;
the v13.3 roadmap as the post-release item;
two grid capabilities (optional dynamic row heights in buffered grids, and header menus) as the release's candidate outcomes.
Milestone v13.3 (#11, due 2026-10-25) exists. The team reconciled the lanes on A2A this morning, and each steward below self-selected.
The Problem
The file every session starts from describes a release that has shipped. Its shape was also sized for that release: 13.1.0 (2026-07-03) to 13.2.0 took 14 weeks, about 2,210 PR-subject commits and seven cornerstones. That pace is roughly 158 PR commits a week, so the update-roadmap skill's "≈ 100–150 merged PRs" already describes a one-to-two-week release. What broke was cutting nothing for 14 weeks. A 1–2-week release needs one thesis, two or three cornerstones and a visible deferred set.
The Architectural Reality
ROADMAP.md (53 lines) consists of:
the canonical-homes header (L1–7);
## Next: Engine 13.2 (L9–52), which holds:
the gate sentence;
the release-independent line table (L19–25) and its riders paragraph (L27);
the cornerstone table (L29–39), How it runs (L41) and the deferred list (L43–50);
Session intake (L52).
The update-roadmap skill governs the beat:
replace the section, never append to it;
name the cornerstones and their rationale, and let the milestone hold the full set;
make the deferred set explicit;
stewards self-select;
shipped history goes to the release notes.
#19565 (Clio, requirement custody) carries one line-level paragraph after the line table and before ## Next. Its build order, set by the operator on 2026-10-10, is that the paragraph rides this rewrite and has no PR of its own.
The Fix
Lift the line table and its riders paragraph to file level, above ## Next, and point the Engine row's gate at ## Next. They describe the release lines, not one release, so no cut should need to edit them.
Replace the 13.2 section with ## Next: Engine 13.3:
a one-sentence gate in user-observable terms and a short thesis;
a cornerstone table, each row with a done signal: content-sized rows (#9495, steward Ada), grid header menus (#19643, Vega) and a cut the maintainers can run (#19637, Grace);
carry-overs, named without becoming cornerstones;
How it runs (the cadence; the milestone is the live set) and the deferred set;
Point the shipped-history line at the 13.2.0 release.
Disposition milestone #9's nine open items (carry to #11, de-milestone, or leave with their owner) and record each one on this ticket.
Carry #19565's paragraph, How the line is re-read., at file level after the line table and before ## Next, mirroring the Institution's.
Acceptance Criteria
## Next names Engine 13.3 with a one-sentence observable gate, at most three cornerstones (anchor · steward or "open" · done signal), an explicit deferred set and a pointer to milestone #11. No 13.2 cornerstone or history stays inline.
The line table and its riders paragraph sit at file level above ## Next, and the Engine row points at ## Next rather than naming a release.
The shipped-history link names 13.2.0.
No client is named anywhere in the diff.
Each of milestone #9's nine open items has a recorded disposition on this ticket.
#19565's ACs 1–4 hold for the paragraph. It has five elements, each in its own sentence, links D#19394 and its first synthesis, names no date that would stale, and adds no table, file, counter, label or workflow. The cross-family reviewer records the stranger read (#19565's AC-4) in the review. #19565's AC-5, the line on D#19394, follows the merge.
Post-Merge Validation
#19565 closes as completed, citing the merge commit. Its own text says it closes with this rewrite's PR, and a PR resolves only one ticket.
D#19394 records the engine half (#19565's AC-5) in comment 18879350. The body's artifact-(ii) line is its author's to update.
Live latest-open sweep: the latest 20 open issues at 2026-10-12T10:08:38Z show no equivalent. The only open ROADMAP title is #19565, the paragraph, which is out of scope here. A2A claim sweep: my 09:51Z claim precedes Vega's 10:01Z claim, which she withdrew at 10:05Z. MC rationale sweep: no prior v13.3 roadmap. Own-assignment sweep: #14790, #18985, #19569, #13015 and #16217, none of which touches ROADMAP.md. Structure map: N/A, since this is a docs file.
Context
Engine 13.2.0 shipped on 2026-10-11 (tag
13.2.0, npm latest, neomjs.com deployed).ROADMAP.mdstill opens with## Next: Engine 13.2and points session intake at milestone #9, which has closed 141 items and still holds 9 open ones. The operator's direction on 2026-10-12:Milestone v13.3 (#11, due 2026-10-25) exists. The team reconciled the lanes on A2A this morning, and each steward below self-selected.
The Problem
The file every session starts from describes a release that has shipped. Its shape was also sized for that release: 13.1.0 (2026-07-03) to 13.2.0 took 14 weeks, about 2,210 PR-subject commits and seven cornerstones. That pace is roughly 158 PR commits a week, so the
update-roadmapskill's "≈ 100–150 merged PRs" already describes a one-to-two-week release. What broke was cutting nothing for 14 weeks. A 1–2-week release needs one thesis, two or three cornerstones and a visible deferred set.The Architectural Reality
ROADMAP.md(53 lines) consists of:## Next: Engine 13.2(L9–52), which holds:The
update-roadmapskill governs the beat:#19565 (Clio, requirement custody) carries one line-level paragraph after the line table and before
## Next. Its build order, set by the operator on 2026-10-10, is that the paragraph rides this rewrite and has no PR of its own.The Fix
## Next, and point the Engine row's gate at## Next. They describe the release lines, not one release, so no cut should need to edit them.## Next: Engine 13.3:## Next, mirroring the Institution's.Acceptance Criteria
## Nextnames Engine 13.3 with a one-sentence observable gate, at most three cornerstones (anchor · steward or "open" · done signal), an explicit deferred set and a pointer to milestone #11. No 13.2 cornerstone or history stays inline.## Next, and the Engine row points at## Nextrather than naming a release.Post-Merge Validation
Merged as
9b9e47b0cb(#19644, 2026-10-12). #19565 is closed as completed. The dispositions are in issuecomment-6122137250.Out of Scope
Related
Milestone #11 · #19565 · #9495 · #19643 · #19637 · #14790 · #18985 · #19640
Live latest-open sweep: the latest 20 open issues at 2026-10-12T10:08:38Z show no equivalent. The only open
ROADMAPtitle is #19565, the paragraph, which is out of scope here. A2A claim sweep: my 09:51Z claim precedes Vega's 10:01Z claim, which she withdrew at 10:05Z. MC rationale sweep: no prior v13.3 roadmap. Own-assignment sweep: #14790, #18985, #19569, #13015 and #16217, none of which touchesROADMAP.md. Structure map: N/A, since this is a docs file.Origin Session ID: daac81df-5205-405e-a3af-aec56e5cca45 Retrieval Hint: "v13.3 roadmap 1-2 week cadence content-sized rows header menus cut without ruleset bypass"