bdc6f2f9b8
A rule can describe an action and still be unusable when the action's input has no source. That is what happened here: the acceptance-side rules were amended three times before the wording could be executed. Add rule one, item four: a checker must print the denominator, that is how many objects it was supposed to verify, and silence is not a pass. The rule carries both halves: - output side: list every object name together with its verdict, never a bare aggregate OK - checking side: write down the expected object list first, count how many distinct objects appear in the output, then reconcile the two The object list may only come from the task description or from the dispatcher. It must never be derived from the checker's own output, because a derived list always agrees with that output and the check can then never turn red. A report whose object list is absent or has no traceable origin is treated as coverage unverified, not as passed. Task description gains a fifth required item, the expected object list. A dispatcher who omits it has not defined the denominator, and the executor must ask instead of guessing. write_scopes and any list of files an executor happened to touch are action ranges, not object lists; the two sets may be entirely disjoint. Recorded with the measured contrast that motivated it: the same checker with the list taken from its own output passes both when one side is injected and when both are; with the list fixed by the task description it fails as soon as one object is missing. The reference case is a self-check script over two role files that was only ever fed a bad sample for one of them. It reported two failures instead of four and nobody noticed, because the count itself carries no information about how many objects were covered. Wording only where the subject changed; no rule bodies from the two earlier rounds were rewritten.