chore(release): release 1.0.0-beta.69

[ScriptedAlchemy]

🤖 I have created a release beep boop

1.0.0-beta.69 (2026-10-04)

Features

• index: report accurate generic ambiguity census (f4b8918)
• retrieval: disclose route, churn, misses, and co-change (20175c2)

Bug Fixes

• health: steer agents to the weakest dimension (59ce651)
• health: steer agents to the weakest dimension (2b5f04e), Refs #3010

---

This PR was generated with Release Please. See documentation.

[changeset-bot]

⚠️ No Changeset found

Latest commit: b178726

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]

Note

Newer findings are available below. Devin Review posted a newer report on this PR, in addition to the findings presented here.

Devin Review found 1 new potential issue.

🐛 1 issue in files not directly in the diff

🐛 Release lockfile blocks locked builds

The tracedecay, tracedecay-cli, and tracedecay-project lock entries remain beta.68 while their manifests inherit beta.69. Cargo's --locked builds and the release integrity check fail.

[devin-ai-integration]

Devin Review found 1 new potential issue.

🐛 1 issue in files not directly in the diff

🐛 Release builds fail on stale package versions

With the workspace at beta.69, Cargo.lock records beta.68 for tracedecay, tracedecay-cli, and tracedecay-project. Locked CI and release builds fail because Cargo cannot update those entries.