chore(release): release 0.1.0-beta.2

[ScriptedAlchemy]

🤖 I have created a release beep boop

0.1.0-beta.2 (2026-08-19)

Features

• mount privacy remediation, multi-root dashboard scope, native-integration notifications (70182de)
• privacy: rescan at-rest LCM store bytes under current detector (1c58d39)
• privacy: rescan at-rest LCM store bytes under the current detector (327011a)
• scout: remount the Context Scout producer path and Plan 20 flag (ab6099e)

Bug Fixes

• daemon: harden project privacy and status routing (f1655c8)
• daemon: join reconciliation workers before closing retained graphs (59b3760)
• graph-db: scale batch bound and keep budget identity (2af6170)
• privacy: scan labels and drain retained statuses (a19bc5a)
• scout: keep hook cycles live and retryable (d9e69f7)
• sessions: carry admission retry verdict through jsonl ingest wrap (42cb37d)

---

This PR was generated with Release Please. See documentation.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c0ea8d8

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3490c0b1b0

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Update Cargo.lock with the prerelease version

When this commit is merged or tagged, Cargo.toml and version.txt report 0.1.0-beta.2, but the root tracedecay entry in Cargo.lock remains 0.1.0-beta.1. This leaves the tagged source metadata inconsistent and violates the lock-version invariant enforced by tests/release_safety_test.sh; the beta release workflow also explicitly expects its lockfile update to accompany the release PR. Include the generated Cargo.lock bump in this release.

Useful? React with 👍 / 👎.

[ScriptedAlchemy]

🤖 Created releases:

• v0.1.0-beta.2

🌻