core tests: migrate prompt caching turns to profiles

[bolinfest]

Summary

This removes the explicit SandboxPolicy constructors from core/tests/suite/prompt_caching.rs. The tests still exercise the same prompt-cache invariants across permission and turn-context changes, but the permission source is now PermissionProfile.

Changes

• Uses PermissionProfile::workspace_write_with() for workspace-write override scenarios.
• Uses PermissionProfile::Disabled for the no-sandbox per-turn override.
• Projects profiles through turn_permission_fields() or to_legacy_sandbox_policy() only to populate compatibility fields on existing ops.
• Removes the SandboxPolicy import from prompt_caching.rs.

Verification

• cargo check -p codex-core --tests

[chatgpt-codex-connector]

💡 Codex Review

codex/codex-rs/tui/src/app_server_session.rs

Lines 1116 to 1120 in d8c60c2

	if file_system_policy.has_full_disk_write_access() {
	permission_profile
	.network_sandbox_policy()
	.is_enabled()
	.then_some(codex_app_server_protocol::SandboxMode::DangerFullAccess)

Preserve sandbox override for full-write managed profiles

When thread_params_mode is remote, thread_start_params_from_config/thread_resume_params_from_config/thread_fork_params_from_config depend on this helper to populate sandbox. For a managed profile with full-disk write access but restricted network, this branch returns None, so the request sends neither sandbox nor permission_profile. That drops the caller’s intended permission override and lets the server fall back to its own defaults, which can change both capability and safety semantics for remote sessions.

---

codex/codex-rs/tui/src/chatwidget.rs

Lines 9813 to 9815 in d8c60c2

	) && !current_permission_profile
	.file_system_sandbox_policy()
	.can_write_path_with_cwd(cwd, cwd)

Avoid treating non-CWD writable profiles as read-only

The read-only preset match only checks that cwd is not writable, not that all writes are disallowed. A managed profile that can write outside cwd (for example, a specific cache directory) will still satisfy this condition and be shown as the active “Read Only” preset. That mislabels effective permissions in the /permissions UI and can mislead users into thinking write access is fully disabled.

ℹ️ 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".