#2943 stagecraft studio: a Board view of every work item by stage

Add a Board view to the studio: every work item in a factory, laid out by the stage it is in, so a person sees at a glance where all the work stands.

Why

Seth, 2026-10-02: "I expect users will also want a view of the board, a listing of each work item and where it is in the factory organized by stage." The studio shows a factory's design (Design mode, #2807) and simulated runs (Simulate, #2808). Nothing shows the real work running through it.

What it shows

• One column per stage, in the factory's flow order, the same order Design mode's lane layout uses. A card for each live work item on its current stage. Terminal stages are collapsed or counted, with done and abandoned items hidden behind a toggle.
• Each card shows:
  • the key and title;
  • its tracker ref, if bound (for example ABC-12 for Linear);
  • how long it has been in the stage;
  • its cycle in the stage, when above 1;
  • whether it waits on a person: highlighted, with how long it has waited (from the run's awaiting state, as metrics compute it);
  • whether it is parked by a limit (cycle limit, or the dispatch cap from #2703);
  • whether it is pinned to an older definition than the factory's current one (a digest mismatch).
• Filters: waiting on a person, parked, stale pin, and free-text search on key and title.
• Clicking a card opens the work-item view (the companion issue for a single work item's place in the factory).
• Live updates: cards move when a work item's run record changes, using the studio's existing file-watch and SSE channel, or a light poll if run records aren't watched. Say which and why.

Data

• A read-only server route, for example GET /api/work-items?factory=<name>. It lists run records of work items started on that factory with one swamp data query over modelType == "@swamp/stagecraft/work-item" && name == "run" and filters on the pinned factory name. Return only the fields the board needs. The page computes nothing from payloads it doesn't need.
• The studio stays read-only: no route writes, and the board never advances, approves or reassigns anything. Moving work is the agent's job, as everywhere in stagecraft.
• Scale: this should be fine for hundreds of items. Say what happens at thousands, for example paging or counting per column.

Relation to #2810

#2810, Operate mode, planned tokens on the Design graph for live items, plus each item's journal in Simulate's panels. This issue and its companion split that into a board and a work-item view. #2810 is closed in favour of the two, and its server route idea lives here.

Done when

• The studio has a Board view. On a repo with work items in several stages, including one waiting on a person, one parked and one pinned to an older definition, each shows correctly, and the board updates as an agent advances an item.
• A studio test covers the route and the column assignment.
• Keyboard navigation and WCAG 2.2 AA, like the rest of the studio.
• The skill's studio section and the README mention it.

Out of scope: any write action from the page, and cross-factory boards (one factory at a time, using the existing factory picker).