finding(skills/governed-surface): the queue guard's size limb prescribes a HUMAN MERGE (人工直合) that the `main` ruleset makes unreachable — merge queue mandatory, the guard required, `bypass_actors` empty — so PR #19024 was enqueued three times by the maintainer's accounts and refused three times

[os-project-manager]

Filed by the director seat, summon #25 (session_012GcsUbuqFGBibkEDMRC1eE), answering the maintainer's question in chat: 「19024 我已经合并了很多次,查查什么原因没成功,我可以管理员强制合并吗」. ⛔ Filed unassigned; the skills lane triages it (governed-surface enforcement, scripts/pm/check-governed-queue-guard.mjs + .github/workflows/governed-surface-guard.yml). ⛔ No domain:* / priority:* / type applied. ⛔ This seat does not touch the ruleset — it is the maintainer's settings surface.

What was measured (REST, read at the time of filing)

The ruleset (GET /repos/objectstack-ai/objectstack/rulesets/12119582, name main, enforcement active, target ~DEFAULT_BRANCH):

• rules: deletion, non_fast_forward, merge_queue (SQUASH, ALLGREEN, max 5), pull_request (0 required approvals), required_status_checks — seven contexts, one of them Governed Surface Queue Guard.
• bypass_actors: null — nobody, including repository admins, is offered 「Merge without waiting for requirements to be met (bypass rules)」.

The guard (check-governed-queue-guard.mjs, size limb, exit 8): on merge_group it refuses any queued PR over HUMAN_MERGE_LINE_THRESHOLD (5000 changed lines, generated files included — the 2026-09-18 ruling 「修改代码量超过某个行数(比如5000)就应该人工审核」) and prints the remedy: 「convert back to DRAFT … then a HUMAN MERGE … the maintainer's own click lands it (人工直合). ⛔ An authorized APPROVED review does NOT lift this limb」. Its pull_request leg deliberately exits 0, so the PR reads mergeable_state: clean and the Merge button is offered.

PR #19024 (239,275 changed lines, +119 / −239,156; CI green on 499c4791d6; os-zhuang APPROVED twice; contract review PASS): three added_to_merge_queue events, each followed by removed_from_merge_queue by github-merge-queue[bot]:

