chore: bump version to 0.0.2 for stable release

[NiveditJain]

Summary

• Bumps version from 0.0.2-beta.2 to 0.0.2 for the first stable release.

Test plan

• CI passes (quality, test, build, test-e2e)
• Verify npm publish picks up the correct version

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Released version 0.0.2 as stable (promoted from beta release).

[coderabbitai]

Warning

Rate limit exceeded

@NiveditJain has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 16 minutes and 35 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 16 minutes and 35 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 446296f9-4ac3-4fe7-81d7-21553fa53276

📥 Commits

Reviewing files that changed from the base of the PR and between 27d8330 and eaca188.

📒 Files selected for processing (2)

• .github/workflows/publish.yml
• scripts/publish-aliases.mjs

📝 Walkthrough

Walkthrough

The package.json version field was updated from 0.0.2-beta.2 to 0.0.2, promoting the package from a beta release to a stable release candidate.

Changes

Cohort / File(s)	Summary
Version Release package.json	Updated version field from 0.0.2-beta.2 to 0.0.2, marking the transition from beta to stable release.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 From beta's burrow, we've come so far,
Version 0.0.2 shines bright like a star!
No longer testing, now stable and true,
This rabbit hops proudly—the release hops right through! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is largely incomplete. It lacks the required 'Type of Change' section and the checklist section from the template, providing only a summary and test plan instead.	Add the 'Type of Change' section (mark 'Chore' or similar) and the complete checklist with all required checks (lint, tsc, test, build).

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: bumping the version to 0.0.2 for a stable release, which directly matches the package.json modification.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch luv-53

---

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 and usage tips.}