chore(release): remove operational beta changesets - #6804
Conversation
There was a problem hiding this comment.
Ladon verdict: Approve
Approve — delete-only changeset cleanup before the next 3.2 beta.
This PR removes four changesets (instrument-3-2-surfaces, isolate-storyboard-processes, restore-proposal-handoff, stabilize-storyboard-runner), 20 deletions across 4 files, no additions. The reviewer traced each to its source commit and confirmed none of the source PRs touched static/schemas/source/** or static/compliance/source/** — wire schemas and compliance assets are untouched. The version bump is preserved (six other minor protocol changesets remain), the require-human-release-approval safeguard stays in the pool, and no dist/** released artifact is modified.
No blocking or Medium findings. The sole finding is Low (dropped changelog description for a docs/reference touch) and is omitted from blocking consideration.
Decision-table walk: no critical/high (row 1 no); gated_paths false (row 2 no); high_risk false, no deletions in high-risk paths (row 3 no); no medium data-loss/schema/infra findings (row 4/5 no); no prior escalation (row 6 no); no no-auto-approve team match (row 7 no); zero medium findings (row 8 no) → row 9 approve.
Note: review_decision is REVIEW_REQUIRED, but gated_paths is false so the row-2 hard gate does not apply.
Summary
Remove four operational-only changesets before the next 3.2 beta is generated:
These changes remain on
main; they simply no longer appear in the published protocol changelog. Protocol-facing changesets and the release-approval safeguard remain in the beta pool.Verification
node scripts/check-changeset-protocol-scope.cjs origin/mainnpx --yes @changesets/cli@^3.0.0 status --since=origin/main