Recovering native lifecycle acceptance after a retained Claude session misses the task-opening hook

A multi-client CLI release has exact candidate bytes, a verified backend, and successful native acceptance for Codex and Cursor. One retained Claude workflow repeatedly produces a substantive prose answer but never invokes the automatic task-opening hook, so the release must remain blocked. The recovery needs to preserve the original root and all failure evidence, distinguish a real native miss from a runner receipt bug, and complete the same release workflow without bypassing the native gate.

The release is paused at the npm publication checkpoint. The exact candidate archive, source binding, deployment evidence, candidate native evidence, and release record are preserved. Registry tags remain on the prior public version, and no npm publication or latest promotion occurred. The only outstanding action is completing npm web authentication before resuming the existing coordinator checkpoint; no rebuild is required.