PR #270 now conflicts with origin/release after PR #269 merged first. Please rebase feat/event-driven-lifecycle-apis onto current origin/release, resolve the shared bin/release and docs/agents/system/devops-cycle-design.md conflicts, rerun the lifecycle API focused checks plus full-suite/rubocop evidence, force-push with lease, and resubmit for QA.
Created
Jun 28, 22:09
Started
Jun 29, 03:57
Completed
Jun 29, 05:06
DevOps handoff
Type
Feature
Shape
ui+db
Worktree Slug
event-driven-lifecycle-apis
Repositories
mcritchie-studio
Release Slug
—
Branch
feat/event-driven-lifecycle-apis
Acceptance Criteria
Expected Test Plan
Checks Run
Agent Context
Mr. McRitchie wants McRitchie Studio to expose explicit APIs for deployment and broader lifecycle events instead of inferring progress from coarse Release timestamps. Re-envision the event spine so agents can hit simple authenticated endpoints such as start/complete/fail for deployment checkpoints and potentially design/build/review lifecycle steps. Prefer /complete over /pass. Introduce mandatory usage fields where appropriate, including model, tokens, and cost, so agents learn to send complete event data. Move deterministic tracker and lifecycle logic onto events while preserving existing task/release state as coarse lifecycle summary.
Stage Timeline
Who handled each stage, the time it took (measured), and the model / tokens / cost reported (best-effort) — plus who's on it right now. — means the agent didn't report that metric.
Conversation
QA review feedback, agent handoffs, and follow-up notes for this task.
PR #270 now conflicts with origin/release after PR #269 merged first. Please rebase feat/event-driven-lifecycle-apis onto current origin/release, resolve the shared bin/release and docs/agents/system/devops-cycle-design.md conflicts, rerun the lifecycle API focused checks plus full-suite/rubocop evidence, force-push with lease, and resubmit for QA.
Sealed-bid sizing
Edit →Alex (PM)
—
Avi (PO)
—
Dev
XL
Actual
XL
We emailed a one-tap sign-in link to . It expires shortly and can only be used once.
No email? Check spam, or close this and try again.