fix(scan): report requests the reserve held back as unasked, not failed

The measured-cost run left 99 taint requests unasked to keep time for
arbitration and reported them as `query_failed` -- an engine that could not
answer -- because they were simply missing from the answer. They are now
`query_budget_reserved`, both as a degradation and as each question's outcome
reason, and are no longer double counted when nothing answered.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_01EmM1j46qgKMh3zqD1QMwEo
This commit is contained in:
Marius Ciepluch
2026-09-23 08:51:12 +02:00
co-authored by Claude Opus 5.5
parent 1b28465a61
commit d930f5bc69
3 changed files with 37 additions and 4 deletions
+1
View File
@@ -435,6 +435,7 @@ _COVERAGE_DEGRADATIONS: dict[str, str] = {
),
"files_unparsed": "{count} file(s) could not be parsed and are absent from the graph: {files}.",
"query_failed": "A `{kind}` query failed for {requests} region(s), so those regions were not decided.",
"query_budget_reserved": ("{requests} `{kind}` question(s) were not asked, to keep time for deciding the ones that were answered."),
"query_too_expensive": (
"{requests} `{kind}` question(s) could not be answered even when asked alone, spending up to "
"{max_seconds} s each, so those regions were not decided. This is the cost of the question, not a transient failure."