zm-oai ed59a6c1cd Preserve the CLI MXC preference in executor config reads (#51525) ...

## Why

Executor config reads omitted the startup `features.prefer_mxc` override, so clients could not see the CLI sandbox preference.

## What changed

- Include the explicit CLI `features.prefer_mxc` value in `environmentConfig/read` as a `session-flags` layer, above project config and below legacy managed file and MDM config.
- Retain only this preference from startup overrides.
- Expose `windows_mxc_allowed_by_config` to share MXC eligibility checks after callers resolve the active permission profile.

## Testing

Add CLI and remote executor coverage for preference propagation and filtering, plus a unit test verifying that both legacy managed config sources retain precedence.

GitOrigin-RevId: 5ac6f5257f1e807c2f197dcf5dcb2385cedca0ea

2026-10-07 00:29:04 +00:00

..

examples

Require content kinds for extension prompt fragments (#40177)

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

src

Expose selected environments to MCP contributors (#51503)

2026-10-06 23:07:48 +00:00

tests

Preserve the CLI MXC preference in executor config reads (#51525)

2026-10-07 00:29:04 +00:00

BUILD.bazel

extension: add initial typed extension API (#21736)

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

Cargo.toml

Bind Guardian async scores to target environment permissions (#47830)

2026-09-24 12:34:04 +00:00

notes.md

extension: add initial typed extension API (#21736)

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