[cixzhang]

Summary

Release operators can run the frozen v0.7.12 repair gate without a Git output-buffer failure or stale workflow-contract expectations. This is the second and final corrective policy sync: exactly three tooling/test files, with no package, product, API, Changeset, release-output, assertion behavior, timeout, or retry change.

Exact ports from main

• scripts/release/active-release.mjs and scripts/release/active-release.test.mjs — exact port from 73c1a49170c9b0e0ddf39df2d197eb2e6cdce19c (#10923).
• .github/scripts/touched-components.test.mjs — exact workflow-contract expectation port from c7558e8d3af (#10634).

Gate

• validate-policy-carry accepts this exact head from release head 75010433f5e001f116619ffd6a0469db9031b0ac with bundle digest 6ff8c247c067b3f43d2de9109dc53176d10120f469bf59af9b12655e9d62c0ab.
• scripts/release/active-release.test.mjs plus .github/scripts/touched-components.test.mjs: 85/85.
• This pull request is the exact-head review surface. After CodeBunny approves this head, Release fast-forwards this same commit to release/v0.7.12; it is not squash-merged.
• The complete visual, accessibility, RTL, product, and test release gate reruns on the resulting branch head before test(BottomSheet): deflake v0.7.12 release contract #10845 or publication proceeds.

Accessibility

Not applicable — this changes release tooling and its contract tests only.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
astryx	Ready	Preview	Nov 10, 2026 1:56am UTC

[astracat-bot]

AI review status for this pull request.

Review status	Updated
🟢 Reviewed (for maintainers only)	Nov 10, 2026, 2:01 AM UTC

[astracat-bot]

Approved pending CI: the remaining required checks on this head are still running.

This commit is the second and final v0.7.12 policy sync that AST-017 FR61 and DEC-32 allow: it changes exactly scripts/release/active-release.mjs, scripts/release/active-release.test.mjs and .github/scripts/touched-components.test.mjs, and each change matches work already merged on main. validate-policy-carry from main accepts this exact head, and the two release test files pass 85/85. The failing release-bump check is expected: its pull-request validator admits only a version bump or a test repair, and FR61 lands this commit by fast-forward instead of a merge.

[Automated review]