(CODUX-142) Wire weighted progress into sprint summaries

[numnx]

🧩 Task: Wire weighted progress into sprint summaries

Automated task PR opened by Code UX for T02.

📋 Summary

Sprint: Sprint 204 · Sprint Progress · Task: T02

Expose live weighted sprint completion using task lifecycle stages and coding tool-call telemetry, preserve raw completed-task counts, and refresh/render fractional progress accurately across the dashboard and documentation.

🤖 Model & Provider

Provider	Codex CLI
Model	gpt-5.6-sol

⏱️ Timing

Started	2026-07-11 02:30:17 UTC
Finished	2026-07-11 02:34:59 UTC
Duration	4m 42s

📊 Token Usage

Metric	Value
Input tokens	102,470
Cached input tokens	1,491,200
Output tokens	9,285
Total tokens	1,602,955
Invocations	1
Tool calls	26
Active time	4m 20s

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

✅ 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 sprint summary hydration so `SprintRecord.completion` reports weighted progress from task state and coding tool calls instead of counting only fully completed tasks.

## Scope
- `src/repositories/project-management/sprint-summary-query.ts`
- `src/repositories/project-management-repository.ts` in `mapSprintRow` and related aggregation types
- `tests/backend/repositories/project-management-repository.test.ts`
- Consume the calculator from `src/domain/sprint/sprint-progress.ts` produced by T01

## Implementation Requirements
1. Extend the batched sprint aggregation to load each task's status, `is_merged`, `merge_indicator`, and the sum of `provider_invocations.tool_call_count` for that task where `purpose = 'task_coding'`; exclude planning, CI-fix, QA, and unrelated invocation telemetry.
2. Calculate the sprint percentage from the task-level helper, round only to one decimal place, clamp the result to `0..100`, and return `0` for sprints with no tasks.
3. Keep `tasksCount` and the existing fully completed task semantics unchanged so task-counter copy remains a raw completed/total count.
4. Extend repository tests to cover a ten-task sprint with coding tool-call progress, `coding_completed` at 5%, CI at 7.5%, full completion at 10%, no-CI jumps, telemetry filtering, and the existing batched aggregation behavior; update prior integer-only expectations where one-decimal precision is now correct.

## Constraints
- Preserve the existing `SprintRecord.completion` contract as a numeric percentage; do not expose raw telemetry rows through the API.
- Keep summary reads batched through `executeChunkedInQuery`; do not introduce one query per sprint or task.
- Do not alter project-level `completedTasks` aggregation or sprint status derivation.

## Verification
- Run `pnpm run test:backend -- tests/backend/repositories/project-management-repository.test.ts tests/backend/domain/sprint/sprint-progress.test.ts`.
- Run `pnpm run typecheck`.
- Confirm the sprint collection returns fractional completion values while raw completed-task counts remain unchanged.

🌿 Branch Info

Base: feature/CODUX-204-sprint-progress
Head: task/feature-codux-20-t02-codex-cbf0afc2-mrfqyqel

---

🤖 Generated by Code UX