Fix Codex Desktop delivery and pin Windows hooks

[tbelajonas71]

Summary

• recognize both Codex composer glyphs so Ultra sessions remain injectable
• restore/reclaim Codex Desktop hook bindings and report hook-bound delivery truthfully
• keep bound exit:timeout desktop sessions addressable while excluding genuinely stopped rows
• pin generated Windows Claude and Codex hooks to the exact installer executable, preserving configured Claude hook timeouts

Why

Codex Desktop can render U+00BB at higher reasoning levels while submitted history uses U+203A. Treating only U+203A as the prompt caused the screen parser to report old submitted text as pending input and reject every delivery. Separately, a normal hook timeout was being treated like a hard stop, and bare hcom hook commands could resolve an older executable from a long-running desktop process's PATH.

Verification

• cargo fmt --all -- --check
• cargo clippy --all-targets --all-features -- -D warnings
• cargo test --all-features -- --test-threads=1 (full suite green; real-tool/PTY tests remain opt-in/ignored as upstream defines)
• parallel-only launcher races reproduced under the default runner and all four pass individually
• focused Codex hook suite: 52/52
• focused Claude hook suite: 101/101
• live Windows Codex controls passed at both High (U+203A) and Ultra (U+00BB)