Omena 5.4.0 and Rust crate train 0.4.0

This release coordinates the editor, CLI, 51 publishable Rust crates, generated WASM and NAPI bindings, and selected build-tool integrations. Registry uploads remain separately verified, non-atomic operations even though the artifacts share one versioned source commit.

Platform surface

• omena-reactive joins the public crate train with branded graph identities, non-exhaustive data records, and delta-fold dependency rebuilding covered by public-surface and language-server parity checks.
• Source-front-end, cascade, transform, proof, and cache read-set authorities now flow through their product consumers instead of being represented only by disconnected evidence records.
• The extension packages the Rust language server, engine shadow runner, and selected TypeScript backend from the same immutable revision used to build the CLI and SDK bindings.

Explicit opt-ins

• Linked-order bundle emission remains opt-in. This release does not use the extension's reserved next major or change the established default byte producer.
• External Sass Interface File trust tiers and authenticated publication evidence remain explicit inputs. An unverifiable cache artifact is not a substitute for local source authority.
• Strict minification, closed-world transforms, and advanced proof or analysis carriers remain explicit APIs; their presence does not make research-only contracts product defaults.

Behavior corrections

• Query identifiers are ordered with a locale-independent comparison, and external-string lengths preserve UTF-16 code-unit meaning across the Rust and TypeScript implementations.
• Workspace occurrence caches bind extractor scope and imported-style read sets, revalidate source freshness when watcher coverage is absent, and avoid rebuilding unrelated entries for an unrelated edit.
• Conditional class arguments no longer become unconditional facts. Guarded cascade winners include stylesheet source-order bases and reconcile the independently computed planes before returning a definite result.
• Rewrite issuance binds the trusted catalog identity, while external SIF cache data must reconcile with local regeneration or an authenticated publication boundary before elevated provenance is accepted.

Version scope

The extension advances from 5.3.0 to 5.4.0. The Rust crate train, CLI, and release-managed npm surfaces advance from 0.3.0 to 0.4.0. The Rust minor increase intentionally absorbs reviewed pre-1.0 constructible-record and runtime-contract changes; exact legacy wire projections remain available where the published 0.3.0 API requires compatibility.

The Rust train contains 51 publishable crates. omena-reactive is a first publication and therefore uses the protected bootstrap authentication path for this train before subsequent releases return to registry trusted publishing. See version governance for the machine-checked axis policy and the release runbook for the non-atomic registry procedure.