jif d28be12577 Honor per-thread unload delays in app-server (#55270) ...

## Why

Thread unload timing used the server-wide delay, ignoring per-thread configuration overrides. Clients need to control how long individual idle, unsubscribed threads remain loaded.

## What changed

- Resolve unload timing from each loaded thread's `thread_unload_delay_secs` configuration. Setting it to `0` allows immediate unloading once the thread has no subscribers or activity.
- Allow this runtime retention override in `experimentalPredictionMode` forks while continuing to reject other configuration overrides. Reject negative values and delays too large to schedule.
- Replace the source-specific immediate-unload behavior with explicit configuration.

## Testing

Extend integration coverage for per-thread delays, unloading after active turns finish, fork overrides, and invalid prediction-fork delays. Verify that immediate unloading preserves persistent history and that cold resumes and ordinary nested forks use their default delay instead of retaining the previous runtime's override.

GitOrigin-RevId: fcb82bd73a101260c51e2a8476f94320c23ac929

2026-10-19 12:30:33 +00:00

..

common

Add experimental thread item lookup by ID (#52637)

2026-10-09 16:50:24 +00:00

suite

Honor per-thread unload delays in app-server (#55270)

2026-10-19 12:30:33 +00:00

all.rs

[codex] Use expect in integration tests (#28441)

2026-06-15 21:53:47 -07:00

prompt_prefix.rs

Add an app-server prompt prefix compatibility test (#51857)

2026-10-07 22:21:33 +00:00