Desktop silently skips changed project hooks pending trust with no in-app review path

Environment

• Windows
• Codex Desktop
• Bundled CLI: 0.147.0-alpha.1.2
• Project-local .codex/hooks.json
• SessionStart command hook

Reproduction

1. Mark the project trusted in ~/.codex/config.toml.
2. Add or change a project-local SessionStart hook.
3. Restart Codex Desktop.
4. Create a new task in the project.
5. Observe that the hook context is absent, with no actionable warning or

hook-review control in Desktop.

1. Run the same startup through `codex exec

--dangerously-bypass-hook-trust`; the hook completes and its context is
present.

1. Open the interactive CLI, enter /hooks, and trust the exact definition.
2. Restart Desktop and create another task; the hook now executes correctly.

Expected

Desktop should clearly report that a discovered project hook is awaiting
review and either:

• provide an in-app review/trust action; or
• explain that /hooks must be entered inside an interactive CLI using the

same CODEX_HOME.

The UI should distinguish project trust from command-hook trust.

Actual

The hook is silently skipped. Project trust appears sufficient, but a separate
definition-level approval is required through another surface. Successful hook
execution is also difficult to observe because its developer context is hidden.

Documentation suggestions

• Explicitly distinguish project trust from hook-definition trust.
• Document which surfaces can approve hooks.
• State that /hooks is an interactive CLI command, not a Desktop prompt or

codex /hooks shell command.

• Explain that any definition change invalidates the previous approval.
• Document how statusMessage is surfaced—or not surfaced—in Desktop.
• Provide a normal, non-bypassed validation procedure.