chore(release): release 1.0.0-beta.76

[ScriptedAlchemy]

🤖 I have created a release beep boop

1.0.0-beta.76 (2026-10-08)

Bug Fixes

• observability: keep aborted coverage failed closed (8c2d8fc)
• observability: keep terminal writes before maintenance (af903db)
• observability: recover joined owners on mount demand (adfc517)
• observability: retain durable terminal coverage proof (b4d17d9)
• observability: reuse final write settlement on shutdown (75ae3c5)
• observability: settle retired owners and batch writes (97491c3)
• observability: settle retired owners and batch writes (1ff4b39)

---

This PR was generated with Release Please. See documentation.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9ec42cf

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[devin-ai-integration]

Devin Review found 1 potential issue.

[devin-ai-integration]

🔴 Release binaries retain the previous version

If this head is merged before metadata regeneration, Cargo.toml says beta.76 while the generated Bazel targets and Cargo.lock remain beta.75. The integrity guard rejects the lock, and Bazel builds report beta.75 under a beta.76 release tag.

Learn more

The CLI's generated Bazel target still declares version = "1.0.0-beta.75" here, which Bazel supplies as CARGO_PKG_VERSION to the product runtime. The release integrity guard also requires Cargo.lock to match every workspace-inherited package version. This PR changes the workspace version but not those generated files. The release workflow normally runs update-release-pr-lockfile and keeps the PR draft until it finishes; the failure applies if this head is merged or used to build before that update lands.

Example: Building the CLI from this head for tag v1.0.0-beta.76 embeds beta.75 from the unchanged Bazel rule, while the release guard finds beta.75 lock entries against beta.76 manifests.

Recommended fix: Allow the release metadata updater to push its lockfile and regenerated BUILD files, then verify the release integrity guard and generated BUILD check against the completed head before merging.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[ScriptedAlchemy]

🤖 Created releases:

• v1.0.0-beta.76

🌻