Run the checks

The application uses Node’s test runner for colocated TypeScript tests. Run commands through the package’s configured scripts and installed release toolchain.

Application commands

From the repository root:

pnpm test
pnpm typecheck
pnpm lint

Run the affected focused tests during implementation, then the required complete checks for the release. Inspect failures and skipped cases, not only the exit code or total count.

Documentation commands

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

Content checks validate metadata, links and public boundaries. Tests cover origin/navigation/customer contracts and endpoint drift. The build compiles MDX and creates Pagefind output.

Database and native suites

Some database checks require dedicated local setup. A skipped SQL suite is not a native database pass. Workbook and text-PDF source tests also need the corresponding runtime check when packaging or native dependencies change.

Do not point a test command at a populated user database without a bounded authorized fixture plan.

Reporting results

State the source revision, the checks that ran and the behavior each establishes. Keep failure evidence before fixing it. Review evidence boundaries before treating a mocked test as hosted acceptance.