The opponent shows up, and the death loop dies

"still very weak and slow opponent. it also spawns at places where it is
impossible to react to my serve. so i win like always. in the cases i dont
win there is a bug. when trying to serve after i got hurt i get hurt again
and again until i die".

The death loop was G.serveNum. Tennis's pointTo is the only thing that ever
reset it, and the match bypasses pointTo entirely — so the first fault of the
match armed "second serve" permanently, and every missed serve after it was a
double fault, a point, and blood, repeating to death. Exactly the spiral a
rattled player serves into. matchReady(), the match's own point boundary,
resets it now; a regression pins it.

The receiver starts every point on its mark: matchReady drops it onto the
exact receiver position the tennis branch computes for O, deuce/ad mirrored,
instead of a random spawn x or wherever the last rally left it. An opponent
that cannot reach the serve is not weak, it is absent.

And the base opponent is a player now: matchSpeedBase 1.4 (the duel's 2.8m/s
lumber was tuned for one sudden-death point), matchFlub 0.08 (0.2 gives away
a fifth of all returns). Measured with the same autopilot that previously won
seven straight games: it now loses the match. Possibly too hot — the two
dials are named, Oliver's thumb decides.

40 tests, 15 seeds clean.

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

src/config.js

@@ -386,8 +386,13 @@ export const TUNE = {
   matchPlayerHp: 8, // your pool for the MATCH — richer than the gore mode's 4, because a real game
                     // has rallies you deserve to lose without the run ending ("the player is too
                     // weak in this mode"). Their point still costs 1; matchHeal is how you last
-  matchSpeedPer: 0.12, // racketAI speed grows this much per opponent felled...
-  matchFlubKeep: 0.82, // ...and its whiff chance keeps only this much — the ladder now that hp is flat
+  matchSpeedBase: 1.4, // racketAI speed multiplier for opponent ONE — the duel's 2.8 m/s lumber was
+                       // tuned for a single sudden-death point and read as "very weak and slow"
+                       // across a whole game (~3.9 m/s now, rising per rung)
+  matchSpeedPer: 0.12, // ...growing this much per opponent felled
+  matchFlub: 0.08,     // the match's own whiff base — the duel's 0.2 gives away a fifth of all
+                       // returns, which across a game is an opponent that beats itself
+  matchFlubKeep: 0.82, // ...and it keeps only this much per rung — the ladder now that hp is flat
   matchHeal: 2,     // hp back for a game won (the duel's healPerDuel rate)
   // The timing windows, DRAWN (the match's whole ask: "what is the possible tap window, what is the
   // sweet spot"). Numbers shared with the mechanics they visualise, so the picture cannot lie: