619915de96
migrateCodexHooksMapFormat re-emitted the raw `[hooks.<X>]` path segment as the leaf TOML key of the new `[[hooks.<EVENT>]]` block. When the legacy table key was a `<file>:<event>:<line>:<col>` location identifier and the real event lived in an `event = "..."` body field, the migration emitted a header like `[[hooks."C:\\Users\\helen\\.codex\\config.toml:session_start:0:0"]]` that Codex 0.124.0+ refuses to load — causing `npx get-shit-done-cc@latest` to abort the Codex runtime install on Windows configs that pre-date AoT. Mirror the flat-AoT branch in the map-format and stale-namespaced-AoT branches: when the section body declares `event = "..."`, that name wins as the leaf key and `event` is excluded from the re-emitted handler body. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
945 B
type, pr
| type | pr |
|---|---|
| Fixed | 3346 |
Codex AoT hooks migration uses event-name leaf key, not location tuple — migrateCodexHooksMapFormat in bin/install.js re-emitted the legacy [hooks.<X>] section's path segment verbatim as the leaf TOML key of the new [[hooks.<EVENT>]] two-level nested AoT block. When the legacy table key was a <file>:<event>:<line>:<col> location identifier (with the actual event name in an event = "..." body field), the migration produced a header like [[hooks."C:\Users\helen\.codex\config.toml:session_start:0:0"]], which Codex 0.124.0+ refuses to load. The map-format and stale-namespaced-AoT branches now mirror the flat-AoT branch: when the section body declares event = "...", that name wins as the leaf key (and event is excluded from the re-emitted handler body). npx get-shit-done-cc@latest no longer aborts the Codex runtime install on Windows configs that pre-date the AoT migration. (#3346)