Bring the swing log to every rally mode, and time the gold ring

Oliver wants to hand over a log of why he missed balls. It existed behind
a scoreboard tap but was gated on G.mode === 'tennis', so the Climb, the
cup and training (which run as 'splatter') logged nothing. It now writes
in every rally mode: hits with shot, tap age and any quality cap, misses
with the new let-it-bounce reason, and a WON/LOST line naming why each
point went. Tapping the open log copies all 200 entries with a header.

Its first catch: the gold ring went gold at a distance, which is too
early for the slow balls steps 1-3 brought in. It is now timed off the
ball's real path to his reach (against where his run is taking him):
gold means touch now. ringTime 0 restores the old ring. v365.

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

src/config.js

@@ -643,6 +643,10 @@ export const TUNE = {
   matchRingSweet: 2.7, // m — contact distance where the rings kiss (the 30-tapped-points benchmark
                        // lands hits tapping at 2.2..3.2 m, so the sweet spot is its centre)
   matchRingBand: 0.5,  // m either side of sweet that draws gold — the plausible window, made visible
+  ringTime: 1,      // 1 = the ring is TIMED (gameplay.ringCue): gold while a touch now centres the contact in
+                    // the swing window, at any pace. 0 = the old distance ring (matchRingSweet/Band)
+  ringBand: 0.35,   // share of the half-window either side of the sweet moment that draws gold (edge = q 0.65)
+  ringLead: 0.9,    // s before contact the timed ring appears
   // ---- THE READ (2026-08-28, Oliver: past the HEAD COACH "the opponents are very fast and barely
   // make mistakes any more — we need a twist"). The dead staff LEARN YOUR PATTERNS: land the same
   // lane readHabit times in a row and the opponent has the habit — an EXPECTED ball is anticipated