(CODUX-222) Teach dashboard agents bounded planning follow-up

[numnx]

🧩 Task: Teach dashboard agents bounded planning follow-up

Automated task PR opened by Code UX for T03.

📋 Summary

Sprint: Sprint 222 · Improve planning ETA guidance · Task: T03

Give dashboard-assigned agents immediate, machine-readable planning ETA guidance, enforce one-minute in-progress rechecks without duplicate planning or settings changes, preserve terminal scheduler wakeups, and document the complete asynchronous lifecycle.

🤖 Model & Provider

Provider	Codex CLI
Model	gpt-5.6-sol

⏱️ Timing

Started	2026-07-13 19:27:46 UTC
Finished	2026-07-13 19:32:57 UTC
Duration	5m 11s

📊 Token Usage

Metric	Value
Input tokens	90,897
Cached input tokens	1,302,784
Output tokens	8,886
Total tokens	1,402,567
Invocations	1
Tool calls	22
Active time	4m 34s

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

✅ 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
Make every dashboard-assigned Project Manager follow the MCP planning guidance through success or terminal failure without treating an ETA overrun as a failed invocation.

## Scope
- Edit `.code-ux/agents/project_manager.md`
- Update `tests/backend/services/code-ux-default-assets-service.test.ts`
- Verify existing bundled-revision behavior in `tests/backend/services/agent-preset-sync-service.test.ts`
- Consume the `planningGuidance` contract defined by T01

## Implementation Requirements
1. Update the programming delegation flow so the agent reads `planningGuidance.estimatedCompletionAt`, `nextCheckAt`, `recheckIntervalMs`, `status`, and `isTerminal` from `manage_sprints` results instead of inferring completion from task absence or elapsed wall time.
2. Require one non-duplicate self-wakeup for the initial `nextCheckAt`; on `manage_sprints get` results that remain `in_progress`, schedule the next one-shot check at the returned time, which must be one minute later.
3. Explicitly forbid diagnosing failure, calling `plan` again, requeueing work, changing provider/model/settings, or presenting missing tasks as an error while planning remains non-terminal, even when the ETA has elapsed.
4. On `succeeded`, inspect generated tasks and actual auto-start state before reporting. On `failed`, `cancelled`, or `paused`, stop polling, report the terminal evidence, and do not retry or change configuration without justified recovery direction.
5. In terminal wakeup handling, list and cancel any obsolete pending planning-status wakeup created by the same agent so the existing completion/failure wakeup does not produce a later duplicate turn.
6. Strengthen the bundled-asset regression test with the ETA fields, one-minute cadence, no-resubmission rule, and terminal cleanup guidance.

## Constraints
- Preserve the broader Project Manager operating manual, approval boundaries, scheduler timing modes, and duplicate-wakeup discipline.
- Use only one-shot `scheduler_code_ux` wakeups; do not introduce recurring schedules or polling storms.
- Do not grant new tools or broaden MCP authorization.
- Preserve customized and alternately routed preset behavior handled by bundled base-update synchronization.

## Verification
- Run `pnpm exec vitest run tests/backend/services/code-ux-default-assets-service.test.ts tests/backend/services/agent-preset-sync-service.test.ts`.
- Run `pnpm run lint`.
- Confirm the bundled instructions direct initial checking at ETA, subsequent checking every minute, terminal cleanup, and no planning/settings mutation while status is in progress.

🌿 Branch Info

Base: feature/CODUX-222-improve-planning-eta-guidance
Head: task/feature-codux-22-t03-codex-a65ac484-mrjm6zzo

---

🤖 Generated by Code UX