AirDef v0.3.x: enemy intelligence, cold launch, MP4 and stability #131

Merged

chexit merged 106 commits from kimi-work into main 2026-11-06 15:41:20 +00:00

Conversation 0 Commits 106 Files Changed 367

+209589 -77976

chexit commented 2026-11-06 15:40:58 +00:00

Owner

Copy Link

Copy Source

🤖 Agent: Kimi Code PR.

AirDef v0.3.x: kimi-work → main

Ветка содержит 107 коммитов, включая завершённый #127.

• честная EnemyPicture и structured intent;
• durable air state с save/restore;
• холодный пуск и плавная тяга;
• физическая логистика RM48U;
• реальный MP4 и акустика;
• camera-ready API 30;
• нормали динамических моделей;
• единый числовой каталог;
• исправления fuel traps, коллизий, навигации и сохранений.

Проверки на итоговом e7934a1eb:

• core release 232 + 8 сценариев (8 ignored);
• adapter 68 + 1 boundary + 5 сценариев;
• настоящий WASM 30 шагов;
• Metal/offscreen и реальные MP4/cold-launch приёмки.

Стабильный v0.3.0 уже опубликован с этим коммитом. Полный changelog будет приложен к v0.4.0-rc1 после merge.

🤖 Agent: Kimi Code PR. # AirDef v0.3.x: kimi-work → main Ветка содержит 107 коммитов, включая завершённый #127. - честная EnemyPicture и structured intent; - durable air state с save/restore; - холодный пуск и плавная тяга; - физическая логистика RM48U; - реальный MP4 и акустика; - camera-ready API 30; - нормали динамических моделей; - единый числовой каталог; - исправления fuel traps, коллизий, навигации и сохранений. Проверки на итоговом `e7934a1eb`: - core release 232 + 8 сценариев (8 ignored); - adapter 68 + 1 boundary + 5 сценариев; - настоящий WASM 30 шагов; - Metal/offscreen и реальные MP4/cold-launch приёмки. Стабильный `v0.3.0` уже опубликован с этим коммитом. Полный changelog будет приложен к `v0.4.0-rc1` после merge.

chexit added 106 commits 2026-11-06 15:40:58 +00:00

