jif ed6dde9fda Decouple session isolation from subagent attribution (#44521) ...

## Why

Session isolation relied on Guardian source attribution. An explicit policy lets callers control inherited capabilities independently of how a session is attributed.

## What changed

- Add `SessionIsolation` with default `Inherit` and opt-in `Isolated` modes, captured at session startup through `ExtensionDataInit`.
- Use the policy to control inherited instructions, extensions, execution rules, and MCP resources. Isolated sessions retain managed execution rules and omit executor-discovered MCP servers.
- Explicitly isolate Guardian reviewers while preserving source-based fallback for older callers and saved reviewers.

## Testing

Extend delegate tests to cover isolation independently of attribution, update execution-policy coverage to supply the explicit policy, and assert that managed reviewers do not inherit the parent's configured MCP tools.

GitOrigin-RevId: f0ab42fa2f0237860ec661e72693ab191216afbf

2026-09-10 12:52:27 +00:00

..

examples

Require content kinds for extension prompt fragments (#40177)

2026-08-23 03:12:58 +00:00

src

Decouple session isolation from subagent attribution (#44521)

2026-09-10 12:52:27 +00:00

tests

Discount an approval's own code-mode wrapper from Guardian score lag (#43527)

2026-09-07 17:35:23 +00:00

BUILD.bazel

extension: add initial typed extension API (#21736)

2026-05-11 11:06:24 +02:00

Cargo.toml

Preserve verified answers across history compaction (#42293)

2026-09-02 15:07:11 +00:00

notes.md

extension: add initial typed extension API (#21736)

2026-05-11 11:06:24 +02:00