Context
#19185 (iteration 2) swept the notes to 0b79d4d1c4, and #14800's cut list (IC 5815935089) starts the cut's sweep there. Since then, besides #19185 itself, 19 merges have landed on dev (6fd8f8b774, 2026-09-25 15:10Z), and the notes cite none of them. Sweeping them now, while their PRs are hours old, leaves the cut with only its own items: /release-notes §3 has the cut consume deposits, never re-mine cold.
The Problem
- The notes are missing these reader-facing changes:
- two VDOM delta repairs (#19189, #19191);
findBy and forEach, which were quadratic (#19193);- two external contributors' fixes for curated issues (#19200, #19089);
prepare inside a git-dependency build (#19205);- two Workstation tear-out repairs (#19208, #19212);
- the portal's DevIndex card and home-page links (#19184, #19221);
- the contributor claim path (#19195, #19211).
Store#forEach now passes one shared, read-only copy as its callback's third argument, where 13.1 passed a fresh copy per call. Code that mutates that argument can see the difference, and the upgrade table has no row for it.- The banner still says "iteration 1 of N", although #19185 was iteration 2.
The Fix
In resources/content/release-notes/v13.2.0.md:
- Add one line per reader-facing merge, in its chapter, and check each claim against its PR (§4).
- Add a Public behavior to check row for
Store#forEach's third argument.
- Change the banner to iteration 3.
On #14800, move the cut list's sweep start to this PR's sweep head. The internal merges ride the Full Changelog (#19182, #19214, #19216, #19218, #19198, #19207, #19199), and the PR body lists them.
Acceptance Criteria
Out of Scope
- The cut's own items: the
blob/dev → 13.2.0 re-point, the designations, the refreshed counts, the Full Changelog and removing the banner.
- #19157's path move, which comes after the cut.
Related
#14800 (parent) · #19183 and #19185 (iteration 2) · #19157
Sweeps at 15:12Z:
- Live latest-open: the latest 20 open issues, none equivalent.
- Org search (
13.2 notes): #14800, #19101, #14790, #19047 and #17871, none equivalent.
- A2A: the last 30 messages in every read state, no claim on the notes.
- MC:
query_raw_memories on the late-merge sweep, 6 results, no conflicting decision.
- Own assignments: #14800 (the parent) and #19157 (the path move after the cut).
Origin Session ID: d2d30528-b6fe-423b-86ce-ab945396a201
Authored by Grace (Claude Opus 5.5, Claude Code) 🖖
Context
#19185 (iteration 2) swept the notes to
0b79d4d1c4, and #14800's cut list (IC 5815935089) starts the cut's sweep there. Since then, besides #19185 itself, 19 merges have landed ondev(6fd8f8b774, 2026-09-25 15:10Z), and the notes cite none of them. Sweeping them now, while their PRs are hours old, leaves the cut with only its own items:/release-notes§3 has the cut consume deposits, never re-mine cold.The Problem
findByandforEach, which were quadratic (#19193);prepareinside a git-dependency build (#19205);Store#forEachnow passes one shared, read-only copy as its callback's third argument, where 13.1 passed a fresh copy per call. Code that mutates that argument can see the difference, and the upgrade table has no row for it.The Fix
In
resources/content/release-notes/v13.2.0.md:Store#forEach's third argument.On #14800, move the cut list's sweep start to this PR's sweep head. The internal merges ride the Full Changelog (#19182, #19214, #19216, #19218, #19198, #19207, #19199), and the PR body lists them.
Acceptance Criteria
0b79d4d1c4to the PR's sweep head has its line.Store#forEachrow./release-notes§5).Out of Scope
blob/dev→13.2.0re-point, the designations, the refreshed counts, the Full Changelog and removing the banner.Related
#14800 (parent) · #19183 and #19185 (iteration 2) · #19157
Sweeps at 15:12Z:
13.2 notes): #14800, #19101, #14790, #19047 and #17871, none equivalent.query_raw_memorieson the late-merge sweep, 6 results, no conflicting decision.Origin Session ID: d2d30528-b6fe-423b-86ce-ab945396a201
Authored by Grace (Claude Opus 5.5, Claude Code) 🖖