[stefan-jansen]

The migration guides ask users to compare Backtest and Live but do not give an executable comparison or identify a tested package stack. Add the existing installed-wheel dependency-matrix command, explain what it compares, and name the separately verified published shadow quickstart stack.

Closes #132.

Verification:

• Exact documented command uv run --locked python scripts/qualification/check_dependency_matrix.py passed: 103 contract tests in each of minimum, locked and maximum profiles; portable API snapshots identical. It builds and installs the actual Live wheel. The behavior source was main 0408aaf, unchanged by these two documentation edits.
• Candidate Live 0.1.3.dev11+g0408aaf; minimum/locked Backtest 0.1.0 and Specs 0.1.1; maximum Backtest 0.1.12 and Specs 0.1.5. These are distinct from the published shadow reference stack named in the guide.
• uv run mkdocs build --strict passed.
• uv run python scripts/qualification/check_documentation_links.py passed all 131 links. The generated migration cross-link, target heading, command and version table were inspected in the built HTML.
• Normal commit hooks passed. Current-head applicable hosted checks are required before merge.

The recorded published shadow run does not establish the package versions for a separate historical parity log. The guide keeps these results separate and requires the actual reported versions for each new comparison. No provider credentials, venue orders, release or deployment are involved.

AI assistance: Codex prepared and reviewed the documentation, executed the existing public verification command, and checked the resulting documentation and links.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[stefan-jansen]

Superseded by the combined maintainer-directed maintenance PR #121 to avoid qualifying and merging this queue separately. This PR head and its regression/documentation evidence are preserved in #121 and in a verified recovery archive. The accepted issue remains open until the combined fix lands; this closure does not claim the fix is merged. Follow-up work continues in #121.