jif 2a452d7dc1 Keep the latest Guardian risk score during concurrent sampling (#38580) ...

## Why

Concurrent Guardian samples can finish out of order, allowing an older sample to
replace the thread's newer in-memory security risk score.

## What changed

- Record when each `SecurityRiskScore` sample starts while preserving compatibility
  with records that have no timestamp.
- Add `ExtensionData::insert_if` so checking and replacing a typed attachment happen
  under the same lock.
- Update Guardian V2 to replace the thread's risk score only when the completed sample
  is newer than the stored one.

## Testing

- Verify concurrent conditional inserts retain the newest value.
- Verify Guardian-generated risk scores include a sampling timestamp.

GitOrigin-RevId: 6543a4e5497da4c623331050789e91613f931c4b

2026-08-14 13:44:51 +00:00

..

src

Keep the latest Guardian risk score during concurrent sampling (#38580)

2026-08-14 13:44:51 +00:00

BUILD.bazel

Support detect and import MCP, Subagents, hooks, commands from external (#19949)

2026-04-29 00:45:24 +00:00

Cargo.toml

Sync updates to imported external agent sessions (#36356)

2026-07-31 16:17:44 +00:00