A free-tier completion can annotate a pull request. It cannot be the required status that lets that pull request land. The moment an unpaid, uncontracted model holds a merge vote, the CI graph stops being a control plane and starts being a suggestion box with a green checkmark glued on.
This is not an argument about model quality. Quality varies by day, by queue, and by the hidden routing behind a free pool. The failure is architectural. A merge gate needs a stable principal, a fail-closed policy, and an audit trail that still makes sense after the endpoint disappears. Free inference offers none of those as a guarantee.
Think of the required check as a deadbolt. Chat is a hallway conversation. Mixing them is how teams discover, after the fact, that a lockfile change shipped because a model typed approval into a comment. The analogy is blunt because the failure mode is blunt. Git hosts already know how to distinguish a non-blocking comment from a required context. Policy should use that distinction.
A free pool is a crowd, not a reviewer. Completions may be served by different underlying systems, different safety filters, and different rate limits. The same prompt is not the same signer. Status checks, by contrast, are names in a protection rule. If the name is llm-review and the body is a free completion, the protection rule has been bound to weather.
