Changelog

Notable changes to Bridge's public surfaces. The library contract is defined in docs/api.md; only bridge.api changes are tracked at contract level — internal namespaces may change in any commit.

0.2.2 - 2026-07-30

Added

• Stable bridge.api library contract and machine-readable inventory via (bridge.api/contract).
• Exact candidate verification with explicit --index / --tree, verified frontier approvals in Git-private state, disposable linked-worktree evidence execution, and candidate-bound receipts.
• Candidate-aware pre-commit and pre-push hooks.
• Canonical status summary (:summary-version 1) shared by bridge.api/check, bridge.api/status-summary, and CLI summary output.
• Reproducible Clojars packaging as com.blockether/bridge, including the preferred JVM JSON and YAML backends.
• Linux and Windows CI coverage plus a clean packaged-consumer smoke test.

Changed

• bridge check --format json is now the canonical JSON status-summary format.
• Stable CLI commands now follow the 0.2.x compatibility contract. Experimental commands remain opt-in previews outside that contract.
• YAML writes snake_case keys and accepts both legacy kebab-case and snake_case input.
• Working-tree Git detection executes Git directly instead of through Bash, including on native Windows.
• Subsystem fingerprints are content/mode based; timestamp-only changes no longer stale evidence.
• Release automation checks out the exact tag commit, validates tag/version agreement, runs all gates before deployment, and creates the GitHub release only after Clojars succeeds or already contains the version.

Removed

• The redundant bridge check --format summary-json alias; use --format json.
• Raw bridge.api/build-status, bridge.api/planned-actions, and bridge.api/next-action; use the stable canonical summary instead.
• The SysMoBench-specific adapter and example corpus from core Bridge; product integrations now live outside the core distribution.
• Generated target/ contents from version control.