Runs page: repositories as headings, one line per run, and a plus that starts a run from an open issue #522

Closed
opened 2026-11-13 01:41:03 -05:00 by cmoriarty · 1 comment
Owner

What happens
On the Runs page every run title is bold and bright, every row carries a bordered repository tag, and the repository name itself is small grey text. Nothing says what to read first. Starting a run on a repository already on the page means opening New Run at an empty repository field, and the issue is the last thing it asks for.

Fix

  • The repository name is the heading and the only bright text. One line per run, titles in regular weight, stopped runs a step dimmer. Only a running run, or one that needs you, gets a bright title. The repository tag goes where it only repeats the heading.
  • A plus beside each repository lists its open issues, with search. Picking one opens New Run with entry, repository and issue answered, on the pipeline step.
  • New Run asks for the issue right after the repository, before the pipeline.

Done when

  • The Runs page reads as in the mock below, and falls back to stacked lines at phone width.
  • Plus, pick an issue, land on the pipeline step with the issue filled in: covered by a browser test.
  • From Start a run, the wizard asks for the issue before the pipeline.

Related: #361 rethinks the wizard's options; this only moves the issue step.

Mock
The Runs page, one line per run

The plus menu of open issues

New Run, opened from the menu

Where to look: ui/src/components/Runs.tsx, ui/src/components/NewRun.tsx, openspec/specs/new-run/spec.md.

**What happens** On the Runs page every run title is bold and bright, every row carries a bordered repository tag, and the repository name itself is small grey text. Nothing says what to read first. Starting a run on a repository already on the page means opening New Run at an empty repository field, and the issue is the last thing it asks for. **Fix** - The repository name is the heading and the only bright text. One line per run, titles in regular weight, stopped runs a step dimmer. Only a running run, or one that needs you, gets a bright title. The repository tag goes where it only repeats the heading. - A plus beside each repository lists its open issues, with search. Picking one opens New Run with entry, repository and issue answered, on the pipeline step. - New Run asks for the issue right after the repository, before the pipeline. **Done when** - The Runs page reads as in the mock below, and falls back to stacked lines at phone width. - Plus, pick an issue, land on the pipeline step with the issue filled in: covered by a browser test. - From Start a run, the wizard asks for the issue before the pipeline. Related: #361 rethinks the wizard's options; this only moves the issue step. **Mock** ![The Runs page, one line per run](/attachments/224caeb4-3437-4bdb-b60e-e9581dca04e5) ![The plus menu of open issues](/attachments/e5d45125-aa71-475d-9efe-ca93b195b625) ![New Run, opened from the menu](/attachments/b83347f4-4c97-4d69-b797-be862613ba84) Where to look: `ui/src/components/Runs.tsx`, `ui/src/components/NewRun.tsx`, `openspec/specs/new-run/spec.md`.
Author
Owner

Shipped in pull request 523 (main 494ccf71), archived in pull request 528.

  • Home: the repository name heads each group, a run is one line from 768px up and three on a phone, and only a run that is going or waiting on you has a bright title.
  • A run's tag reads issue #6 or nothing; it no longer repeats the heading.
  • The plus beside a repository lists its open issues, searched on the forge, with Describe a feature instead. Picking one opens New Run with entry, repository and issue answered.
  • New Run asks for the issue right after the repository.

Evidence

  • New tests, failing before the change by construction (no plus, the old order): the step order and what a new answer clears (ui/src/lib/methodology.test.ts), the tag (ui/src/lib/forge.test.ts), and two journeys in ui/e2e/newrun.spec.ts. The suite passes: 845 backend, 177 unit, 58 journeys.
  • Tried on the laptop against the real runs at 1440, 844 and 400px before the pull request, and on seeded live, waiting, failed and project rows.
  • After the deploy the console shows a plus on all 13 repository groups, and the menu lists a repository's open issues.

Differs from the mock

  • The list is wider (max-w-6xl); between 768 and 1024px resume and archive are icons and the settled count is hidden; a live run's backend has its own column.
  • Start a run with a New Run tab open shows that page as it was left. Only the plus replaces it.
**Shipped** in pull request 523 (main `494ccf71`), archived in pull request 528. - Home: the repository name heads each group, a run is one line from 768px up and three on a phone, and only a run that is going or waiting on you has a bright title. - A run's tag reads `issue #6` or nothing; it no longer repeats the heading. - The plus beside a repository lists its open issues, searched on the forge, with `Describe a feature instead`. Picking one opens New Run with entry, repository and issue answered. - New Run asks for the issue right after the repository. **Evidence** - New tests, failing before the change by construction (no plus, the old order): the step order and what a new answer clears (`ui/src/lib/methodology.test.ts`), the tag (`ui/src/lib/forge.test.ts`), and two journeys in `ui/e2e/newrun.spec.ts`. The suite passes: 845 backend, 177 unit, 58 journeys. - Tried on the laptop against the real runs at 1440, 844 and 400px before the pull request, and on seeded live, waiting, failed and project rows. - After the deploy the console shows a plus on all 13 repository groups, and the menu lists a repository's open issues. **Differs from the mock** - The list is wider (`max-w-6xl`); between 768 and 1024px resume and archive are icons and the settled count is hidden; a live run's backend has its own column. - `Start a run` with a New Run tab open shows that page as it was left. Only the plus replaces it.
Sign in to join this conversation.
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#522
No description provided.