(CODUX-183) Update project-manager wakeup guidance

[numnx]

🧩 Task: Update project-manager wakeup guidance

Automated task PR opened by Code UX for T04.

📋 Summary

Sprint: Sprint 183 · Scheduler Wakeups and Guidance · Task: T04

Extend scheduler wakeups so project-manager chat workers can schedule delayed follow-up messages that fire only after the originating invocation has completed, and update project-manager guidance to use that capability for sensible delayed follow-ups.

🤖 Model & Provider

Provider	Codex CLI
Model	gpt-5.5

⏱️ Timing

Started	2026-07-07 13:43:40 UTC
Finished	2026-07-07 13:47:17 UTC
Duration	3m 37s

📊 Token Usage

Metric	Value
Input tokens	61,281
Cached input tokens	805,248
Output tokens	5,848
Total tokens	872,377
Invocations	1
Tool calls	31
Active time	2m 40s

Included usage estimate (subscription/local login): $0.88

✅ QA Review

⏳ QA review runs after this PR is opened. Check the task card in the dashboard for the outcome once it lands.

📝 Full Task Prompt

## Objective
Update the project-manager chat instructions so virtual MCP-capable workers choose `manage_scheduler.schedule_wakeup` for sensible delayed follow-ups instead of pretending they can wait inside a completed reply.

## Scope
- src/services/chat-reply-prompt.ts
- tests/backend/services/chat-reply-prompt.test.ts

## Implementation Requirements
1. Add `scheduler` to the JSON-action output domain list in `buildJsonOutputInstructions` so non-native structured management actions can propose scheduler actions.
2. Add `scheduler` to the native MCP tool domain list in `buildMcpNativeOutputInstructions`, including `list`, `schedule_wakeup`, `schedule_chat`, `schedule_sprint`, `schedule_quicksprint`, `update`, `delete`, and `run_due` at the same detail level as neighboring domains.
3. Add explicit guidance that when the user asks to be reminded, to resume after some time, to check back after task completion, or to wake up after X seconds, the project manager should call `manage_scheduler` with `action: "schedule_wakeup"`, `projectId`, `bodyMarkdown`, and `delaySeconds` or `scheduledFor`.
4. State that wakeups scheduled from a native MCP reply are automatically associated with the current invocation and should be used for end-of-task delayed follow-ups because they will not fire until the originating invocation has completed.
5. Add tests asserting MCP-native prompts mention `schedule_wakeup`, `delaySeconds`, and current-invocation completion behavior, and JSON-mode prompts include the `scheduler` domain.

## Constraints
- Keep the existing warning that dashboard chat is reply-only and must not claim completed code changes.
- Do not instruct agents to manually sleep, hold the process open, or poll in a long-running response.
- Do not weaken approval guidance for destructive or settings actions.
- Keep prompt text concise enough that it does not dominate the chat replay prompt.

## Verification
- `pnpm exec vitest run tests/backend/services/chat-reply-prompt.test.ts`
- `pnpm run lint`
- Success means generated project-manager prompts advertise scheduler wakeups and all existing prompt behavior remains covered.

🌿 Branch Info

Base: feature/CODUX-183-scheduler-wakeups-and-guidance
Head: task/feature-codux-183-scheduler-wakeups-and-guidance-t04-codex-mrap9e4g

---

🤖 Generated by Code UX