Add presentation hint for quiet managed hooks

[abhinav-oai]

Why

Hooks can run on every turn, which makes routine hook activity noisy in the client. Admins may want to silence hooks such that they're only surfaces when there are E.rrors or other "steering" actions like a Block or Feedback.

What

• add a per-hook visibility_hint with the narrow shape default | hidden
• allow hidden to take effect only for managed hook sources, keeping the user-facing hook config surface unchanged
• thread the hint through hook config, runtime summaries, and app-server notifications
• keep trust hashing stable by excluding this presentation-only hint from hook identity normalization

Reviewer Note

Most of the diff is just plumbing, the key file to review is codex-rs/tui/src/history_cell/hook_cell.rs

Presentation rules

Hook visibility	Hook outcome	Transcript behavior
default	running	Only render while running.
default	completed with no entries	Do not render a completed row.
default	all else	Render exactly as reported.
hidden	running	Do not render the running row.
hidden	completed with no displayable entries	Do not render a completed row.
hidden	completed with only Context entries	Do not render a completed row.
hidden	completed with Context plus user-facing output such as Warning	Render the hook row and keep only the user-facing entries.
hidden	Blocked, Failed, or Stopped	Always render so the transcript explains consequential hook behavior.

[abhinav-oai]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3648614f8c

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

[lukehinds]

I really wish this issue were given some priority - its a real mess of a UX having the tool dump its output every call.