docs: prepare the v0.6.3 release — changelog, docs freeze, version bump

[devops-thiago]

What type of PR is this?

• 📝 Documentation

Description

The manual release-prep steps from docs/RELEASING.md, in one PR.

Changelog. Writes the [0.6.3] section, which was empty despite five substantive fixes landing since v0.6.2. Entries cover #723 (secondary-limit budget + refusal logging, closes #722), #721 (file-level thread fallback, #712), #720 (overturned-decline disclosure on every body and named closures, #713/#714), #719 (verification coverage counts only acted-on verdicts, #710), #724 (verifier receives the PR description, part of #711), and #717 (docs deploy dispatched from the release workflow). Entries are sourced from the merged PR descriptions and follow the file's established voice: mechanism first, measured numbers kept, issue numbers referenced where an issue exists. The dated heading matches the format release.yml extracts release notes from.

Docs freeze. Archives the 0.6.2 docs version per the procedure #715 added: snapshot taken from the v0.6.2 tag (so the archived pages carry that release's expanded includes, not the working tree's), npm run docs:archive -- 0.6.2, working docs restored from HEAD, and current.label moved to v0.6.3. The post-restore git status check was clean — only the archive artifacts and versions.json changed, nothing resurrected. This is the freeze RELEASING.md notes was missed at four consecutive cuts.

Version. pom.xml moves from 0.6.3-SNAPSHOT to 0.6.3, the version release.yml checks against the tag. The only occurrence in the tree.

Related Issues

Refs #715 (freeze procedure). Release preparation for v0.6.3.

How Has This Been Tested?

• Manual testing

npm run build renders the archived 0.6.2/ pages (index, architecture with its mermaid blocks, commands) alongside the current docs. The changelog section sits immediately after [Unreleased] with the dated-heading format release.yml's note extraction expects, and every entry's issue/PR references resolve.

Checklist

• My code follows the project's coding standards
• I have performed a self-review of my own code
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have updated the documentation accordingly
• My changes generate no new warnings or errors

Additional Notes

The changelog section is dated 2026-08-15. If the tag is cut tomorrow instead, bump the date in the heading before tagging — release.yml matches the version, not the date, so this is cosmetic but worth keeping honest.

After this merges, the release is two commands: tag the merge commit v0.6.3 and push the tag. The docs site deploys itself this time (#717), and the post-release bump PR opens automatically.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[thrillhousebot]

🤖 ThrillhouseBot PR Summary

What this PR does

Writes the previously empty [0.6.3] changelog section in CHANGELOG.md, documenting five fixes and one automation change landed since v0.6.2: secondary-limit retry budget and refusal logging (#722), file-level thread fallback (#712), overturn-decline disclosure on every review body (#713/#714), verification coverage counting only acted-on verdicts (#710), verifier receiving the PR description (#711), and release-triggered docs deploys (#717).

Description vs. Implementation

No mismatch found between the PR description and the change.

Changes Overview

• Files changed: 1
• Lines added: +18
• Lines removed: 0

Changed Files

File	Change	Summary
CHANGELOG.md	Modified	Inserts the new 0.6.3 section (intro, six Fixed bullets, dated heading) between [Unreleased] and [0.6.2], matching the prior release heading format.

Risk Assessment

Risk	Count
🔴 Critical	0
🟠 High	0
🟡 Medium	0
🔵 Low	0

No new issues found in this PR, but the review cannot be approved until required CI is confirmed green.

⚠️ Required CI Checks Status

Some required checks are still pending or have failed:

Check	Type	Status	Detail
format	check-run	⏳ Pending	-
trivy	check-run	⏳ Pending	-
frontend	check-run	⏳ Pending	-
test	check-run	⏳ Pending	-
dependency-review	check-run	⏳ Pending	-

---

Automated review by ThrillhouseBot. Reply with /review to re-run.

[thrillhousebot]

ThrillhouseBot found no issues in this PR, but some checks are still pending or failed:

• Check frontend is pending
• Check trivy is pending
• Check format is pending
• Check test is pending

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud