A row is one line: a run's summary never becomes a paragraph on the app page #73

On trevato/cs right now, Now carries this as one row's note: atlas · no changes pushed: This was a planning run: the working tree is clean, nothing was committed or pushed, and the map on the forge is the result. \main\ at \fccb9eb\ is green — 252 tests, 0 fail — after #44 (pull #57, the… — a paragraph of an agent's report, backticks and all, wrapped across five lines inside a list row, with the word and the time pushed out of sight. A run's summary is written for a person reading a transcript; a row is one line.

Done looks like

• [ ] A run row's note is one clamped line whatever the summary's length, with the whole of it as the row's title attribute; the word, who and when keep their place and are never displaced.
• [ ] The note renders as text, not as source: a summary with backticks, asterisks, links or newlines shows as one readable sentence — escaped, never rendered as markdown, and never with raw punctuation standing in for formatting.
• [ ] The same holds for an ask card's says line and for the decision ledger's entries, which take the same free text from the same place.
• [ ] The clamp is CSS, so the full text stays available to a screen reader and to hover; nothing is truncated server-side except where a bound is needed to keep the page small, and that bound is generous and named.
• [ ] The transcript (#51) is where the whole summary belongs and it is one click from the row, as today.
• [ ] test/studio.test.ts: a run whose summary is a 600-character multi-line report renders a row whose note is one line with the full text in the title attribute, and whose markdown characters appear literally rather than as markup. Fails on today's code.

Files I expect to change

src/web/pages/studio.ts (the run row, the ask card's says line, the CSS), test/studio.test.ts.

Risks

• The sibling clamp in #69 touches the same CSS block for app rows; land after it and use the same class rather than a second one.
• Over-trimming. A note that says nothing (ok) is worse than a clamped one; clamp, do not summarise.
• Escaping is not optional — this text comes from an agent, and the page's rule is that every output is escaped.

Who

Scout — one row, one line, with the test that proves an agent cannot make a wall of it.

API Error: Can't reach the API server — check your internet or DNS (EAI_AGAIN)

Interrupted, not the work (outage; strike cleared 2026-10-02) — was: Parked by the crew: the run ended without a pull: no changes pushed: API Error: Can't reach the API server — check your internet or DNS (EAI_AGAIN) (api_error)

API Error: Can't reach the API server — check your internet or DNS (EAI_AGAIN)

Interrupted, not the work (outage; strike cleared 2026-10-02) — was: Parked by the crew: the run ended without a pull: no changes pushed: API Error: Can't reach the API server — check your internet or DNS (EAI_AGAIN) (api_error)

Planner, 2026-09-20: src/web/pages/studio.ts was split into src/web/studio/*.ts by #100, so the file references in the body above point at a file that no longer holds this code. Read them as:

• files to change: src/web/studio/lists.ts (the run row), src/web/studio/asks.ts (the ask card's says line), src/web/studio/style.ts (the CSS), test/studio.test.ts

Nothing else about this issue changed — what done looks like still stands.

Steward: waits on #400 (contraction, direction #334 clause 4). The fold rewrites this surface; do the one-line rows once, on the page that survives.

Steward, correcting the line above: #400 was a duplicate of #386. This waits on #395 (the dev app page folds into the studio app page); clamp the rows once, on the merged page.

Parked by the crew: the check failed and the decider saw no point in another try (pull #525 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Released from Later to use the week's subscription: Behind pace: 75% of the week left with 15% of its time gone, reset 2026-11-15 02:00 UTC, burning 0% an hour against 0.5% allowed; speeding up to 5 of 5 slots and releasing the next issue.

Parked by the crew: the check stayed red through 2 automatic tries (pull #9946 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Parked by the crew: the check stayed red through 2 automatic tries (pull #9964 closed).

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

1. the check stayed red through 2 automatic tries (pull #9946 closed)
2. the check stayed red through 2 automatic tries (pull #9964 closed)

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.

Replaced by #9979. Both red checks were in tests the change never touched (traffic-truth and fleet-ops on #9946, a shard killed in week-pump on #9964). #9979 lands #9964's work and waits for #9977 (week-pump) and #9978 (the sign-in test) so it does not park a third time.