Twinned from https://github.com/cfsh/ninefold/issues/384 by tools/beads/import_github.py's reconcile pass.
From the playtest sitting 2026-08-02 (build e4facb9). Evidence: [capture-4](https://github.com/cfsh/ninefold/blob/4e33831b4b2b37fd2667abf4c1b2094b1a6f940e/playtest-logs/2026-08-02-e4facb9/capture-4.png) in [playtest-logs/2026-08-02-e4facb9/](https://github.com/cfsh/ninefold/tree/4e33831b4b2b37fd2667abf4c1b2094b1a6f940e/playtest-logs/2026-08-02-e4facb9).
Aedan's words:
> "L3 to fit the notes in view — we actually scrolled it down so that the top notes are up high and there's a lot of blank underneath. I think we could put it in the middle. So instead there should be, say, two or three empty rows above and two or three empty rows below. For this pattern with notes spanning C4 to G#4, when I press it, it scrolls up so that there are five empty rows below B3 down to F#3."
Current: L3 fits the pattern's notes into view but leaves the occupied range hugging the top of the viewport, with a large blank region below it — measured on his pattern, five empty semitone rows below the lowest note (B3 down to F#3).
Wanted: centre the occupied pitch range vertically, with roughly 2–3 empty rows of padding above the highest note and 2–3 below the lowest, so the notes sit in the middle of the roll rather than at the top.
Note this is the behaviour behind the hint PR #354 renamed to "L3 · fit notes in view" — the new name makes the current framing more obviously wrong, since it promises a fit and delivers a top-align. #354 is wording only and should not be held for this; this is the behaviour change.
None.
No comments.
