5tratumOS v0.8.5

5tratumOS v0.8.5

This coordinated update includes all OS 0.8.4 changes and requires the signed 5tratMux 0.9.49-or-newer app update before reporting completion. This is the MAIN release.

• Restore automatic MUX Attack monitoring and app-validated launches with Local 5TRATMUX selected. Existing evidence thresholds, persistence, route health, mission scope, cooldowns and portfolio restoration remain enforced. Ordinary Local AI fleet comparisons cannot authorize attacks or invent event probabilities.
• Correct the fleet merge that let stale pool status override a freshly reporting MUX miner and incorrectly park its Orbit craft.
• Retain automatic updates of existing Mux Flight downloads to 0.1.1 after active flights close, signed Local AI catalogue/runtime setup, on-demand pinned model downloads, and every previous OS/Orbit fix.

Local AI remains experimental, paid-only and initially available on compatible AVX2 Intel/AMD hosts. ARM OS updates remain supported. Mux Flight is optional; its existing signed-trial access ends when the trial expires. Model weights are downloaded on demand and are not stored in the source repository.

Verification: 112 existing focused MUX checks, 8 new Local AI launch regressions, 1 adapted contract test, 8 JavaScript checks, and 8 focused fleet/Orbit checks passed. Final OS archives retain all 164 payload files and verify the signed Local AI metadata. Protected native builds and installed-node results are recorded with the coordinated native release. These tests do not promise a natural MUX opportunity at a fixed interval or establish that every intermittent visibility issue is resolved.

Source: OS 076169d06670a77aec26a4b60848087b1dec4e5c; native b96ff11c941a3903fe0a041f82583db335c9627b.
OS archive SHA-256: 3b331a685e7963e0e7c3564c3620c260e1125e52a57d2e9f251cfddd6a8460ba (58,720,927 bytes).
Mux Flight 0.1.1 uses the unchanged verified feature archive published with OS 0.8.3.

OS archives use the established SHA-256 update mechanism. Native app and scoped Local AI metadata use the existing pinned signing key; no OS signing policy or administrator key is replaced.