When a check warns

Take prose, the check over the sentences agents write to each other. There is no command for it. It runs on every build and warns. The only thing you ever do is read one file when it complains:

.hyperpower/runs/<run-id>/gates/prose.log

A real run of it, against a real contract:

understand.json  summary
  pronoun: opens on "This" with no referent named
understand.json  summary
  vague: "properly" is not checkable
understand.json  summary
  passive: "are refreshed" hides the actor
understand.json  assumptions.0.claim
  hedge: "probably" belongs in a typed field, not the sentence

Four complaints, each naming the file, the field, the rule and the word. The sentence it was reading:

This handles the login flow properly. Tokens are refreshed on expiry.

Rewritten so each complaint goes away:

loginFlow reads the cached token before it calls the auth endpoint.

Same contract, run again:

PASS - contract prose clean across 1 contract(s), 7 rule(s), in 0s

That is the whole feature. Nothing to invoke, nothing to configure on day one.

If a rule does not suit your tree

Turn it off rather than living with the noise. Every rule and word list is a config key:

gates:
  prose:
    rules_remove: [passive]
    words:
      vague_add: [flow, pipeline]

The same shape works for every check. Start a noisy one as a warning, fix the backlog, then promote it:

gates:
  lint: { enabled: true, blocking: true }