release-check

Prompt file imported from Rotorsoft/act-root (.claude/commands/release-check.md). Copyright stays with the author.

Verify the current branch is mergeable. Run every gate in parallel and surface a single consolidated report.

Gates (run all in parallel)

1. Typecheck — pnpm typecheck. Must be clean.
2. Tests + coverage — pnpm test. Coverage must be 100% on every metric (statements / branches / functions / lines). Anything below is a fail.
3. Lint — pnpm lint. Warnings are fine; errors fail the gate.
4. Build — pnpm build. Must complete without TS errors.
5. Charter-covered diff — git diff master --stat -- libs/act/src/builders/ libs/act/src/act.ts libs/act/src/types/ports.ts libs/act/src/types/index.ts libs/act/src/ports.ts. If any file in that list changed, explicitly note "charter surface modified — categorize as additive/breaking before merging."
6. Doc-staleness audit — run the doc-grep recipe from CLAUDE.md "Pre-handoff workflow → Doc audit":

   # Identify renamed/removed identifiers in this PR
   git diff master --diff-filter=D --name-only -- libs/act/src/ libs/act-*/src/
   # For each renamed/removed symbol, grep for it in docs
   grep -rln "<old-name-or-shape>" docs/docs book CLAUDE.md libs/*/README.md

   When the PR migrates a callsite to a new primitive (e.g., query → query_stats), also grep for the old behavioral description in docs/docs/architecture/ ASCII diagrams. Report hits — they must be updated in this PR, not a follow-up. Skip cleanly when this is a no-public-surface PR (deps bump, internal refactor).

Output

Print a single table:

End with a one-line verdict: READY TO MERGE or NOT READY: .

Conventions

• Run the four pnpm gates with & and wait for concurrency. Don't serialize.
• Use coverage/coverage-summary.json (vitest leaves it after pnpm test) for coverage percentages — jq '.total'.
• If the user wants a deeper drill on any failure, run the relevant package's targeted command (pnpm -F <pkg> typecheck etc.). Don't drill unprompted.