Run the coach locally
Heuristic fixtures and full pr-ready
Local CLI entrypoint (`npm run pr-ready`) that runs the shared core against git, a path, or the remote API. modes — no AWS required for the demo path.
PR Readiness Coach Walkthrough
Check branch readiness before you open a pull request — local CLI, AWS API, GitHub Actions comments, Kiro hooks, and an owner UI sharing one core.
What you’ll learn
Section titled “What you’ll learn”See the architecture
Shared core powering CLI, Lambda, hooks, and Amplify SPA with dual API key
Machine-client auth for `POST /analyze` — GitHub Actions and CLI send `x-api-key`; never bake the key into the SPA. / Cognito
Owner UI auth — Cognito email/password → JWT `Authorization: Bearer` for `/runs` and `/ui/analyze`. Self-sign-up is disabled. auth.
Deploy to AWS
CDK stack, Bedrock models, Amplify zip deploy
SPA hosting path: CDK creates Amplify app/branch with auto-build off; a separate job zip-uploads the Vite build — no GitHub↔Amplify Git connection., and OIDC on main.
Wire CI and IDE feedback
Warn-only PR comments and warn-only
CI and Kiro hooks always exit 0 — they coach with comments/reports but never hard-block merges in v1. Kiro hooks that coach without blocking merges.