Automation and Tools

Beyond Cursor itself, we rely on scripts and CI to keep the project consistent and deployable. This page summarizes what runs where and why.

Package scripts (pnpm)

The single entry point for automation is package.json scripts. Key groups:

• Dev and run — pnpm dev, pnpm dev:infra, pnpm dev:all, pnpm dev:all:datadog (with Datadog agent), pnpm build, pnpm start.
• Quality — pnpm typecheck, pnpm lint, pnpm test, pnpm run e2e, pnpm check:cycles, pnpm semgrep / pnpm semgrep:ci.
• Documentation — pnpm docs:dev, pnpm docs:build, pnpm docs:ai-ecosystem:generate.
• Release — pnpm release (semantic-release), pnpm release:dry (no publish).
• Linear — pnpm linear:workon, pnpm linear:list-context, pnpm linear:create-issue, etc.
• Render — pnpm render:deploy, pnpm render:status, pnpm render:watchbuild, pnpm render:blueprint:sync.

The assistant (and developers) are instructed to use these scripts rather than ad-hoc commands. See the main Documentation Guide for docs-specific scripts and the runbook.

CI (GitHub Actions)

• Main pipeline — Runs on push/PR: install, typecheck, lint, test, e2e, pnpm docs:build, cycle check. Merge is blocked if any step fails.
• Release pipeline — Runs after successful CI on main: semantic-release computes next version from conventional commits, updates changelog, tags, and publishes GitHub Release.
• Docs deploy — On push to main when docs/, docs-site/, or src/**/*.documentation.md change: build the docs site; Render deploys the static site per render.yaml.
• Renovate — Optional workflow for validating dependency upgrade PRs (e.g. run tests and merge when green).

CI ensures that the same quality gates that run locally (typecheck, test, e2e, docs build) also run in the cloud, so the main branch stays in a known-good state.

When automation runs

Trigger	What runs
Save / edit in IDE	Lint-staged and formatters can run on save; rules guide the assistant.
Pre-commit (Husky)	Lint-staged (format + lint), then typecheck, test, contract coverage, semgrep, e2e in parallel.
Push / PR	Full CI: typecheck, lint, test, e2e, docs build, cycle check.
Merge to main (docs paths)	Docs deploy workflow; Render builds and serves the docs site.

Adding a new automation (e.g. a new script or CI job) should be documented here or in the Reference if it’s AI-ecosystem-specific (e.g. a new Cursor command that wraps it).