mesh-delivery-gate: read mesh/check alone on a base that requires it (issue 1302, S1-S10)

Once main requires mesh/check, the controller publishes no verdict for it and
the gate, which moved deliveries on the controller's checked, would hold every
pull request proposed. A head's mesh/check is now its verdict, from the
forge's status event (gitea now sends the status's words) or its open pull
requests. The Approve is asked only on the checker's verdict at exactly the
heads the ask covers, so a member judged alone never passes its group; a
group on mesh/check asks no composed check and owes no mesh/merge-gate; a
member's mesh/check that changes withdraws the ask. Nothing is asked of the
controller for such a base, and recheck refuses, naming checker_pull. hq's
mesh/repo-check keeps today's path.

modules/mesh-delivery-gate/module.json

@@ -79,6 +79,7 @@
     "mesh-delivery.groups",
     "mesh-delivery.pulls",
     "mesh-delivery-teller.answers",
+    "mesh-delivery-checker.verdicts",
     "mesh-controller.assignments",
     "node-engine.have"
   ],