v2.0.0

Changelog (1.28.0 -> 2.0.0)

Release 2.0.0 closes the long migration from the historical cdx-logics-vscode and flow-manager surfaces to one canonical product and runtime contract: logics-manager.

Why 2.0.0

• The extension, npm bin, Python package, generated instructions, and assistant-facing workflow contract now converge on logics-manager.
• The legacy flow-manager assistant compatibility bridge has been removed instead of merely hidden behind fallback wording.
• The plugin now behaves more cleanly as a thin VS Code client over the bundled runtime and canonical CLI surface.
• Release and packaging surfaces now reflect the same product identity, which makes this a true contract milestone rather than a routine minor bump.

Highlights

• Canonicalized the assistant/runtime contract around logics-manager and removed the remaining flow-manager bridge surface.
• Simplified plugin runtime snapshots and diagnostics so the supported steady state is the bundled logics-manager runtime, not historical compatibility markers.
• Kept request authoring, workflow actions, diagnostics, and generated instructions aligned on the same canonical CLI.
• Closed the full req_189 migration slice and synchronized the linked Logics backlog, task, and request docs.
• Prepared the release toolchain, curated changelog flow, and README for the post-migration product shape.

What Changed

Canonical Runtime and Assistant Contract

• Removed the legacy Claude bridge variant and assistant alias that still exposed flow-manager as a normal workflow surface.
• Updated plugin request-authoring and assistant prompts so they prefer the canonical logics-manager contract everywhere.
• Tightened runtime and diagnostics wording so repo-local runtime checkouts and canonical bridge files are described as the normal path.

Plugin and Runtime Simplification

• Reduced runtime snapshot fields to the product-relevant bridge state instead of carrying legacy compatibility markers through production flows.
• Realigned tests and fixtures with the canonical bridge/runtime contract.
• Preserved the integrated-runtime model without reintroducing clone or submodule bootstrap logic into the normal product path.

Packaging, Release, and Documentation

• Bumped the extension, npm, and Python package version surfaces to 2.0.0.
• Aligned package-lock.json root metadata with the canonical package name logics-manager.
• Updated the release README guidance and curated changelog metadata for the new major release.
• Switched the release workflow’s Logics validation steps to canonical python -m logics_manager ... entrypoints instead of legacy flow-manager script paths.

Upgrade Notes

• Treat logics-manager as the only supported operator-facing CLI and assistant-facing workflow surface.
• If you previously relied on flow-manager bridge names or $logics-flow-manager, migrate those references to the canonical Logics assistant/runtime entrypoints generated by the current runtime.
• Existing repositories should continue to use the bundled runtime path; the release does not reintroduce manual clone/submodule bootstrap behavior.

Validation and Regression Evidence

• npm run lint:ts
• npm test
• npm run test:npm-cli
• npm run release:changelog:validate
• python3 -m logics_manager lint --require-status