Home is headed by its repositories, and a plus starts a run from an open issue (#522) #523

Merged
cmoriarty merged 1 commit from claude/runs-page-hierarchy into main 2026-11-13 02:50:22 -05:00
Owner

Closes nothing by itself: braid#522 is closed when the change is archived.

What changed

  • Home: the repository name is each group's heading and its brightest text. A run is one line from 768px up and three lines on a phone. Only a run that is going or waiting on you has a bright title; resume and archive are grey until the row is pointed at or focused.
  • Tags: a run's tag no longer repeats its heading. It reads issue #6, or nothing for a run started from a brief.
  • Plus: beside each repository, a menu of its open issues, searched on the forge, with the arrows, Enter and Escape. Picking one opens New Run with entry, repository and issue answered. Describe a feature instead hands over the first two.
  • New Run: the issue is asked right after the repository and folds to a line with change. Another repository clears it; another issue keeps the pipeline.

Where it differs from the mock on the issue

  • The list's column is max-w-6xl: narrower, a 1440px screen still cut the long titles.
  • Between 768 and 1024px, resume and archive are icons and the nodes-settled count is hidden.
  • A live run's backend has a column of its own before the state, so live and finished rows line up.
  • Start a run with a New Run tab already open shows the page as it was left, as before. Only the plus replaces it.

Tests

  • ui/src/lib/methodology.test.ts: the step order per entry, and what a new repository or issue clears.
  • ui/src/lib/forge.test.ts: the tag keeps the issue number and drops only its own group's repository.
  • ui/e2e/newrun.spec.ts: two journeys, the plus to a started run, and the wizard asking for the issue before the pipeline. The test server has no forge, so the first reads the request the console sends to POST /api/runs.
  • No existing assertion changed. ./tools/test.sh passes: 845 backend, 171 unit, 58 journeys.

Screenshots (the real console on seeded runs; the issues in the menu are the test's)
Home at 1440px

The plus menu New Run opened from an issue Home at 400px The plus menu at 400px New Run at 400px

OpenSpec change: openspec/changes/runs-page-hierarchy/.

🤖 Generated with Claude Code

Closes nothing by itself: braid#522 is closed when the change is archived. **What changed** - **Home**: the repository name is each group's heading and its brightest text. A run is one line from 768px up and three lines on a phone. Only a run that is going or waiting on you has a bright title; resume and archive are grey until the row is pointed at or focused. - **Tags**: a run's tag no longer repeats its heading. It reads `issue #6`, or nothing for a run started from a brief. - **Plus**: beside each repository, a menu of its open issues, searched on the forge, with the arrows, Enter and Escape. Picking one opens New Run with entry, repository and issue answered. `Describe a feature instead` hands over the first two. - **New Run**: the issue is asked right after the repository and folds to a line with `change`. Another repository clears it; another issue keeps the pipeline. **Where it differs from the mock on the issue** - The list's column is `max-w-6xl`: narrower, a 1440px screen still cut the long titles. - Between 768 and 1024px, resume and archive are icons and the nodes-settled count is hidden. - A live run's backend has a column of its own before the state, so live and finished rows line up. - `Start a run` with a New Run tab already open shows the page as it was left, as before. Only the plus replaces it. **Tests** - `ui/src/lib/methodology.test.ts`: the step order per entry, and what a new repository or issue clears. - `ui/src/lib/forge.test.ts`: the tag keeps the issue number and drops only its own group's repository. - `ui/e2e/newrun.spec.ts`: two journeys, the plus to a started run, and the wizard asking for the issue before the pipeline. The test server has no forge, so the first reads the request the console sends to `POST /api/runs`. - No existing assertion changed. `./tools/test.sh` passes: 845 backend, 171 unit, 58 journeys. **Screenshots** (the real console on seeded runs; the issues in the menu are the test's) <img src="/attachments/0889ceba-0270-4d03-a1c4-504cb53795b6" alt="Home at 1440px" width="900"> <img src="/attachments/1e14c077-4d39-487a-8228-0a24ab2c55bb" alt="The plus menu" width="900"> <img src="/attachments/73d3320f-287c-46d6-8b98-00444011a43f" alt="New Run opened from an issue" width="900"> <img src="/attachments/0a7dc513-9210-421c-8708-f9d534dfd082" alt="Home at 400px" width="360"> <img src="/attachments/ed4a5624-8731-490c-8705-3297877628b7" alt="The plus menu at 400px" width="360"> <img src="/attachments/22912a5b-36f4-4d52-827a-57ce5c3efbca" alt="New Run at 400px" width="360"> OpenSpec change: `openspec/changes/runs-page-hierarchy/`. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
feat(console): Home is headed by its repositories, and a plus starts a run from an open issue (#522)
All checks were successful
test / suite (pull_request) Successful in 1m17s
957a808697
On Home every run title was bold and bright, every row carried a bordered
repository tag, and the repository's own name was small grey text, so nothing
said what to read first. Starting a run on a repository already on the page
meant opening New Run at an empty repository field, with the issue asked last.

- The repository name is each group's heading and its brightest text. A run is
  one line from md up and three lines on a phone; only a run that is going or
  waiting on the operator has a bright title.
- A run's tag no longer repeats its group's heading: `issue #6`, or nothing.
- A plus beside each repository lists its open issues, searched on the forge.
  Picking one opens New Run with entry, repository and issue answered;
  `Describe a feature instead` hands over the first two.
- New Run asks for the issue right after the repository. The step order and
  what a new answer clears are pure functions in lib/methodology.ts.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
cmoriarty force-pushed claude/runs-page-hierarchy from 957a808697
All checks were successful
test / suite (pull_request) Successful in 1m17s
to c0fd931361
All checks were successful
test / suite (pull_request) Successful in 1m49s
2026-11-13 02:48:11 -05:00
Compare
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/braid!523
No description provided.