CI and releases
Agentful uses GitHub Actions for static checks, builds, unit tests, reporting, mutation planning, docs builds, and deployment.
Local Gate
Section titled “Local Gate”vp run gate:fastvp run test:unit:bevp run test:unit:fevp run docs:buildThe broader quality command includes the same static checks and unit suites used by CI.
vp run qualityCI Gate
Section titled “CI Gate”The reusable quality workflow runs:
- Mutation registry checks.
- Workflow lint.
- Dependency audit.
- Tool type checks and tool tests.
- ESLint and Prettier.
- TypeScript type checks across workspaces.
- Production builds, including docs.
- Backend and frontend unit test report runs.
- Holistic testing report artifact.
Coverage floor reporting remains visible, but blocking enforcement should be phased in only after the committed baseline is high enough to make the gate actionable.
Mutation Testing
Section titled “Mutation Testing”mutation-registry.json maps production files to Stryker packs or exemptions.
Pull requests run only packs owning changed files. Scheduled baseline runs cover
the full registered mutation surface.
Docs Deployment
Section titled “Docs Deployment”The docs site builds from apps/docs and deploys to Cloudflare Pages project
agentful-docs. Production deploys should bind agentful.app and keep
agentful.sh available for CLI/install flows or redirects.