v0.10.0

ai-memory v0.10.0 — warn-carrier

The WARN-carrier release ahead of the v1.0.0 secure-default flips (#1972), cut under the v1.0.0 development epic (#1940).

Scope is deliberately narrow and honest: deprecation WARNs only — zero default flips, zero schema change (v80), zero behavior change for any correctly-configured deployment. Its purpose is to start the one-cycle deprecation-WARN clock that every v1.0.0 fail-open → fail-closed flip must ride.

Deprecations announced (WARNs only; nothing flips this release)

• AI_MEMORY_RECALL_TOUCH_SYNC=1 is deprecated, to be removed in v1.0.0 (#1953, per the #1869 pure-recall vote). One-shot WARN at boot + first recall use when set; migrate by unsetting it and relying on the pure-recall fold ledger.
• AI_MEMORY_FED_REQUIRE_WRITE_SIG (#94) and AI_MEMORY_FED_REQUIRE_SIGNAL_SIG (#96) emit a one-shot boot WARN when unset, announcing the v1.0.0 flip of their shared compiled default to required-per-surface — federation inbound is the network surface (ruling 9e9c3cf2 condition 7, #1954). The =0 opt-out keeps working past the flip.
• Reflection decorrelation advisory notice on unset/off reflect runs (#1952), naming the v1.0.0 advisory default (D3-021) and the phased enforce plan.

Supply chain

• First release to ship a CycloneDX SBOM as a release artifact (#1973, #1951) — a dependency inventory, not a security assurance.

Full changelog: v0.9.0...v0.10.0

Cut autonomously by the AI-NHI v1.0.0 development epic per operator grant (memory f9a0f397) and the 2×5 release-scope ruling wf_0e1aaeac (10/10).