Abhinav 0452dca986 hook trust metadata and enforcement (#20321) ...

# Why

We want shared hook trust that both the app and the TUI can build on,
but the metadata is only useful if runtime behavior agrees with it. This
PR adds a single backend trust model for hooks so unmanaged hooks cannot
run until the current definition has been reviewed, while managed hooks
remain runnable and non-configurable.

# What

- persist `trusted_hash` alongside hook state in `config.toml`
- expose `currentHash` and derived `trustStatus` through `hooks/list`
- derive trust from normalized hook definitions so equivalent hooks from
`config.toml` and `hooks.json` share the same trust identity
- gate unmanaged hooks on trust before they enter the runnable handler
set

# Reviewer Notes

- key file to review is `codex-rs/hooks/src/engine/discovery.rs`
- the only **core** change is schema related

2026-05-05 19:13:55 +00:00

..

schema/generated

Support MCP tools in hooks (#18385)

2026-04-23 07:33:57 +00:00

src

hook trust metadata and enforcement (#20321)

2026-05-05 19:13:55 +00:00

BUILD.bazel

start of hooks engine (#13276)

2026-03-10 04:11:31 +00:00

Cargo.toml

Spill large hook outputs from context (#21069)

2026-05-05 05:03:18 +00:00