Triple-C

Author	SHA1	Message	Date
shadowdaoandClaude Opus 5.5	c09f4c4475	ci: run vitest and cargo test on every PR Secret Scan / scan (push) Successful in 5s Details Build App (Preview) / compute-version (pull_request) Successful in 5s Details Secret Scan / scan (pull_request) Successful in 6s Details Build App (Preview) / create-release (pull_request) Successful in 1s Details Build App (Preview) / build-macos (pull_request) Successful in 2m48s Details Build App (Preview) / test (pull_request) Successful in 4m41s Details Build App (Preview) / build-linux (pull_request) Successful in 5m2s Details Build App (Preview) / build-windows (pull_request) Successful in 5m9s Details Build App (Preview) / prune-previews (pull_request) Successful in 5s Details The preview workflow is the PR check, but until now it only built: neither test suite ran anywhere but a developer's machine. That matters most for the app-command ACL census from #60. An ungranted command compiles fine and only fails at runtime, so `cargo test` and vitest's capabilities.test.ts are the guards that catch it before merge. The new `test` job runs `npm ci`, `npm run build` (tsc, plus the dist/ that generate_context! needs), `npx vitest run` and `cargo test --locked`. It has no `needs`, so it runs alongside the three platform builds instead of delaying them. Verified in a fresh clone: 975 vitest and 675+3 cargo tests pass, and the tree stays clean. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-09-23 10:09:48 -07:00

Compare commits

Diff Content Not Available