Import can report success while retaining stale Claude hook wiring

What happened

Codex CLI /import reported success when importing a Claude Code setup, but the converted Codex hook wiring retained a stale hook snapshot. The source setup later removed a validator function and its current hook caller, while the imported Codex hook still called the deleted symbol. A valid Stop event then failed with an AttributeError.

Reproduction shape

1. Import a Claude Code setup that includes project hooks.
2. Update the source setup so a hook function and its registration are retired.
3. Keep using the imported Codex project configuration.
4. Load the current shared validator from the stale imported hook.
5. Trigger the affected hook event.

The imported configuration can still invoke the retired call even though the current source wiring no longer does.

Expected behavior

Import should perform Codex-specific post-conversion validation before reporting success. At minimum it should verify that converted hook registrations resolve, imported hook modules load against current shared dependencies, and unsupported or stale Claude-specific wiring is removed or reported as a partial import with actionable items.

Actual behavior

Import completed successfully, but the stale converted snapshot later blocked a valid workflow. There was no import-time warning that the resulting Codex configuration was not live-compatible.

Environment

• Codex CLI 0.150.1
• Source: Claude Code project customization
• Target: Codex CLI project customization

This report is intentionally reduced to the compatibility pattern and contains no private project paths or credentials.

Start at the Codex CLI /import entry point and trace project-hook conversion and the validation performed before success is reported. Inspect how converted hook registrations and shared validator dependencies are loaded. Done means stale or unsupported wiring is removed or reported with actionable import feedback before the import succeeds.