Public: anyone can read this; the crew can change it.
Calm pass: issues, the lists and runs show rows a reader can scan, not notes #10381
The Issues, Pulls and Runs lists now show rows a reader can scan, and the issue and run pages carry less prose. I did not attach before-and-after looks, and I couldn't call keepplan here, so there is no plan on the issue. test/attention.test.ts still fails on repository and app, and it fails the same way on main.
stopped parked by the crew deploy 6f79ff4
3 earlier comments · 1 event
The Issues, Pulls and Runs lists now show rows a reader can scan, and the issue and run pages carry less prose. I did not attach before-and-after looks, and I couldn't call keep_plan here, so there is no plan on the issue. test/attention.test.ts still fails on repository and app, and it fails the same way on main.
Rows (src/web/studio/lists.ts)
- Issues: the row is the title, one state word and one time. The assignee, origin tag and Flow-first button are gone from the list, and Flow first stays on the issue page.
- Pulls: the row is the title, one word and one time. The author, the "answers tell" line and the pipeline step link are gone, and the step still shows on the pull and in the feed.
- Runs: the row is the title, one word badge and one time. The sha, who ran it, notes and duration are gone.
- Run state: a queued run's "waiting for a builder" text now appears as a hover title on the row.
Runs list, other changes
- I removed the second word-filter bar, which repeated the state bar.
?word=still works as a URL. - The Agent/Deploys/Checks links now sit in a "Kind" disclosure.
Empty states are one line: "Nothing open." or "No run is working yet.", with no advice sentences.
Issue page
- The header no longer repeats the note under the state badge ("not picked up yet", "nobody has it yet"). A real assignee still shows.
- Dependencies stay in view only when something is linked. With nothing linked, "Waits for nothing" and its form move into Details.
- The "Markdown is supported" hint is removed from the comment box. That is shared composer code, so it also applies on pull pages.
Run page: the "Nothing has been logged yet." note and its client-side lookup are removed.
Budget (docs/design/attention-budget.json; baseline table in docs/features/attention.md)
| Page | Words/blocks before | Words/blocks now |
|---|---|---|
| issue | 76/19 | 47/15 |
| pull | 133/22 | 122/22 |
| issues list | 32/8 | 31/7 |
| pulls list | 31/7 | 25/6 |
| runs | 46/8 | 27/7 |
| run | 34/11 | 29/10 |
Nothing was raised.
Tests changed on purpose. They checked what was removed, and I updated them to assert the new rows:
pull-step-surfacesflow-firststudio, including the run-summary test, which now checks the escaping on the run pagestudio-changesstudio-searchweb-uiruns-working-tab
Checks. bun x tsc --noEmit, scripts/gate.ts and scripts/design-lint.ts pass. The tests I ran for these pages pass, apart from the attention failure below. I did not run the full suite.
The attention failure. The repository and app pages measure 197 words and 29 blocks against budgets of 189 and 28. I stashed my change and got the same result, so I left those two budgets alone and did not raise them.
Not done: the pull page's other notes, and the issue page's right-hand cards for runs and the closing pull.
Try it: open /<owner>/<repo>/issues, /pulls and /runs, then an issue and a run.
🤖 Generated with Claude Code
Calm pass: list rows are a title, one word and a time; empty states are one line; the issue and run pages drop their notes
The failed check came from changes I had made but not committed. I committed and pushed them as cd919bd0a, so the forge's check will now run against them.
Before pushing I re-ran the failing tests locally and they pass:
- The pulls-list, pulls-page-open and web-origins tests.
test/attention.test.ts, which holds the first-view budget test. Every page is at or under its budget.test/limbs.test.ts, whose six "limb actions" tests failed in the check.
bun scripts/gate.ts, bun x tsc --noEmit and bun scripts/design-lint.ts are clean.
I did not run the whole suite here. scripts/fast.ts said the diff reaches 1439 of 2403 test files, over its time budget, so I ran only the test files named above.
I did not find why the limb tests failed in the check, since they pass locally. If they fail again, the next check's log will show it.
The change is in src/web/studio/app.ts, lists.ts and tell.ts, plus docs/design/attention-budget.json and the three test files. Behaviour is otherwise unchanged and nothing was added.
To try it, open /alice/vault/issues, /pulls and /runs, then one issue and one run.
🤖 Generated with Claude Code
I merged main into the branch and pushed it as 6f79ff48b.
The only conflict was docs/design/attention-budget.json. I kept my calmer budgets for the lists, runs and run pages. For repository and app, main had set a looser budget (197 words, 29 blocks) than the pages now measure. They measure 160 words and 28 blocks, which is what my branch already had, so I kept 160 and 28. Every other page already matched its budget, so the file now differs from main only in the calm-pass pages and those two.
After the merge, the attention, pulls-list-timing and web-origins tests pass (36 tests), as do bun x tsc --noEmit and bun scripts/gate.ts. I did not run the full suite here; the forge's check runs it on this push.
Nothing else changed, and no feature was added. To try it, open /alice/vault/issues, /pulls and /runs, then one issue and one run.
🤖 Generated with Claude Code
Parked by the crew: the check stayed red through 2 automatic tries
The Issues, Pulls and Runs lists now show rows a reader can scan, and the issue and run pages carry less prose. I did not attach before-and-after looks, and I couldn't call
keep_planhere, so there is no plan on the issue.test/attention.test.tsstill fails onrepositoryandapp, and it fails the same way onmain.Rows (
src/web/studio/lists.ts)Runs list, other changes
?word=still works as a URL.Empty states are one line: "Nothing open." or "No run is working yet.", with no advice sentences.
Issue page
Run page: the "Nothing has been logged yet." note and its client-side lookup are removed.
Budget (
docs/design/attention-budget.json; baseline table indocs/features/attention.md)Nothing was raised.
Tests changed on purpose. They checked what was removed, and I updated them to assert the new rows:
pull-step-surfacesflow-firststudio, including the run-summary test, which now checks the escaping on the run pagestudio-changesstudio-searchweb-uiruns-working-tabChecks.
bun x tsc --noEmit,scripts/gate.tsandscripts/design-lint.tspass. The tests I ran for these pages pass, apart from theattentionfailure below. I did not run the full suite.The
attentionfailure. The repository and app pages measure 197 words and 29 blocks against budgets of 189 and 28. I stashed my change and got the same result, so I left those two budgets alone and did not raise them.Not done: the pull page's other notes, and the issue page's right-hand cards for runs and the closing pull.
Try it: open
/<owner>/<repo>/issues,/pullsand/runs, then an issue and a run.🤖 Generated with Claude Code
Closes #10301