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.3.0 - 2026-08-12

Breaking changes and migration

• Bridge 0.3 intentionally rejects the retired top-level phases field and artifact-paths.phases. Remove both before loading an older profile. The migrate-profile command converts a current EDN profile to YAML; it does not translate removed phase, prompt, or artifact workflows.

• Replace removed phase and artifact commands with the canonical check → run-evidence → check loop. Keep prompts, observable semantics, omission rationale, reports, and planning state as ordinary documents.

• bridge.api/status-summary is removed because its input was an internal build-status map with no supported public producer. Use bridge.api/check, which returns the canonical summary directly.

• A 0.2 candidate frontier whose profile contains retired fields cannot be loaded by 0.3. Create a governance-only commit that removes those fields, review it directly, and bootstrap that tree as the new explicit frontier before verifying later candidates:

  bb bridge check --tree <cleaned-governance-tree> \
    --frontier <cleaned-governance-tree> --approve --format json
  

Changed

• Canonical status summary version 2 reports the normalized fresh receipts used by the check. Receipt discovery and freshness filtering happen once in build-status; convergence and summary generation are projections of that snapshot.
• Profile, policy, and evidence-receipt validation use direct validators with path-specific errors instead of a generic runtime schema interpreter and resource database.
• Legacy profile artifact-paths.evaluations, expected-artifacts, mechanism-family, and derived-artifacts fields remain accepted but are discarded before normalization and do not appear in profile summaries or debug output. artifact-paths.policy is accepted metadata but does not select the policy; use verification-policy-path or the default .bridge/verification-policy.yaml.
• bridge-path-sandbox is declarative policy for external capability-enforcing operators such as Vis. Bridge validates the declaration but does not enforce filesystem access itself.
• Stable CLI commands follow the 0.3.x compatibility contract. Experimental commands remain opt-in previews outside that contract.
• Evidence commands use Git Bash directly on native Windows, and timed-out process trees are terminated before capture cleanup.

Removed

• The standalone analyze-change command and workflow action, plus the change-intent-card artifact and schema. check owns change detection and obligation analysis.
• generate-brief, generate-observable, plan-seed, and stub-artifact, implicit planning phases, and the verification-brief and plan-seed schemas.
• The observable-contract and omission-decision-record artifact schemas and their former effects on coverage, evidence inference, staleness, and policy.
• The prose/report artifact layer (bridge-index, namespace/formal/differential cards, assumption/completeness/scope/changelog ledgers, reports, and feasibility studies) and its coverage, completeness, missing-artifacts, and feasibility-report commands.
• The parallel evaluation subsystem and eval command. Evaluations now use canonical evidence commands and evidence-run receipts.
• Template and phase orchestration: list-templates, render-prompt, init-phase, run-phase, and run-phases.
• Legacy artifact reference traversal, subject aliases, and query. Evidence receipts are grouped by their exact subject.
• Hard-coded mechanism-family obligations, mtime-based derived-output tracking, and recursive citation discovery. Policies own rerun requirements, subsystem fingerprints use content and executable mode, and citations remain prose.
• Standalone init-profile and summary, the disabled TUI, and next --tui.
• bridge.api/status-summary; use bridge.api/check.

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.