🤖 refactor: reuse standard task report reminders

[ammar-agent]

Summary

This follow-up to #2986 keeps the existing awaiting_report recovery behavior but trims one special case: waiter-triggered recovery now reuses the standard completion reminder instead of carrying a separate waiter-only prompt variant.

Background

PR #2986 introduced a few paths that can re-prompt an awaiting_report task. The waiter-specific reminder text and enum branch were the odd ones out, because they duplicated the same completion-tool guidance with different copy. Reusing the normal reminder keeps the recovery path while simplifying the state machine.

Implementation

• waiter-triggered recovery still nudges awaiting_report tasks, but now reuses the default completion reminder path
• dropped the now-unused "waiter" completion-recovery reason and prompt string
• added a regression test that proves waitForAgentReport() no longer emits distinct waiter-only reminder copy

Validation

• bun test src/node/services/taskService.test.ts
• make static-check

Risks

Low. This keeps the waiter-side recovery hook intact; it only removes the separate waiter-only reminder variant.

---

Generated with mux • Model: openai:gpt-5.4 • Thinking: xhigh • Cost: $146.35

[ammar-agent]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 817568d10b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[ammar-agent]

@codex review

Please take another look.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. 👍

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".