Tests and quality checks#

The complete gate is pnpm verify. Its stages are maintained in repository scripts/tooling; link that source instead of copying an inventory that drifts as checks evolve.

The pre-commit hook runs pnpm check:commit: staged formatting, strict typed lint and critical tests start in parallel. Critical Vitest tests use the commit tag and an explicit file selection in tooling/workflow/commit.config.mts. pnpm test:commit runs just that suite. A shared eight-second deadline terminates owned processes and blocks the commit on timeout. Full verification remains required in CI and before handoff. See commit-check policy.

The commit gate certifies both working-tree content and the staged index, so restaging different bytes while checks run blocks the commit. Gate tests cover the full admission, execution and ownership lifecycle through real Git fixtures. Shared child handling drains output and cleanup before returning: commit checks terminate immediately; ordinary POSIX workflows get one second for graceful shutdown, while Windows child trees terminate immediately.

Check the behavior you changed#

Choose an observable public seam: a supported package export, guarded command, built artifact, or user journey. Test meaningful expected behavior and relevant failures. Avoid assertions mirroring implementation or proving that constants equal themselves.

• Portable model changes need validation, retained identity/history and invalid-input coverage.
• Workflow/tooling changes need real command/lock/source-identity checks, including relevant error cases.
• Browser changes need real interaction checks, relevant keyboard behavior, and desktop/mobile layouts.
• Documentation changes need accurate links/anchors, buildable pages and runnable supported examples.

Browser testing, static quality, architecture checks, and consumer verification hold the exact conventions.

Run supported commands#

Build before standalone checks that resolve supported package declarations in a fresh checkout. The complete gate establishes dependency-order artifacts itself. Use targeted unit/browser commands during development, then stop the owned dev server before the final gate.

pnpm build
pnpm format:check
pnpm verify

Guarded entry points prevent conflicting output mutation in one worktree. Internal *:checks commands are gate implementation, not shortcuts for parallel operation.

Evidence is part of completion#

Every change requires automated browser verification and observed T3 evidence from its own worktree, plus direct acceptance checks. Screenshots show an observed state; they do not prove every behavior or replace tests. Source changes, commits and rebases invalidate source-bound evidence and require the final checks again.

Follow worktrees and browser verification and reliability for exact run records and PR screenshot requirements. GitHub checks defines the hosted quality gate used at merge review.