I read this as implementation of Todo 7 only - I’ll inspect the plan, Python rules, reporting code, and canonical authority seams before creating red tests.


I read this as the required red phase - the legacy weekday/KPI seam is characterized (unchanged source hash and two exact boundary tests pass), so I’ll add a real-authority synthetic-week test that fails only because the aggregate builder is absent.


I read this as green implementation after a valid red - I’ll add one descriptor-bound aggregate module, expose its typed API, and keep the legacy reporting file untouched.


I read this as recovery from a failed local refactor step - the temporary transformation emptied only the new untracked builder, so I’ll restore it through a patch, rerun the focused red/green test, and keep the extraction within the 250-line limit.


I read this as manual library QA - I’ll exercise the real registered canonical and sidecar authorities in a disposable temp root, including restart, pin disagreement, corruption, and serialized privacy checks.


I read this as verification - I’ll run the Todo 7 suite, unchanged reporting/KPI suite, Todo 3/4 profile tests, and inspect the available static gates in parallel.


I read this as completing Todo 7 with final type, evidence, and verification gates - I’ll resolve remaining workspace checks, generate the required evidence, and verify only the Todo 7 scope.


I read this as a final tooling reconciliation - I’ll make the direct summary API explicit, refresh language-server state, and rerun the affected verification.


I read this as implementation completion - Todo 7 is complete.

COMPLETED
- Added typed, privacy-safe KST Monday-Sunday aggregate builder with authority/pin fail-closed checks.
- Preserved legacy reporting unchanged (SHA-256 `1e002746...ff1d0`).
- Verified: 54 tests passed; ruff, ty, basedpyright, compileall, no-excuse, and LSP diagnostics clean.
- Evidence: `.omo/evidence/nutricoach-v140-weekly-operations/task-7-summary.json` and `task-7-summary-red.json`.


I read this as a Todo 7 repair - I’ll replace the invalid RED provenance with a self-contained manifest runner and make weight classification exact Decimal, without touching other todo scopes.


I read this as a Todo 7 repair completion - r2 meets the RED provenance and Decimal-boundary requirements.

DoneClaim: RED reproduces twice from a manifest-verified predecessor snapshot, importing `customer_reporting` before failing solely on `MISSING_WEEKLY_OPERATIONS_SUMMARY_CAPABILITY`; Green passes the same assertion. Exact `Decimal("0.3")` boundaries are directional. Verified 72 focused and 210 Todo3/4 tests, static/LSP clean, and residue absent.

Evidence: `.omo/evidence/nutricoach-v140-weekly-operations/task-7-summary-r2.json`