CLAUDE.md credits scrp-monitor-agent-idle.sh --verbose with a cap meter it does not have: the value is the host statusline, absent on whey

CLAUDE.md states: "--verbose also reads the shared 5h/7d subscription-cap meter - status line carries 5h:NN%left ->HH:MM | 7d:NN%left - use this instead of reasoning about the shared cap from API dollar pricing." That reads as a capability of this script. It is not. The script has no cap-meter code at any version through v2.8; --verbose dumps the last 4 raw pane lines, and the meter appears among them ONLY because the HOST'S statusline renders it. Measured venus 2026-09-18, --verbose nw-venus-cc: the line "Available: 5h:76% -> 08:40 - 7d:86% -> 6.7 days" is present, so the rule reads as working HERE. But the statusline is host config, not a protocol - this same file already documents (v2.5) that whey renders NO statusline at all since context-warn.sh was deleted from its working tree, and that this script therefore emits statusline=absent there. On whey the documented instruction silently returns nothing, and the agent following it cannot see that it got a degraded answer, because --verbose prints whatever the pane had. This is the "verify the primitive before writing a rule that requires it" class: a convention loses to the primitive every time, and the cost is invisible to the agent following the documented path. Two ways out, and it is a decision, not a defect: (a) amend the CLAUDE.md sentence to say the meter comes from the host statusline and is absent where no statusline renders; or (b) make it true - parse the Available: line into a first-class field (e.g. cap_5h= cap_7d=) and emit cap=absent where the statusline does not render it, which is the same shape as the existing statusline=absent and codex_status=absent fields. I own the script; I do not own the venus CLAUDE.md wording, and the claim is fleet-wide, so route (a) needs nw-venus-cc and the CLAUDE.md-routing rule. Raised by the reviewer during OPS-267 and filed rather than rediscovered later.