Agents Builders

Side by side releases

Archived
side-by-side-releases

Created

Jun 22, 16:16

Started

Jun 22, 16:16

Completed

Jun 22, 16:35

DevOps handoff

Type

Feature

Shape

ui-only

Worktree Slug

side-by-side-releases

Repositories

mcritchie-studio

Release Train

Branch

feat/side-by-side-releases

QA URL

Production URL

ui

Acceptance Criteria

  • Current and last releases render side by side on desktop
  • Both modules stack vertically on narrow screens
  • Layout keeps dark and light theme parity

Expected Test Plan

  • component

Checks Run

  • [component] /deployments wraps Current + Last release modules in a div.grid.lg:grid-cols-2 (side-by-side lg+, stacked below); covers active+last and empty-state+last

Agent Context

Layout-only: on /deployments, the Current Release and Last Release modules currently stack vertically (see operator screenshot). Put them SIDE BY SIDE on wide screens, stacked on narrow. The two are rendered sequentially in app/views/tasks/_board.html.erb (~L214-216, gated on current_release || last_release, renders _current_release then _last_release). Wrap BOTH renders in a responsive grid container, e.g. <div class='grid grid-cols-1 lg:grid-cols-2 gap-4 mb-6'> ... </div>, so lg+ = two columns, below lg = one column. CRITICAL FOOTGUN (burned 3x, in memory): grid items must NOT carry their own mb-* — margin on a grid cell shrinks the visible box. So DROP the mb-6 from each card's outer div in _current_release.html.erb (BOTH the present AND the empty-state branches) and _last_release.html.erb; let the grid gap + the container's mb-6 handle spacing. Pick the cleaner alignment for unequal-height cards (empty Current is short, Last is tall with member pills) — items-start (top-aligned natural heights) usually reads better than stretch; your call, but verify BOTH states look right: (1) active release present + last (two full cards) and (2) Current empty-state + last (short card beside tall card). Keep dark/light theme parity. ui-only shape → [component] test that /deployments wraps the two modules in the grid container (or asserts both modules present within the grid).

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.

No task feedback has been recorded yet.

Sealed-bid sizing

Edit →

Alex (PM)

Avi (PO)

Dev

Actual