chore: release 0.9.3

[ramarivera]

Version-only bump. Ships the achievement-banner expiry fix from #170.

The trophy banner rendered from the shared status.json with no TTL while reactions expire on a sweep, so a single unlock pinned every session's bubble until some path happened to call writeStatusState with no achievement — observed live as a "Diplomat" banner stuck for ~5h.

writeStatusState now stamps achievementAt and the statusline expires the banner on the same reactionTTL clock as a reaction. Validity and age are separate gates: a zeroed or malformed stamp never renders regardless of TTL, and reactionTTL=0 disables expiry only.

Note: .claude-plugin/plugin.json and marketplace.json still read 0.8.0. That drift predates this release and is what #110 is for — deliberately not touched here.

🤖 Created with the help of AI (Claude Opus 5).

---

Note

Release version 0.9.3

Bumps the package version from 0.9.2 to 0.9.3 in package.json.

^{Macroscope summarized e5916ef.}

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 15 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: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 2227ba20-5715-44d4-9c67-486633116306

📥 Commits

Reviewing files that changed from the base of the PR and between 290057d and e5916ef.

📒 Files selected for processing (1)

• package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/bump-0.9.3

---

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

[devin-ai-integration]

Devin Review found 1 potential issue.

[Copilot]

Pull request overview

This PR performs a version-only release bump to publish 0.9.3, aligning the package version with the shipped achievement-banner expiry fix from #170.

Changes:

• Bump @ramarivera/coding-buddy version from 0.9.2 to 0.9.3 in package.json.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.