63ebd4ac6c
build / mod (push) Failing after 25s
order_raid read one picture and one list of recon marks for the whole order, but the Plan kept neither: plan_step priced each kind's first route on whatever picture_of_defences() held at the tick the budget reached that kind, so one raid could hold several versions of the map at once. A retarget job carried its version's contacts, yet price_grid_known aged them at self.tick, so two jobs of one version reached on different ticks could disagree about a contact's own sensor. KnowledgeSnapshot fixes the observation tick together with the contacts and marks read at it. The plan stores the order's snapshot and passes it explicitly to price_grid_on/price_grid_known; radar_strikes takes the order's marks instead of re-reading the recon memory. A retarget job shares its adaptive tick's snapshot and prices age at the snapshot's tick, never at the current one: current time still cancels a stale job (prune_air, job_live), separately from the version's own arithmetic, and an explicitly new retarget gets a new snapshot and may use a fresh report. The save rebuilds each version's snapshot from the contacts and the marks reported by it; the section format is unchanged. Nothing here reads the force: only published kinds and the contacts' own observations. SDK-free regressions: a Smart order of two kinds whose land answers starve while a visible contact is disclosed mid-wait keeps every kind's targets and routes on the order's snapshot (and differs from an order that knew the contact from the start); two jobs of one version worked out across the emission-belief boundary price the same world, a new version with a fresh report believes again, and a new version without one does not. Co-Authored-By: Kimi Code <noreply@moonshot.ai>