A station counted any own plot, however old, as a busy refine/fire
channel: a network heartbeat kept a stale contact's track fresh, so two
long-expired own fire plots still held both channels of the engagement
radar and a new contact nearby got only a coarse search plot, even with
the search radar running.
Channel occupancy now follows the station's own tracking.
Track::holds_channel requires an own (never relayed) refine/fire plot no
older than the station's track_ttl — three missed turns, the same value
that already bounds a contact without a fresh measurement. The planner
counts channels with the same Sam::own_channels_used(now) the panel,
monitor, map and "why" views read, so the UI and the allocation cannot
disagree about a stale channel. A stale channel frees for a new contact
without the network's survey track being removed; the hard per-profile
limit and the own measurement's provenance are unchanged, and a relayed
plot still never holds a channel.
Test: two contacts take both channels at the station, then leave its
reach while the search radar beside them keeps relaying them; a third
contact arrives nearby and gets its own fire channel (the test fails on
the old counting), and the relayed survey tracks of the old contacts
stay.
Co-Authored-By: Kimi Code <noreply@moonshot.ai>
The core recon flights and partial reports (9d8f3da57) had no player-facing
or diagnostic consumer: enemy_picture().recon/recon_sorties were read only by
core tests. This adds the missing layer on top, without touching the mechanics,
models or textures.
- Map: a tracked recon aircraft is a recognisable yellow hollow diamond with a
"разведчик" label, a role line in the selection panel and a filter legend; in
the sandbox truth mode it gets an amber marker of its own.
- Battle UI: the summary panel and the map show the flight's coarse phase
(разведка → донесение → завершение) only while the player's network actually
holds a recon aircraft — what the visible aircraft are doing, not what the
enemy learned. The truth mode adds a recon count line.
- Diagnostics and after-action review: /airdef recon and the menu page
"Разведка противника (разбор)" (from Main and Replays) list the enemy's marks
best-first with the reason each outranks the rest — priority = freshness×4 +
quality×3 + observed role (recon::priority_parts, cross-checked against
Mark::priority by a test) — plus the sortie phases and the drones aimed at a
mark. The omniscient enemy picture is never shown in the normal HUD; it is
explicit debug/review only.
recon_view reads only the current report types (EnemyPictureReport, ReconReport,
ReconSortieReport); the sim side only widens visibility and adds priority_parts
and the is_recon_drone/recon_status read helpers. Tests: recon_view, panel,
command tree, priority_parts cross-check. README and IMPLEMENTATION-STATUS updated.
Co-Authored-By: Kimi Code <noreply@moonshot.ai>
- a radar's fresh track reaches a post as a cue only: it points the head
but never enters the post's tracks, seen or own set
- a searching post's sector follows the turning head, not the fixed base
heading; switching contacts drops the old contact's picture
- dead and blinded posts spend no probe budget and never observe
- the icon alias is part of the generator, so the placeholder item uses
the radar texture without a duplicate PNG or a hand-written asset
- part diagnostics read "Опт" for a passive post's sensor
- tests: cue wiring, turning sector, contact switch, dead post, graphics
preset; generator alias
Cherry-picked from 3697a1764aec7a7bdc6311918453dd51e26ecabf onto the
#132/#133/#134 base: the cue-wiring test's track literal now carries the
shared class/source/product/quality contract instead of a DroneKind.
Co-Authored-By: Kimi Code <noreply@moonshot.ai>
- new Optical unit kind with its own catalog row and deploy item
- bounded one-contact line-of-sight checks against land and blocks
- day/night reach and hold timing; obstacle and unknown geometry block sight
- independent class observation with source, time and uncertainty, never DroneKind
- map/monitor/panel statuses and a line to the selected contact
- tests: day/night, wall/unknown, ageing, no kind leak, bounded work, passivity
Cherry-picked from 3ae21123964a9d3234bb2b3efc9ff926d64fc77d onto the
#132/#133/#134 base: the cue test's track literal now carries the shared
class/source/product/quality contract instead of a DroneKind.
Co-Authored-By: Kimi Code <noreply@moonshot.ai>
Give the separate radar three real profiles over SamKind::Radar and the
typed catalog variants:
- radar_search: coarse, slow, long-range search plots; no fire authority.
- radar_height: raised mast, local refinement of low plots; no fire authority.
- radar_track: local search, fast revisit, two refined/fire channels.
- radar_multi remains the compatible universal profile, not best everywhere.
Tracks now carry the measuring station, product (search/refine/fire), and
quality (separate from identification), and keep the station's own plot when a
fresher network relay replaces the published position. A relay never refreshes
the measurement or authorizes a launch. Ordinary launches need the battery's
own confirmed fire plot; launcher-only batteries use a supporting radar's own
plot, and the existing heavy far shot keeps its cue-radar exception.
Per-tick refinement/fire work is bounded by profile channels and local search
radius. Off, damage, network and save/replay behavior are preserved: new saves
write the stable profile ID, old role-only lines migrate, and embedded SAM
radars keep their own fire authority. The deploy menu, status lines, map,
monitor, radar scope and /airdef why explain the profile, source, age, quality,
channels and refusal reason.
Models/textures are untouched: all profiles reuse the existing radar
silhouette (the separate art zone remains for its owner).
Tests: profile single/pair/full scenarios and duplicate station, channels,
relay source/age/quality, Off/damage, save migration, replay, embedded and
Multifunction radars, catalog/generator checks, airdef-mod suites, core lib
(non-balance on one thread; the four active balance tests in release) and core
scenarios.
Co-Authored-By: Kimi Code <noreply@moonshot.ai>
A radar track is what the network measured, and it never carried the
target's own answers: the tactical Track loses `kind: DroneKind` and the
true velocity, and gains what the measurements say instead.
- Track now holds a ClassEst (unknown / probable / firm) plus an observed
velocity: none from the first blip, then the change of the measured
places between real measurements, smoothed so one noisy pair does not
flap the class. The classifier's bands sit between the game's speed
clusters (Class::of_speed); a new contrary measurement replaces the
hypothesis, an agreeing one firms it.
- The class estimate is separate from track confirmation (Track::ident):
a track can be confirmed with its type still unknown. The estimate
grows only on real measurements — a forecast and a relayed copy add
nothing — and it travels with the measurement it grew from, ageing
with the track and gone when the track drops.
- Roles, last chance, the reserve and the interceptor count read the
estimate, never the target's class. Explicit policy for the unknown:
an unidentified track stays a candidate under the general rules (and
the system with no roles holds its fire at everything); the map, the
monitor, the summary panel and /airdef why read the same estimate and
name the reason — «Трек подтверждён · тип не определён», «вероятно
крылатая ракета». The exact model stays in the sandbox's truth mode.
- A gun or a launcher lets go of a target that classified out of the
roles since it was taken; a first blip no longer rules a contact out
as a threat to guarded objects (it has no measured course yet).
Old saves and replays are untouched (tracks are derived, not persisted);
the simulation stays deterministic (the classifier is pure arithmetic on
the measurement noise). The doctrine/first-blip/last-chance tests gained
classified tracks where the contract provably changed; new tests cover
the classifier's steps, kind-independent estimates, first-blip blindness,
and relays and forecasts adding no confidence.
Co-Authored-By: Kimi Code <noreply@moonshot.ai>
- mini radar: class-shaped blips that merge into one with a count
- map: larger track markers and trails, hover card with distance, type,
status, target and interception
- explicit network vs sandbox truth: true drones, routes and aims drawn
apart from the network tracks, with their own trails
Co-Authored-By: Kimi Code <noreply@kimi.com>
Sam::status, Comps::describe/worst and Sam::parts_text formatted
player-facing Russian in the simulation. The adapter now owns that
text: battery_view::sam_status for the panel and map, why_view::parts
and why_view::worst for the monitor and the status line. The core keeps
the data and gains only the accessors the adapter needs
(preparing_cell, public cells/reload_time/magazine/gun facts).
Texts are unchanged; the adapter tests pin the existing strings.
Co-Authored-By: Kimi Code <noreply@moonshot.ai>
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>
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>
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>
Far raids over mountains with a 300-block known disc: crashes from 19 to 2 of 368 (mixed), 22 to about 9 (smart). Balance tests gain hilly land.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
#101: radars locate sites from launches, /airdef sites, /airdef strike; sites launch slower (15/25/50 ticks) so a strike can come in time. #48: M opens the map on the network's picture, with an editor. #47: guard, sector, reserve and salvo per system. #94: vehicles route round slopes and water and say when they cannot get through. #96: reverb, and a menu switch for the acoustics. #92: generated files are validated before the swap, repo map.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>