McRitchie Studio
Say Hi 👋
Agents Builders
← All Tasks
Sizing

Build and Deploy QA Release — one-trigger QA-department workflow + kickoff chip

Archived
task-79fdd136a1ee

Created

Jun 22, 03:36

Started

Jun 22, 14:05

Completed

Jun 22, 14:53

DevOps handoff

Type

Feature

Shape

ui-only

Worktree Slug

build-deploy-qa-release

Repositories

mcritchie-studio

Release Train

—

Branch

—

Pull Request

https://github.com/amcritchie/mcritchie-studio/pull/90

Local URL

http://localhost:3014

QA URL

—

Production URL

—

ui devops-workflow agent-behavior docs

Acceptance Criteria

  • Copy-paste 'Build and Deploy QA Release' kickoff chip in the current-release section of the board (prominent), driving the SOP.
  • SOP documented (devops-cycle-design.md): assess active release -> pull eligible reviewed tasks in -> review submitted + promote to reviewed + fold into the release -> assemble + QA-deploy ALL members across repos (gems handled per D1) -> stop at the prod gate (ask the operator).
  • Avi's role/personality doc encodes the 'maximize throughput — get everything that passes QA into a release' disposition.
  • Chip + SOP are repo-agnostic — they drive the unified multi-repo release (depends on the multi-repo conductor task).

Expected Test Plan

  • [component] the current-release chip renders and carries the 'Build and Deploy QA Release' kickoff text

Checks Run

  • [component] tasks_controller_test renders the Build-and-Deploy-QA-Release chip in #current-release
  • [unit] application_helper_test devops_kickoffs + qa_release_kickoff contract (full suite 963/0, zeitwerk clean)

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.

Comment 5 days ago

DEPENDS ON Task A (task-f25fabc1b67c, multi-repo conductor). This is Mr. McRitchie's MAIN trigger / one-stop QA-department run. SOP: (1) assess the active non-shipped release + its assembled members; (2) pull eligible reviewed tasks into it (Avi bias: maximize throughput) — create+name+slug the release if none exists; (3) work the submitted queue -> promote passing ones to reviewed + fold them into the release; (4) assemble + QA-deploy ALL members across repos (gems handled per D1); (5) stop + ASK the operator for the production deploy. Encode Avi's 'ship everything that passes QA' disposition in his role doc.

Comment 5 days ago

QA (Avi): APPROVE-WITH-NITS — chip + SOP + Avi throughput trait verified accurate vs the live conductor; 2 §1.4 doc nits FIXED (Release.current not featured; dropped nonexistent 'bin/release state'). PR #90 (base release).

Sealed-bid sizing

Edit →

Alex (PM)

—

Avi (PO)

—

Dev

—

Actual

—