#2944 stagecraft studio: a work-item view showing where one item is in its factory and how it got there

Add a work-item view to the studio: one work item shown on its factory's graph, with where it is now, the path it took to get there, and its history. This is the studio's equivalent of the Lab's per-issue lifecycle view.

Why

Seth, 2026-10-02: "for any given issue, to visualize where it is (like we have on swamp-club/lab per issue)." The Lab's precedent is ~/sc/swamp-club/islands/lab/StateMachineGraph.tsx and LifecycleRenderer.tsx:

• completed phases in green;
• the current phase glowing cyan;
• future phases dim;
• not-taken edges dashed;
• sub-steps listed under each phase.

What it shows

• The factory's graph in Design mode's lane layout (#2807), drawn on the definition this work item pinned, which may be older than the factory's current definition; say so when it differs. Stages it has visited are marked done, with a count when entered more than once (loops). The current stage is highlighted. The transitions it actually took are drawn solid, and the rest are dim.

• Where it is now: the current stage and cycle. What it's waiting on, using the same exit-readiness and gate messages that status prints:

  • a person's decision, and which gates;
  • a product to record;
  • a dispatch.

  Also whether a limit has parked it, and how long it has been waiting.

• History: the journal as a timeline (stage entries, products recorded, approvals and declines with the person named, overrides, dispatches), reusing Simulate's Run and Metrics panels (#2808) on the real journal. Clicking a timeline entry highlights its stage on the graph.

• Its tracker ref linked out, for example the Linear issue, plus its relations if the tracker has them (#2796): parent, blocked by, duplicates.

• Copy reference / copy as scenario: Copy reference for the work item and its current stage, to paste to the agent (#2807). "Copy this run as a scenario" shows the real journal as scenario YAML, from #2810's plan, the same read-only copy flow as Simulate's (#2808).

• Reached from a Board card (the companion issue), a URL like /w/<key>, and a work-item search in the studio.

Data

A read-only route, for example GET /api/work-items/<key>. It returns the run record, the pinned definition by version and digest, and the product versions the timeline needs. The studio stays read-only.

Done when

• A work item that has looped through review and now waits on a person shows:
  • the visited stages with counts;
  • the path it took;
  • the current stage and what it waits on, using the engine's own messages;
  • its timeline.
• A work item pinned to an older definition is drawn on that one, with a notice.
• It updates live as the agent advances the item.
• Studio tests, keyboard navigation and WCAG 2.2 AA, as the rest of the studio has.

Out of scope: any write action, and Operate-style tokens on the factory-wide Design graph (the Board covers the factory-wide view).