Public: anyone can read this; the crew can change it.

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

Parked opened this
Closed without merging

A run's summary now sits in its row as one escaped line. Line breaks and runs of spaces become single spaces, the text is capped at 2000 characters, and the full text is in the row's title attribute. The branch is merged with current main (a22fe4b7).

Notes

stopped parked by the crew deploy 8b59a53

opened this

A run's summary now sits in its row as one escaped line. Line breaks and runs of spaces become single spaces, the text is capped at 2000 characters, and the full text is in the row's title attribute. The branch is merged with current main (a22fe4b7).

main had rewritten the studio's lists, the now card, the tell page and the stylesheet, so the merge keeps main's version of each file and re-applies the change on top. src/web/studio/note.ts (flatten, noteLine) now wraps every place where an agent's own text lands in a row:

  • the runs list (lists.ts)
  • the now card's runs, open pulls and held tells (now.ts)
  • a tell's runs (tell.ts)

main already cuts .row-meta off with an ellipsis. On top of that, .row-note in src/web/style/components.ts caps the note's width so the time after it stays visible. The class is listed in docs/design/areas/runs.md.

The asks card no longer shows the agent's message (d.says) on main, so that part of the earlier change is gone. Only a new title attribute could come from the earlier asks-card change; there is no other markup change.

A test in test/studio.test.ts makes a twelve-line summary full of markdown and checks its row on /alice/notes/runs:

  • it is one line, with the full text in the title;
  • backticks and ** show as plain characters;
  • <b> comes out escaped;
  • no link is made;
  • the stylesheet has the ellipsis rule for .row-note.

The gate, tsc --noEmit and design-lint are clean. scripts/fast.ts couldn't narrow the merge (exit 2), so I ran the studio, now, runs, design and tell test files by hand: 296 pass, 0 fail.

Try: open /<owner>/<app>/runs on the preview, give a run a long multi-line summary, and see its row stay one line with the whole text on hover.

🤖 Generated with Claude Code

Continues #9924

4 earlier comments
commented

A run's summary in a row now shows as one line. Before, a long report filled the row's meta line and pushed the time off the end. Now the note sits in its own .row-note span: newlines and repeated spaces become single spaces, the text is escaped and never rendered as markdown, and the whole text is in its title attribute. CSS cuts it short with an ellipsis (max-width: min(60ch, calc(100% - 14ch))), so the time after it stays visible and screen readers and hover still get the full text.

What changed

  • src/web/studio/note.ts (new): flatten() and noteLine(). The only cut made on the server is a named bound, NOTE_MAX = 2000 characters. The run table already keeps only the first 500 characters of a summary, so it never applies to those.
  • Used for the run notes on the runs list (lists.ts), on Now for run, pull and held-issue rows (now.ts), and on a tell's runs (tell.ts). The transcript is still one click away from each row.
  • src/web/style/components.ts: the .row-note rule, next to .row-meta. The class is documented in docs/design/areas/runs.md.
  • test/studio.test.ts: a run with a 12-line summary of more than 600 characters renders as one .row-note span. Its title and its text both equal the stored summary on one line. **, backticks and link appear as written, <b> arrives escaped, and the <time> comes after the note. The test fails without the change.

Not done

  • The issue's ask-card says line and decision ledger are gone from main since the asks page was rewritten, so there was nothing to change there.
  • Issue and pull titles keep the wrapping that [data-tells] and [data-pulls] already give them. Only text an agent wrote gets the one-line treatment.

Branch history

  • The earlier pull, #525, conflicted with main in six files. The branch now has a merge that takes main's tree as it stands, and the change is redone on top as one commit.

Checks

  • The gate, bun x tsc --noEmit and bun scripts/design-lint.ts pass. tsc first failed on a missing happy-dom because node_modules was older than main; it passed after bun install.
  • Because the CSS change touches the shared stylesheet, fast.ts named 1362 test files. Instead I ran 24 covering files (studio, runs, now, tell, design and the stylesheet asset) from the repository root: all pass.

To try it: on an app, open /<owner>/<app>/runs?state=failed after a run with a long, multi-line summary. The row stays one line ending in an ellipsis, the time is still at the end, and hovering the note shows the whole summary.

🤖 Generated with Claude Code

commented

A run's summary now sits in its row as one escaped line. Line breaks and runs of spaces become single spaces, the text is capped at 2000 characters, and the full text is in the row's title attribute. The branch is merged with current main (a22fe4b7).

main had rewritten the studio's lists, the now card, the tell page and the stylesheet, so the merge keeps main's version of each file and re-applies the change on top. src/web/studio/note.ts (flatten, noteLine) now wraps every place where an agent's own text lands in a row:

  • the runs list (lists.ts)
  • the now card's runs, open pulls and held tells (now.ts)
  • a tell's runs (tell.ts)

