(CODUX-147) Plan unplanned scheduled sprints before launch

[numnx]

🧩 Task: Plan unplanned scheduled sprints before launch

Automated task PR opened by Code UX for T02.

📋 Summary

Sprint: Sprint 206 · Fix: Schedule Sprints · Task: T02

Make after-sprint schedules trigger only after successful source completion and launch unplanned target sprints through planning while preserving direct starts for already planned sprints.

🤖 Model & Provider

Provider	Codex CLI
Model	gpt-5.6-sol

⏱️ Timing

Started	2026-07-11 03:42:57 UTC
Finished	2026-07-11 03:45:58 UTC
Duration	3m 1s

📊 Token Usage

Metric	Value
Input tokens	49,294
Cached input tokens	653,824
Output tokens	5,615
Total tokens	708,733
Invocations	1
Tool calls	17
Active time	2m 33s

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

✅ 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 due sprint scheduler entries choose the correct launch path based on whether the target sprint already contains tasks.

## Scope
- `src/services/scheduler-service.ts` — `SchedulerServiceDeps`, `executeEntry`, and the scheduled sprint execution path.
- `src/app/dependency-factory/dashboard-factory.ts` — wire the existing planning service into `SchedulerService`.
- `tests/backend/services/scheduler-service.test.ts` — update service fixtures and add planned-versus-unplanned dispatch regressions.

## Implementation Requirements
1. Add a narrow planning capability to the scheduler dependencies and pass the concrete `PlanningAgentService` from the dashboard dependency factory.
2. For a scheduled sprint target, inspect `projectManagementRepository.listTasks(projectId, sprintId)`: call `planningAgentService.planSprint(projectId, sprintId, { autoStart: true })` when no tasks exist, and call `executionControlService.orchestrateSprint(projectId, sprintId)` when tasks already exist.
3. Ensure the planning path does not call orchestration a second time, and add tests proving unplanned targets plan and auto-start, planned targets start directly, and planning failures flow through the existing scheduler failure handling.

## Constraints
- Preserve the existing scheduler claim, in-flight, success, and failure lifecycle.
- Do not replan or delete existing tasks, and do not change quicksprint, chat, task, node-flow, or memory-remediation execution paths.
- Use the existing planning service and `autoStart: true`; do not introduce a second planning implementation or new provider configuration contract.

## Verification
- Run `pnpm exec vitest run tests/backend/services/scheduler-service.test.ts`.
- Run `pnpm run lint`.
- Run `pnpm run build`.
- Confirm a zero-task scheduled sprint invokes planning exactly once and a task-backed sprint invokes direct orchestration without invoking planning.

🌿 Branch Info

Base: feature/CODUX-206-fix-schedule-sprints
Head: task/feature-codux-20-t02-codex-34a402af-mrftk8je

---

🤖 Generated by Code UX