frontapp-openapi-client

Scaffold a new resource vertical end-to-end (helper + Pydantic domain + MCP tools + tests + docs). Use when starting a new "client.<resource>" surface such as drafts (#14), contacts (#2), messages (#4), tags/inboxes (#5). Requires the `vertical-planner` agent to produce a plan first.

Open a PR for the current feature branch — self-review the diff, organize commits, push, create the PR, wait for CI and review, then address feedback. Use when implementation is complete and ready for review.

Watch CI on multiple open PRs in parallel, surface real failures with their job-log tails, and chain into `/review-pr` when comments arrive. Use when 2+ PRs are open at once and individually polling each would burn context.

Address PR review comments — fetch all unresolved comments, fix the issues, validate with `uv run poe check`, commit, push, and reply to each comment on GitHub. Use when asked to handle PR review feedback.

Refresh the vendored Front OpenAPI spec from upstream and regenerate the Python client safely. Use when pulling upstream API changes, when a new endpoint is needed, or when debugging codegen drift. NEVER edit the vendored spec or generated files directly — patch scripts/vendor_spec.py instead.