docs: prepare the v0.2.3 release

[patramsey]

Closes [Unreleased] as 0.2.3, folding in the demo recording and the config-path correction that landed after the section was first written.

Why cut this now

0.2.2 users are still running the unvalidated namecom open. The argument validation is the one change in this batch they can't get any other way, and it's a behavior change (namecom open <not-a-domain> now errors) that deserves its own release note rather than riding along silently in a later one.

15 commits since v0.2.2.

The README status block is now labelled

It sits directly beneath a GIF of real output, and its numbers are invented — 47 domains, three plausible expiry dates. Two adjacent things that look alike, one real and one not, with nothing saying which is which.

Recording a real namecom status was the obvious alternative and isn't usable — the sandbox account reports:

6516 domains  1 expiring within 7 days  2 unlocked
Expiring soon
  askdjflksdjlfkjsdlkfjslk1111.com.mx 2024-07-22  (-741 days)

So the honest fix is a label, not a substitution.

Also (not in this diff)

CLAUDE.md's config-path claim is corrected locally to match what the README and the Path() doc comment now say. It's gitignored so it can't ride along here, but it was the last copy still asserting ~/.config on every platform — the claim that sent an earlier credential search to a directory macOS never uses.

Test plan

• go build ./..., golangci-lint run, go test -race -count=1 ./... all clean
• Changelog links resolve; [0.2.3] compare link added, [Unreleased] retargeted
• Real namecom status output checked before deciding not to use it

After merge

Tagging v0.2.3 triggers release.yml, which publishes binaries and pushes to the Homebrew tap. I won't push that tag without you saying so.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!