v0.4.0 — Downstream integration

v0.4.0 — Downstream integration

This release establishes executable, verified downstream consumption paths for Axiolid: an external Rust or C/C++ application can now depend on an immutable released Axiolid without checking out this workspace, importing implementation-private crates, or reverse-engineering capability and refusal semantics.

Milestone: https://github.com/axiolid/kernel/milestone/8

Downstream integration surface (v0.4 scope)

• Downstream integration profiles and a capability handshake (#50)
• A supported Rust application facade and provider path (#51)
• A versioned, memory-safe C ABI for native consumers (#52)
• CMake integration and cross-platform native artifacts, Linux/macOS/Windows (#53)
• Black-box downstream consumer probes and compatibility CI (#54)
• A machine-checked, mutation-tested 2D-only dependency closure for narrow consumers such as ifc-geometry (#1)
• Release automation: version bump and changelog rollover, wired into the standard gate (#10)
• Executable downstream integration quickstart guides for narrow Rust crates, the Rust facade, plain C, and C++/CMake (#55)

Full details: see docs/CHANGELOG.md under ## [0.4.0], and the per-feature ADRs it links to.

Consuming this release

• Rust: pin a git dependency to this tag or its commit, or to the corresponding axiolid-* versions once published to crates.io (publication itself remains a manually-dispatched, verify-then-execute workflow — see scripts/publish-workspace.py and docs/adr/0043-release-version-changelog-rollover-is-a-checked-reviewed-script.md).
• C/C++: fetch the native release archive attached to this GitHub Release, or use the Axiolid::axiolid CMake integration to build from this immutable source tag.
• Start here: docs/guide/downstream-integration.md.