The heavy WASM scenario (wasm_flat_budget, 64 integrated complexes vs two
`airdef wave oreshnik 40 2600`) lost intercepts at the tick-2102 checkpoint:
522 (main) -> 302 (#133) -> 243 (#134). Decomposed by A/B on one fixture, one
host (2bcce64), one SDK, each slice built from its own commit:
- 522 -> 302 (#133): Track.vel became an estimate from noisy measured places
(it was the target's true velocity); the forecast, the aim lead and the
interceptor's launch Fix all read it. Forcing the class estimate to Unknown
leaves the count unchanged (native 296 ~= 294), so class/roles is not the
cause. The pre-#133 522 used the target's true velocity, which the #133
contract "class and speed only from measurements" forbids; this portion is
the intentional cost of honest measurement-only tracks and is kept.
- 302 -> 243 (#134): the network cue was extended from the separate engagement
radar to every fire-quality radar, including each weapon's embedded radar.
Cueing every relayed contact each tick flooded the embedded fire control with
one-tick plots whose noisy velocity degraded guidance. Restricting the cue
back to separate radars recovers the whole drop: 243 -> 325.
- own_fire_within / FIRE_QUALITY / channels are NOT causes here: relaxing the
own-fire gate or the channel limit each changed nothing (243 -> 243). Embedded
radars always measure Fire plots of quality >= 64 and have no channel limit.
- #140 does not affect this loadout, by fact: the fixture deploys no separate
radar, so every profile is embedded with channels = 0; the channel-age bug
binds only where a profile has channels, and the channels-off A/B was flat.
Fix: the cue looks only through a separate fire-quality radar
(sam.kind == SamKind::Radar); the embedded radar keeps its beam/revisit/lock
acquisition as before #134. All radar profiles, channel limits, own-fire
authority and the measurement-only class/speed contract are preserved; no
target truth is injected.
Measured after the fix (WASM, fuel budget 300M/tick): checkpoint 325 intercepts
/ 2011 hits, fuel max 118M; final (tick 3302, two late Smart raids) 385 / 2472,
fuel max 176M; zero fuel failures. The first late raid reports the #135 recon
flight ("Разведка противника: впереди налёта высланы разведчики"); the second
is silent (recon budget spent) — the fixture now expects exactly that instead
of the stale empty chat that stopped the scenario.
Tests:
- airdef-mod/tests/saturation.rs: deterministic native replica of the checkpoint
(same sim, host block tracer) asserting the restored count and a regression
threshold, plus the #140 loadout fact (no separate radar, channels = 0).
- Sim::launch_audit (why.rs): on-demand tolerance diagnostic counting why each
(system, drone) pair holds fire — no track / stale / no authority / role /
doctrine / reach / claimed / not ready / not aimed / terrain / ready.
- sensor_tests: a network plot cues a separate fire radar but not the embedded one.
- wasm_flat_budget baselines re-measured with provenance comments; the asserted
fixture SHA in tools/airdef.py updated.
Verification: `python3 tools/airdef.py test-budgets` passes both stages and the
two late raids (283 steps, fuel failures = 0). airdef-core 292 + 8, mod lib 104,
mod scenarios 5, saturation 2 — all green. A/B record:
docs/measurements/issue-145-intercept-regression.json.
Co-Authored-By: Kimi Code <noreply@moonshot.ai>
Integration note (shipped engine 8e711f969): the tick-2102 checkpoint baseline is
unchanged and passes on the shipped engine (325 intercepts / 2011 hits). The final
stats baseline was re-measured on the shipped engine with #146 integrated (one
knowledge snapshot per Smart order changes the two late raids): 414 / 2463, world
8885 sections / 420671 rays / 3442845 cells. The asserted fixture SHA in
tools/airdef.py was updated to match. python3 tools/airdef.py test-budgets passes
all 283 steps with zero fuel failures (tick max 184608537 / 300000000).
The replay's sounds, the raid map's counts and the struck objects now read
the recording's event and scene journals by time instead of every pass over
the whole journal: partition points over the journals (with a stable time
index built at close only when a journal is out of order), the map's kill
and hit prefix indices, each object's first hit, and marker/time-line paths
that stop at the map's shape cap. Blasts, smoke, debris and the fire replay
read bounded windows back from the moment.
The sets, order and names stay exactly as they were: tests compare every
reader against the full journal filter, including tied times, out-of-order
journals and arbitrary forward and back seeks. The replay_bench example
measures a 10-minute raid with nearly full journals (playback, reverse seek,
pause, MP4); its result is docs/measurements/issue-150-replay-ranges.json.
Co-Authored-By: Kimi Code <noreply@moonshot.ai>
Preserve the adapter facade and move adapter-only checks out of domain tests. Late tracks do not reveal an unseen launch origin or its timestamp.
Co-Authored-By: Codex GPT-6.1 Terra <noreply@openai.com>
The mod (airdef-mod/), its generated models and sounds, the fork's patches
over upstream Horizon (horizon-patches/, HORIZON_COMMIT), a cross-platform
build/install/run script (tools/airdef.py), CI that builds and releases on
every push (.gitea/workflows/build.yml) and a setup guide (docs/INSTALL.md).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>