Tell the 13.2 Engine story through reader outcomes

Context

The flat resources/content/release-notes/v13.2.0.md draft on dev@d4a65cf9 is iteration 1 of the release-notes epic #14800. An operator read the merged survey addition in PR #19117 and rejected its tone and narrative arc. The sentence beginning “Chapter nominations: none from this slice” illustrates the miss: it reports an editorial routing decision to the public reader. That decision already has a durable home in the NEO_INLINE_CODE_4 survey ledger.

The problem is broader than that sentence. The operator's second correction is about scale: 27 Grid PRs across four days are a side quest in a release window with roughly 995 Engine PRs at the #14800 census snapshot. SharedWorker groups also belong in the 13.2 scope. A further operator correction separates Dock's own pane vocabulary from the older Neo.dashboard.Panel class: citing generic Container/Panel retention beside the Dock migration falsely implies an API relationship. The current opening introduces issue/PR arithmetic and release gates before letting a developer picture the Dock workspace or grid edit they will use. The Dock chapter gives epic and line-count tables before the visible change; the Grid chapter counts authors and rate-limit days before its real turning point, the public example's six failed interactions. The apps/guides section exposes 44-PR partitioning and a nominations verdict, then offers a setup checklist.

The Problem

A release note is a reader-facing explanation of what changed and why it matters. Here, internal survey method has become the document's organizing voice. The result makes a large Engine release feel like an internal status report and leaves the path from symptom → architectural turn → user outcome hard to follow. This fails the /release-notes §5 precedent bar: v13.0 and v13.1 make a concrete change or failure legible first, then use numbers and citations as proof. The v13 notes reset (#12695, #12698; Memory Core session 728442d6-a2a0-4481-a631-a3112ce6d703) already identified the same failure class: an inventory taking the place of a release narrative. That precedent is a source to apply, not another set of counts to paste into the note.

The Architectural Reality

• The flat staging file is the publish.mjs source of authority. /release-notes §1 requires the “iteration 1 of N” banner on dev until the final cut; the correction must keep it while removing unrelated process prose from the chapters.
• #14800 owns the notes; #19100 holds the 44-PR audit. PR #19113 merged the upgrade path under #19102 on 2026-09-23, and its full migration table is incorporated here. The #19101 Dock survey was deposited on 2026-09-24 for this notes PR to fold; no second PR edits the staging file.
• The #14800 Engine census partitions 995 PRs at its snapshot: 344 Dock, 187 components, 172 build/package, 126 tests, 102 runtime, 44 apps/guides, and 20 organism meta. The area survey tickets are #19101, #19099, #19102, #19098, and #19100. These are mining populations, not chapter quotas; later merges require a cut-time refresh.
• SharedWorker groups need a dated status distinction. The App Worker logical Group binding and transaction history shipped in #18351/#18360. Canvas SharedWorker per-window-group ownership and group-routed ports remain under #19103 and D#18730; describe that work as release scope, not a shipped capability until its PR merges and passes acceptance. Runtime SharedWorker reply/error/routing repairs are separate shipped changes.
• The Dock story already has evidence for the old tab-selection/resize failure, the serializable App Worker document, real browser-window projections and restoration. The Grid story already has the broken public example, the logical editing session across pooling, and the six-of-eleven evaluation reversal. Honest limits remain: the second-window renderer kill is open; screen-reader and real OS IME runs have not been claimed.

The Fix

Make one editorial pass over the existing note, not a new notes surface. Mine the full Engine population and choose the release's real hero arcs from reader outcomes, rather than preserving the first two chapters by inertia. Dock remains a major arc; Grid may be a compact chapter or digest beat after comparison with runtime, components, build/package and SharedWorker work. For each chosen arc, lead with what a developer can do or feel, then explain the specific failure and engine decision that changed it. Turn the apps/examples/guides inventory into a short reader path from seeing a working example to building and extending one. Keep source links and honest bounds adjacent to the claims they qualify. Move survey counts, re-home decisions, author/seat bookkeeping and chapter nominations to the existing issue/PR record, not another public-note appendix. Preserve the required iteration banner and the eventual Full Changelog tail.

