release: promote 0.0.11-beta.13 to stable 0.0.11

[NiveditJain]

Stable release: 0.0.11

Cuts the first stable release of the 0.0.11 line. This PR only prepares main; the actual npm publish happens when the GitHub Release v0.0.11 is created (see How publishing works below).

Changes

• package.json: 0.0.11-beta.13 → 0.0.11. Dropping the -beta suffix makes publish.yml publish under the latest dist-tag instead of beta.
• CHANGELOG.md: add the ## 0.0.11 — 2026-06-26 section with a promote-to-stable Docs entry, mirroring the existing 0.0.10 convention. The per-beta 0.0.11-beta.* sections below it carry the full feature/fix/docs detail for the cycle.

Sanity check (all CI gates run locally, green)

Gate	Result
frozen-lockfile install	✅ no drift
quality — lint	✅ 0 errors (5 pre-existing no-img-element warnings)
quality — tsc --noEmit	✅ clean
quality — version-consistency	✅ no-op (no packages/)
test — unit	✅ 1895 passed / 104 files
build (bun run build)	✅ Next.js + dist bundles + standalone prune
docs — validate:mdx	✅ 300 pages parse cleanly
test-e2e	✅ 298 passed / 13 files

failproofai --version (fresh CLI build) reports 0.0.11.

How publishing works (for the merger)

Publishing is driven by GitHub Releases, not by merging this PR (.github/workflows/publish.yml):

1. Merge this PR so main is at 0.0.11.
2. Create a GitHub Release tagged v0.0.11.
3. publish.yml publishes 0.0.11 to npm under latest, publishes the alias packages, then auto-bumps main to 0.0.12-beta.0 with a [skip ci] commit.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Released version 0.0.11 and updated the package version accordingly.
• Documentation
  • Added a new stable changelog entry for 0.0.11.
  • Noted that 0.0.11-beta.13 has been promoted to stable, with details retained in the related beta notes.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 7f56a776-6e7b-4a48-b635-aea52411e33d

📥 Commits

Reviewing files that changed from the base of the PR and between cff2578 and 5e3c2c8.

📒 Files selected for processing (2)

• CHANGELOG.md
• package.json

---

📝 Walkthrough

Walkthrough

package.json was bumped to 0.0.11, and CHANGELOG.md gained a new stable 0.0.11 entry noting that 0.0.11-beta.13 was promoted to stable.

Changes

Stable release update

Layer / File(s)	Summary
Version and changelog update package.json, CHANGELOG.md	The published package version changes to 0.0.11, and the changelog adds a 0.0.11 stable entry referencing the promoted beta release.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇 Hop, hop, the version’s bright,
Stable now in morning light.
Changelog puffs a tiny cheer,
Beta dreams are settled here.
0.0.11 dances free,
A carrot toast from me!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the stable release promotion from 0.0.11-beta.13 to 0.0.11.
Description check	✅ Passed	The description is detailed and covers purpose, changes, validation, and publishing, but it does not use the full template structure.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

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

[NiveditJain]

Superseded by #460, which makes the same stable-release change on a luv-cut-0.0.11 branch per the repo's release convention (block-version-bumps reserves version edits for luv-cut-X.Y.Z branches). #460 also consolidates the 0.0.11-beta.* CHANGELOG entries into a single 0.0.11 section.