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>

test.js

@@ -807,6 +807,9 @@ test('an aimed return can be played OUT, but only by mistiming it', () => {
   };
   assert.ok(pOut(0) > 0.02, 'a badly timed flick CAN go out: ' + (pOut(0) * 100).toFixed(1) + '%');
   assert.ok(pOut(0) < 0.25, '...but not the coin toss it was (every flick under q 0.66 went out)');
+  // ...and "make it a little harder to hit the out" (2026-08-18) is a NUMBER, not a vibe: the
+  // worst-case rate was halved off 15%, and this is what stops flickReach drifting back up.
+  assert.ok(pOut(0) < 0.10, 'a mistimed flick lands nearer the middle than the line: ' + (pOut(0) * 100).toFixed(1) + '%');
   assert.equal(pOut(1), 0, 'a perfectly timed flick never goes out');
   for (let q = 0.05; q <= 1.0001; q += 0.05)
     assert.ok(pOut(q) <= pOut(q - 0.05) + 1e-9, `risk falls as timing improves (q ${q.toFixed(2)})`);