Quick fix: a running verdict whose asks state names no ask is asked again when mesh-delivery-view's build_usage backlog shows every check stream with 0 waiting and 0 held and no unreadable row, and no step of the candidate runs; otherwise it refuses, naming the stream that holds asks. Adds the invoke mesh-delivery-view.build_usage to the checker's manifest. Thorough fix (not built): a group check asked while a lone member's own ask ran was swallowed by the checker's claim of one check per candidate; noted on issue 1373. Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h