Test Payne
Run the default checks from the repository root after installing the locked dependencies:
pnpm lint
pnpm typecheck
pnpm test
pnpm docs:validate
pnpm docs:smoke
pnpm buildPostgreSQL integration tests require PAYNE_TEST_DATABASE_URL and are separate:
pnpm test:integrationLocal-live documentation smoke requires the full Compose stack and can change the official local scenario by introducing Day 2 evidence:
pnpm docs:smoke:local-liveThis infrastructure-dependent check is never reported as passed when it was not run. It does not automatically reset volumes after a failure.
Check a release candidate
The static/public release command composes repository hygiene, credential, asset, claim-evidence, sample, documentation, link, lint, type, unit-test, and production simulation checks:
pnpm release:staticFrom the clean intended release commit, verify that no ignored or untracked file is required. This command needs registry access if the pnpm store is not already warm. It creates and removes only a task-specific temporary directory:
PAYNE_RELEASE_CLEAN_CLONE=1 pnpm release:staticThe local-live release rehearsal is destructive only to the Payne Compose project
and the named Payne/DataHub local volumes listed by pnpm local:reset. Configure
one supported Gemini or Ollama provider first. The command preserves containers,
volumes, and safe reports after a failure so you can inspect them.
pnpm release:local-liveThe rehearsal polls persisted job and gate projections with bounded timeouts. It
does not open the gate page, set database state, substitute fixture adapters, or
tear down a failed environment. Run pnpm local:reset before another full attempt.