Skip to content

Match the verification page's deterministic checks to CI #357

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
abhishekgahlot2 merged 1 commit into from
Oct 17, 2026
Merged

Match the verification page's deterministic checks to CI #357

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 10 additions & 4 deletions docs-site/docs/operations/verification.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,12 +14,18 @@ combination. Passing the first layer does not imply the second.
```bash
bun run typecheck
(cd backend && bun run test)
(cd frontend && bun test components)
(cd frontend && bun run test)
(cd frontend && bun run lint)
for p in packages/*/; do (cd "$p" && bun run typecheck && bun run test); done
bun test scripts/agent-docs.test.ts
```

The backend suite uses an isolated test database. Shared package suites cover
the provider-neutral client, harness, sandbox, artifact, CLI, and conformance
contracts.
The backend suite uses an isolated test database. The frontend test script runs
`components`, `app`, and `lib`, the same tests CI runs. Shared package suites
cover the provider-neutral client, harness, sandbox, artifact, CLI, and
conformance contracts. Each package installs on its own, so run
`bun install --frozen-lockfile` in the frontend, the backend, and every package
folder first.

For the documentation site:

Expand Down
Loading