v0.2.1

Muse and Instinct are supported connector surrogate targets, with a shared native/CLI contract, route discovery, memory, local wallet and bank-verification fixtures, and separate provenance. Muse-specific CLI/client treatments remain available.

• targets --json publishes capabilities; check --suite surrogate checks the
  catalog and projection for either target without calling a model or service tool.
• Indexed memory fixtures separate account isolation, future-access unlinking
  and stored-context deletion. Source-scoped stale facts obey the same lifecycle.
• A named surrogate-parity release gate requires exact cases for both targets;
  distribution verification checks distinct installed-wheel runs, readiness and exports.
• Package metadata identifies both supported surrogate targets. Inventory
  generation reads the package version, and tests check version, lock and archive
  consistency.
• Refresh dependency inventories and original notices for the locked dependency
  updates, including the Rolldown native binding.
• CI summaries report sealed setup/reporting failures as status: error with
  an error detail, consistent with exit code 2.
• Shared CLI reports use target-neutral provenance. Surrogate readiness detects
  escaped credentials and hides them even in schema keys. Indexed source names
  have the same constraints in the published schema and scenario loader.
• Connector run locks, CI summaries and JUnit now record the emulation
  target. Comparing older Muse evidence with a new run can report lock
  changes; published Muse scenario digests and older summary validity are
  preserved. Text presentation is also available as an assumed Muse treatment.
• Connector-only interface profiles are rejected by other execution commands
  instead of labeling a run with host behavior those commands do not implement.
• Update optional MCP Inspector to 2.11.0 and its locked MCP SDK and Vite
  dependencies to patched versions. Fresh init projects receive the same
  manifests as the repository.
• Pin certifi to 2026.10.19 and workflow uv to 0.13.4 to remove the emSign
  trust root affected by compromised intermediate CA keys.
• Rebuild the notice archive in the same member order used by release generation. Original license and notice text is unchanged; the bundled inventories carry the new version and lock digest. Regression checks cover ordering, ZIP metadata and source contents.

The v0.2.0 tag produced no published packages because its notice archive failed the consistency check. Version 0.2.1 includes that correction and the Instinct update.

Both targets are labeled surrogates. Release qualification covers local consumer testing and the verified distribution; it does not establish real assistant behavior or admission.