Primary review blocked PR 258. Required rework: (1) resync feat/suite-consistency-cleanup with current origin/release (now 9e999735) and resolve conflicts in app/views/tasks/_task_card.html.erb, docs/ECOSYSTEM.md, docs/agents/index.md, docs/agents/modules/app-registry.md, docs/agents/modules/ports-and-processes.md, docs/agents/system/new-app-onboarding-sop.md, and test/models/release/prod_smoke_test.rb; GitHub reports PR 258 DIRTY/CONFLICTING so bin/release merge is unsafe. (2) Rerun bin/full-suite-check suite-consistency-cleanup after the conflict resolution; bin/dor-check currently fails because full-suite and RuboCop evidence is stale for current head a982af9. (3) Re-run bin/install-agent-docs from the suite-consistency worktree and then bin/install-agent-docs check; check currently fails because /Users/alex/projects/AGENTS.md is out of date with branch docs, despite handoff recording green. (4) Update the task/PR handoff with fresh evidence for every affected repo, including an explicit Turf Vault PR #5 docs-only/no-CI rationale or check, before resubmitting. Cross-repo PRs observed clean: chain-ops #6, turf-monster #169, studio-engine #11, turf-vault #5; mcritchie-studio is the blocker.
Created
Jun 27, 20:10
Started
Jun 28, 14:39
Completed
Jun 28, 16:43
DevOps handoff
Type
Chore
Shape
backend
Worktree Slug
suite-consistency-cleanup
Repositories
mcritchie-studio, chain-ops, turf-monster, studio-engine, turf-vault
Release Slug
—
Branch
feat/suite-consistency-cleanup
Acceptance Criteria
Expected Test Plan
Checks Run
Agent Context
Consistency cleanup from the 2026-06-27 drift audit. Mr. McRitchie approved: upgrade all Rails apps to 8.1, align Studio Engine docs with 0.11, assign Rolio 3300-3399, consolidate release_train/release_slug naming around canonical release_slug, update legacy product links, and standardize QA/production server metadata. Ready PRs: mcritchie-studio https://github.com/amcritchie/mcritchie-studio/pull/258; chain-ops https://github.com/amcritchie/chain-ops/pull/6; turf-monster https://github.com/amcritchie/turf-monster/pull/169; studio-engine https://github.com/amcritchie/studio-engine/pull/11; turf-vault https://github.com/amcritchie/turf-vault/pull/5. Turf Vault now has origin/release and PR #5 targets release. QA URLs use qa.<canonical-host>; production URLs/smokes use mcritchie.studio and turfmonster.media, with app.* hosts kept only as legacy aliases. Reworked Avi feedback: Chain Ops now has importmap binstub/config, db/schema.rb, RuboCop fixes, green local checks, and green GitHub CI; Studio Engine Consumer CI now checks out repos at hyphenated repo paths and is green. Worktree URLs: Studio http://localhost:3008; Turf Monster http://localhost:3101; Chain Ops allocated http://localhost:3301, app default now 3400 after merge.
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.
QA review found merge blockers. Chain Ops PR #6 is draft and CI is red: scan_js calls missing bin/importmap, lint fails Gemfile:21 and app/services/localnet.rb:74 for array bracket spacing under the upgraded RuboCop, and test fails because db/schema.rb is missing. Studio Engine PR #11 is docs-only but required consumer CI is red in the mcritchie_studio suite because AgentWorktreeTest cannot find the expected mcritchie-studio checkout. Keep all suite PRs out of review/merge until checks are green and draft PRs are marked ready.
QA review found one remaining generated-doc blocker. The reworked Chain Ops, Turf Monster, Studio Engine, Turf Vault, and Studio PR checks are green, and local targeted tests passed, but live bin/install-agent-docs check in the suite-consistency-cleanup worktree fails because /Users/alex/projects/AGENTS.md is out of date with docs/agents/index.md. The drift covers the Rolio/Chain Ops port range lines and release_slug vocabulary. Refresh/install the generated agent docs or otherwise make bin/install-agent-docs check pass, then resubmit.
Reworked screenshot feedback: task card titles and QA feedback notes now line-clamp inside the card. Synced Studio branch with release, stabilized the Codex title retry test, regenerated root agent docs, reran full-suite/DoR, and GitHub PR #258 is clean with all checks green.
Primary review blocked PR 258. Required rework: (1) resync feat/suite-consistency-cleanup with current origin/release (now 9e999735) and resolve conflicts in app/views/tasks/_task_card.html.erb, docs/ECOSYSTEM.md, docs/agents/index.md, docs/agents/modules/app-registry.md, docs/agents/modules/ports-and-processes.md, docs/agents/system/new-app-onboarding-sop.md, and test/models/release/prod_smoke_test.rb; GitHub reports PR 258 DIRTY/CONFLICTING so bin/release merge is unsafe. (2) Rerun bin/full-suite-check suite-consistency-cleanup after the conflict resolution; bin/dor-check currently fails because full-suite and RuboCop evidence is stale for current head a982af9. (3) Re-run bin/install-agent-docs from the suite-consistency worktree and then bin/install-agent-docs check; check currently fails because /Users/alex/projects/AGENTS.md is out of date with branch docs, despite handoff recording green. (4) Update the task/PR handoff with fresh evidence for every affected repo, including an explicit Turf Vault PR #5 docs-only/no-CI rationale or check, before resubmitting. Cross-repo PRs observed clean: chain-ops #6, turf-monster #169, studio-engine #11, turf-vault #5; mcritchie-studio is the blocker.
Reworked primary blocker: merged current origin/release 0b1d1f7 into Studio PR #258, resolved conflicts in task card/docs/prod smoke files, regenerated root agent docs, reran full-suite-check (2012 runs, 9296 assertions, RuboCop clean), reran install-agent-docs check, dor-check, session-preflight, and confirmed GitHub reports PR #258 CLEAN/MERGEABLE with all checks green. Task evidence also records Turf Vault #5 as docs-only/no configured CI.
Sealed-bid sizing
Edit →Alex (PM)
—
Avi (PO)
—
Dev
MEDIUM
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.