chore: cut 0.6.0 — bump version + consolidate CHANGELOG

[xdotli]

What

Cuts the final 0.6.0 release (the in-my-lane release-mechanics steps):

• pyproject.toml: 0.6.0.dev0 → 0.6.0. benchflow.__version__ derives from package metadata, so this is the single source of truth. (uv.lock updates to match.)
• CHANGELOG.md: folded the accumulated [Unreleased] RC-loop entries and the earlier 0.6.0 — 2026-06-10 draft into one dated ## 0.6.0 — 2026-06-13 section — Added / Changed / Renamed / Removed / Fixed, each appearing once (merged the duplicate Changed/Fixed subsections). Updated the Added adoption-router bullet to the shipped bench eval adopt names (it still used the pre-rename bench agent create|run|verify).
• Refreshed a stale 0.6.0.dev0 comment in test_cli_docs_drift.py.

Verification

• Full suite 4068 passed, 49 skipped; ruff/ty clean. Version + docs-drift + install-URL guards pass (the RC-wheel pins stay mutually consistent; base version still ties to pyproject 0.6.0).

⚠️ Publish-time follow-ups (NOT in this PR — yours to do)

1. Install-doc URLs still point at the rc.6 wheel (benchflow-0.6.0rc6-…whl). Switch README / getting-started / etc. to the final 0.6.0 / PyPI install after the wheel is published — changing them now would 404. (The drift guard enforces RC-pin consistency today; it'll want updating when the final-install docs land.)
2. Merge chore: release v0.6.0 #665 (release → main).
3. PyPI publish of the 0.6.0 wheel.

Once this merges, #665 carries the version bump + consolidated changelog.

---

Note

Low Risk
Release-metadata and documentation only; no application or CLI runtime code changes in the diff.

Overview
Cuts the final 0.6.0 release by moving pyproject.toml from 0.6.0.dev0 to 0.6.0 (package metadata remains the version source of truth).

CHANGELOG.md folds prior [Unreleased] / duplicate 0.6.0 draft material into a single ## 0.6.0 — 2026-06-13 section with one each of Added / Changed / Renamed / Removed / Fixed, and updates the adoption-router bullet to the shipped bench eval adopt CLI names (replacing pre-rename bench agent create|run|verify).

tests/test_cli_docs_drift.py refreshes a comment so the pyproject version tie-in no longer references 0.6.0.dev0.

^{Reviewed by Cursor Bugbot for commit 508a8a7. Bugbot is set up for automated code reviews on this repo. Configure here.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 508a8a7673

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Update packaged install docs before cutting 0.6.0

When this final 0.6.0 version is tagged, the public-release workflow builds the distribution from this commit and pyproject.toml uses README.md as the package readme; that README still tells users to install the 0.6.0-rc.6 wheel and says 0.6.0 is not on PyPI (README.md lines 29-31 and 45-54, with the same message in docs/release.md). That would make the PyPI page and source distribution for the stable release advertise obsolete RC installation instructions, so the docs need to be switched before the final tag/build rather than after publishing.

Useful? React with 👍 / 👎.