feat(permissions): apply inherited profiles at runtime

[viyatb-oai]

Stack

This PR is stacked on #22270. Review #22270 first for the config-level extends resolver and merge semantics; this follow-up contains the runtime and protocol wiring on top of that foundation.

Why

The resolver in #22270 makes inherited permission profiles well-defined in config, but selected profiles still need to flow through runtime permission compilation, network-proxy selection, and the active-profile metadata exposed to clients. This PR keeps that integration separate from the inheritance rules themselves so each diff has a narrower review surface.

What changed

• Resolve selected custom permission profiles before compiling runtime sandbox and network policy, including supported built-in baselines such as :read-only and :workspace.
• Preserve the selected profile's extends metadata on the active permission profile while the resolved permissions drive runtime behavior.
• Update network proxy profile loading so built-in defaults and inherited custom profiles select the effective network policy consistently.
• Add runtime coverage for built-in extension baselines, active-profile metadata, and network-proxy selection.
• Refresh app-server protocol comments and generated schema/TypeScript fixtures for the now-active extends field.

Validation

Run on the full inheritance stack before the PR split:

• cargo test -p codex-config
• cargo test -p codex-core permissions_profiles_
• cargo test -p codex-core selected_network_from_tables_
• cargo test -p codex-core default_permissions_profile_can_extend_builtin_workspace

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fdf7559323

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".