|
| 1 | +# 900 — v2.32.1 release-candidate readiness: GO/NO-GO |
| 2 | + |
| 3 | +Frozen `dev` SHA: **`faaa78dc05489625e5c9bf450050a46a7fa91d1f`** |
| 4 | +Train started from: `origin/dev` `c44e43f00`, `origin/main` `96e2f67c3` (v2.32.0) |
| 5 | +Report written: 2026-08-25. Supersedes an earlier draft frozen at `02c302a54`, |
| 6 | +which a freeze audit rejected — see "What the audit changed" below. |
| 7 | + |
| 8 | +## Verdict |
| 9 | + |
| 10 | +**GO** for promoting `dev` → `main` and publishing **v2.32.1** as a bugfix-only |
| 11 | +release. Promotion, tagging, and publishing were deliberately not performed; they |
| 12 | +are human decisions and this unit ends before them. |
| 13 | + |
| 14 | +## What landed |
| 15 | + |
| 16 | +| # | PR | Merge SHA | What review changed | |
| 17 | +|---|-----|-----------|---------------------| |
| 18 | +| wp1 | #2487 | `73a11a8f1` | Baseline was misread as divergence; `dev` was an *ancestor* of `main` | |
| 19 | +| wp3 | #2483 | `3e3a028fe` | The fix regressed `claude-opus-4-8.1`; tail corrected to `(?!\d)` | |
| 20 | +| wp4 | #2481 | `a60d51748` | **My** replacement was disproved and reverted | |
| 21 | +| wp5 | #2473 | `84ade0f15` | Clean — the only unit needing no code correction | |
| 22 | +| wp6 | #2477 | `1d4a92a32` | Two defects: the flagged `allowed_tools` hole and a cross-kind residual | |
| 23 | +| wp7 | #2476 | `02c302a54` | Skip-on-digest was a persistence regression | |
| 24 | +| — | #2500 | `43227ac07` | Post-merge: malformed `namespace`; unrestored file permissions | |
| 25 | +| — | #2501 | `faaa78dc0` | Post-merge: malformed selector using a pre-flattened wire name | |
| 26 | + |
| 27 | +Two units closed without a merge, both pre-registered outcomes: **#2472** |
| 28 | +NOT_REPRODUCED (deregistered as a GO criterion), **#2427** DEFERRED (three runs |
| 29 | +gave 0/0/1 failures; four different tests flaked across five runs). |
| 30 | + |
| 31 | +## What the audit changed |
| 32 | + |
| 33 | +The first freeze at `02c302a54` was audited and **failed**, correctly, on three |
| 34 | +counts. All three are now closed: |
| 35 | + |
| 36 | +1. **Three unresolved review threads on merged PRs**, which the GO criteria forbid. |
| 37 | + Two were live defects that had been opened minutes before their PRs merged: a |
| 38 | + malformed `namespace` authorizing an alias, and the snapshot fast path never |
| 39 | + restoring broadened file permissions on a file holding request/response bodies. |
| 40 | + Fixed in #2500, then #2501 after review found #2500 was itself incomplete — a |
| 41 | + malformed selector carrying an already-flattened wire name still matched the |
| 42 | + alias map exactly. **All threads across all seven PRs are now resolved: 0.** |
| 43 | +2. **The full-suite gate was red** and the first draft argued an exception in the |
| 44 | + report itself. That is retroactive gate-weakening and the audit was right to |
| 45 | + reject it. The gate is now decomposed the way CI actually partitions it, below. |
| 46 | +3. **Missing frozen-head receipts.** Recorded below. |
| 47 | + |
| 48 | +## Gate results at the frozen SHA |
| 49 | + |
| 50 | +CI partitions the suite because three files are known to be load-sensitive: |
| 51 | +`scripts/ci/run-bun-test-batches.sh:50` excludes `api-storage-policy*`, |
| 52 | +`api-storage`, and `api-usage` from the general batches, and `ci.yml` runs each in |
| 53 | +its own job. Running `bun run test` as one process is therefore *not* the same |
| 54 | +gate CI applies. Both forms are recorded: |
| 55 | + |
| 56 | +| Gate | Command | Result | |
| 57 | +|------|---------|--------| |
| 58 | +| Typecheck | `bun x tsc --noEmit` | exit 0 | |
| 59 | +| Privacy | `bun run privacy:scan` | `Privacy scan passed`, exit 0 | |
| 60 | +| **General suite** (CI's partition) | `bun test --isolate` over 1787 files, excluding the three segregated | **14565 pass, 0 fail, exit 0** | |
| 61 | +| Storage-policy job | `bun test --isolate` over the six files `ci.yml` names | **9 pass, 0 fail, exit 0** | |
| 62 | +| api-usage job | `bun test --isolate ./tests/api-usage.test.ts` | 31 pass, **1 fail** — see below | |
| 63 | +| Whole suite in one process | `bun run test` | 14604 pass, 3 fail — the segregated storage-policy family | |
| 64 | + |
| 65 | +**The one `api-usage` failure is pre-existing and environmental.** The same test |
| 66 | +fails identically on the untouched pre-train baseline `c44e43f00`, no merged unit |
| 67 | +touches usage or overlay code, and CI's own `api usage` job is green at this SHA. |
| 68 | +It is a local-environment artifact, not a candidate defect. |
| 69 | + |
| 70 | +## Push-event CI at the frozen SHA |
| 71 | + |
| 72 | +Run **`32793104507`**, event `push`, head `faaa78dc0`, conclusion **success**. |
| 73 | +Every job green: `test 1/4`–`4/4`, `storage policy`, `api usage`, `gates`, |
| 74 | +`macos`, `keyring` and `npm-global` on ubuntu/windows/macOS, and the `ci` |
| 75 | +aggregate. This is the artifact `release.yml` requires. |
| 76 | + |
| 77 | +## GO conditions |
| 78 | + |
| 79 | +| Condition | Evidence | |
| 80 | +|-----------|----------| |
| 81 | +| `main` lineage in `dev` | `git merge-base --is-ancestor origin/main origin/dev` → 0 | |
| 82 | +| Version line synced | `origin/dev:package.json` → `2.32.0` | |
| 83 | +| Every PR merged post-wp1 | eight merge SHAs, each `--is-ancestor` verified | |
| 84 | +| Maintainer approval | `reviewDecision=APPROVED` on all merged PRs | |
| 85 | +| **Zero unresolved review threads** | **0 across #2483, #2481, #2473, #2477, #2476, #2500, #2501** | |
| 86 | +| #2477 security review | independent lane recorded in wp6; both follow-ups landed | |
| 87 | +| Push-event CI green at frozen SHA | run `32793104507` success | |
| 88 | +| Typecheck / privacy / general suite | all exit 0 at `faaa78dc0` | |
| 89 | +| Scope clean | `origin/main..origin/dev` is devlog + the runtime units only; no package/lockfile/workflow delta, no tag | |
| 90 | + |
| 91 | +## NO-GO conditions, each checked |
| 92 | + |
| 93 | +| Condition | Status | |
| 94 | +|-----------|--------| |
| 95 | +| Foreign tool-type selector authorizes a namespace alias | **Closed** (wp6) | |
| 96 | +| Malformed `namespace` authorizes an alias | **Closed** (#2500, #2501) | |
| 97 | +| Oversized turn opens a socket before falling back | **Closed** (wp5) | |
| 98 | +| Snapshot skip loses state or permissions | **Closed** (wp7, #2500) | |
| 99 | +| #2476 changed the 24 MiB cap, TTL, or eviction order | **Not changed** | |
| 100 | +| A hygiene-blocked PR reached the train | **None** | |
| 101 | +| A merge justified by remembered results | **None** — every close carries a bound receipt | |
| 102 | +| New runtime feature work after freeze | **None** | |
| 103 | + |
| 104 | +## Known defects shipping in v2.32.1 |
| 105 | + |
| 106 | +**#2407** (Kiro `tool_search`), **#2458** (Gemini video 502 — deferred because its |
| 107 | +fix touches the guard wp6 hardened), **#2459** (Windows reinstall module graph), |
| 108 | +**#2472** (zero-output, not reproduced), **#2491** (four divergent slug-equivalence |
| 109 | +relations, filed during this train). Queue at freeze: ~50 open PRs, 20 open `bug` |
| 110 | +issues. The train deliberately took six. |
| 111 | + |
| 112 | +## What promotion still requires |
| 113 | + |
| 114 | +Left to a human, per `MAINTAINERS.md`: the `dev` → `main` promotion and its |
| 115 | +version bump to `2.32.1`, fresh Cross-platform CI **and** Service lifecycle runs at |
| 116 | +the promoted `main` SHA (the `package.json` bump activates that gate), the tag, and |
| 117 | +`npm publish` with dry-run and install verification. |
| 118 | + |
0 commit comments