(CODUX-183) Document scheduler wakeups

[numnx]

🧩 Task: Document scheduler wakeups

Automated task PR opened by Code UX for T05.

📋 Summary

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

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:52:35 UTC
Finished	2026-07-07 13:56:15 UTC
Duration	3m 40s

📊 Token Usage

Metric	Value
Input tokens	63,627
Cached input tokens	665,344
Output tokens	6,142
Total tokens	735,113
Invocations	1
Tool calls	26
Active time	2m 50s

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

✅ 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 canonical documentation so scheduler wakeups and project-manager delayed follow-up behavior match the implemented backend contract.

## Scope
- docs/dashboard/scheduler.md
- docs/mcp/tools-and-contracts.md
- docs/architecture/chat-thread-runtime.md
- docs/index.md and docs/SUMMARY.md only if a new dedicated page is added; otherwise verify existing Scheduler links remain correct

## Implementation Requirements
1. In `docs/dashboard/scheduler.md`, add wakeups to the scheduler overview, backend contract, runtime execution list, and due-entry behavior notes.
2. In `docs/mcp/tools-and-contracts.md`, add `schedule_wakeup` to `manage_scheduler`, document `delaySeconds`, `scheduledFor`, `bodyMarkdown`, optional thread/connection/title fields, `sourceInvocationId`, and `resumeAfterInvocationCompletion`.
3. In `docs/architecture/chat-thread-runtime.md`, document that native MCP chat replies pass the current execution invocation to Code UX MCP calls and that scheduler wakeups created during that reply defer until the invocation reaches `completed`.
4. Include one concise example payload for an explicit wakeup after X seconds and one example for a scheduled ISO wakeup.
5. Cross-check terminology so docs consistently call the feature `wakeup` and do not imply recurring wakeups are required for the core use case.

## Constraints
- Do not edit generated docs-release or docs-web copies unless the repository already documents a required generation workflow for this change.
- Do not claim dashboard UI support for creating wakeups unless a UI task has added it.
- Do not claim checks passed unless they were actually run by the worker.
- Keep docs source-of-truth under `docs/`.

## Verification
- `pnpm run lint`
- Manually verify `docs/dashboard/scheduler.md`, `docs/mcp/tools-and-contracts.md`, and `docs/architecture/chat-thread-runtime.md` mention `schedule_wakeup` consistently.
- Success means documentation explains both explicit delayed wakeups and invocation-completion gated wakeups without contradicting existing scheduler behavior.

🌿 Branch Info

Base: feature/CODUX-183-scheduler-wakeups-and-guidance
Head: task/feature-codux-183-scheduler-wakeups-and-guidance-t05-codex-mrapl43l

---

🤖 Generated by Code UX