Briosa 0.7.0

Server 0.7.0 introduces behavioral compatibility contract 1.0 for the independent SA 2024.1.0508.5 and 2026.1.0529.7 products. Contract-aware clients can select a compatible installed distribution independently of the exact protocol artifact used to build the client. Exact SA target, activated SDK identity, connected SA identity, and execution readiness remain mandatory.

The server locates its exact SA application through Windows installation evidence and file-version checks. Ambiguous copies require an explicit per-process path. Briosa does not switch COM registration or make concurrent SA execution safe.

Use Installer 0.3.0 or newer for the new schema-3 packages. Keep older server distributions while existing applications require them: client 0.1.0 retains its exact Server 0.6.0 pin, and client 0.1.1 retains its exact Server 0.6.1 pin. See the selection and compatibility contract and compatibility evidence.

Both target products passed package/protocol/conformance reproducibility checks, packaged fake-SDK scenarios, and Windows signing verification in the release workflow. This initial contract-aware server has an explicit bootstrap exception because its protocol artifacts must precede contract-aware client publication; subsequent server releases require retained published-client compatibility tests. No new licensed-SA validation is claimed.

What's Changed

• Publish the server and Installer runtime patches in the shared catalog by @davidalucas in #206
• Separate behavioral compatibility from server build identity by @davidalucas in #212

Full Changelog: v0.6.1...v0.7.0