[ScriptedAlchemy]

Why

#4574 was merged independently while its writable repair branch was being verified. Master now contains the drifting-corruption ERROR event and the generated runtime-core test dependency correction. The existing corruption-refusal regression still needs to verify the event severity and diagnostic fields.

Changes

• Strengthen the actual corruption-refusal test: exactly one ERROR event, the container path, and both fault messages. Preserve the typed corruption result and the assertion that the container is not deleted.
• Retain the concurrent rebase onto master at cbaedba.
• Apply the pinned formatter to the Pi and hook-replay files introduced by the concurrent fix(sessions): make host ingest and hook redrive converge instead of re-driving permanent failures #4567 merge. These two formatting-only changes are required by the repository-wide formatting gate.

Validation

• Root and independent source review verified the event capture configuration and assertions against the actual tracing output format.
• The rebased corruption test and generated Bazel dependency are byte-identical to the previously reviewed repair.
• The maintained BUILD generator check passed: all 60 generated BUILD files are current. The dependency correction is now inherited from master.
• Pinned Rust formatting, whitespace checks, and maintained commit hooks passed; the two formatting blobs were independently reproduced using the pinned formatter.
• Hosted CI must execute the native graph-store regression and finish the required gates before merge. The full native dependency build was not repeated locally after exceeding this environment's memory.

Original failing job: https://github.com/ScriptedAlchemy/tracedecay/actions/runs/40405385367/job/121862232508

---

[changeset-bot]

⚠️ No Changeset found

Latest commit: 47b1b8e

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

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