Eric Traut dbf67f34a0 Emit exec-policy warnings for freshly loaded thread config (#31253) ...

## Why

App-server initialization captures exec-policy parse warnings only once.
Each `thread/start` then reloads config for that thread's cwd and
rereads its `.rules` files, so rules that become malformed after
initialization—or belong to a different project—are dropped without a
fresh warning to the requesting client.

## What changed

- Validate exec-policy rules against the freshly loaded per-thread
config during `thread/start`.
- Send the existing structured `configWarning` only to the connection
that requested the thread.
- Preserve nonfatal startup and avoid repeating an identical warning
already delivered during initialization.

This is intentionally separate from the TUI `legacy_core` cleanup in
#31179 and the managed-requirements fallback fix in #31188.

2026-07-06 10:17:15 -07:00

..

common

telemetry: log structured direct tool-call timing (#30334)

2026-07-02 13:53:56 -07:00

suite

Emit exec-policy warnings for freshly loaded thread config (#31253)

2026-07-06 10:17:15 -07:00

all.rs

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

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