bug:cptr 0.9.21 ignores `danger-full-access` for Codex

Environment

• cptr 0.9.21
• Codex running inside a Docker container
• Open WebUI using cptr
• Codex profile configured with danger-full-access

Expected behavior

When the Codex profile is configured with danger-full-access, cptr should
start Codex with that sandbox mode, for example:

codex exec --sandbox danger-full-access

Actual behavior

The Codex start path appears to map the configured approval mode to
workspace-write, even when danger-full-access is configured. The relevant
behavior appears equivalent to:

def _sandbox_for_approval(value: str) -> str:
    if value == "ask":
        return "read-only"
    return "workspace-write"

As a result, Codex starts Bubblewrap. When cptr itself runs inside Docker,
this causes nested-sandbox failures and write errors.

A direct invocation of codex exec --sandbox danger-full-access works
correctly in the same container, which suggests that the problem is in the
cptr Codex launch path rather than Docker or Codex itself.

Workaround

I patched the cptr Codex launch path so that danger-full-access is passed
through unchanged. After that change, Open WebUI works correctly and Codex no
longer starts the nested Bubblewrap sandbox.

Request

Could you confirm whether this behavior is intentional? If not, please fix the
sandbox/approval mapping so that danger-full-access is respected and passed
to Codex unchanged.

Beim Kopieren die äußeren vier Backticks am Anfang und Ende weglassen.

Start at the cptr Codex launch path and inspect the _sandbox_for_approval mapping described in the issue. Verify that danger-full-access reaches codex exec unchanged, then run the relevant project tests or a direct Codex invocation to confirm that nested Bubblewrap is avoided.