Phase 7 dogfood tracker — log qualifying merges + reviewed transcripts

[cbeaulieu-gt]

Tracking issue for the Phase 7 (#145) amended dogfood gate (ratified 2026-05-06).

Amendment rationale: the original gate measured action-surface churn on this repo. Phase 6 inverted that — the runtime is the iteration surface, and the action directories are stable. Dogfood traffic now sourced from designated external consumers where real PR review activity already happens.

Gate definition (all must hold)

1. Calendar: ≥ 2 weeks since Phase 6 cutover (2026-05-06)
2. Designated consumers: cbeaulieu-gt/job-matcher-pr + cbeaulieu-gt/siege-web
3. Volume: ≥ 20 successful claude-pr-review.yml runs aggregated across both
4. Incident bar (strictest): 0 incidents (any user-reported issue, runtime-level failure, or PR-review defect requiring rollback)
5. Transcript review: 5 reviewed across both consumers

Calendar gate

• Phase 6 cutover: 2026-05-06 (PR Phase 6: promote/rollback automation, freshness alarm, prune (#144) #209 merged at b080630)
• Earliest calendar unlock: 2026-05-20

Per-consumer run log

cbeaulieu-gt/job-matcher-pr (primary, @v2)

#	PR	Run ID	Date	Outcome	Incident?
1
2
...

cbeaulieu-gt/siege-web (secondary, @v2.0.0)

#	PR	Run ID	Date	Outcome	Incident?
1
2
...

Aggregate count: 0 / 20 required · Incident count: 0 (must stay 0)

Transcript review log (need 5 across both consumers)

#	Consumer	PR	Run ID	Reviewer notes	Reviewed by
1
2
3
4
5

Incident definition (strictest bar)

ANY of the following resets progress and requires investigation before resuming the count:

• User-reported behavior issue on a claude-pr-review.yml run (review hallucination, wrong-file edits, missed critical review item, etc.)
• Runtime-level failure: container fails to start, agent crashes, wrong overlay loaded, persona drift
• PR-review defect requiring runtime-rollback.yml invocation
• Any GHCR digest resolution failure on a designated consumer

Update protocol

• After each claude-pr-review.yml run on a designated consumer: append a row to the appropriate consumer table
• After reviewing a run for behavior quality: append a row to the transcript review log
• If an incident occurs: comment on this issue with the run ID, root cause, and proposed remediation; reset the volume counter to 0
• When all gate conditions hold: comment "Gate cleared", close this issue, then Phase 7: dogfood, delete legacy tag-claude/ + ci-failure.yaml, cut v2.x.y, update v2 floating tag #145 unblocks

Related

• Parent: Phase 7: dogfood, delete legacy tag-claude/ + ci-failure.yaml, cut v2.x.y, update v2 floating tag #145 (Phase 7) — body amended 2026-05-06 with new gate
• Epic: Epic: containerized runtime for Claude-powered CI jobs #130
• Milestone: Containerized Claude Code CI runtime
• Phase 6 close-out: PR chore(docs): delete Phase 6 plan file #217 (plan-file deletion, in flight)

🤖 Generated by Claude Code on behalf of @cbeaulieu-gt