feat(sandbox): support launch-configured permission profiles

[zfy0701]

Summary

• allow a trusted launcher to pass Codex app-server configuration overrides and map ACP modes to named permission profiles
• select the mapped profile for new, resumed, and loaded threads, and update it when the ACP mode changes
• preserve additional workspace roots and omit the legacy per-turn sandbox policy while a named profile is active
• keep profile definitions opaque to the adapter and keep approval-reviewer selection independent

Motivation

Named Codex permission profiles can express runtime policy that the legacy ACP sandbox policy cannot represent. This adds a generic integration point for ACP hosts without embedding any operator-specific policy in codex-acp.

Validation

• npm run typecheck
• npm test (345 passed, 28 skipped)
• npm run build
• Linux app-server smoke test covering session creation and all three ACP mode transitions; the selected named profile remained active, additional workspace roots were forwarded, and Auto reviewer remained independent
• Linux sandbox smoke test confirming that a profile-level file deny remained effective without a legacy per-turn sandbox override

Created by Codex . GPT-5.6