The highest-risk function to refactor next, as one work packet: score, uncovered lines, effort estimate and the commands that verify the fix. Reach for it when you want one item to act on; worklist is the same ranking as a survey.

The run's whole risk ranking: every function over its ceiling, then the queue under it ordered by ccn times recency-weighted churn. Use it to survey the repo; next_item hands out one packet from the top.

Run history, newest first: id, kind, verdict, commit and lane set. Use it to date the store or to check which commit the other tools answer from.

One function's whole context in one call: scored row, ratchet mark, uncovered lines, duplication twins, churn and change-coupling partners. The deepest single read; explain is the slimmer history-only view.

One function's score trajectory across runs plus its ratchet mark. Use it to see whether a function is improving or decaying; brief adds the full context around the newest score.

Config and repo agreement check: typo keys, empty scopes, missing lane cwds, unresolvable runners. Run it first when any other tool answers strangely or an expected file is missing from the ranking.

File pairs that keep landing in the same commits: dependencies no import statement reveals. Use it to learn what else an edit usually drags along before touching a file.

Near-duplicate function pairs by normalized line shingles, with the containment percent. Use it before a refactor so twins get folded together instead of one copy getting fixed alone.

The debt burn-down: every open ratchet mark with its age, plus repayment velocity from git history. Use it to see whether marked debt is being paid down or piling up.