SERVE UP was dropping you into gore whatever you picked

THE MENU BUG, and it explains three reports at once. cStart's handler was
`addEventListener('click', start)` — and addEventListener hands a listener the
MouseEvent as its first argument, so `start(modeId = pickedMode)` never saw its
default: modeId was an EVENT OBJECT. `G.classic = modeId === 'classic'` was
therefore always false and the zombie branch never fired. Picking CLASSIC or
ZOMBIE TENNIS on the setup screen did nothing at all; SERVE UP always started
the gore mode. A default parameter only applies to `undefined`, and a click
handler always passes something. `() => start()`.

That is also why "in normal tennis i dont see the ball circles and the serve
hint bar": there was no normal tennis to be in. Both are drawn unconditionally
in render() and the tennis struggle hints are already mode-gated correctly.
Verified through the real menu after the fix: CLASSIC gives mode=tennis with
no bodies on court, ZOMBIE gives match=true against the SHAMBLER in its own
body. Every other bare handler in the codebase takes no parameters — checked.

THE MOP BOY had the same class of bug one layer down. sendBoy was called and
mopWorthIt() refused: it tests `d.z >= COURT.netZ - 2`, the NEAR half, because
in the gore mode everything dies on the near court. A match's blood is all on
the FAR side, where the body stands and bleeds through four wound stages, so
the boy could never qualify. The near-side bias stays; the match is the
exception.

DANIEL was being dropped, not missing. Two causes, both mine: the asides were
queued at 0.7-1.5 s and matchPoint fires the score call at 0.4 s with a clip
over a second long — voice() drops anything that would start while he is still
talking (one man, one microphone). And asideEvery is 55 s, a whole match game.
Delays moved past the score call; matchAsideEvery is 15 s, which fits a mode
whose events are a limb and your blood rather than a wave of bodies.

THE FALL: quicker down, longer on the floor (0.09/0.11/2.0/0.30). And it was
genuinely SHRUNKEN — the generator draws fall rows smaller than standing rows
(the brute's buckle came back 190 px against a 224 px stance) and _zsheet's one
global scale preserved that faithfully, so the body shrank the moment it
started to fall. A fall row is anchored on its own buckle now, which must draw
at standing height. All seven generated families re-cut: 224/153/98/181 against
the hand-made racket family's 224/154/85/179 — the convergence is the check.

THE FLICK: 0.42 made going out impossible, which fixed the 8-in-10 bug and
overshot it ("too easy. i must be able to play out"). 0.62 puts risk back where
it belongs — ~15% out at quality 0, 5% at 0.75, and never on a perfect flick.
The test now asserts that shape: bounded, monotonically falling, zero at 1.

59 tests green.

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

src/config.js

@@ -31,7 +31,12 @@ export const TUNE = {
   flickWidth: 3.95,        // m off centre a PERFECTLY timed flick reaches. The singles line is 4.115,
                            // so this is the corner with 17 cm to spare. Raising it past the line does
                            // not make the flick punchier, it makes a perfect one go out.
-  flickReach: 0.42,        // how much of an aimed shot's width a MISTIMED flick gets (1 = all of it).
+  flickReach: 0.62,        // how much of an aimed shot's width a MISTIMED flick gets (1 = all of it).
+                           // 0.42 made going out IMPOSSIBLE, which fixed the 8-in-10 bug and then
+                           // overshot it: "flicking: too easy. i must be able to play out." At 0.62
+                           // a mistimed flick CAN sail (~15% of the time at quality 0, on the worst
+                           // half of the scatter) and a perfectly timed one never can — the risk is
+                           // back and it is timing, not a coin toss, that decides it.
                            // Reach x quality must stay under the sideline once aimError is added on
                            // top, or the flick goes out — which is exactly the bug this fixed:
                            // 3.3 * 0.45 + 2.4 = 3.89 against a 4.11 m line. Raise it and the flick
@@ -184,6 +189,10 @@ export const TUNE = {
   bossHopX: 2.0,    // m of ground one hop covers (the eased arc lands it at about 2/pi of this)
   racketEvery: 3,   // games between racket-zombie (plain opponent) spawns — was EVERY won game, which
                     // is why he read as "the boss" and why a real boss would not have stood out
+  matchAsideEvery: 15, // ...but 55 s is a whole match game. In the match his asides are tied to
+                       // things that happen every point or two — a limb, your blood — so the gore
+                       // spacing muted him almost entirely. Same ONE cooldown mechanism, a value
+                       // that fits the mode's own event rate.
   asideEvery: 55,   // s between the umpire's sarcastic asides in splatter (jittered +-40%). He never
                     // acknowledged that the match had changed; now he comments on it, disapprovingly.
   racketHpPerGame: 0.12, // the racket zombie stiffens as the run goes on (floored into whole hp)