Integrate radio-delivered convoy cover and conservative squad ammunition reports
This commit is contained in:
@@ -10,7 +10,29 @@ The user has also authorized **RHS, WCS and BMP** dependencies. Keep external as
|
||||
|
||||
## Coverage
|
||||
|
||||
The rows below preserve the initial audit baseline. Subsequent convoy implementation is tracked in [convoy-migration.md](convoy-migration.md) and the inventory's `post_audit_updates`: it is now a partial implementation with native driving still unproven.
|
||||
The rows and counts below preserve the initial audit baseline at `e7b4141`;
|
||||
current follow-ups are recorded here and in the inventory's `post_audit_updates`.
|
||||
They do not recalculate that historical inventory or imply complete feature parity.
|
||||
|
||||
The [convoy follow-up](convoy-migration.md) now has native driving evidence:
|
||||
[02:50:35](evidence/native-2026-09-20-025035-convoy-driving/report.json) completes
|
||||
181 assertions, with all six original vehicles moving at least 20 m and the lead
|
||||
over 100 m. It preserves nineteen exact seat occupants, finite truck cargo and
|
||||
one canonical manual dispatch. Automatic startup counts, combat/dismount/reboarding,
|
||||
unloading and long-route reliability remain unfinished.
|
||||
|
||||
[Delivered casualty reconciliation](ai-migration-progress.md#delivered-casualty-reconciliation-follow-up)
|
||||
now unions body and status reports by immutable initial formation slot. The
|
||||
[03:05:33 native run](evidence/native-2026-09-20-030533-body-radio-casualties/report.json)
|
||||
completes 45 assertions: actual corpse LOS, no HQ loss before radio delivery,
|
||||
and overlapping squad status without double-counting. This was one arranged
|
||||
visibility case. Deleted-corpse transit, complete wiped formations and a transfer
|
||||
before death have actual-method regression coverage rather than native proof.
|
||||
|
||||
Both native runs have zero script/runtime failures but retain four external
|
||||
localization errors, so strict native qualification still fails. Neither provides
|
||||
multiplayer, ordinary full-mission or FPS evidence. Earlier packaged playtests
|
||||
remain bound to their older source.
|
||||
|
||||
Status means **implementation presence against the described capability**, not native or multiplayer qualification. Implemented rows can still need real gameplay validation. Partial rows must not be presented as full migration. The categories are not equally weighted, so their counts cannot support a completion percentage.
|
||||
|
||||
@@ -489,7 +511,7 @@ Local manifests and PAKs for all six authorized external addons are installed un
|
||||
6. **Remaining owned behavior:** random prison/start variants, skill/equipment policies, automatic outfits and optional autonomous escape mode. Preserve requested settings and command semantics as each subsystem becomes usable.
|
||||
7. **Qualification:** source checks then hidden/muted exact-input native runs; finally ordinary human escape, multiple real clients, overlapping tasks/capture/losses/restarts, and matched-workload FPS measurements. Do not call old mod compile logs or source-policy tests multiplayer proof.
|
||||
|
||||
**Bounded next production slice:** migrate `SniperOptics` as a small AI equipment service for newly registered physical soldiers. Preserve compatible mounted optics, validate native mount/ownership callbacks, retain its bounded startup schedule and never retry an accepted unknown operation. Use direct authorized or verified vanilla scope resources; no original global attachment-base override. This is independent of the belief/planner work and can be tested without changing force counts. An even smaller companion change is the configurable native skill floor; neither should be mistaken for completion of ground/air logistics.
|
||||
**Bounded next production slice:** migrate `SniperOptics` as a small AI equipment service for newly registered physical soldiers. Preserve compatible mounted optics, validate native mount/ownership callbacks, retain its bounded startup schedule and never retry an accepted unknown operation. Use direct authorized or verified vanilla scope resources; no original global attachment-base override. This is independent of the belief/planner work and can be tested without changing force counts. The owned Expert skill floor was fixed rather than configurable; the successor now implements that minimum and finite Stinger selection. Convoy-gunner CYLON specialization remains separate. These equipment policies do not establish completion of ground/air logistics.
|
||||
|
||||
## Native evidence that exists today
|
||||
|
||||
|
||||
Reference in New Issue
Block a user