3a91d87b081f5dfb80c24e3c2a9a3afd4808f541
The reticle was a chevron trail on the ground and a draw meter across the bottom. The trail was a RAY — it pointed at the target but said nothing about the ball getting over the net — and the meter sat in the apron, which is exactly where your thumb is while you pull, so the one readout that mattered mid-gesture spent the whole gesture underneath your hand. Now the aim IS the flight. previewServe runs the same targeting and the same loft solve hitServe fires with (both extracted, neither duplicated), so the arc you see is bit-identical to the ball you get — verified: vx/vy/vz/g all match to zero at quality 1.0, where the aim error vanishes. A preview drawn from a second copy of the maths is worse than no preview; it lies with confidence. One object now carries all three readings, up-court where you are looking: the parabola is WHERE, the colour is WHETHER (cool blue still means it only staggers), and the band's thickness and opacity are HOW MUCH — which is the part a hue cannot carry on its own. Because the arc ends at the auto-picked target, a weak pull and a full one at the same shambler draw the same curve in different colours: "pulling further does not reach further" made visible. A shadow tracks the arc along the lawn. An arc hanging in the air is ambiguous about where it comes down, and that trail is what pins it. The apron is left to the gesture demo alone, drawn bigger now that it owns the space, with its chevrons lifted clear of the player's legs. Tennis and the duel still serve to the box, not at shamblers — checked both. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Languages
JavaScript
75.2%
Python
15.8%
HTML
7.3%
Shell
1.4%
Swift
0.2%