Create an authenticated McRitchie Studio API endpoint that formats and sends canonical Discord production release notes from deployed task slugs.
Created
Jun 18, 23:01
Started
Jun 18, 23:01
Completed
Jun 19, 16:15
DevOps handoff
Type
Feature
Shape
—
Worktree Slug
release-notes-api
Repositories
mcritchie-studio
Release Train
2026-06-19-release-notes-api-qa
Branch
mcritchie-studio main aa750fa
Local URL
http://localhost:3026QA URL
https://qa.mcritchie.studioProduction URL
https://mcritchie.studio/api/v1/release_notesAcceptance Criteria
Expected Test Plan
Checks Run
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.
No stage changes recorded yet.
Conversation
QA review feedback, agent handoffs, and follow-up notes for this task.
Avi QA review: PR #51 is merged at 39cd28e and included in current main aa750fa, deployed to McRitchie Studio QA release v37. Focused release-notes tests passed: 7 runs / 37 assertions / 0 failures; RuboCop passed with 388 files and no offenses; route proof shows POST /api/v1/release_notes. GitHub CI was green for lint, scan_js, scan_ruby, and test. QA dry-run proof returned status 200 with delivered=false and dry_run=true, grouped app sections, production task links, and no Discord send; the temporary QA task was removed. Production currently 404s for /api/v1/release_notes until this task is deployed, so the first production rollout including this task should call the API after deploy verification. Task moved to prod_ready. No production deploy performed.
Production shipped: McRitchie Studio v72 / 4af95f8. Production URL: https://mcritchie.studio/api/v1/release_notes. Verification included production health checks, relevant route smokes, dyno status, and release notes posted to Discord. Task marked done.
Sealed-bid sizing
Edit →Alex (PM)
—
Avi (PO)
—
Dev
—
Actual
—
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.