Counter-strikes collide, persist and record their flights (#106 #108 #109 #113) ... 31d967b036

Co-Authored-By: Kimi <noreply@moonshot.ai>

Separate live and replay worlds, refresh acoustic lifecycle (#105 #110 #111 #112) ... cd3c4ed76d

Co-Authored-By: Kimi <noreply@moonshot.ai>

Bound counter-strike steps and check terminal collisions (#106 #117) 5860c5009f

Keep radar-controlled gun accuracy independent of darkness 733dc07863

Match counter-strike launch audio and live smoke to replay (#109) afe320786d

Pin the standalone Horizon fork as a submodule (#104) ... 4761ae7d70

Replace patch-stack reconstruction with safe pinned initialization and legacy checkout migration; use an engine-local packer and write artifact identities.

Co-Authored-By: Codex <noreply@openai.com>

Build canonical simulation without Horizon SDK and remove hidden launch fixes (#87 #107) ... 5f07027faa

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>

Check chassis footprint and bound pending route exploration (#114) ... e7c00267b1

Reject narrow corridors, recheck motion clearance, and wait for footprint data before flooding the shared query budget.

Co-Authored-By: Codex GPT-6 Luna <noreply@openai.com>

Separate authored assets and install generated output transactionally (#92) ... 657d8f16c6

Co-Authored-By: Codex <noreply@openai.com>

Share stable content IDs across raids, inventory and item dispatch (#91) ... 5ad6ea8ad9

Co-Authored-By: Codex <noreply@openai.com>

Use the standalone Horizon fork merged with v0.2.97 (#72) ... 63972995a1

Client library: 1227 passed, 42 ignored. SDK/packer/runtime: 59 passed. Built macOS arm64 client with mods and packaged actual AirDef WASM. Native HDR and Windows/Linux runtime smoke remain unverified.

Co-Authored-By: Codex <noreply@openai.com>

Record measured scene transitions and isolate combat effects from recorder (#88) ... f28e68db62

Capture actual missile launch/ignition, track transitions, fire state, SAM health and components. Keep legacy fallback and bound scene transitions to 65536. Renderers still use incremental adapters; shared SceneTimeline remains follow-up work.

Co-Authored-By: Codex <noreply@openai.com>

Make export own its playback and centralize session exits (#89) ... 814f8c7e83

Co-Authored-By: Codex <noreply@openai.com>

Remove seed-only defenders and reject unsupported player-launched strikes (#118) ... 29b047abaf

No compatible coordinate-strike loadout is implemented yet. Preserve flight and collision mechanics through explicit test fixtures without allowing generic stock or player position to create a production missile. Physical carriers, typed ammunition and logistics remain to implement.

Co-Authored-By: Codex <noreply@openai.com>

Apply route node limit before waiting for geometry (#114) ... efb2f20e58

Co-Authored-By: Codex <noreply@openai.com>

Explain unavailable coordinate-strike loadouts in map and documentation (#118) ... ad96018c0a

Co-Authored-By: Codex <noreply@openai.com>

Validate the actual hmod in the pinned host sandbox (#102) ... dedb0213c7

Keep runtime compilation in an opt-in CI tier; run asset consistency on regular builds. Sandbox checks do not substitute for GPU, capture or maximum-scenario budgets.

Co-Authored-By: Codex <noreply@openai.com>

Install the pinned raster generator dependency in CI (#92) ... 4a3500fdc0

Co-Authored-By: Codex <noreply@openai.com>

Add three art pilots and derive chassis envelopes from final models (#115 #114) ... 5620347ffe

Keep authored JSON separate from generated output. Export rotated model bounds for SDK-free navigation and check grazing voxel corners. Include unretouched in-game before/after captures and explicit art/performance limits; pilots are an intermediate pass, not completion of the full asset set.

Co-Authored-By: Codex <noreply@openai.com>

Record acoustic fixture results and ship source notices with game bundles (#96 #102) ... ac866d64a0

Co-Authored-By: Codex <noreply@openai.com>

Clarify gun burst counters and record the verified realism follow-up (#91) ... c4b72da3ff

Co-Authored-By: Codex <noreply@openai.com>

Refine ground vehicle silhouettes and publish in-game model checks (#115) ... e84a5e9fa7

Preserve launcher grids and authored materials; fix the Buk radar intersection and regenerate geometry bounds. Register the separate RM48U game visual for the upcoming carrier path.

Co-Authored-By: Codex <noreply@openai.com>

Launch typed ground strikes from carriers and isolate presentation state (#118 #88 #89) ... d4adbb1e47

Share read-only scene data for smoke and displayed blasts; preserve cold ejection and flight-relative recording samples. Keep finite typed depot inventory, expose per-world smoke readiness through the pinned API26 engine, and invalidate presentation resources on world changes.

Validation: core suite 156 unit tests plus 4 scenarios and the new targeted recording regression; adapter 50 unit tests, boundary check and 4 scenarios; real WASM contract 16 steps; asset pipeline and bounds checks; macOS Metal client build and HD frame.

Co-Authored-By: Codex <noreply@openai.com>

feat: add shared radar batteries and animated cold launch ... 966b52f9fc

Separate search and engagement roles, support launcher-only SAMs, animate individual tube lids and delay ground strike spending until ejection. Preserve battery configuration and launch poses in saves and replay.

Co-authored-by: Codex <codex@openai.com>

docs: document cold launch visual checks and battery validation ... 2689d933e7

Co-authored-by: Codex <codex@openai.com>

docs: establish current project status and engineering handoff ... a7d400ea7e

Co-authored-by: Codex <codex@openai.com>

feat: attenuate indirect blast damage behind known cover ... c96676f3e5

Use a bounded read-only pre-destruction occupancy sample; preserve conservative damage for unresolved geometry and do not defer or repeat damage on replies.

Co-authored-by: Codex <codex@openai.com>

Deliver typed strike rounds by transport loader ... c775f31544

Co-authored-by: Codex <codex@openai.com>

Exercise strike delivery across movement and save restore ... 952a10f360

Co-authored-by: Codex <codex@openai.com>

Add persisted radar emission switch ... 26b258f00f

Co-authored-by: Codex <codex@openai.com>

Observe emitting radars and expose emission control ... 0df225a2de

Co-authored-by: Codex <codex@openai.com>

Test radar silence and replay seeking ... 88f940546b

Co-authored-by: Codex <codex@openai.com>

Update network risk fixture for observed radar ... 9e1e0f5543

Co-authored-by: Codex <codex@openai.com>

test: preserve delivery requests alongside radar emission saves ... b377a5d8d2

Co-authored-by: Codex <codex@openai.com>

Prototype finite interceptor motor and coast ... 143d9b2858

Co-authored-by: Codex <codex@openai.com>

Use swept meeting point for interceptor impact ... 932a8b7761

Co-authored-by: Codex <codex@openai.com>

Cover lead for crossing target ... 6b6293f353

Co-authored-by: Codex <codex@openai.com>

Record energy loss and exercise meeting geometry ... f3985d5363

Co-authored-by: Codex <codex@openai.com>

Use interceptor energy for residual fuse chance ... 44a023006d

Co-authored-by: Codex <codex@openai.com>

Release interceptor engine source at burnout ... e3ca3fbd8c

Co-authored-by: Codex <codex@openai.com>

Match impact speed to swept segment ... e38ca0d9ab

Co-authored-by: Codex <codex@openai.com>

Target SEAD strikes at observed radar contacts ... ce76f20074

Co-authored-by: Codex <codex@openai.com>

Apply coast drag after interceptor burnout ... a7b8cb980a

Co-authored-by: Codex <codex@openai.com>

test: exercise radar silence through the real WASM boundary ... 6e2d661b39

Co-authored-by: Codex <codex@openai.com>

docs: describe implemented realism mechanics and verified handoff ... e70d7a667b

Record actual save field positions, motor phases, finite typed delivery, last-known radar contacts and blast-cover policy. Include per-seed baseline measurements and distinguish native/WASM checks from pending GUI acceptance.

Co-authored-by: Codex <codex@openai.com>

fix: synchronize the engine submodule URL before updating ... d3378b37a2

Reproduce stale upstream configuration with real local Git repositories, including the already-matching pin fast path.

Co-authored-by: Codex <codex@openai.com>

Return loaded RM48U to depot by truck ... bb931ab95c

Co-authored-by: Codex <codex@openai.com>

Preserve pending delivery and command completion behavior ... e9fbaba1d6

Co-authored-by: Codex <codex@openai.com>

Test interrupted return pickup ... b0085cb3e8

Co-authored-by: Codex <codex@openai.com>

Add opt-in heavy WASM budget tier ... 4dddea2e8c

Co-authored-by: Codex <codex@openai.com>

feat: consume scoped engine capabilities and preserve safe fallbacks ... 910f02ca92

Pin API27, diagnose prepared states, gate capture ownership and keep far-sound fallback until acoustics is prepared. Retain engine changes in build provenance and cancel invalid return reservations after cell loss.

Co-authored-by: Codex <codex@openai.com>

Test WASM budget report failure paths ... 8d5d0d1dd7

Co-authored-by: Codex <codex@openai.com>

build: reuse the pinned engine target cache for its packer ... aab3e784b8

Co-authored-by: Codex <codex@openai.com>

docs: record API27 readiness and reverse logistics verification ... 19c53fda4c

Document capability milestones, budget limits versus measurements, real-game no-audio observations, reverse pickup reservation and the Windows stale-URL fix.

Co-authored-by: Codex <codex@openai.com>

Slightly densify missile smoke trails ... 692ae77af7

Co-authored-by: Codex <codex@openai.com>

Verify sequential raid requests in budget scenario a41a4d17cf

Exercise overlapping menu raids on answered terrain ... 296a64ffaa

Co-authored-by: Codex <codex@openai.com>

Exercise overlapping Oreshnik splits and recording ... bd091e60df

Co-authored-by: Codex <codex@openai.com>

test: pin real render-query fixtures and correct raid coverage claims ... 8f5603847e

Archive the original budget report as insufficient proof of overlapping raids. Pin callback/fuel diagnostics and an opt-in flat render world that services actual guest queries.

Co-authored-by: Codex <codex@openai.com>

Add overlapping raids budget scenario with flat terrain ... 326817db9a

Co-authored-by: Codex <codex@openai.com>

Cover HD grid during overlapping raids ... 3afebae6bd

Co-authored-by: Codex <codex@openai.com>

Run flat terrain scenario in budget report ... bf8551e1a8

Co-authored-by: Codex <codex@openai.com>

test: freeze the exact budget fixture used by the runtime ... 293236490b

Derive synthetic terrain metadata from the fixture and copy the same bytes that were hashed before building.

Co-authored-by: Codex <codex@openai.com>

docs: record verified overlap stress and unresolved Windows report ... 10f24b5df8

Keep the corrected historical coverage claim, archive the real flat-world WASM run, explain trap diagnostics and the small HD trail density change.

Co-authored-by: Codex <codex@openai.com>

Bound height cache invalidation per explosion ... 1f28f8361f

Co-authored-by: Codex <codex@openai.com>

Exercise two maximum menu raids with terrain replies ... cc48302b36

Co-authored-by: Codex <codex@openai.com>

fix: explain empty strike stock and ground attack prerequisites ... cbd6067e8f

Show typed depot cargo separately, identify an empty nearby depot, and document loading, reconnaissance, two ID namespaces and reverse pickup.

Co-authored-by: Codex <codex@openai.com>

build: pin optional per-callback WASM fuel profiling ... 3b470ddc8a

The opt-in test CLI reports measured guest fuel separately from host and GPU costs; runtime limits remain unchanged.

Co-authored-by: Codex <codex@openai.com>

test: verify empty nearby depot feedback in WASM ... ab737e7390

Co-authored-by: Codex <codex@openai.com>

docs: archive the reproduced fuel failure and bounded cache fix ... d410e2c92d

Preserve the diagnostic trigger, scenario, before/after logs and scope of equivalent counters. Update ground strike guidance, Windows acceptance status and profiler semantics.

Co-authored-by: Codex <codex@openai.com>

test: record measured callback fuel in budget reports ... 63aefc7621

Co-Authored-By: Codex <noreply@openai.com>

Separate battery status from player-facing text ... 375fdf2d80

Co-Authored-By: Codex <noreply@openai.com>

Move world cache report to presentation adapter ... cb73cb7ccc

Co-Authored-By: Codex <noreply@openai.com>

Share aircraft and item catalog with asset generation ... eea1b3692e

Co-Authored-By: Codex <noreply@openai.com>

Represent damage diagnostics as typed reasons ... 0c870c10d5

Co-Authored-By: Codex <noreply@openai.com>

Share sound identifiers and metadata with resource generation ... 1553976484

Co-Authored-By: Codex <noreply@openai.com>

Use catalog sound identifiers throughout runtime ... daa9ed7cbc

Co-Authored-By: Codex <noreply@openai.com>

build: pin point-light handshake and mass acoustics fixture ... 4c7c887917

Co-Authored-By: Codex <noreply@openai.com>

Refine Lancet silhouette with swept X wings ... 53669887dd

Co-Authored-By: Codex <noreply@openai.com>

Refine cruise silhouette and document model comparisons ... cfae0c1253

Co-Authored-By: Codex <noreply@openai.com>

build: pin source-manager processing handshake ... d45d59df9f

Co-Authored-By: Codex <noreply@openai.com>

Verify aircraft models as lit mod instances ... 914f723d1f

Co-Authored-By: Codex <noreply@openai.com>

feat: expose light and sound processing diagnostics with isolated cameras ... c1a595b773

Co-Authored-By: Codex <noreply@openai.com>

docs: hand off catalog, model, API29 and acoustics continuation ... 56339b076e

Co-Authored-By: Codex <noreply@openai.com>

docs: archive clean API29 WASM fuel acceptance ... 632061d2ad

Co-Authored-By: Codex <noreply@openai.com>

End the show when its world closes and verify the MP4 lifecycle (#89) ... 675967ce42

A frame hook ends an active film or export when the world is gone. The game
stops ticking at the title screen but keeps rendering, so an export used to
keep recording the title with its playback clock frozen (a sec=10 request
produced 3898 frames) and went on after re-entering the world. Session
cleanup runs once with WorldChange and cancels the capture.

Real short exports on a scratch home and world (pin 57f8b2853, API 29,
Metal): h264+AAC both 2.07 s with non-silent audio, reported frames equal
ffprobe nb_frames; cancel, SDK refusal, encoder failure and restart all
leave no capture running; 1920x1080 works. The engine still leaves
*.audio.raw and *.ffmpeg.log behind on an encoder error (game/film.rs).

Co-Authored-By: Kimi Code <noreply@moonshot.ai>

Fix dynamic model lighting and document GPU comparison (#123) ... 503e6e29af

Co-Authored-By: Kimi Code <noreply@moonshot.ai>

Pin the engine that frees a failed film take's files ... cec7257ea1

horizon 60cc7b11d (on top of 57f8b2853, API 29) removes a failed or
cancelled take's video, raw sound and log, carries the log's last lines
in the error, and only creates <name>.mp4 after a successful finish.

Co-Authored-By: Kimi Code <noreply@moonshot.ai>

docs: record the engine cleanup for failed film takes ... e6a7000440

Engine 60cc7b11d removes a failed or cancelled take's video, raw sound
and log, carries the log's last lines in the error, and only creates
<name>.mp4 after a successful finish. A real failing encoder on the
scratch world left no temporaries and kept the earlier film byte for
byte; successful audio and no-audio control films still verified.

Co-Authored-By: Kimi Code <noreply@moonshot.ai>

docs: record the real MP4 acoustics check (#96) ... abf3d76fdb

Pairs of the same replay exported with acoustics on and off on the
scratch world (no HORIZON_NO_AUDIO): acoustics and capture ownership
both ready. The open field has no reverb send by design, so it shows
occlusion/air absorption only; the stone court's on-track is quieter
and darker, and its residual after a gain fit is low-passed and
stereo-decorrelated, i.e. the wet path. A clean reverb tail/RT60 in a
real MP4, echoes alone and listening remain open. No code changes.

Co-Authored-By: Kimi Code <noreply@moonshot.ai>

feat: generate simulation numeric profiles from catalog/specs.json ... ead87343d2

catalog/specs.json is now the single copy of the numeric rows for
DroneSpec, MissileSpec and SamSpec: speed, guidance, warheads, models'
parts, RCS, seekers, launch and motor sounds, mount drives, gravity,
the Oreshnik split height and logistics limits, plus the named part
sets. tools/gen_catalog.py generates airdef-mod/src/sim/specs_generated.rs
(included by mod.rs, so the mod and airdef-core compile the same rows)
and unit_specs_generated.rs (included by units.rs). The hand-written
spec matches are gone; DroneKind::spec, MissileKind::spec and
SamKind::spec read the generated constants.

load_specs validates the schema, sound references, kind coverage against
content.json, named-part references and unused rows. gen_catalog.py
--check already runs in the CI generated-assets step, so a JSON/Rust
drift fails the build.

Every value was compared with the literals at 632061d field by field.
The only mismatch was the P1-SUN motor voice pitch in JSON (1.6 instead
of the actual 1.7, the flame == 0 branch in voices.rs); the JSON was
corrected and behaviour is unchanged. Save keys, raid order, RNG and
gameplay traces are untouched.

Verified: core release 194 passed + 8 scenarios (7 ignored), adapter
64 unit + 1 boundary + 5 scenarios, WASM contract 27 steps, catalog and
model generators fresh, asset/sound/model-bound/report tests pass.

fix: keep the P1-SUN motor voice at its played 1.6 pitch ... 0937ac9e05

The old engine_voice returned early for flame == 0 with
(DRONE_LANCET, 0.8, 1.6), so the later `P1sun => 1.7` match arm was
unreachable. The catalog migration mistook that arm for the played value
and stored 1.7, which changed the interceptor drone's flight sound.
specs.json is back to 1.6 and specs_generated.rs is regenerated.

Adds missile_engine_voices_keep_their_played_values, pinning P1-SUN to
(DRONE_LANCET, 0.8, 1.6) and M48N6 to (MISSILE_FLIGHT, 1.0, 0.88).

The continuation and handoff text now describe the early return instead
of the dead arm, and tools/airdef_assets/catalog.py gets its final
newline back.

Verified: gen_catalog --check and test_gen_assets, core release
195 passed + 8 scenarios (7 ignored), adapter 64 unit + 1 boundary +
5 scenarios, WASM contract 27 steps.

refactor: validate specs without a per-kind name list ... 325119b726

The armed/support check in load_specs named the ten armed kinds, so a new
unit type would still have required a code edit and repeated the coupling
#91 is removing. Drop it: optional missile/gun rows are still validated
generically, and the existing kind-coverage check against content.json
already ties specs to the catalog.

validate_specs now takes the document, content identities and sound
events, and a test shows a hypothetical unit kind is accepted from a
specs row plus its content entry alone. No data or balance changes.

Verified: gen_catalog --check fresh, test_gen_assets 10 tests, core
release 195 passed + 8 scenarios (7 ignored), adapter 64 unit +
1 boundary + 5 scenarios, WASM contract 27 steps.

Measure the #120 balance grid across batteries, ranges and target classes ... 46d2274c8d

Wider same-seed sampling of the finite-burn/coast change: baseline 2689d93
(pre-#120) against the current tree, 6 variants x 8 seeds of a 46-drone raid
(batt10/20/50, near200, far1500, hills20). Harness-only: Result carries the
tally's fuse/expired/orphaned/energy_lost counts and a new ignored
sim::balance::issue_120_grid test; no simulation parameters changed.

Findings: kills are equal or up and leaks equal or down in every variant;
fuse misses drop (far1500 70 -> 38 over 8 seeds); hills terrain losses fall
(scrubbed 6 -> 2). MotorEnergyLost never fires in the 48 scenarios and
expired stays <= 1: coast ends before drag reaches the 25% guidance
threshold. Leaks stay concentrated in the ballistic/fast classes
(Iskander/Kinzhal/Kh22/Zircon). No confirmed defect, so no tuning.

Full airdef-core suite: 193 + 8 passed, 0 failed (baseline side 169 + 4).

Co-Authored-By: Kimi Code <noreply@moonshot.cn>

Report camera readiness in /airdef capabilities ... 9217f9a5cc

Pin the engine at 6a53a626c (API 30) and show render.camera-status: the
calling run's set-views cameras, whether the last noted frame was a world
frame, the request's world generation, each camera's reason and the run's
own main-view selection. As the other lines, this is a host milestone:
availability, request, preparation and why, not a GPU frame or a visible
picture. A unit test pins the line: readiness stays per camera and apart
from the run's main-view selection.

docs/ENGINE.md, the 4 November continuation and the status table now say
what prepared means (a picture encoded into the camera's target, or a
world frame drawn from it as this run's screen view, only for the run
whose selection the screen used), the per-run/per-world resets, and what
remains: GPU acceptance.

Verified: python3 tools/airdef.py check (gitlink, packer, mod needs 30,
fork 30, game 30); test-wasm 27 steps; airdef-mod 65 unit, 1 boundary and
5 scenarios; python3 -m unittest discover -s tools 28 tests.

Co-Authored-By: Kimi Code <noreply@moonshot.cn>

Record the Metal/offscreen camera picture acceptance ... 61aaa0bf35

The final engine 6a53a626c with the API30 AirDef build was run in the
real game (macOS, Apple M5, Metal, --offscreen, a clean HORIZON_HOME and
copied test worlds), not only in the sandbox: the monitor and the film's
main view report ready with the picture actually drawn (screenshots show
the panel and picture area, not a registered target), an empty set-views
drops the request, a world change bumps the generation and clears it, and
AirDef's next submission prepares the camera again in the new world.

Fixes nothing: no defect showed. It also records what the run does not
prove (a human visual check, Windows/other GPUs, two runs with the same
local id on the GPU, a mod reload on the GPU), the per-tick
set-views/set-main-view ordering that can honestly read awaiting-frame
between tick and note (not flicker), and that a title trip back into the
same world keeps the request because the generation is per world.

Co-Authored-By: Kimi Code <noreply@moonshot.cn>

Fix the UI-event fuel trap on a second large raid order ... d45629ae29

The Windows log for #122 showed the mod stopping in the UI event
(fuel budget 1e9, remaining 0) with known_units <- order_raid <-
launch_wave <- ui_select: order_raid recomputed the planner snapshot
known_units() for every drone, and the snapshot itself rescanned the
whole force and the dedup list per intel entry. A second big Smart
order cost drones x intel-log x force-size inside one event.

Reproduced in actual WASM with measured per-callback fuel through the
exact ui_select(BTN_LAUNCH) handler (diagnostic guest, trigger.patch):
before, a 111-drone second order at revealed=13172/known=144 exhausted
exactly 1e9 and stopped the mod (an 11-drone order at the same state:
247805865); after, the same scenario passes with max command fuel
32946177/1e9, failures=0, and /stats at tick 2602 byte-identical.
A stacked single-point layout dies to one warhead (known=0, cheap
order), so the scenario deploys spread clusters with a moved player.

Fix: one known_units snapshot per order_raid passed to radar_strikes
and choose_target; known_units is a single O(log + force) set pass;
price_grid_on reuses its snapshot. Emitter/network targeting and
carrier choice semantics are unchanged (native equivalence test
against the former predicate; WASM checkpoint counters equal).
Limits unchanged; HD/recording untouched; wave size unrestricted.

Committed regressions: native snapshot-equivalence and
second-smart-order tests; the heavy WASM fixture now orders two Smart
raids through the wave screen's launch function (airdef preset +
airdef raid) with EW and a combat intel log, four accepted orders
asserted; the light contract covers preset and the empty-wave refusal.

Core release 195 + 8 scenarios; adapter 65 + 1 boundary + 5 scenarios;
light WASM 30 steps; heavy WASM 283 steps (tick max 182413686/300M,
command max 6939810/1e9, failures 0). Windows GUI acceptance remains
external and is not claimed.

Co-Authored-By: Kimi Code (Moonshot AI) <noreply@moonshot.cn>

Unblock supply trucks from an impossible RM48U return (#128) ... dc36d67eb7

step_supply sent every free truck into the return branch whenever any
S-400 had a pending ground_return, even when that return could not
proceed (the system moving, damaged, reloading or preparing, its round
already claimed by another truck, the route marked unreachable, or no
depot with room). The branch then found no target, cleared the job and
stopped the truck, so independent typed supply requests starved.

The return now keeps its priority only while it is executable: a
carrier holding a reserved round looks for a depot with room in reach,
an empty one for a system ready to hand a round over. Otherwise the
claim stays untouched and only real RM48U demand (a requesting system
with depot stock, or ground rounds aboard for one) pulls the truck
into the typed supply branch; without such demand it holds its watch
exactly as before. Redirecting a reserved round to a waiting request
clears return_cargo once the last one leaves the truck, and a stale
return_cargo with an empty hold no longer sends the truck to a depot
handover it cannot complete.

Regressions: three sim tests (moving claimant, pickup claimed by
another truck with damaged/save-restore phases, unreachable route) and
one full-drive lib test with a mid-flight state round trip; the rounds
are conserved in every phase and the actual return completes once the
claimant is back. All three sim tests fail on the old code.

Checks: core release 200 passed/8 ignored + 8 scenarios; adapter
67 unit + 1 boundary + 5 scenarios; real WASM test-wasm 30 steps.

Keep unfinished retarget routes in a bounded job queue (#127) ... 6f7b041c8b

A mass retarget used to clear every selected drone's route before the planner's per-tick work ran out: the rest flew straight for ever. Route jobs now carry the drone id, new aim, target unit, knowledge version and the intel snapshot, stay in a FIFO across ticks and are drained under the same WORK_PER_TICK. An old safe route is kept until its replacement is ready; a cancelled job falls back to a straight run. Jobs are replaced in place per drone, cancelled when the drone or unit is gone, and retarget routes reuse the original plan's known relief. An in-flight drone no longer turns to a unit behind its turning circle. Core release tests, adapter tests and the real WASM contract pass.

fixup! Keep unfinished retarget routes in a bounded job queue (#127) ... a47812aadd

The relief snapshot was still global: a smart plan finishing while a retarget job waited could replace Sim::known_relief, so the pending route was planned on the newer map. RouteJob now carries Arc<KnownRelief> for its knowledge version; Sim::known_relief keeps the same Arc only to seed new jobs. retarget_relief reads the job's snapshot, and relief sampling, price grids and route caches are keyed by that version. The new regression makes a job wait, swaps the global relief for another grid with a wall, and checks the pending route and sample stay those of the original version; outside its grid is Unknown. Core release, adapter and WASM contract pass.

fixup! Keep unfinished retarget routes in a bounded job queue (#127) ... a592ece6e3

The planner caches were keyed by (kind, relief Arc pointer, start, aim): two jobs with the same relief but different known-units snapshots could reuse each other's price grid and route. Key relief sampling by its Arc pointer but key prices and routes by the whole knowledge version: adaptive tick plus the known-units and relief Arc pointers. Regression creates two same-start, same-aim jobs on one relief with different known snapshots and checks their routes differ, while a third job of one version still reuses the route cache. Core release, adapter and WASM contract pass.

Stage the cold launch and spool every interceptor's motor (#129) ... 1261c30724

The interceptor's launch is one sequence: the cap opens, the round is
thrown out unlit and slows under linear gas drag (`cold` ticks), the motor
lights where it has reached, it turns with a growing rate while thrust
spools up (`boost` ticks), and full guidance starts only at `cold + boost`.
A rail launch lights at once but spools over the same `boost` ticks; the
electric P1-SUN has no rocket spool or plume.

S-400/500 now hold the unlit ejection for 20/24 ticks (1.00/1.20 s at
20 Hz); IRIS-T/Tor keep shorter 8-tick throws. Ignition, its sound, flame
and recorded MotorIgnition event all use the missile's current position.
The RM48U strike follows the same 20-tick choreography, counts the throw
in its flight time and starts its recorded smoke at ignition.

Maximum speed, turn, accel, pk and every collision rule are unchanged.

Co-Authored-By: Kimi Code <noreply@kimi.com>

Record the #129 balance and the cold-launch capture ... 56093b3a55

The stage contract and profiles are in 4b013fb. This commit adds the
measured balance (the #120 grid on identical seeds and the 12-seed raid),
the replay/export video with four stills, and updates the user and handoff
documentation. The visual files are provided for human review; the agent
that captured them has no image input and checked only the encoded
parameters, shot boundaries and the first large plume.

Co-Authored-By: Kimi Code <noreply@kimi.com>

Normalize #129 measurements and pair the cold-launch capture ... 0b645d77e9

Write both measurement CSVs with LF instead of CRLF so the range no longer
fails `git diff --check` on trailing whitespace; the parsed data is unchanged.

Add a matched before/after capture: one copied world, scenario and seed, the
same client/director and the same export command. The baseline hmod is built
from dc36d67 and the final one from the #129 code. Both launch shots start at
frame 94; the first centre illumination is frame 101 (0.233 s) before and
frame 121 (0.900 s) after, against the 0.25/1.00 s cold rules. Raw probe,
hashes and the measurement method are in issue-129-pair.json. The two MP4s
in docs are CRF26 storage copies; the CRF16 originals stay in the scratch
homes.

These are replay exports, not live footage. The capturing agent still has no
image input, so composition is left for human review; the frames before the
launch are not pixel-identical because these are two live sessions.

Co-Authored-By: Kimi Code <noreply@kimi.com>

Give the enemy a last-observation picture and observed-capability pricing (#127) 8fc10c07a1

Give the enemy a structured intent and a durable route queue (#127) ... e7934a1ebb

Stage 2 of #127. A smart drone now carries why it is aimed where it is
(Intent: plan, sead, react, replace) apart from the aim bookkeeping
(unit, since, switches, confidence). Assignments are throttled per
adaptive tick and per contact, a fresh disclosure replaces an aim only
after a hold, within a switch cap and when the change is worth a new
route, and a killed aim is replaced as a separate, lower-priority
decision. The queue is bounded and taken by priority (plan > sead >
react > replace); unknown land is no longer free in a replanned route.

The autosave now carries the air state: the drones in flight, the launch
queue, every pending job with its id, aim, unit, version, priority,
intent and relief version, the contacts the jobs were chosen from and
the relief snapshots they plan over. The format is a versioned `air 1`
section; older saves read as before, scenarios do not carry the sky,
stale, ghost and duplicate jobs are cancelled on load, and the section is
bounded (512 drones, 512 route points, 4096 contacts, 8 reliefs, 900 KB).
A periodic save waits while a raid is only being planned.

enemy_picture() now explains targets and pending jobs (aims, aimed_by,
pending_jobs, reason, work_per_tick) in English, and intel_bench records
the queue and intent evidence next to completion, losses and failures.

chexit merged commit c525feb465 into main 2026-11-06 15:41:20 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

area:architecture

Границы модулей, контракты, состояние сессии и развитие общей архитектуры

area:audio

Звуки, громкость, задержка распространения и аудиоассеты.

area:logistics

Боезапас, склады, ТЗМ, обслуживание и заявки снабжения.

area:persistence

Сохранение, загрузка, сценарии и изоляция состояния между мирами.

area:rendering

Шейдеры, GPU-ресурсы, освещение, геометрия, эффекты и рендер API.

area:simulation

Полёт, обнаружение, планирование налётов, наведение, повреждения и игровая логика.

area:tooling

Сборка, CI, тесты, инструменты разработки и инструкции установки.

area:ui

HUD, радары, мониторы, меню, текст и интерфейс реплеев.

needs:profiling

До существенной оптимизации измерить стоимость в игре/WASM/GPU; native-оценки и чтение кода не заменяют профиль Mac.

priority:P1

Первый проход: поломки боя/сохранения и основной запрос по FPS. Гипотезы производительности сначала профилировать.

priority:P2

Следующий проход: обычные баги, безопасные улучшения и вспомогательные оптимизации.

priority:P3

Позже: косметика, новые удобства, латентные дефекты и дорогие оптимизации без подтверждённой необходимости.

type:bug

Подтверждённый дефект поведения или обработки состояния; способ проверки указан в issue.

type:docs

Документация, инструкции и соответствие описания текущему коду.

type:enhancement

Новое поведение, баланс или улучшение удобства.

type:performance

Оптимизация затрат CPU/GPU, памяти, I/O или передачи данных; не обещает прирост без замера.

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

chexit

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: chexit/airdef#131