Charlie Marsh 86102db5a1 Reject unsupported history modes when loading rollouts (#34344) ...

## Why

The first session metadata record defines a rollout's history mode. If that
record uses an unsupported mode, skipping it as a parse error can cause later
metadata copied from fork history to be treated as canonical.

## What changed

- Validate session metadata history modes before deserializing rollout lines,
  while continuing to tolerate unknown modes in copied fork history.
- Simplify thread status registration to pass only the thread ID instead of a
  fully materialized `Thread`.

GitOrigin-RevId: 9de4313d4a76b279d32bb49b2016a4f5d07507c1

2026-07-20 13:39:29 +00:00

..

src

Reject unsupported history modes when loading rollouts (#34344)

2026-07-20 13:39:29 +00:00

BUILD.bazel

Extract rollout into its own crate (#15548)

2026-03-24 18:10:53 -07:00

Cargo.toml

Move sleep items to the extension-owned lifecycle path (#33159)

2026-07-14 21:01:54 +00:00