Commands and checks

Run checks in the package that owns the change. Source checks, compiled output and a working browser flow provide different evidence.

Application checks

At the repository root:

pnpm typecheck
pnpm lint
pnpm test
pnpm build

Types catch incompatible interfaces; lint checks source rules; tests exercise their stated cases; a build checks production compilation. Review what the tests actually assert when interpreting a pass.

Documentation checks

From the repository root:

pnpm --dir documentation check
pnpm --dir documentation test
pnpm --dir documentation typecheck
pnpm --dir documentation build

The content checker validates public metadata, internal routes and private-reference boundaries. Tests cover navigation, origins and useful customer contracts. The docs build compiles pages and creates the Pagefind search index.

Complete the affected acceptance

For a docs navigation change, inspect the compiled route, sidebar, mobile drawer and search results. For a financial command, inspect the actual saved result and fresh owned read, including failure/retry behavior. A unit test cannot establish mail delivery or a bank account’s reconciliation.

When a check fails

Read the first actionable failure and its owning file. Fix the actual source or configuration issue rather than weakening a meaningful assertion. Repeat the affected check after the change, then continue to the necessary runtime acceptance. Use test guidance for choosing additional coverage.