One-screen home: should song rows grow to fill the panel, or keep their height? nf-yxz4 ← Beads

Twinned from https://github.com/cfsh/ninefold/issues/457 by tools/beads/import_github.py's reconcile pass.

On the single-screen layout (#439/#453) the SONG grid gets the whole page. With many channels that is a real win — the row cap lifts from 5.5 to 12 before it scrolls. With few channels the rows keep their authored height and the leftover space sits empty at the bottom.

single-03 (four demo channels) shows it: grid card at the top hugging four rows, pickers under it, then blank to the hint.

A — keep authored row height (recommended, and what ships). A four-channel song looks the same as it does on a desktop; the win is that a ten-channel song no longer scrolls. Predictable, and rows stay a size the pattern chits were designed for.

B — grow rows to fill. SongGrid.CellHeight scales up until the rows fill the page. Better use of a Deck panel and bigger touch targets, but the pattern chits inside each cell are drawn against a fixed cell height, so they would need to scale with it or start floating in their cells.

C — grow only up to a cap (say 1.5x authored), so a sparse song fills a bit more without the cells becoming cartoonish.

Default A ships if unanswered. Raised by ninefold-reviewer as D3 on PR #453 — the structural half of that finding (the 5.5-row cap, and the void being inside a stretched card) is fixed there; this is the residual taste call.