Claude Project Tracker

refreshed 2026-10-09 00:19:20Z

What's pending across every project

1 open · sorted by priority then due-date
priority all urgent high low
Filtered by tag diagnostic  clear
todo high
Diagnose why coverage and mutation tasks never dispatch (22-26 metrics dark per run)
Every one of the 12 runs reviewed reports Coverlet, altcover, nyc, vitest, Stryker.NET and StrykerJS producing nothing. That is the entire "are the tests any good?" half of the product, dark in every run. Do NOT accept the claim that the capability is missing. coverlet_runner.py:159-162 runs `dotnet test --collect:"XPlat Code Coverage"`, and altcover_runner.py, stryker_net_runner.py, stryker_ts_runner.py and vitest_coverage_runner.py all exist. Adding a new harness would duplicate working code. (One uploaded consolidated report claimed the opposite and cited runtime_planner.py:120, which is a function that caps planner loop iterations.) Steps: take one run where these rows read "planned tasks did not start", pull the planner's decision for those specific tool assignments, and establish which of three things happened — the task was never created, it was created and never leased, or it was dropped at the readiness gate. Each has a different fix. Only then write the ticket. This is fix-plan item 1.6 and is the only item where the cause is genuinely unknown.
backend/wb-cpu-worker/app/analyzers/csharp/coverlet_runner.py:159-162shared/scoring/gate_scoring.py:1692
Testable (Pramora) · testable-platform · by saravanan@scrumclaw.ai
9d ago
09-29 16:26

Add an item