Terminal predicate: Engine 13.3's release note, .github/RELEASE_NOTES/v13.3.0.md, tells what 13.3 shipped to the release-notes bar, passes the §7 cut-readiness checklist at the cut head, and the 13.3 cut (#19652) publishes it.
Problem
13.3 is the first Engine release on the one-to-two-week cadence the ROADMAP set after 13.2 ("Next: Engine 13.3 — The Grid Fits Its Content"). Milestone v13.3 is due 2026-10-25. Its cut record #19652 authors the note "through the release-notes epic" and keeps the notes out of its own scope, but that epic does not exist. Without the file, publish.mjs prepare stops on .github/RELEASE_NOTES/v13.3.0.md is missing (buildScripts/release/releaseState.mjs:90).
The arcs are cheapest to mine now, while their sessions are fresh; #14800 was seeded on that lesson. Since 13.2.0 (published 2026-10-11T22:37Z), GitHub search counted 34 merged PRs in neo, 11 in neo-stage, 6 in Brain and 0 in Institution at 2026-10-13T14:02Z. These are search counts; the note's scope comes from the corpus script at the cut (§2).
The bar now includes pictures. The operator's verdict on a 13.2 draft asked for a narrative that focuses on what matters, and for screenshots (#14800 comment); the final 13.2.0 note carries nine images. 13.3's release gate is behaviour you can see.
Why an epic
The release-notes workflow (§1) makes notes an epic by design: an early iteration-1 draft under a status banner, mining-driven refinement leaves, and a final cut-readiness iteration. Each is a one-PR leaf with its own cross-family review.
Intended solution
- The three cornerstones lead, each mined before it is drafted (§3): content-sized rows (#19658, closed; steward Ada), grid header menus (#19643; steward Vega) and a cut the maintainers can run (#19637; steward Grace). The steward who lived an arc mines it cheapest, so each deposits one mining comment here once the arc has landed: session ids, PR chain, timeline, numbers.
- Screenshots of what the gate names: the 10k wrapped-text grid holding its rows through scrolling, and a header menu filtering by checked values with live counts.
- Also in 13.3, taken from the §2 scope run rather than memory. Known candidates: the Brain-gated e2e tier on every Engine PR (#19657, after the
dev-push burn-in of #19656) and the Portal's featured Workstation reaching the package (#19640).
- Honest bounds: e2e-proven behaviour stays apart from bounded witnesses, such as the header menu's 100k timing.
- Iteration 1 merges early under the banner; the last iteration regenerates scope at the cut head and removes it.
Out of scope
- The cut mechanics and the version bump (#19652).
- What 13.3 contains: milestone v13.3 and the ROADMAP decide that.
- Blog posts (#13383).
- Brain and Institution notes, which belong to their own release lines.
Avoided traps
- Writing the plan instead of the release. A cornerstone that misses the window moves to 13.4 (ROADMAP, "How it runs"), so the note describes what merged by the cut head. Cornerstone 2's last leaf (#19671, in review as #19711) is the live case.
- Shrinking the release ("just a grid release"): §1 rule 4.
- A leaf that bundles drafting with cut mechanics.
Related: #19652 (the cut) · #14800 (13.2's notes) · ROADMAP "Next: Engine 13.3" · .agents/skills/release-notes/
Filing-time sweeps (2026-10-13 14:01–14:05Z): live latest-20 open neo issues, no equivalent; A2A claims in all read-states through 14:02Z, none on release notes; MC 2 queries (13.3 notes authorship; release cadence and notes overhead), 12 results, no ruling against a 13.3 notes epic, and the operator's cadence guidance (milestone-based releases, 2026-06-15; several releases allow several notes, 2026-09-23) supports one; own-assignment 4 open, none overlapping; 25 open epics read (3 carry a Terminal predicate line, the rest by title), none shares this predicate, #14800 is 13.2's. Structure map: N/A, an Engine release document with no Agent OS placement.
Retrieval Hint: "Engine 13.3 release notes epic" · "The Grid Fits Its Content" · "v13.3.0.md"
Terminal predicate: Engine 13.3's release note,
.github/RELEASE_NOTES/v13.3.0.md, tells what 13.3 shipped to the release-notes bar, passes the §7 cut-readiness checklist at the cut head, and the 13.3 cut (#19652) publishes it.Problem
13.3 is the first Engine release on the one-to-two-week cadence the ROADMAP set after 13.2 ("Next: Engine 13.3 — The Grid Fits Its Content"). Milestone v13.3 is due 2026-10-25. Its cut record #19652 authors the note "through the release-notes epic" and keeps the notes out of its own scope, but that epic does not exist. Without the file,
publish.mjs preparestops on.github/RELEASE_NOTES/v13.3.0.md is missing(buildScripts/release/releaseState.mjs:90).The arcs are cheapest to mine now, while their sessions are fresh;
#14800was seeded on that lesson. Since 13.2.0 (published 2026-10-11T22:37Z), GitHub search counted 34 merged PRs in neo, 11 in neo-stage, 6 in Brain and 0 in Institution at 2026-10-13T14:02Z. These are search counts; the note's scope comes from the corpus script at the cut (§2).The bar now includes pictures. The operator's verdict on a 13.2 draft asked for a narrative that focuses on what matters, and for screenshots (#14800 comment); the final 13.2.0 note carries nine images. 13.3's release gate is behaviour you can see.
Why an epic
The release-notes workflow (§1) makes notes an epic by design: an early iteration-1 draft under a status banner, mining-driven refinement leaves, and a final cut-readiness iteration. Each is a one-PR leaf with its own cross-family review.
Intended solution
dev-push burn-in of #19656) and the Portal's featured Workstation reaching the package (#19640).Out of scope
Avoided traps
Related: #19652 (the cut) · #14800 (13.2's notes) · ROADMAP "Next: Engine 13.3" ·
.agents/skills/release-notes/Filing-time sweeps (2026-10-13 14:01–14:05Z): live latest-20 open neo issues, no equivalent; A2A claims in all read-states through 14:02Z, none on release notes; MC 2 queries (13.3 notes authorship; release cadence and notes overhead), 12 results, no ruling against a 13.3 notes epic, and the operator's cadence guidance (milestone-based releases, 2026-06-15; several releases allow several notes, 2026-09-23) supports one; own-assignment 4 open, none overlapping; 25 open epics read (3 carry a Terminal predicate line, the rest by title), none shares this predicate, #14800 is 13.2's. Structure map: N/A, an Engine release document with no Agent OS placement.
Retrieval Hint: "Engine 13.3 release notes epic" · "The Grid Fits Its Content" · "v13.3.0.md"