Instead of multiple revise steps, design arrow visual #16
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Having hardcoded extra iterations isn't good design, it would look better if the two steps being repeated had arrows pointing to each other, with a count next to it like "x3". Which would then show the result, and how many were actually needed.
Shipped as the OpenSpec change
spine-review-loop(archived asopenspec/changes/archive/2026-09-14-spine-review-loop/;run-spineis a new main spec). Commitf5e8266.What changed — the spine draws the review-and-revise loop as one loop where it began: a
reviewrow and areviserow joined by arrows pointing at each other, each with how many of its rounds actually ran (×2,×1) and its latest round's status (not neededwhen none ran). Rounds that were not needed are not counted or shown.Decision to review: this is the visual only. The pipeline still declares its bounded rounds (
.r2,.r3) as nodes; making the number of rounds dynamic is a scheduler change and is not in this one.Tested: unit tests for the grouping (two rounds/one revision, clean first review, running round-2 lens, no revise steps);
e2e/review-loop.spec.tsagainst the fake osfd (counts, arrows, hidden rounds, open/close order, running lens under the closed loop, selection opening it); vitest 332, Playwright 18 passed.