feat: let a size rejection be waived

A release below §5.5's floor was rejected with no way through, so a
policy wrong about one title left three Rick and Morty S09 packs
visible and none grabbable.

`allow_below_floor` relaxes the floor for one title into a soft fail,
never a pass: the release is waived, so automatic grabbing still skips
it and the import records a §5.7 waiver. The deck offers the one click
on a rejected row where the rule has an override, which is exactly what
§9.3's override is for.

Stored verdicts are re-derived when a title's overrides change — the
deck and the daemon's grab gate both read that column, so without it
the row the operator just acted on would keep reading `rejected`.

Closes #210

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

.impeccable/surfaces/web-src-main-ts.md

@@ -29,9 +29,15 @@ reads the library as derived status, not flags.
   counts behind cyan show/hide toggles. Release name is a secondary
   truncated line, full string plus indexer/date/bytes on row expand. Every
   waived/rejected row carries a verdict chip naming the rule. Grab is its
-  own control per row; on a waived row it is "waive + grab" and writes the
-  per-title override (rule→override mapping in releases.ts — bookkeeping,
-  never policy; verdicts always come from the API). Esc steps back one
+  own control per row; where the rule that failed has an override it reads
+  "waive + grab" and writes the per-title override (rule→override mapping in
+  releases.ts — bookkeeping, never policy; verdicts always come from the
+  API). A rejected row offers it too — §9.3's one click exists precisely for
+  the rule the operator disagrees with, and a size rejection (#210) is only
+  ever rejected. What the click produces stays a waiver: the row re-reads as
+  a dashed WAIVED, never eligible. When ELIGIBLE is empty and something is
+  waivable, its "none" line carries the count, so the way out is not folded
+  inside a collapsed bucket. Esc steps back one
   layer: deck → search results → board.
 - Removal (§7.4, issue 104): REMOVE is a quiet control in the deck head,
   never a row affordance — a dense list is the wrong place for a delete.