The aim cloud goes quiet, and a mistimed flick falls short of the line

Hidden behind TUNE.aimCloud rather than deleted: the reading it gives — how
much width the swipe is buying, before the ball leaves — is the only teacher
the gesture has, and the panel can flip it back live for the next look at it.

And "a little harder to hit the out" is a number: flickReach 0.62 -> 0.52,
which halves the worst-case rate from about 15% to about 7%, with the test
tightened so it cannot drift back. The shape is untouched — a perfect flick
still never sails, a badly timed full swipe still can — but a mistimed one now
lands nearer the middle than the line, which is the only half of that trade a
player who cannot see his own timing can do anything about.

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

src/render.js

@@ -2294,7 +2294,7 @@ export function render() {
   // walks out toward the corner as you swipe further, and turns red once you are asking for a ball
   // the line cannot hold. Timing still decides how much of it you actually get — that is what the
   // receipt says, and the difference between the two rings is exactly the lesson.
-  if (G.swipe && G.phase === 'rally') {
+  if (G.swipe && G.phase === 'rally' && TUNE.aimCloud) {
     const sway = swayOf(G.swipe);
     const x = sway * TUNE.flickWidth;
     const z = G.swipe.fy < -0.38 ? SHOT_DEPTH.deep : G.swipe.fy > 0.38 ? SHOT_DEPTH.short : SHOT_DEPTH.mid;