jif-oai d2ebb8d8ca feat: add thread idle lifecycle hook (#24744) ...

## Why

Extensions can currently observe thread start, resume, and stop, but
they do not have a lifecycle point for the host to say that immediately
pending thread work has drained. That makes idle follow-up behavior
harder to express as extension-owned logic instead of host-specific
plumbing.

This adds an explicit idle lifecycle hook so an extension can react when
a thread becomes idle while the host keeps ownership of whether any
submitted follow-up input starts a turn, is queued, or is ignored.

## What changed

- Added `ThreadIdleInput` with access to the session-scoped and
thread-scoped extension stores.
- Added a default `on_thread_idle` method to
`ThreadLifecycleContributor`.
- Re-exported `ThreadIdleInput` from the extension API surface.

## Testing

Not run; this only extends the extension API trait surface with a
default hook and exported input type.

2026-05-27 15:17:23 +02:00

..

examples

Make context contributors async (#22491)

2026-05-13 16:43:28 +02:00

src

feat: add thread idle lifecycle hook (#24744)

2026-05-27 15:17:23 +02:00

BUILD.bazel

…

Cargo.toml

Make extension lifecycle hooks async (#23291)

2026-05-18 13:53:58 +02:00

notes.md

…