Regression of #42: /codex:rescue still cannot prompt via AskUserQuestion in 1.0.3

Bug

Regression of #42. In codex@1.0.3 the rescue.md frontmatter correctly lists AskUserQuestion in allowed-tools, but /codex:rescue still fails to prompt the user.

Reproduce

1. Have a resumable rescue thread from a previous session (so task-resume-candidate --json reports available: true).
2. Run /codex:rescue <task> without --fresh or --resume.
3. The command prints the two options as plain text (1. Start a new Codex thread (Recommended) / 2. Continue current Codex thread) with a note: The AskUserQuestion tool is not available in this environment. I'll present the choice as text instead.
4. The user's reply is not routed back to the command — codex-companion.mjs task is never invoked.

Expected

AskUserQuestion should render an interactive picker (as /codex:review does) and the selected option should be translated into --resume or --fresh before calling the companion.

Environment

• Claude Code on Windows 10, Git Bash
• codex plugin version 1.0.3 (installed via marketplace)
• rescue.md frontmatter currently includes:

  context: fork
  allowed-tools: Bash(node:*), AskUserQuestion
  

Suggested fix

Compare frontmatter of rescue.md with review.md — review.md declares disable-model-invocation: true and its AskUserQuestion call works. rescue.md uses context: fork instead, which appears to be the regression vector.

Consider aligning rescue.md with the working pattern from review.md, or addressing the root cause identified in #94 (remove the subagent layer entirely and call codex-companion.mjs directly from rescue.md).

Context

• #42 — original issue (fix landed but behavior regressed)
• #94 — related, suggests removing subagent layer

Compare rescue.md with review.md, focusing on their frontmatter and AskUserQuestion handling, then trace how codex-companion.mjs task is invoked. Reproduce the resumable-thread flow described in the issue. Done means /codex:rescue presents an interactive picker and routes the selection to --resume or --fresh before invoking the companion.