Testing & Release Checks

Start with the Changed Behavior

pnpm test:isolated __tests__/invoices
pnpm typecheck:tests:changed

The isolated command removes inherited provider credentials from the test process. Vitest discovers tests in __tests__/ and lib/**/__tests__/, including both .test.ts and .test.tsx files. Use a specific file for a smaller change.

Verify the Repository

pnpm verify
pnpm typecheck:auxiliary
pnpm exec eslint <changed-files>

verify checks financial route guards, authentication, organization scoping, application types, and the isolated unit suite. It stops at the first failed stage. A passing focused suite does not replace a failed repository gate.

For browser checks, use an isolated local or staging data plane and the relevant Playwright spec. Tests that create financial records require disposable test data. Email delivery needs separate authorization.

Local Release Checks

GitHub Actions are disabled by the owner as of September 29, 2026. Run the relevant checks locally before merging. Vercel’s Git integration handles the deployment after changes reach main.

Proof to Keep

Record the changed behavior, commands, results, and any unresolved gate. Money, permissions, tenant access, and migration changes need their failure and retry paths checked. Proposed SQL needs proof against the candidate schema in an isolated database; a linked advisor report only describes the already-applied database.

The repository’s docs/guides/testing.md, docs/guides/database.md, and docs/guides/release.md are the authoritative procedures. Historical workflow files describe the former hosted pipeline.