McRitchie Studio

Agent Context

Board-UI feature on the ASSEMBLED column (primarily the /deployments 6-lane board's assembled lane; mirror on /tasks board cards where it applies). GOAL (operator): when Avi works a deployment, his INTENT shows in the assembled card's crew, and the assembled column becomes a live indicator of WHAT is currently being deployed + by whom. CURRENT BEHAVIOR (read first): app/helpers/stage_agents_helper.rb — crew model has FOUR fixed compartments (Build · Review · Assembled · Shipped) per crew_clusters/crew_columns (~L92-169), BUT a lane only renders when it has entries, and the comment (~L145) says 'Only a shipped task earns the fourth (shipped) lane' — so an ASSEMBLED task renders only 3 clusters (build · review · assembled); the 4th deploy/ship slot is absent until shipped. The avatars partial is app/views/components/_stage_agent_avatars.html.erb; board cards app/views/tasks/_task_card.html.erb + _board.html.erb. TWO-PART FIX: (1) On the assembled column, RESERVE + render the 4th (shipped/deploy) slot even while the task is still 'assembled' (an empty slot reserves its grid column so nothing reflows on hover — match the existing fixed-compartment idiom). (2) POPULATE that slot from the deploy/ship INTENT: bin/task intent --to shipped (or assembled->shipped) --actor <slug> records an agentic intent (an agent STARTING a stage) that already renders for the review pair pre-->reviewed (see reviewer-select records intents + the live-ticker pattern). stage_lane('shipped') already maps a shipped-stage entry to :shipped, so a ship INTENT entry should flow into by_lane[:shipped] — verify the intent->entries pipeline (how intents become crew entries / stage_agent_groups) and ensure a ship intent on an ASSEMBLED task surfaces in the reserved 4th slot WITH a live ticker (live_since), exactly like the build-lane live counter while building. So: Avi (or the conductor at the ship step) records the ship intent -> his avatar + live ticker appears in the assembled card's 4th slot -> visible 'being deployed by Avi' indicator. Per the deploy-flow design, assembled is Steffon's (Platform Engineer) QA lane and shipped is Avi's ship lane — decide whether the 4th slot shows the ship-owner (Avi) intent, or both assembled-owner + ship intent; default to surfacing whoever holds the active deploy intent. TESTS (ui+db shape, component+integration): helper unit — an assembled task with a recorded ship intent yields a reserved+populated 4th cluster (live_since set); board integration — the assembled card renders 4 fixed slots and shows the deploy-intent avatar + ticker. WATCH the board Alpine test gotchas (Nokogiri can't read Alpine @click/x-data; assert on rendered static markup / data-* not Alpine directives) and the x-show-owns-display rule. Match existing avatar/cluster styling; dark-mode parity. Out of scope: changing the deploy flow itself or bin/release; this is display + intent surfacing only.