chore(release): prepare 0.6.0

[Dhi13man]

Why

The public corpus now includes four additional calibrated final-output cases, and the Codex adapter now validates collaboration lifecycles emitted by the exactly pinned Codex 0.146.0 runtime. These are non-breaking Skivolve changes, not old-runtime compatibility; together with the accumulated dependency maintenance since v0.5.0, they warrant a minor release.

What Changed

• Prepare package and citation metadata, install documentation, site metadata, support policy, issue guidance, changelog, sitemap dates, and deterministic comparator authorities for 0.6.0.

Evidence

• ruff check . and ruff format --check .: passed; 241 Python files were already formatted.
• python -m compileall -q skivolve cases tests: passed.
• python scripts/validate_site.py site: passed.
• python -m build --no-isolation, python -m twine check dist/*, and installed-package smoke: passed for the 0.6.0 wheel and sdist.
• Comparator and plain-language lock generators, repeated twice: byte-identical on the second pass; all authority hashes match.
• Comparator calibration tests: 74 passed. Shared verifier tests: 31 passed, 1 skipped because Node is unavailable in WSL.
• JSON duplicate-key validation: 352 files passed. Markdownlint and Prettier checks on changed Markdown passed.
• Full local unit execution reached 424 tests but retained six environment-bound errors: Node is unavailable in WSL and the installed Codex executable intentionally differs from the repository protocol lock. Exact-head Ubuntu CI is therefore the release authority.

Trust And Compatibility

• I considered manifest, corpus, comparator, provider, result, and package compatibility.
• I preserved or intentionally versioned source bindings, isolation, spend accounting, blinding, and release authority.
• I added adversarial calibration for changed oracle behavior.
• I added a changelog entry for a user-visible or compatibility change.
• I removed credentials, private holdout content, live evidence, results, caches, and host-specific paths.

Review Guide

Start with CHANGELOG.md, the package-version surfaces, and skivolve/comparator-profile-authority.json. The four release-lock JSON files should only rebind the package-source hash induced by the version change. The unchanged schema identifiers intentionally remain canonicalized at v0.5.0; exact-head Linux CI and the post-merge protected-main checks remain mandatory before tagging.