Prepare v0.1.0 product release

[kabudu]

Summary

• Promotes the v0.1.0 product release notes in CHANGELOG.md.
• Updates changelog compare links for the product tag.
• Hardens the real-release workflow by retrying crate publish dry-runs around crates.io index propagation.
• Uses the CHANGELOG.md v0.1.0 section as the GitHub Release notes.

Validation

• scripts/plan-real-release.py --release-version v0.1.0 --json-out /tmp/permeantos-real-release-plan.json
• scripts/check-real-release-config.py --release-version v0.1.0 --require github-release --require binaries --require rust --json-out /tmp/permeantos-real-release-config.json
• scripts/check-release-version.py --release-version v0.1.0 --release-kind product --json-out /tmp/permeantos-release-version.json
• scripts/check-package-readiness.py --json-out /tmp/permeantos-package-readiness.json
• scripts/check-publishing-policy.py --json-out /tmp/permeantos-publishing-policy.json
• scripts/check-crate-packaging.py --json-out /tmp/permeantos-v0.1.0-release.../crate-packaging.json
• scripts/validate-release.py --version v0.1.0 ... --json-out /tmp/permeantos-v0.1.0-release.../release-validation.json
• Local release-note extraction smoke check
• git diff --check

Release Safety

This PR still does not publish anything by itself. After merge, I will tag the merge commit as v0.1.0, push the tag, dispatch the manual Real Release workflow, and watch for the protected environment approval gates.

[kabudu]

Self-review complete.

Checked:

• CHANGELOG.md has a dated 0.1.0 section and compare links are updated.
• Real Release now uses changelog-derived release notes.
• Crate publishing has retry behaviour around crates.io index propagation before each publish.
• Release validation passes in strict tag mode for v0.1.0.
• PR CI is green.

No material findings remain.