fix(u7): six defects from the heid bug-hunt panel, and five vacuous falsifiers

Cross-frontier panel (Gróa/Hulda/Regin/Kimi) on U7's diff, thread
01M368G2Y0JMTJ2T7M3JMTXV5Z. Four of the six fixes are for defects no test in
this repo could have caught, and the panel's guard-strength passes found five of
my own falsifiers green under the exact change they forbade.

THE 4-OF-4 FINDING — the group anchor could land on the WRONG artifact.
The anchor was the raw rel spliced into an href fragment while the tile id was
equally raw. A browser matches a fragment against ids RAW FIRST and only then
percent-decoded, so raw-on-both-sides is not merely unencoded, it is AMBIGUOUS:
with `a b.png` and `a%20b.png` in one booth, the first's href resolves to the
fragment `item-a%20b.png` and the raw pass matches the SECOND file's id. That is
the misfiled-judgment failure invariant 6 exists to prevent, arriving through a
path invariant 6 never looked at. Both sides now use `Item.url`
(`quote(rel, safe="/")`), which is injective here and is the convention
booth_flag has always used. The original test asserted the href occurred as SOME
id on the page — true while pointing at the wrong one.

GRÓA'S STRONGEST SOLO — a zero-hit filter removed the way back.
The rail was gated on the FILTERED list, so a valid filter with no matches
removed the rail, the filter links and the route back to `all`, while the
empty-booth branch announced the booth was empty with rail.total still holding
the real count. No recovery without editing the address bar, and it degraded the
same way with JavaScript off, on the surface the operator actually reviews on.
Gated on all_items now, with an explicit no-match row.

HULDA — one unrepresentable filename took out the INDEX, not just its booth.
A non-UTF-8 filename reaches CPython as a surrogate and quote() raises on it,
outside any per-item handler. booth_items feeds list_booths, so one 0xff byte in
one booth's filename 500s every booth's card. Such a file cannot be linked,
served or zipped, so it is skipped like a dotfile.

HULDA — the `f` shortcut has never worked. The selector named `.flagbtn`, which
nothing in this repo emits, so it fell through to the hidden target input;
clicking a hidden input does not submit its form, and the handler called
preventDefault anyway. Now clicks the flag form's real button, verified end to
end in a real browser.

GRÓA — a group jump was undone by the next keypress. The jump scrolls, the
cursor stayed at -1, and the next arrow focused tile 0 and scrolled back. The
cursor now picks up from the viewport, which also fixes the general
scroll-then-arrow case. Asserted on real scroll geometry in Chromium.

HULDA — the caption sidecar was read whole before being truncated, so a
pathological file was a MemoryError the OSError handler does not catch. Bounded
at the read, and deliberately NOT by st_size: a FIFO reports 0.

ACCEPTED KNOWN RISKS, both now documented rather than implied: no cap on rail
row count (1,000 groups of two would render 1,000 rows; the largest live booth
is 66 items and picking a cap without a booth that needs one is invented work),
and Item.group sits mid-dataclass (one construction site, keyword-only, grepped).
The docstring now names the UPPER median explicitly — two arms flagged that
"the middle group" admits both readings for an even count.

FIVE VACUOUS FALSIFIERS, found by the arms and not by me: the anchor test
survived v[0]->v[-1]; the informativeness guard survived sizes[-1]; the group
count survived len(v)+1; the zero-hit filter test used a fixture that HAD hits;
and the escaping test asserted over the whole page, so it went red on a code
comment. All rewritten, all mutation-proved. The table is up to 20 rows and one
drifted when I changed the line under it — reported by the harness, not silently
skipped, which is the behaviour tests/test_mutation_check.py exists to hold.

660 green; 20/20 proved. Deployed; 21/21 booths 200.

Held for design-dev, not fixed here: Gróa's finding that the sticky rail has no
scroll-margin, so a fragment jump tucks the target under it. It is one line in
base.html, the file he is rewriting from scratch.

booth/app.py

@@ -1036,7 +1036,11 @@ def create_app(
         insertion order, so walking `shown` once IS the rule.
 
         ⚠ THE RAIL IS ABSENT UNLESS GROUPING IS INFORMATIVE: two or more
-        groups, and the middle group holding more than one item. TWO
+        groups, and the UPPER MEDIAN group holding more than one item — for an
+        even count that is the larger of the two central sizes, so `[1, 2]`
+        renders and `[1, 1, 2]` does not. Named precisely because "the middle
+        group" admitted both readings and two panel arms flagged the ambiguity.
+        TWO
         degeneracies, not one. The contract named only the first --
         `sindra` and `sc-iso-spread` put every file in ONE group, and a rail
         with a single row cannot navigate. The second is the one the live set
@@ -1051,13 +1055,33 @@ def create_app(
             if it["group"] is not None:
                 by_group.setdefault(it["group"], []).append(it)
         sizes = sorted(len(v) for v in by_group.values())
+        # `sizes[len(sizes) // 2]` is the UPPER median; the `< 2` term
+        # short-circuits, so the index is always valid. No upper bound on the
+        # ROW COUNT: 1,000 groups of two pass this and render a 1,000-row rail.
+        # Accepted known risk — the largest live booth is 66 items and picking
+        # a cap without a booth that needs one is the invented work the roadmap
+        # gate exists to prevent. Raised 2-of-4 by the panel, 2026-09-22.
         if len(sizes) < 2 or sizes[len(sizes) // 2] <= 1:
             return []
         return [
-            # The anchor is the FIRST member's existing tile id. The template
-            # already stamps `id="item-<rel>"` on every figure; minting a
-            # parallel `#group-<key>` would be a second identity for one tile.
-            {"key": k, "n": len(v), "anchor": f"item-{v[0]['name']}"}
+            # THE ANCHOR IS BUILT FROM `url`, NOT `name`, and the template
+            # stamps the tile id from `url` too. Both sides must use the same
+            # percent-encoded string or the jump lands on the wrong artifact.
+            #
+            # A browser matches a fragment against ids RAW FIRST and only then
+            # percent-decoded, so a raw rel on both sides is not merely
+            # "unencoded" — it is AMBIGUOUS. With `a b.png` and `a%20b.png` in
+            # one booth, the first's href resolves to the fragment
+            # `item-a%20b.png` and the raw pass matches the SECOND file's id.
+            # `Item.url` is `quote(rel, safe="/")`, which is injective here
+            # (`a b` -> `a%20b`, `a%20b` -> `a%2520b`), and it is the convention
+            # `booth_flag` has always used for exactly this reason.
+            #
+            # Found 4-of-4 by the heid bug-hunt panel, 2026-09-22. The original
+            # anchor test could not see it: it asserted the href occurred as
+            # SOME id on the page, which stayed true while pointing at the wrong
+            # one.
+            {"key": k, "n": len(v), "anchor": f"item-{v[0]['url']}"}
             for k, v in by_group.items()
         ]