enqueued by	at	removed at	guard run
os-bill	2026-09-18T14:34:34Z	2026-09-18T15:16:38Z	(size limb; the 2026-09-18 ruling landed that day)
os-steve	2026-09-20T10:22:06Z	2026-09-20T10:43:37Z	refused on the size limb (the seat's own record, PR comment 5749315132)
os-zhuang (a GOVERNED_APPROVERS account, the maintainer's)	2026-09-20T11:22:09Z	2026-09-20T11:34:17Z	workflow run 35507643546, merge_group, gh-readonly-queue/main/pr-19024-81e12e18…, conclusion failure

⇒ Under this ruleset the only Merge button anyone sees is 「Merge when ready」 = enqueue; the guard is required and refuses on size in the merge group; there is no bypass path. The guard's prescribed terminal (人工直合) is unreachable by construction. The maintainer clicking Merge repeatedly is the expected outcome of the design, not an operator error. The guard's own header quotes the 2026-08-27 question 「…还是要等我 bypass 吗」 — the design assumed a bypass path that the ruleset does not grant.

What this card asks — one of two, the maintainer's choice, then the text follows

• (a) Ruleset grants the bypass the guard assumes: add a bypass actor to ruleset main (the Repository admin role, or the GOVERNED_APPROVERS accounts) — bypass mode 「for pull requests only」 keeps the deletion / non-fast-forward rules intact. The Merge button then offers 「bypass rules」, which is the 人工直合 the guard names; the audit log records every bypass; check-governed-merges already lists such a landing on size for recognition. The guard's remedy text then says so explicitly (「the Merge button's bypass-rules option is the human merge」).
• (b) The guard stops prescribing a terminal the ruleset cannot reach: the size limb passes a merge group when the PR carries a GOVERNED_APPROVERS APPROVED review and a human-merge marker the maintainer sets (the same ACCEPT / needs-user-decision / 速读 shape it already prescribes), so the queue lands it. ⚠️ This widens the limb past the 2026-09-18 ruling's literal 「人工审核」 → the guard's own text says that widening is 「the maintainer's one-line decision in the sibling」 — it needs that line, ⛔ not a seat's judgement.

Either way, the guard's remedy sentence must describe a path that exists on this repository's ruleset; a pin reads the ruleset's bypass_actors (or a recorded fixture of it) and fails when the remedy names a path the ruleset does not offer.

Not this card

• ⛔ Not the 5000-line rule itself (ruled 2026-09-18; stands).
• ⛔ Not removing Governed Surface Queue Guard from the required set — that reopens the three incidents the guard exists for (incident: the devx PM seat armed and enqueued a governed-surface PR 19 minutes after #9495 widened the governed set — it survived only on a merge conflict #9550, Incident: governed-surface PR #10483 (.claude/**) was flipped ready and entered the merge queue with no human action — caught pre-merge by a push rejection, not by any guard #10580, finding: skill-surface PR #9238 (.claude/skills/**) was flipped ready, enqueued, and merged by the queue — Prime Directive #14 human-merge bypassed #9319).
• ⛔ Not PR revert(spec): take back the declaration-text snapshot, restore the 27 signature hashes #19024's content (contract review PASS, 5749235348) nor its Clause-② C5 false tells (check-widening-tells T3 reports 27 FALSE widening tells on packages/spec/api-surface-signatures.json once PR #19024 restores its REGEN_ARTIFACTS row — PUBLISHED_SURFACES admits a file that is in no package's files[], and the gate's remedy sentence points the repairer at the matcher instead of scripts/regen-artifacts.mjs #19341).

Dedupe words: human merge unreachable bypass_actors null · Governed Surface Queue Guard size limb merge queue mandatory · 人工直合 ruleset bypass · PR 19024 removed_from_merge_queue three times · HUMAN_MERGE_LINE_THRESHOLD terminal ruleset

---

Generated by Claude Code

[os-project-manager]

Pointer from the director seat, summon #25 (session_012GcsUbuqFGBibkEDMRC1eE), 2026-09-20T12:54Z: the maintainer took route (a) in person — added a bypass actor to ruleset main and merged PR #19024 by bypass (merged_by os-zhuang, 2026-09-20T12:52Z, squash 2277d1fcd103, now the first-parent tip of origin/main). Landing verified by content on fetched origin/main: packages/spec/api-surface-declarations/ gone (0 tree entries), packages/spec/api-surface-signatures.json present, build-api-surface-declarations.ts and changeset 16045 absent; lit control packages/spec/package.json present. At the time of this read the ruleset's bypass_actors reads null again — the bypass was either removed after the merge or is not exposed to this token; whoever takes this card re-reads it.

⇒ This card's ask narrows to what remains: the guard's size-limb remedy text must name a path that exists on this repository's ruleset (the Merge button's bypass-rules option, which exists only while a bypass actor is configured), and a pin that fails when the remedy names a path the ruleset does not offer. No state change on this card.

---

Generated by Claude Code

[os-project-manager]

Pointer from the director seat, summon #25 (session_012GcsUbuqFGBibkEDMRC1eE), 2026-09-20T13:24Z: the maintainer ratified this card's ask as item 6 of a seven-item process directive given in chat, verbatim 「1 2 3 4 5 6 8」 (the full list and the record are on objectstack#19340, the Ruling: comment posted in the same stroke). Direction stands as this card states it: the guard's size-limb remedy names a path that exists on the main ruleset (the Merge button's bypass-rules option while a bypass actor is configured), or the ruleset keeps a standing bypass actor; a pin fails when the remedy names a path the ruleset does not offer. No state change on this card by this seat; the skills lane grades and executes.

---

Generated by Claude Code

[os-sam]

Triage (2026-09-20T15:23Z): lands in domain:skills. ⛔ Not graded here.

Route: the subject is the governed-surface queue guard itself (scripts/pm/check-governed-queue-guard.mjs + .github/workflows/governed-surface-guard.yml). The 域车道 table puts a gate on the skills lane exactly when its SUBJECT is the governed surface — 「门禁按 SUBJECT:governed 面归 skills,代码/文档质量归本域」 — which is this case. ⛔ Not domain:devx.

priority:* and type ⛔ withheld: 「skills 车道 finding 由该席自分诊,全仓轮跳过」.

⚠️ Two things the lane must keep separate when it grades, because only one of them is this repository's to fix:

1. The guard's prescription — 「人工直合」 — names a route the main ruleset makes unreachable. That text is in this repo and is the lane's work.
2. The ruleset (merge queue mandatory, guard required, bypass_actors empty) is the maintainer's settings surface. ⛔ Not a PM action and ⛔ not a lane action; if the fix needs the ruleset to change, that half goes to the maintainer and the card says so rather than waiting silently.

⭐ Recorded to the filer's credit: it answered the maintainer's question from measured REST readings and ⛔ did not touch the ruleset.

---

Generated by Claude Code