Auto-approve DangerFullAccess patches on non-sandboxed platforms

[Sing303]

What?
Auto-approve patches when SandboxPolicy::DangerFullAccess is enabled on platforms without sandbox support.
Changes in codex-rs/core/src/safety.rs: return SafetyCheck::AutoApprove { sandbox_type: SandboxType::None } when no sandbox is available and DangerFullAccess is set.

Why?
On platforms lacking sandbox support, requiring explicit user approval despite DangerFullAccess being explicitly enabled adds friction without additional safety. This aligns behavior with the stated policy intent.

How?
Extend assess_patch_safety match:

• If get_platform_sandbox() returns Some, keep AutoApprove { sandbox_type }.
• If None and SandboxPolicy::DangerFullAccess, return AutoApprove { SandboxType::None }.
• Otherwise, fall back to AskUser.

Tests

• Local checks:

  cargo test && cargo clippy --tests && cargo fmt -- --config imports_granularity=Item

  (Additionally: just fmt, just fix -p codex-core, cargo check -p codex-core.)

Docs
No user-facing CLI changes. No README/help updates needed.

Risk/Impact
Reduces prompts on non-sandboxed platforms when DangerFullAccess is explicitly chosen; consistent with policy semantics.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[Sing303]

I have read the CLA Document and I hereby sign the CLA

[Sing303]

recheck

[aliceTheFarmer]

same problem, not fixed yet

[angeloprado]

can someone approve this? It's making windows usage overly challenging

[Sing303]

Hi @bolinfest @nornagon-openai @pakrym-oai — friendly ping for a review/decision on this PR.
Users are blocked and asking for this fix (refs: #2860, #2969, #2828, #2710).

Workflows are pending maintainer approval (so CI hasn’t run yet). The branch is up to date with main.

If you’re not the right reviewers, could you please tag the right owner? Thanks!

[febrianmosii]

yes please, this issue quite challenging, the rest is great..

[bolinfest]

Thanks for this!