Native Workbench run 4 created both helicopter and BTR wrecks with active smoke. Each maximum crate held six scoped rifles, 48 matching magazines, one RPG-7, two rockets and one loaded disposable Stinger: 58 root items. Both slots completed without replacement.
Run 5 tested the final inventory race handling: the first rifle was deliberately deleted before insertion. It remained a spent grant; 18 of 19 planned items reached storage. Preparation waiting and persisted settings reload also passed. The armored-site screenshot is from this run.
Run 6 compiled the final production source, verified helicopter ground contact to within 2cm, active smoke and all 19 planned items at default rifle/ammo settings with both launchers forced on. Preparation waiting, settings reload and native menu bounds passed. The helicopter screenshot is from this run.
All 728 production source/resource files match the final native snapshot; the test-only project configuration and generated resource database are excluded. Hashes are recorded separately. No test fixture was added to the production addon.
Targeted regressions passed for worker lifecycle, loot planning, inventory races, settings boundaries/migration, admin command routing and generated layout bounds. All 51 owned prefabs have unique saved root IDs.

The runner reported smoke-completed, confirmed cleanup, and unchanged source/external addon inputs. The successful runs had no script/runtime failures. The runner's overall exit status remains nonzero because of pre-existing external localization GUID, vehicle-field and DLC ownership errors. These are local Workbench integration tests, not a dedicated multiplayer or late-join test.

The smoke uses the engine's ReplicatedParticleEffectEntity. Scope and ammunition pairings were checked against the installed 1.9 prefabs; the WCS Stinger is an inspected disposable launcher with an initial missile.

Early test iterations caught and corrected preparation-time shutdown, too few terrain candidates and a duplicate inherited crate replication component. The retained fixture files document the maximum-load, removed-item and final-grounding checks. Private profiles and full logs remain under .local/crash-sites.