chore(release): v0.6.0

[ojongerius]

Release commit for v0.6.0 — promotes [Unreleased] to [0.6.0] and bumps package.json to 0.6.0.

Tracks #118 / #119 (ar_query_receipts filter, ordering, and chain-default fixes). The full bullet list is already on main in CHANGELOG.md.

Why this is a separate PR

scripts/release.sh tried git push origin main v0.6.0 which the branch protection on main rejected (PRs required). The tag v0.6.0 was already accepted on the remote and points at the commit on this branch (c7c7075), so we need to land this exact SHA on main.

Merge strategy

Use "Create a merge commit" — preserves the commit SHA so tag v0.6.0 stays reachable from main's history. Rebase or squash would change the SHA and orphan the tag.

After merge

I'll run gh release create v0.6.0 --generate-notes to fire publish.yml → npm publish.

Test plan

• CI green on the changes shipped here (the ar_query_receipts PR fix(tools): add timestamp/chain filters and newest-first ordering to ar_query_receipts #119 and the prep PR chore: prep v0.6.0 changelog and gitignore Claude Code state #123 already merged)
• Reviewer: confirm "Create a merge commit" is selected (not rebase/squash)
• After merge: GitHub Release created → publish.yml succeeds → @agnt-rcpt/openclaw@0.6.0 on npm