chore: bump to 1.0.0-beta.12

[chhhee10]

Bumps the version so a release can be cut. beta.11 is already on the registry, and the publish preflight refuses a version that is — deliberately, because the root package publishes last, so a burned version would run the whole cross-compile and strand four orphan platform packages before taking E403.

What changed

File	Change
package.json	1.0.0-beta.11 → 1.0.0-beta.12
Cargo.toml	workspace version, same bump
Cargo.lock	the three crates re-stamped
CHANGELOG.md	new ## 1.0.0-beta.12 section

Cargo.toml moves with package.json because the quality job compares them: the release tag the CLI builds its daemon download URL from is the npm version, and the binary at that URL reports the Cargo one.

A correction that came with it

The 1.0.0-beta.11 CHANGELOG section listed the worker-orphan fix ("Stop daemon crash/restart cycles from orphaning live workers"). The published v1.0.0-beta.11 tag is at 1918b891 — one commit before that fix landed. It was documented as shipped in a release that does not contain it.

That surfaces in the worst way: someone hits orphaned workers, reads the changelog, upgrades to beta.11 to get the fix, and still has the bug. The entry now sits under beta.12, which is the release that actually carries it.

The handler.test.ts entry stays under beta.11 — the tag does include that one.

Verification

Ran the gates the quality and rust-quality jobs run:

• version-consistency (root vs Cargo workspace) — passes at 1.0.0-beta.12
• bunx tsc --noEmit — exit 0
• bun run lint — 0 errors (5 pre-existing warnings, untouched)
• cargo fmt --check — clean
• vitest run __tests__/ci/ — 45/45 (release-pipeline + daemon-packages, the version-sensitive suites)

🤖 Generated with Claude Code

https://claude.ai/code/session_015BDLTPtbQvUE62eCfQrUbf

Summary by CodeRabbit

• Release
  • Released version 1.0.0-beta.12.
  • Updated release notes with fixes for daemon worker and socket handling.
  • Added release information for version 1.0.0-beta.11.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3069ec55-1318-4fb1-86fa-128f357d756d

📥 Commits

Reviewing files that changed from the base of the PR and between 786dbf7 and 3322d06.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (3)

• CHANGELOG.md
• Cargo.toml
• package.json

---

📝 Walkthrough

Walkthrough

The project version changed to 1.0.0-beta.12. The changelog now includes the beta.12 release heading and reorganizes the beta.11 entries.

Changes

Release metadata

Layer / File(s)	Summary
Version and changelog update Cargo.toml, package.json, CHANGELOG.md	Both package manifests use version 1.0.0-beta.12. The changelog includes the beta.12 and beta.11 release headings.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• FailproofAI/failproofai#506: Updates package release versions and changelog entries.

Suggested reviewers: niveditjain

Poem

A rabbit checks the version line,
Beta twelve now hops in time.
Changelog leaves the trail clear,
Beta eleven rests nearby.
Packages match, release is bright.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the version bump to 1.0.0-beta.12, which is the main change.
Description check	✅ Passed	The description clearly covers the version bump, changelog correction, rationale, changed files, and verification, but omits the template sections.
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.

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

package.json

ESLint skipped: missing config or dependency (missing-dependency). The ESLint configuration references a package that is not available in the sandbox.

---

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