Draw the laser like the ball's aim band, and let the two be compared

TUNE.beamBand flips between the two looks live from the T panel. 1, the new
default, draws the laser the way the BALL's aim trajectory is drawn: a path down
the lane whose width comes from each point's own projection scale, so it narrows
into the distance like everything else on the court, with a shadow on the lawn to
pin it there. 0 is the solid widening cone.

The cone was a true projection, which is why it was not obviously wrong to me --
but it GROWS in world width, so on screen it opens out while the court recedes,
and the eye reads that as a shape stuck to the screen rather than a plane lying
in the world.

The kill follows whichever look is on, in both fireBeam and drawBeamCuts.
Otherwise the comparison would be a lie: a narrow band that deletes a cone-wide
crowd tells you nothing about how the narrow band plays. Measured down one lane,
the cone takes 9 of 9 and the band 5 of 9.

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

HANDOFF.md

@@ -443,6 +443,16 @@ that holds that height all the way out instead of sloping to the ground — that
 makes the rest possible. Sloping, it lay flat on the grass across the whole far half, so there was
 nothing for it to cut exactly where the crowd stands.
 
+- **`TUNE.beamBand` is a live A/B between two looks**, flippable from the T panel on the phone.
+  **1 (default) = the BAND**: drawn the way the ball's aim trajectory is drawn — a path down the lane
+  whose width comes from each point's OWN projection scale, so it narrows into the distance like
+  everything else on the court, with a shadow on the lawn to pin it there. **0 = the CONE**: the solid
+  widening triangle. The cone IS a true projection, but it grows in world width (0.06 m -> `beamW1`),
+  so on screen it opens out while the court recedes — and the eye reads that as a flat shape stuck to
+  the screen. Oliver: "it does not look correct perspective wise".
+  **The KILL follows whichever look is on** (`beamBandW * 2` vs the cone's taper) in BOTH `fireBeam`
+  and `drawBeamCuts`, or the comparison would be a lie — measured, the cone takes 9 of 9 bodies in a
+  lane and the band 5 of 9.
 - **THE PLANE IS OPAQUE, and that is what settled it.** While it was translucent, its opacity and
   the over/under read were the same dial pulling in opposite directions: readable enough to show the
   split and it veiled the whole cone, subtle enough to look right and you could not tell above from