org-defaults: the pin job's fallback error text claims `schema` is a required check — the repo's own history says it is not

[bdelanghe]

Small, but it is a wrong claim in an error message people will read mid-incident, and it survived two PRs (#99, #100) because nobody in a session can verify the fix.

The contradiction

org-defaults.yml's pin job, in the un-brokered fallback annotation:

a github.token PR triggers no workflow runs, and schema is required on this repo, so such a PR would open and then never be mergeable

But #78's commit message records the opposite, as a measured claim:

Its header also states, measured rather than assumed, that the remaining gap is OPEN: schema is not a required status check here, because .github is absent from the ci-green ruleset.

And infra#160 quotes ci-green.json's own header scoping the ruleset to front-desk-scheduler only, with infra excluded — .github likewise unlisted. Two merges on 2026-08-03 (#97, #98) went through with no required-check gate visible, consistent with #78.

Why it was flagged rather than fixed

From a cloud session there is no way to read the live ruleset state (org endpoints are walled — the same class as infra#162's table), and .github-private#203 records that ci-green is committed but not yet applied, so even reading org/rulesets/ci-green.json settles intent, not live state. Replacing one unverified claim with another would be the exact I4 failure (docs/session-capability-invariants.md): an undated "is/is not" in a place that steers the next incident response.

Done when

Someone with settings access checks whether schema is a required status check on this repo, then either:

• it is not (expected): reword the annotation — the consequence of the fallback is "PR opens but the recursion guard means no pull_request run appears on it", not "never mergeable"; or
• it is (ci-green got applied and widened since bootstrap-pin: generate the pin, stop failing PRs that cannot fix it, and terminate #78): the text is right, add a dated note beside it saying when that became true.

Either way the claim gets a date and a method, which is what it is missing.

Context

• bootstrap-pin: generate the pin, stop failing PRs that cannot fix it, and terminate #78 — the measured "not required" claim
• pin: stop using a token the scope assertion just rejected (#87) #99 — where this was flagged instead of silently edited ("One thing I did not change")
• infra#160, .github-private#203 — ci-green scope and applied-state
• docs/session-capability-invariants.md I4 — a "cannot"/"is" is a claim with a date and a method