Briosa 0.9.0

Briosa 0.9.0 delivers the reviewed runtime redesign for both independent SpatialAnalyzer targets, 2024.1.0508.5 and 2026.1.0529.7. The host and worker now use explicit typed execution values and outcomes; supported MP RPCs use handwritten typed mappings instead of descriptor-interpreted runtime dispatch. Admission is bounded before mapping, lifecycle cleanup retains ownership until resolved, and normal operation dispatch avoids CLR reflection.

Breaking compatibility change: the runtime contract is major 2. Use the matching 0.4.0 .NET, JavaScript/TypeScript, or Python client. The three robot Machine ID inputs are collection/instrument identifiers on new protobuf field numbers; old fields are reserved. Major-1 clients reject 0.9.0 before MP work.

The two exact-target server packages are built, tested, and signed separately. Portable CI exercises the full server suites and packaged fake-SDK compatibility matrix against the six published major-2 clients and twelve retained major-1 clients. Licensed package validation of the preceding 0.9.0-dev.2 candidate covered external readiness, read-only smoke, two string-setter RPCs, and SDK stop against both matching SA/SDK targets. The final release source received full portable CI; it was not rerun against licensed SA. Fixture-backed reporting, instrument, and robot scenarios were not executed against licensed SA for this release.

The retained-log sink still scans its shared directory per event to preserve strict cross-process limits. A larger logging-performance change is tracked in #228; no logging speedup is claimed.

See the major-2 migration guide and the reviewed server PRs #223, #226, and #227.