⛔ P0:合并队列已强制但零 merge_group 订阅——队列必需集为空、不校验任何东西;今日已兑现三例带红 Type Check 合入(#3503/#3510/#3516)

[hotlong]

来源:objectstack#5617 的跨仓 required-set 审计(2026-08-07,devx 座位派发,只读)。未认领,交分诊/维护者。 立案不靠记性:维护者今日正在做 required 集配置轮,本单是 objectui 侧的行动清单。

P0 事实(全部实测)

1. 合并队列已被 ruleset 强制(AGENTS.md 的合并指引与仓库实际规则冲突:直接 gh pr merge 会被 405 拒绝,本仓已强制合并队列 #3243 实测直接 push 返 405 Changes must be made through the merge queue)。
2. 但 22 个工作流没有一个订阅 merge_group,repo-wide event=merge_group 运行数 total_count = 0(历史零次)。
3. PR 照常合入 ⇒ 队列的必需检查集必然为空 ⇒ 队列只把 PR 在当前 main 上重建后放行,不校验任何东西。
4. 今日已兑现,与 objectstack#6067→#5615 逐帧同形:ci(scripts): 用独立 tsconfig.scripts.json 给 scripts/ 补上类型门 (#3494) #3498(scripts 类型门,08-06 13:52 合入,自身全绿)在 main 留下 TS2578 → fix(collaboration): 给 CommentThread 的 "+" 表情选择器补上可访问名,而不只是 tooltip (#3478) #3503 / fix(i18n): fallback interpolation replaces all placeholder occurrences #3510 / refactor(app-shell): 删除 RecordFormPage 中不可达的 i18n defaultValue 兜底 #3516 三个 PR 在 Type Check conclusion=failure 的状态下合入 main(分别 02:15:26Z / 02:11:26Z / 02:14:09Z,三者其余检查全绿——红的是被毒化的基线)→ fix(scripts): 删除 check-doc-links 测试中已失效的 @ts-expect-error(修复净 main 上的 TS2578) #3505 事后热修。
5. 附带:Lint / Type Check / Test (shard N/4) / Build & E2E / Changeset Fixed Group Check 全部被 paths-ignore: ['**/*.md','content/**','docs/**',(apps/site/**),'.changeset/**'] 挡住——纯文档 PR 上零 check run(docs(guide): 把 building-crud-app 的两条死链改指真实存在的文档页 #3509 实证)⇒ 这些 context 现状不可直接设为必需(会永久卡死文档 PR)。
6. ⚠️ 叙述差:PR docs(agents): 把 AGENTS.md 的合并指引改写为合并队列的真实路径 (#3243) #3522(今日已验收)把 AGENTS.md 改写为「auto-merge 即入队、由队列重建落地」——在补上 merge_group 之前,「入队」不含任何校验语义,该叙述给出的是虚假安全感。

必须按顺序的三步(顺序反了 = 全仓死锁,cloud PRs #994-996 已踩过)

1. 先补触发器(纯增,不碰任何必需集):给 ci.yml / lint.yml / control-bytes.yml / docs-links.yml 加 merge_group: types: [checks_requested];推一个 PR 入队,确认 gh-readonly-queue/** 世代上真的产生了 check run。
2. 再拆路径过滤:去掉 ci.yml / lint.yml 的 paths-ignore,路径判断挪进 job 内部短路——仓内已有现成先例:ci.yml 的 Build Docs job 的 should_run 写法。改完这些 context 才「必上报」。
3. 最后才把 context 写进必需集(分支保护 + 队列)。

今天就可以安全进分支保护的只有两条(刻意无路径过滤,五种 PR 形态实测全上报):Control Byte Scan、Internal Docs Link Check。队列必需集今天一条都不要加(零 merge_group 订阅时加 = 死锁)。

⛔ 结构性永不可必需:Changeset Bump Policy(反向 paths)、Bundle Analysis(paths)、Live E2E (informational)(continue-on-error: true 恒绿——顺带:它不能充当任何保障)、Close issues referenced in other repositories(合并后才跑)。

关联

• objectstack#5617(治理锚点,含 objectstack 侧同族审计与设置面修正)
• objectstack#6067 / objectstack#6100(objectstack 侧同形事故的当日实例)
• ci(scripts): 用独立 tsconfig.scripts.json 给 scripts/ 补上类型门 (#3494) #3498 / fix(collaboration): 给 CommentThread 的 "+" 表情选择器补上可访问名,而不只是 tooltip (#3478) #3503 / fix(scripts): 删除 check-doc-links 测试中已失效的 @ts-expect-error(修复净 main 上的 TS2578) #3505 / fix(i18n): fallback interpolation replaces all placeholder occurrences #3510 / refactor(app-shell): 删除 RecordFormPage 中不可达的 i18n defaultValue 兜底 #3516(本仓今日证据链)
• AGENTS.md 的合并指引与仓库实际规则冲突:直接 gh pr merge 会被 405 拒绝,本仓已强制合并队列 #3243(队列强制的实测出处)、docs(agents): 把 AGENTS.md 的合并指引改写为合并队列的真实路径 (#3243) #3522(AGENTS.md 叙述差)
• cloud 对照:build-and-test 单 job 双集齐备 + 110 次队列重跑,零红合并——目标形态的现成样板

[claude]

Triage: pm:queue. pm-state only (objectui is a whole-repo seat; no domain:*).

Queued, not escalated — and the split matters. Steps 1 and 2 of the body are pure code in this repo (merge_group: types: [checks_requested] triggers on ci.yml / lint.yml / control-bytes.yml / docs-links.yml; then moving path filtering out of paths-ignore and into in-job short-circuits, with ci.yml's Build Docs should_run as the in-repo precedent). Those are dispatchable as filed and are the entire P0 remedy's foundation. Step 3 — writing contexts into the branch-protection and queue required sets — is a repository-settings action only the maintainer can take, and it is already in their inbox as objectstack#5617 (needs-user-decision, domain:devx). Putting the whole issue in the decision box would have parked steps 1–2 behind a settings round they are a prerequisite for; putting it all in the queue would have implied a dev can do step 3. Hence: queue the code, and the ordering constraint in the body ("顺序反了 = 全仓死锁") is an acceptance condition, not advice.

Severity is real and this repo has no priority:p0 label (objectstack does; objectui's label set does not carry it, and inventing labels nothing queries is against the protocol). Recording it here instead: three PRs merged today with Type Check at conclusion=failure (#3503 / #3510 / #3516, 02:11–02:15Z), hot-fixed by #3505 — realized damage, not a hypothetical. Treat this as front-of-queue.

Cross-repo asymmetry, measured, so nobody generalizes the wrong way: on objectstack's origin/main 4 of 22 workflows subscribe merge_group (ci.yml, lint.yml, merge-queue-triage.yml, spec-liveness-check.yml), i.e. that repo's queue does re-run checks. objectui's 0 of 22 is a genuinely different state. objectstack#6118 (the AGENTS.md rewrite there) has been cross-linked to this issue so its narrative is written from that repo's own measurement.

Dedup (three repos, open issues + PRs): no duplicate in objectui. objectstack#5617 = governance anchor (maintainer's required-set round). objectstack#6067 / #6100 = the same-shaped incidents on that side. objectstack#6121 (finding) = a workflow inviting a required-set entry it cannot satisfy — same family, different repo, deliberately not converged since each repo's workflow set and ruleset is its own.

Point 6 of the body is its own follow-up, not scope creep here: PR #3522 already landed the "auto-merge = enqueue = the sanctioned path" narrative in AGENTS.md, and until step 1 lands that narrative overstates what enqueueing guarantees. If steps 1–2 are not landing immediately, file the one-paragraph caveat separately rather than reopening #3243.

本评论来自分诊座位 Routine(#5474 试点),不构成认领。

---

Generated by Claude Code