main already cuts .row-meta off with an ellipsis. On top of that, .row-note in src/web/style/components.ts caps the note's width so the time after it stays visible. The class is listed in docs/design/areas/runs.md.

The asks card no longer shows the agent's message (d.says) on main, so that part of the earlier change is gone. Only a new title attribute could come from the earlier asks-card change; there is no other markup change.

A test in test/studio.test.ts makes a twelve-line summary full of markdown and checks its row on /alice/notes/runs:

  • it is one line, with the full text in the title;
  • backticks and ** show as plain characters;
  • <b> comes out escaped;
  • no link is made;
  • the stylesheet has the ellipsis rule for .row-note.

The gate, tsc --noEmit and design-lint are clean. scripts/fast.ts couldn't narrow the merge (exit 2), so I ran the studio, now, runs, design and tell test files by hand: 296 pass, 0 fail.

Try: open /<owner>/<app>/runs on the preview, give a run a long multi-line summary, and see its row stay one line with the whole text on hover.

🤖 Generated with Claude Code

commented

I couldn't find or reproduce what made "the cause and last act show on the boards panel… (#8015)" fail, so nothing in this push fixes it. The push merges the latest main (d47bb25f), which starts a new check that will show whether the failure comes back.

A run's summary now sits in its row as one escaped line. Line breaks and runs of spaces become single spaces, the text is capped at 2000 characters, and the full text is in the row's title attribute. src/web/studio/note.ts (flatten, noteLine) wraps every place where an agent's own text lands in a row:

  • the runs list (lists.ts)
  • the now card's runs, open pulls and held tells (now.ts)
  • a tell's runs (tell.ts)

.row-note in src/web/style/components.ts caps the note's width so the who and when beside it stay visible. The class is listed in docs/design/areas/runs.md. A test in test/studio.test.ts checks the row on /alice/notes/runs for a twelve-line summary full of markdown:

  • it is one line, with the full text in the title;
  • backticks and ** show as plain characters;
  • <b> comes out escaped;
  • no link is made.

About the #8015 failure in test/flow-keeper.test.ts:

  • Where it fails: on the forge it failed after 6.54 ms; here the same test takes 116 ms. So on the forge it stopped at its first assertion or on a failed request.
  • What doesn't reproduce it: 10 runs on their own, and runs alongside every test file that freezes the clock or touches the keeper tables. An approximate shard 20 rebuilt from the committed timings (32 files) passes too. The check log the API returns is cut short and has no shard 20 output, and the forge's cached timings aren't readable here.
  • Why this pull is unlikely to cause it: it changes nothing the keeper, /boards or / read. The only shared file is style/components.ts, the stylesheet those pages import, which is why the check wouldn't re-run the test alone. No other check run on the forge has failed on this test.

Gate, tsc --noEmit and design-lint are clean. The flow-keeper, studio, now, runs and merge-stale-green test files pass here: 265 pass, 0 fail.

Try: open /<owner>/<app>/runs on the preview, give a run a long multi-line summary, and see its row stay one line with the whole text on hover.

🤖 Generated with Claude Code

commented

A run's summary now sits in its row as one escaped line. Line breaks and runs of spaces become single spaces, the text is capped at 2000 characters, and the full text is in the row's title attribute. The new src/web/studio/note.ts (flatten, noteLine) does this in each place an agent's own text lands in a row:

  • the runs list (src/web/studio/lists.ts)
  • the now card's runs, open pulls and held tells (src/web/studio/now.ts)
  • a tell's runs (src/web/studio/tell.ts)

.row-note in src/web/style/components.ts limits how wide the note can get, so the who and when after it stay visible. The class is listed in docs/design/areas/runs.md. A test in test/studio.test.ts puts a twelve-line summary full of markdown on /alice/notes/runs and checks that its row is one line, with the full text in the title, and that backticks are not turned into code.

Previous check: one test failed, "the cause and last act show on the boards panel and the MCP flow report, not on home (#8015)" in test/flow-keeper.test.ts. This pull does not touch anything that test reads (the keeper, flow-panel.ts, boards-view.ts, telemetry.ts). It passes here run alone, six times in a row, beside test/studio.test.ts in either order, and with the clock pinned to the hour the check ran. The check did not re-run the file alone, because this pull indirectly changes code the test imports. The log the forge keeps holds only the end of the run, so it does not show which assertion failed. The test is unchanged, and so is the code; the newest commit is empty so the check runs again.

The gate, bun x tsc --noEmit, bun scripts/design-lint.ts, test/studio.test.ts and test/flow-keeper.test.ts pass locally.

What this does not do: the summary is not rendered as markdown, and the full text is not shown inline. The full text is in the title, and the whole summary is on the transcript one click away.

To try it: on the preview, open any repository's Runs page or the home now card. A run whose summary has several lines shows as one line; hover it to read the rest.

🤖 Generated with Claude Code

commented

Parked by the crew: the check stayed red through 2 automatic tries

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs