[bokelley]

What

Integrate the published 3.1.32 release records on 3.2.x, so Build Check goes green again.

Since a4af1a1dc, including the v3.2.9 Version Packages merge ee0ca5077 (run 42545984063), check:published-compliance has failed with: "Published @adcp/sdk bundles are missing from static/compliance/published-versions.json: 3.1.32." Publishing the 3.1.32 SDK bundle advanced the adcp-3.1 npm tag. That is the only failing step. The TypeScript Build failure is the shard aggregator.

How

This follows the 3.1.30 integration in #8570 (2bf592eaff).

• Release records. dist/compliance/3.1.32, dist/schemas/3.1.32 and the signed dist/protocol/3.1.32.tgz tuple are checked out unchanged from v3.1.32. Their tree hashes match origin/main. No existing release artifact is touched.
• Manifest. static/compliance/published-versions.json registers 3.1.32.
• Schema discovery. dist/schemas/index.json is regenerated with the repo's own buildRootSchemaDiscovery(): v3.1 and latest_by_minor["3.1"] move to 3.1.32, and a versions entry is added. latest.json is unchanged.
• Release notes. The 3.1.32 notes are copied verbatim from the tag into CHANGELOG.md.
• Hosted alias tests (server/tests/unit/storyboards.test.ts):
  • the 3.1 alias floor moves to 3.1.32, and 3.1.30 stays pinned as an explicit target;
  • 3.1.32 adds three storyboards (125, not 122), so the two hardcoded-count tests take main's alias-relative form. 3.1.18 stays frozen at 122, and 3.2.x's extra signing-vector checks are kept.

Manifest drift, compared with main: main also registers 3.0.27, 3.0.28, 3.1.27, 3.1.31 and the 3.3 betas. 3.2.x has never carried every maintenance release, and the check needs only what the npm tags package. Only 3.1.32 is missing by that measure, so only it is integrated. 3.2.9 is on 3.2.x and not yet on main; that is the pending forward-merge.

No gated paths (.github/workflows/**, static/schemas/source/**). No changeset: these are already-released records. The forward-merge/ branch prefix matches #8570.

Merge hold

The v3.2.9 Release run 42545984083 is still in progress on ee0ca5077. Release fences every publication phase on the branch, so this PR must not land on 3.2.x until that run finishes. Auto-merge is off for that reason.

Verification

• node scripts/check-published-compliance-versions.cjs: "Published compliance manifest is current for npm tags: adcp-3.0, adcp-3.1, adcp-3.2, latest, rc."
• node tests/immutable-release-artifacts.test.cjs passes.
• storyboards.test.ts and hosted-compliance-version.test.ts: 72/72.
• Hook steps:
  • dynamic-import, format-identity and state-change guards, the scoped server unit suite (68/68) and typecheck pass.
  • The root suite was 1173/1174. The one failure was a 10-second timeout in compliance-validate-input-gates on a loaded VM, and that file passes alone (12/12). I committed with HUSKY=0 because of it.
• The local advisory storyboard matrix was skipped at push (ADCP_SKIP_STORYBOARD_MATRIX=1). No compliance source changed, and CI's matrix is authoritative.

🤖 Generated with Claude Code

[aao-secretariat]

Ladon verdict: Approve

Approve — clean forward-merge of verbatim 3.1.32 release records onto 3.2.x.

The reviewer verified release-artifact immutability: the only modified dist/ file is dist/schemas/index.json (mutable discovery output); all other dist/ changes are pure additions under 3.1.32 paths — no existing semver artifact modified or deleted. The 3.1.32 compliance and schema trees hash-match the v3.1.32 tag byte-for-byte, and the dist/protocol/3.1.32.* tuple is identical. index.json and published-versions.json take minimal, consistent additions with no entries dropped. No static/schemas/source/** change, so no spec drift, oneOf regression, or breaking-class change; changeset absence is correct for already-released records.

Gate checks:

• No no-auto-approve team match.
• gated_paths: false.
• high_risk is true but all high_risk_reasons entries are (added) new files — normal release-record scaffolding, not escalation-worthy. No (deleted)/(modified) sensitive entries with findings.
• No critical/high/medium findings.

Rows 1–8 do not fire; falls through to row 9 → approve.