From 113164fadb9e671ed452a71ad6fcc7110c30890e Mon Sep 17 00:00:00 2001 From: Meta Vens Date: Tue, 29 Sep 2026 22:24:39 +0200 Subject: [PATCH] Record fire control batches 5-8 landing and their follow-ups Co-Authored-By: Claude Opus 5.5 --- docs/fire-control-cut.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/fire-control-cut.md b/docs/fire-control-cut.md index 265452916..00d783dc6 100644 --- a/docs/fire-control-cut.md +++ b/docs/fire-control-cut.md @@ -2676,6 +2676,14 @@ follow-up rulings, all given on 2026-09-30: An out-of-arc round with a selected target bursts after that target leaves. That is ruled behaviour: an out-of-arc target is invalid, so the round takes the no-lock path. +- **Landed, 2026-09-29: batches 5-8 merged at `06001b57`.** 476 tests pass on the merged tree, after Soul + passes 5-7. Recorded follow-ups: + - The push-out follows the flight line, not the ray to the hull point. + - The HUD's burst range is an upper bound when a no-lock round stops at an earlier hull. + - The first-hull stop reads poses at fire time. + - A burst whose first round fails its energy or ammo spend retries every tick, bounded by capacitor refill. + - The first-round cooldown divides by `Cooldown` even when the magazine empties (a reload quirk that + predates this work). - **A round outlives its shooter,** for targeted and no-lock shots alike. Credit and loot with no shooter go nowhere.