Contract Ledger

Scope timing

This leaf completes the current-dev editorial iteration and can merge with the required staging banner. The final cut-time breadth, link and scope-number refresh remains on parent epic #14800's cut iteration; it cannot be an acceptance gate for an early staging merge under /release-notes §1.

Acceptance Criteria

• Reconcile all seven #14800 Engine population slices and their rehomes against dev at this PR's review head, with targeted PR-body/source checks. Select the hero arcs by user value and causal evidence. The opening and two-minute view represent Engine breadth; no 27-PR/four-day Grid count stands in for the release. The epic's final cut iteration owns the later breadth and number refresh.
• Public chapter prose contains no survey partition, chapter-nomination verdict, author/seat accounting or “what the next editor should do” instructions. The mandatory iteration banner and cut-time Full Changelog contract remain.
• Each retained Engine arc preserves source-backed claims and its honest limits. Describe Dock panes as named ordinary component configurations; do not present retained Neo.dashboard.Container or Neo.dashboard.Panel classes as replacements for the removed experimental Dock* files. Keep the published 13.1 Dock* upgrade boundary and the open second-window, screen-reader and real-IME limits wherever those arcs appear. Cover shipped logical Groups and SharedWorker runtime repairs; include per-window Canvas SharedWorker groups in 13.2 scope with their still-open #19103 status until acceptance evidence supports past tense. No new claim rests on a title or memory alone.
• Apps/examples/guides read as an Explore → Build → Extend path with verified live or dev links. The Buffered List remains clearly local until its hosted 13.2 route exists; the #19100 ledger retains the 44-PR audit.
• The merged #19113 upgrade-path contribution is incorporated without overwriting its migration facts. Markdown renders cleanly, links are checked, and the final PR receives cross-family editorial review after the full Engine story is coherent.

Decision Record impact

none — this is an editorial iteration of the existing staging note, with no runtime or architectural contract change.

Out of Scope

Runtime or app changes; publishing/cutting 13.2; operator-owned Release Type/Stability; changing source PR classifications in area ledgers without evidence.

Avoided Traps

• Deleting the iteration banner because it sounds internal — the release-notes workflow requires it until cut.
• Treating the 27 Grid PRs as the release's scale, writing per-window Canvas SharedWorker groups in past tense while #19103 is open, or implying that a Dock pane is a Neo.dashboard.Panel.
• Replacing the ledger with unsupported promotional prose — every factual sentence stays falsifiable at a PR, ticket or live example.
• Moving bookkeeping into footnotes of the same public note — the issue ledger is its proper home.
• Linking the unreleased Buffered List as though the hosted 13.2 site already served it.

Related

Parent epic #14800 · merged PR #19117 / #19100 survey ledger · upgrade-path #19102 / PR #19113 · Dock survey #19101 · /release-notes precedent set.

Live latest-open sweep: checked the latest 20 open Engine issues at 2026-09-23T12:59Z (newest #19118); no equivalent 13.2 narrative-refinement leaf. A2A in-flight sweep: latest 30 messages across read states at 12:59Z; no overlapping claim. MC sweep: six results, with v13 whole-document bar session 728442d6-a2a0-4481-a631-a3112ce6d703 as prior art and no v13.2 decision. KB ticket sweep: #12695/#12698 are v13 precedents, not duplicate v13.2 work. Own-assignment sweep: #19114, #15520, #14230 open; none owns release-note prose. Exact local archive sweep: #10321/#14475 are older release mechanics, not this correction.

Origin Session ID: 01a0cd6f-8c21-7171-9d8c-b15bea1e1e96

Retrieval Hint: query_raw_memories("13.2 release notes chapter nominations survey breadth narrative arc DockLayouts grid cell editing")

Authored by Euclid (GPT-6, Codex).