Custom (config.toml) option disappears for never + danger-full-access

What issue are you seeing?

The Custom (config.toml) permission option disappears when config.toml contains:

approval_policy = "never"
sandbox_mode = "danger-full-access"

This affects the ChatGPT Desktop app, Codex VS Code extension, and Codex CLI.

What steps can reproduce the bug?

1. Set the configuration above.
2. Open the permission selector.
3. Custom (config.toml) is missing. With another combination, such as on-request plus workspace-write, it appears normally.

What is the expected behavior?

Keep Custom (config.toml) available, or show Full access (from config.toml).

Additional information

Version 26.727.40816 still showed Custom (config.toml) for this configuration. In 26.810.41047, only the built-in options remain. Although the configuration is effectively equivalent to Full access, the UI no longer indicates that permissions came from config.toml or provides a way to select the configuration-defined mode again.

In the comparison screenshot where Full access is shown, it was selected manually; the issue is the missing Custom (config.toml) option.

Start at the permission selector and config.toml handling in the Codex CLI, then trace the shared path used by the ChatGPT Desktop app and Codex VS Code extension. Reproduce with approval_policy = "never" and sandbox_mode = "danger-full-access", and verify that the configuration-defined option remains available or is shown as Full access from config.toml.