McRitchie Studio

Agent Context

Fix-forward on #138 (board-aware-crew-columns, already merged into rel-20260623-fb969a + on QA). Two reviewer findings: (1) CARL (medium) + SHANNON (minor): blocked cards now ride the Building dropzone (dropzone-building, data-stage=building) but the CARD is tagged data-stage=blocked. SortableJS onEnd in app/views/tasks/_board.html.erb fires on EVERY drop incl in-place reorders (no same-zone guard ~line 54/59); handleSortEnd then sees oldStage=blocked vs newStage=building, differs, and PATCHes task.stage=building — silently UN-BLOCKING the task just by dragging/reordering it within its column (controller permits :stage with no transition guard, tasks_controller.rb:188). Also the failed-PATCH revert does getElementById('dropzone-'+oldStage)=dropzone-blocked which no longer exists -> card stranded until reload. FIX: add a same-zone guard in handleSortEnd (from===to -> no PATCH) AND/OR align blocked cards to data-stage=building + map the revert to dropzone-building. (2) SHANNON (minor): blocked rides Building which is collapsed <1250px on the deploy board behind the All Stages toggle, so a needs-attention blocked task is hidden by default -> keep Building uncollapsed or surface a blocked indicator on always-visible lanes. Plus stale-comment nits in _stage_agent_avatars.html.erb (grid 'for blocked', crew_overlap peek, locals header board default fiction) and _board.html.erb ('All columns'->'All Stages'). The JS drag interaction is NOT covered by minitest; add coverage at the best available tier (system/Playwright if feasible, else a focused assertion).