You're offline — showing cached data

MC-4383

Require artifact-level evidence before MC reviewer closes content/audio workflows
2026-06-13 08:52:32 SAST
Home Board MC-4383

Require artifact-level evidence before MC reviewer closes content/audio workflows

Systemic workflow fix from Elmar's challenge: MC reviewer/workflow signed off on MC-4365 without testing the user-facing end-to-end outcome. Existing reviewer gates focus heavil...
State Done Next Action Closed Owner Luci Runtime Closed Age 16d ago
MC-4383
Ticket is done; runtime is closed. · profile claude_opus_1m_high · cwd /home/lucienne/workspace/mission-control · uptime 15d 21h · last activity 15d 16h ago

Description

MC-4383
Systemic workflow fix from Elmar's challenge: MC reviewer/workflow signed off on MC-4365 without testing the user-facing end-to-end outcome. Existing reviewer gates focus heavily on code/UI/browser evidence; content/research/audio pipeline tickets need an explicit acceptance-evidence gate too. Problem: - MC-4365 was marked done with unit tests and deterministic dry-run evidence. - The real user concern was daily radio quality: actual episode replay, stale/repeated story suppression, and whether a generated show works. - MC-4374 improved this with a shadow comparison, but still stopped before audio, so full end-to-end audio was not proven. Goal: Add/adjust MC role/reviewer contract so non-UI deliverables cannot be closed merely because code/tests pass when the acceptance criteria imply a real artifact/workflow. Scope: 1. Inspect mc_role_guidance/reviewer prompts/review gate/worker DONE handling from MC-4372/4375/4378. 2. Add an evidence-by-work-class gate for content/research/audio/scheduler pipelines: - code tests are necessary but not sufficient; - must provide a real or shadow artifact when acceptance is user-facing output; - if production side effects are unsafe, require labelled TEST/ALT artifact or explicit blocker. 3. Add regression/smoke test: a ticket with "radio/audio/show" acceptance cannot close with only unit tests/dry-run if no real/shadow artifact or blocker is present. 4. Update docs/runbook. Acceptance criteria: - Reviewer/role contract says artifact/workflow acceptance requires artifact evidence, not just code tests. - Test proves missing real artifact blocks or routes to review rather than done. - Applies centrally, not per-runtime copy/paste. Expected check-in: today.

Activity

done
Luci is working...
Live
No activity yet
Help