New run: one page of rows, and a repository keeps its git flow choice (#541) #544

Merged
cmoriarty merged 3 commits from claude/new-run-sheet-541 into main 2026-11-15 12:55:31 -05:00
Owner

For #541. New run is one page of rows in place of the wizard, in the Sheet layout the owner chose from the mock.

  • One page: every row starts with a value, so you change only what you want. Start run stays on screen and says what is missing, and ⌘↵ starts the run from any field. Cancel is gone: the tab's × closes the page.
  • Recent repositories first: the repositories of the newest runs, archived ones included, each with that run's name, status and date. A search covers every repository on Forgejo, and New project sits beside it.
  • Nothing asked twice: no Entry step and no methodology questions. OpenSpec follows the pipeline, whose row says adds OpenSpec where it would. Git flow is a switch, which says creates develop from main where it would.
  • A repository brings its choices: its newest run's git flow, from the profile's new last_git_flow, and its last tests. Both are read from the runs, so there is no migration. A repository without OpenSpec starts on quick-fix. The pipeline is not remembered, because it belongs to the work.
  • The same request: Start run sends what the wizard sent for the same choices, and POST /api/runs is unchanged.

This takes the recent-repositories part of #361. Batches, suggested issues and the Braid mark stay there.

Tests:

  • A new backend test reads last_git_flow for: a git-flow run, a later run without it, a plan, a retired pipeline name, a repository's own pipeline, no run, and an archived run. It failed before the field existed.
  • A vitest suite checks what a repository brings, what is offered and what is missing. It also checks that the request matches the wizard's for a described feature, an issue, a plan, a one-shot and scripted tests.
  • The New run journeys are rewritten for the page. A new one archives a run whose repository must still be listed, then turns git flow on, starts a run, comes back, turns it off, starts again and comes back. All three journeys fail on main's console.
  • ./tools/test.sh passed in 46 s.

I tried the page from this branch on production's data at 1440 and 390 px, without starting anything. The pictures are of the test server's seeded runs, with Forgejo's lists stubbed, so no real repository shows.

At 1440 px: a repository picked, with git flow turned on and the tests opened; and a new project, planned. The archived tools/recipes is still among the recent repositories.

A repository picked, git flow on, the tests opened A new project, planned

At 390 px: the top of the page, and its options with Start run at the bottom.

The top of the page at 390 px The options and Start run at 390 px

🤖 Generated with Claude Code

For #541. New run is one page of rows in place of the wizard, in the Sheet layout the owner chose from the mock. - **One page:** every row starts with a value, so you change only what you want. Start run stays on screen and says what is missing, and ⌘↵ starts the run from any field. Cancel is gone: the tab's × closes the page. - **Recent repositories first:** the repositories of the newest runs, archived ones included, each with that run's name, status and date. A search covers every repository on Forgejo, and New project sits beside it. - **Nothing asked twice:** no Entry step and no methodology questions. OpenSpec follows the pipeline, whose row says `adds OpenSpec` where it would. Git flow is a switch, which says `creates develop from main` where it would. - **A repository brings its choices:** its newest run's git flow, from the profile's new `last_git_flow`, and its last tests. Both are read from the runs, so there is no migration. A repository without OpenSpec starts on `quick-fix`. The pipeline is not remembered, because it belongs to the work. - **The same request:** Start run sends what the wizard sent for the same choices, and `POST /api/runs` is unchanged. This takes the recent-repositories part of #361. Batches, suggested issues and the Braid mark stay there. **Tests:** - A new backend test reads `last_git_flow` for: a git-flow run, a later run without it, a plan, a retired pipeline name, a repository's own pipeline, no run, and an archived run. It failed before the field existed. - A vitest suite checks what a repository brings, what is offered and what is missing. It also checks that the request matches the wizard's for a described feature, an issue, a plan, a one-shot and scripted tests. - The New run journeys are rewritten for the page. A new one archives a run whose repository must still be listed, then turns git flow on, starts a run, comes back, turns it off, starts again and comes back. All three journeys fail on main's console. - `./tools/test.sh` passed in 46 s. I tried the page from this branch on production's data at 1440 and 390 px, without starting anything. The pictures are of the test server's seeded runs, with Forgejo's lists stubbed, so no real repository shows. **At 1440 px:** a repository picked, with git flow turned on and the tests opened; and a new project, planned. The archived `tools/recipes` is still among the recent repositories. <img src="/attachments/e1f7772a-bc52-43e3-b07d-f6527dcd2d78" width="560" alt="A repository picked, git flow on, the tests opened"> <img src="/attachments/f0e5ff9b-f9b8-4880-bbdf-3601ed12958f" width="560" alt="A new project, planned"> **At 390 px:** the top of the page, and its options with Start run at the bottom. <img src="/attachments/1d0d413b-c80c-440f-bd98-9830032f0358" width="270" alt="The top of the page at 390 px"> <img src="/attachments/015e8b61-339b-4dab-a517-8d05cd1fb3f1" width="270" alt="The options and Start run at 390 px"> 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
New run: one page of rows, and a repository keeps its git flow choice (#541)
Some checks failed
test / suite (pull_request) Has been cancelled
2e6c952663
- New run is one page of rows, as Settings is, and every row starts with a value. Start run
  stays on screen and says what is missing; ⌘↵ starts the run from any field. Cancel is gone:
  the tab's × closes the page. The heading and the tab read "New run".
- The Repository row lists the repositories of the newest runs, archived ones included, with a
  search over every repository on Forgejo, and New project beside it.
- No Entry step and no questions. OpenSpec follows the pipeline, whose row says "adds OpenSpec"
  where it would. Git flow is a switch that says "creates develop from main" where it would.
- A repository brings its newest run's git flow choice, from the profile's new last_git_flow,
  and its last tests; it starts on quick-fix when it has no OpenSpec. The pipeline is not
  remembered: it belongs to the work.
- Start run sends what the wizard sent for the same choices.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
chore(openspec): tick the screenshots task of new-run-sheet-541 (#541)
All checks were successful
test / suite (pull_request) Successful in 2m11s
a4f9c860fc
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
cmoriarty deleted branch claude/new-run-sheet-541 2026-11-15 12:55:31 -05:00
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!544
No description provided.