[ScriptedAlchemy]

🤖 I have created a release beep boop

1.0.0-beta.97 (2026-11-04)

Bug Fixes

• accounting: commit token savings through the project store (#4698) (16f4368)
• build: preserve code-index runtime recursion budget (#4703) (9f2e64b)
• cli: clarify readiness and configuration refusals (#4702) (32afec6)
• doctor: surface retained graph corruption verdicts (#4700) (adbf0e3)
• graph: return warming before rewarm dispatch deadline (#4709) (ba5f8dc)
• project: adopt moved stores by explicit identity (#4701) (ba90ba5)
• scout: separate prompt inference from observed actions (#4699) (2388749)
• scout: validate complete choice probability contracts (#4690) (65ddc06)
• typescript: recheck incomplete configuration inputs (#4708) (402628a)

---

This PR was generated with Release Please. See documentation.

[changeset-bot]

⚠️ No Changeset found

Latest commit: f8bcb9c

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: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[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 binary reports the previous version

A beta.97 Bazel build sets CARGO_PKG_VERSION to beta.96, so the shipped CLI reports the wrong release. Cargo.lock also retains beta.96, causing release integrity validation to fail.

[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 binary reports the wrong version

Building beta.97 through Bazel makes tracedecay report beta.96. Its CARGO_PKG_VERSION comes from this target, while the release manifest names beta.97. The matching stale lockfile entries also fail the release integrity check.

[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 binary reports the prior beta

When Bazel builds beta.97, tracedecay-cli reports beta.96 because its generated target still declares that version. run_upgrade then treats the installed release as outdated.

[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 binary reports the wrong version

A Bazel-built beta.97 release reports beta.96 because CARGO_PKG_VERSION comes from the beta.96 target versions. The CLI also registers beta.96 as its product version, breaking version checks and update detection.

1 flag not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)

[devin-ai-integration]

Devin Review found 1 new potential issue.

🐛 1 issue in files not directly in the diff

🐛 Release binary reports the wrong version

A Bazel-built beta.97 release reports beta.96 because CARGO_PKG_VERSION comes from the stale target version. The lockfile also retains beta.96, so release integrity rejects the mismatched package versions.

1 flag not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)

[ScriptedAlchemy]

Consolidated into #4742 (integrate/open-pull-requests) at the captured head shown in its description, as requested. Continue review and further fixes on #4742. This closure does not assert CI readiness; the replacement remains draft. Source branch retained.