Capture current mission, AI, map and administration development
Include the current addon, terrain integrations, tools, regression tests and recorded development evidence.
This commit is contained in:
@@ -47,3 +47,9 @@ Validation: `tests/test_native_package_external.py` adds 17 offline packaging ca
|
||||
A read-only [resource-owner inventory](evidence/resource-owners-2026-09-30.json) binds the native parser errors to exact decompressed payload hashes and field offsets. The six rejected `Parent` fields are in vanilla BRDM2/BTR70 base prefabs, and `SlidingTrackMaterial` is in the vanilla M151A2 prefab, all in `ArmaReforger/data007.pak`. The two rejected landing-velocity fields are in Parachute Framework's `DefaultPlayerController.et` override. The other four errors are the previously recorded RHS/WCS localization references. Successor prefabs declare none of these rejected fields.
|
||||
|
||||
This establishes resource ownership, not the reason for the engine/resource incompatibility. Installed assets were not changed and strict native qualification still retains all thirteen errors. They must not be relabelled as a clean build or suppressed to qualify a release.
|
||||
|
||||
## Installed dependency review (13 October 2026)
|
||||
|
||||
The native preflight correctly refused a changed RHS project manifest. The installed Workshop versions had advanced: RHS Status Quo is now 0.16.5237, both RHS content packs are 0.16.5236, and the three WCS dependencies are 8.3.0. Parachute Framework remains 1.2.0. The [read-only review](evidence/external-addons-review-2026-10-13.json) verifies all seven original GUID/dependency closures, each project against its matching download size/SHA512 manifest, every approved resource path/GUID against its owning resource database, and the complete 80-file input inventory with SHA256 hashes. The review updates the policy's version labels and the single changed project hash; it adds no dependency or resource permission.
|
||||
|
||||
Installed addon files were not changed. These fingerprints establish the inspected inputs, not engine compatibility. Native runners still capture and verify their own input sets, and any resource/parser errors remain failures.
|
||||
|
||||
Reference in New Issue
Block a user