docs(changelog): record the lint retired-stale fix

[luciferlive112116]

what changed

adds the ## [Unreleased] → ### Fixed changelog entry for the lint
retired-stale fix that landed in #484 (issue #478). changelog only — no
code change.

this pr originally carried the fix itself; #484 landed the same change
first, so it has been reduced to the one piece that wasn't merged with it.

why

CONTRIBUTING requires a CHANGELOG.md entry under ## [Unreleased] for
user-visible changes, and #484 shipped health.py + tests without one.
lint no longer emitting stale_claim warnings for retired claims is
user-visible — anyone parsing vouch lint output sees a different set of
findings. ### Fixed is what the next release notes are rolled from
(CONTRIBUTING §"Release checklist" step 2), so without this the change
ships undocumented.

what might break

nothing. documentation only — no code, no on-disk shape, no kb.*
behaviour.

tests

• n/a — changelog only. no code paths touched.
• the behaviour itself is already covered by the tests that landed with
  fix(lint): exempt retired claims from stale check #484 (test_lint_exempts_retired_claims_from_stale_check,
  test_lint_flags_stale_active_claims).

[coderabbitai]

Warning

Review limit reached

@plind-junior, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 57 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: b4d26821-bbf7-4659-a6bc-8d1d84a1be55

📥 Commits

Reviewing files that changed from the base of the PR and between d0605b7 and 52b0efb.

📒 Files selected for processing (1)

• CHANGELOG.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[luciferlive112116]

#484 landed the same fix first, so i've rebased this onto current test
and dropped my duplicate health.py + test changes — they're already in.

what's left is just the changelog entry, which #484 didn't include. the
retired-stale exemption is user-visible (vouch lint stops emitting
stale_claim for retired claims) and ### Fixed is what the next release
notes get rolled from, so it seemed worth not losing. happy to close if
you'd rather fold it in elsewhere.

[plind-junior]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.