chore(main): release 0.0.2-alpha.0

[mark-brannan-release-please]

🤖 I have created a release beep boop

0.0.2-alpha.0 (2026-10-11)

Fixed

• ci: hold publish on npm 11, not latest (#26) (b82a87c)

---

This PR was generated with Release Please. See documentation.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Repository: mark-brannan/coderabbit/.coderabbit.yaml
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 7b65963e-e94e-458b-8818-afb2cd7c6a41

---

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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.}

[claude]

Claude finished @mark-brannan-release-please[bot]'s task in 22s —— View job

---

Review of #27 (release 0.0.2-alpha.0)

No blocking findings. Release-please version bump only.

What I checked

• Diff against origin/main: the version in .release-please-manifest.json, package.json, and both entries in package-lock.json all read 0.0.2-alpha.0. No other file in the repo carries the old version except a placeholder in .github/ISSUE_TEMPLATE/bug_report.yml:63, which is an example value.
• CHANGELOG.md matches the release-please-config.json section mapping (fix → Fixed). The compare link and the commit hash for b82a87c are consistent.
• No credential-like strings in the diff.
• CLAUDE.md and AGENTS.md don't exist. .writing-rubric.md is present; I didn't apply its prose rules because the CHANGELOG is machine-generated.
• I ran npm ci, which was clean with 0 vulnerabilities. I ran npm test, which passed 13 of 13. There is no build script. I couldn't run npm run build:web or the grep for the old version string through Bash because the tool needed approval. The old-version search used Grep instead.

Finding (judgment): The only change in this release is fix(ci), a publish-workflow change that has no effect on the shipped package. Releasing it publishes a new npm alpha with identical contents. The diff can't settle whether that's wanted, because it's a question of release cadence. The always-bump-patch config makes it automatic. If it isn't wanted, mark ci as hidden in changelog-sections or use a chore(ci) prefix next time.

Caveat: public-issue-guard.sh was not seeded in this environment, so Bash calls ran unguarded or were denied. I posted this as an update to the existing comment, not through gh pr comment, and added no inline comments, since there was nothing to anchor.

[github-actions]

Complexity: no change

Measured 0 changed files, 4ddd849 against 7022205. No function's complexity moved.
Every metric is in the run's complexity artifact: complexity run