Let the file own why the row cap is conditional; the README states that it is

2026-08-25 17:21:20 -04:00
parent 128172d3a8
commit f0c1289519
1 changed files with 5 additions and 6 deletions
@@ -110,12 +110,11 @@ naming every card on the Monitor grid, its width and its order, and generates th
 from it — the column ladder, the span clamps at each width, the row-height cap, and the
 compensation when a conditional card is absent. Column counts are 8/4/2/1 and spans are 1/2/4/8,
 which is what lets the board re-cut itself at any width with no holes and no hand-placed card.
-Breakpoints are arithmetic over `VV_MON_CARD_FLOOR`, never chosen by eye. The row-height cap is
-conditional on the same arithmetic: it applies only where a rung fits one screen, because a rung
-with more rows than that scrolls the page however its rows are sized, and capping there would clip
-every card to buy nothing. `pages/monitor.php` carries the card bodies and nothing about where
-they go; moving a card is moving a line in that array. The page cross-checks the declaration
-against the cards that actually rendered and says so in the browser if they disagree.
+Breakpoints are arithmetic over `VV_MON_CARD_FLOOR`, never chosen by eye, and the row-height cap
+is conditional on the same arithmetic — it applies only where a rung fits one screen.
+`pages/monitor.php` carries the card bodies and nothing about where they go; moving a card is
+moving a line in that array. The page cross-checks the declaration against the cards that
+actually rendered and says so in the browser if they disagree.

 **Caching.** Several endpoints serve from `$VV_CACHE_DIR` (`/tmp/varaverk/api`, tmpfs) rather than hitting live
 APIs on every page view, refreshed by `Tools/api_cache_writer.sh`. `?live=1` bypasses the