Sweep the 13.2 notes' merges since 036cb05a40

Context

The 13.2 notes (.github/RELEASE_NOTES/v13.2.0.md) were last swept up to 036cb05a40 by #19399 (PR #19400, merged 2026-10-05). The #14800 cut list keeps that commit as the start of the sweep at the cut. The cut has not happened yet. Measured at cec2fcce84, dev has 17 first-parent commits since then; 6 touch engine paths.

Sweeps:

• Live: the latest 20 open neo issues at 2026-10-06T15:29Z; no equivalent.
• A2A: the latest 25 lane claims; none on the notes.
• Memory Core: "13.2 release notes iteration sweep…", 4 results; the cut list sets the method, and nothing contradicts it.
• Own assignments: #14800 (the parent) and #15000 (unrelated).

The Problem

Two engine fixes a user can see are not in the notes:

• a hidden component stays removed when a sibling update merges into the parent's render (#19403);
• a fieldset's legend change reaches the DOM (#19405).

Three more change what a 13.2 reader can rely on:

• a field keeps its own margin-bottom whatever order the stylesheets load in (#19412);
• the Dock Layouts card ships visible (#19426);
• the release scripts stamp the note's frontmatter before the release index is built (#19410).

Two existing claims went stale:

• Line 190 says the Portal views and build generators that read the old content location "are tracked in #19166". #19408 closed #19166: the generators now take declared corpus and release-notes roots.
• The package chapter cites a consumer-runtime check that bundles before it packs, and calls the bundle decision (#18823) open. The operator's ruling recorded there (2026-09-18, restated 2026-10-06) is that the package ships no generated bundles and a workspace generates them, with npm run bundle-browser-deps or build-all, which runs it. The cut list carries this correction.

The claim-reply line (#19211) still describes the designed reply. #19414 fixed the first live reply's miscount, and the cut list asks for a live reply link or a stated bound.

The Architectural Reality

• .github/RELEASE_NOTES/v13.2.0.md is the authored path that publish.mjs reads (release-notes-workflow.md §6).
• The #14800 cut list sets the method: a line for each merge that changes what a 13.2 user sees, an upgrade row for each behaviour change, and everything else in the Full Changelog. The scope is engine-only (ruling of 2026-09-23).

The Fix

One iteration PR on v13.2.0.md:

1. Disposition every engine-path first-parent merge in 036cb05a40..<PR base>: a chapter line with its PR link, an upgrade row, or the Full Changelog.
2. Correct line 190 and the package chapter, citing the ruling on #18823.
3. Bound the claim-reply line by the live state: link a correct live reply if one exists, else say none has fired since #19414.
4. Move the banner to "iteration 5 of N", and move the cut list's sweep point to the PR base.

Acceptance Criteria

• Every engine-path first-parent merge in the window is dispositioned, and the PR body gives the count for each disposition.
• Every new claim links its PR. Line 190 and the package chapter match #19408 and the #18823 ruling.
• The claim-reply line states the live state, with a link or a bound.
• The banner reads iteration 5, and the #14800 cut list names the new sweep point.
• A cross-family review approves before the merge.

Out of Scope

• The cut itself: designations, final counts, and re-pointing blob/dev links to the tag (the #14800 cut list).
• The Brain and Institution lines: each writes its own notes.

Related

Parent #14800 · previous iteration #19399 · #18823 (the bundle ruling) · #19166 (closed by #19408).

Origin Session ID: 40a3c119-6419-4e87-9248-002c686708fe