viyatb-oai dfcb5b5994 Support managed network requirements under permissions.network (#58182) ...

## What changed

Allow shared network constraints in `[permissions.network]` in `requirements.toml`, alongside `[permissions.filesystem]`. Apply them throughout configuration loading, network approvals, Windows sandbox policy validation, and `configRequirements/read`, and show their source in `/debug-config`.

Retain `[network_proxy]` and `[experimental_network]`, but reject mixing either with `[permissions.network]`, even across requirements layers. Preserve independent network and filesystem precedence and source attribution, and report unknown nested network fields.

Reserve `network` as a managed requirements table name and reject empty or profile-shaped tables with migration guidance. Profiles named `network` remain valid in `config.toml`. Document that policy publishers must keep using `[experimental_network]` until all readers support the chosen replacement.

## Testing

Add coverage for layered constraints and source attribution, conflicting spellings, profile-name migration errors, unknown-field diagnostics, and cloud validation. Extend API, project discovery, network approval, and Windows policy tests to cover `[permissions.network]`, and verify managed proxy settings remain independent of disabled feature configuration.

GitOrigin-RevId: 994dfca9abf5a7aea914276c0ded8b40d7ed0372

2026-10-29 22:36:06 +00:00

..

src

Support managed network requirements under permissions.network (#58182)

2026-10-29 22:36:06 +00:00

BUILD.bazel

Add Bazel release staging archives (#51850)

2026-10-07 22:11:14 +00:00

Cargo.toml

Honor home deletion preferences during Windows uninstall (#54708)

2026-10-16 21:00:02 +00:00