Add Windows hook command overrides

[abhinav-oai]

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.

[abhinav-oai]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Can't wait for the next one!

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

[eternal-openai]

#[serde(default, rename = "commandWindows", alias = "command_windows")]

Please add camelCase / hooks.json friendly commandWindows as an alias for this, since we allow camelCase in our tomls