max / quasi

Rest learns which pages a reader can go straight to Decided in quasicoherent 0ce21f4b (Max chose a: grow the vocabulary). Rest::jumps is a page number and an address per page. An address per page and not a count, because a renderer cannot build page 5's address out of forward and back without knowing the address grammar, and that grammar is the private vocabulary a conversion exists to retire. The router names the addresses and the renderer draws them, which is the split Row::activate already makes. The number is carried rather than implied by position: what a strip offers is a window around the reader -- MNW's build_pagination_range already windows to five of twenty -- so an index into that list is not the page it names. Which pages to offer stays the host's for the same reason it computes them today; a renderer choosing its own would give a different answer per host for one list. Where the description offered jumps, all three renderers put the strip in place of the "3 / 8" readout rather than beside it: the strip says both numbers already, and printing the position twice is a control arguing with itself. The page being read is drawn as text and not as a control in all three, because one that reloads the page it is on is the lying control control_tag exists to prevent. Rest::is_here answers that once rather than three times. The premise this was filed on was half stale, and it is worth saying which half: position and total were already there. layout::Paging has carried page() and pages_total() since Rest existed, so only the jumps were missing. Also fixed, found while doing it and in the code this had to change: quasi-tui's pager line claimed ONE focus position for a line the focus walk had pushed TWO stops into, so every control below a pager with both directions drew its caret one place early. That is the same defect the_drawing_counts_the_same_table_rows_the_walk_stops_on records for a table of tickable rows, in a second place, and the jumps would have widened it. The line is a list of pieces now -- Prev, the position or the pages, Next -- and the drawing and the focus walk both read it, so they cannot count differently. Prev and Next are printed whether or not they can be pressed, which they were not before: Next had no words at all. Rest::showing is the last piece. audiofiles held the only two struct literals of this type, for a real shape the constructors did not name -- a cap that is a rendering budget, with nothing to press because nothing is missing -- and a literal breaks on every field this type gains. It broke on jumps.