Abhinav 9ab7f4e6ac Add Windows hook command overrides (#22159) ...

# Why

Managed hook configs need a shared cross-platform shape without making
the existing `command` field polymorphic. The common case is still one
command string, with Windows needing a different entrypoint only when
the runtime is actually Windows.

Keeping `command` as the portable/default path and adding an optional
Windows override keeps the config easier to read, preserves the existing
scalar shape for non-Windows users, and avoids forcing every caller into
a `{ unix, windows }` object when only one platform needs special
handling.

# What

- Add optional `command_windows` / `commandWindows` alongside the
existing hook `command` field.
- Resolve `command_windows` only on Windows during hook discovery; other
platforms continue to use `command` unchanged.
- Keep trust hashing aligned to the effective command selected for the
current runtime.

# Docs

The Codex hooks/config reference should document `command_windows` as
the Windows-only override for command hooks.

2026-05-11 22:22:29 +00:00

..

schema/generated

Add compact lifecycle hooks (started by vincentkoc - external contrib) (#19905)

2026-05-06 18:08:31 -07:00

src

Add Windows hook command overrides (#22159)

2026-05-11 22:22:29 +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