What you just told the crew appears where you told it #70

The box is the front door of an app — a sentence becomes an issue and a builder starts on it — and after you press it the page comes back with the tell somewhere in Now and no sign of what happens next. The crew picks it up on its next tick, the run starts, the preview follows; none of that reaches the page you are standing on until you reload.

The app head already refreshes itself on a deploy (#35), and the transcript tails a run live (#51). This is the same machinery pointed at the one thing a person does most: tell the crew something and watch it get picked up.

Done looks like

• [ ] Telling the crew leaves you on the app page with the new tell visible at the top of what is happening now, in the studio's told word, with who it went to.
• [ ] Without a reload, that row becomes waiting when the run is queued and working when it starts, and its title becomes the link to the transcript the moment there is one — driven by the same live stream and fragment pattern the head card uses, one fetch in flight at a time.
• [ ] An empty sentence, a sentence that is only whitespace, and one longer than the box allows are refused at the boundary exactly as today, with the text still in the box and the reason beside it.
• [ ] With JavaScript off the post still works and the page still tells the truth; the refresh pill covers what the live region does not.
• [ ] No layout shift as the row changes state, no new dependency, and the fragment is authorized exactly as the page is.
• [ ] test/studio.test.ts: telling the crew returns the app page with the new tell in Now; the fragment shows that row moving from told to working between two calls; a reader who cannot write cannot tell the crew anything, as today.
• [ ] docs/STUDIO.md, The box, says the page follows what you told it.

Files I expect to change

src/web/pages/studio.ts, src/web/live.ts, src/http/server.ts if the fragment needs a route, docs/STUDIO.md, test/studio.test.ts.

Risks

• Two live regions on one page — the head card and now this one — must share the stream and stay inside MAX_LIVE_STREAMS.
• Conflicts with #55, which is doing the same thing for the home; land after it and reuse whatever it leaves in live.ts rather than adding a second client.
• Claiming more than is true: a tell is not working until a run is running, and the page must not say it is.

Who

Scout — the smallest live region that makes the box feel answered.

Closing this: it is already true in main. tellSubmit (src/web/pages/studio.ts:1866) redirects back to the app page with the builder named and Watch it work below, and #64 left the app page with a live live-now region on run.,pull.,issue.* (studio.ts:1194), so the new tell appears where it was told and moves waiting → working without a reload. Nothing left here worth a run.