One page per branch; Review only names the draft

Decision

• The top bar has one draft action: Review, with the count on it. On a branch it has Branch page instead.
• Review does one job: list the draft's changes (main beside the draft, Undo on each), name it, and save it as a new branch or into an open one. No merge from Review.
• The branch page does the rest, like a pull request: a header with Merge, three checks (synced, conflicts, verify) that open their tabs, and three tabs (Changes, Verify, Conflicts).
• Merge is a confirm over the branch page, with the tag and which branches sync after. Merge is greyed, with the reason beside it, while a conflict is open, while a verify run is not finished, or for someone who cannot merge.
• Verify says whose differences they are: from this branch, or not. "Only your changes moved" is the verdict to look for.
• All branches is a list that opens branch pages; the draft is its first row and opens Review.

Why

The owner found the Branch → Review → Verify flow hard to use. The same changes were listed on four screens (Delta, Review, Verify, Merge) and none was the place to finish. The top bar had three draft controls side by side (the change count, a verify score, Review). Review offered "Save and merge" before anything was checked, Verify was a separate page with no way back into the flow, and Merge was a page holding one button.

Impact

• Review saves only; merging is on the branch page.
• Screens: review · branch · branch-verify · branch-conflicts · branch-merge · branches. The model: branch-verify-merge.

Status

Active

Sources

• The owner's instruction of 2026-10-16: "redo the Branch -> Review, Verify flow again, as UX is very bad".