A change never says which tell it answers, so work whose tell is already closed still reads as open work #289

Every crew branch is named for the tell it answers — scout/13-after-new-app-land-on-a-page-that-shows, mason/4-update-from-parent-merges-when-the-fork — and the studio drops that on the floor. A change's row in /changes and its own page show the title, the word and time(pull.updatedAt) (src/web/studio/lists.ts:262), and nothing anywhere links the change to the tell.

It shows: on this forge pull #22 is open and its tell #13 is closed. The studio therefore offers a person a change to decide, for work the forge already considers done, with nothing on the page saying so — and its preview environment is one of the eight this forge is running.

Done looks like

• [ ] A change whose head branch names a tell (<crew>/<number>-<slug>) shows that tell beside it, as a link, on the change's own page and in the changes list — the studio's vocabulary ("for tell #13"), not "issue".
• [ ] When that tell is closed, the change says so in words a person can act on (e.g. "its tell is already done"), in the same place the word for the change lives, so the row reads true at a glance.
• [ ] Branch parsing is one small named thing with its own test: a branch with no number, a number that matches no issue, a number from another repository, and a slug containing digits all resolve to "no tell" rather than a wrong link or a throw.
• [ ] No extra query per row: the tells for a page of changes are one grouped read, and the bench for /changes does not grow with the number of rows (#48's ground).
• [ ] Tests: a change on scout/13-… links tell #13 and says it is done when #13 is closed; a change on revert-22 or a person's own branch shows no tell and no error. Both fail today.

Files I expect to change: a new small module under src/web/studio/ (or src/core/) that reads a tell number out of a branch name, src/web/studio/lists.ts, the change page in src/web/studio/, test/studio.test.ts.

Risks: the branch convention is a convention, not a contract — treat a parse failure as "no tell", never as an error, and never let a closed tell change the decide word a person acts on (#118 and #280 own that word); this is an extra line, not a new verdict.

Suggested: Mason — a small parser, a grouped read, and two pages that speak the studio's five words.

You've hit your weekly limit · resets Sep 27, 2am (UTC)

Interrupted, not the work (outage; strike cleared 2026-10-02) — was: Parked by the crew: the run ended without a pull: no changes pushed: You've hit your weekly limit · resets Sep 27, 2am (UTC) (api_error)

You've hit your weekly limit · resets Sep 27, 2am (UTC)

Interrupted, not the work (outage; strike cleared 2026-10-02) — was: Parked by the crew: the run ended without a pull: no changes pushed: You've hit your weekly limit · resets Sep 27, 2am (UTC) (api_error)

Re-read by the planner: this park was the crew hitting its weekly usage limit (api_error), not the issue being too big or wrong. Nothing was tried, so what done looks like stands as written; back to ready.