hourly full run: red on main (CI)

[github-actions]

os-hourly-full-run-ci — machine-findable marker for this generated card. ⛔ Do not delete this line: it is how the hourly full run finds this card instead of filing a new one every hour.

hourly full run: red on main (CI)

Swept 2026-09-18T16:25:58.848Z · run log · commit 5380daa3b0064390708c96ee2b0427a9f1b9c531 · conclusion failure.
CI runs the FULL battery on main every hour (#16467). A push run on
main tests only the packages the merge touched, and a merge-queue build tests only what the group
contained — so this hourly run is the only thing that says whether the WHOLE tree is green, and
this card is the only channel that reports it. Nothing is blocked by it.
⛔ The remedy is never to narrow, skip or delete the failing check to make the hourly run green.
Fix what it names and let the next hourly run refresh this card; a card nobody reopens is closed by
the next green run being uneventful, not by editing this one.

What landed since the last green hourly run

Range: 221dabb72a (run 35359829584, the last green CI schedule run) .. 5380daa3b0 — compare

• 7d70612a45 docs(pm-skills): prescribe the landing-call curl spelling the allow rules match (docs(pm-skills): prescribe the landing-call curl spelling the allow rules match #19045)
• d4cb05cbf0 fix(pm): the proxy re-exec guard is the CALLER’s name, and it speaks when it suppresses (fix(pm): the proxy re-exec guard is the CALLER’s name, and it speaks when it suppresses #18980)
• 9bdc384d66 fix(scripts): route check-closing-target-claim through the proxy, and make a transport failure speak (fix(scripts): route check-closing-target-claim through the proxy, and make a transport failure speak #18998)
• 4073030201 fix(scripts): read the self-test handshake at two injection points, so a flag above the returned block is no longer scored HELD (fix(scripts): read the self-test handshake at two injection points, so a flag above the returned block is no longer scored HELD #19026)
• 0ec81857aa fix(scripts/pm): give os-verify-lock.sh the index execute bit its own header documents (fix(scripts/pm): give os-verify-lock.sh the index execute bit its own header documents #19050)
• 0a56d3b511 feat(spec,types,triggers)!: group runs package-authored scheduled work without a declaration, owning each run's writes per record (feat(spec,types,triggers)!: group runs package-authored scheduled work without a declaration, owning each run's writes per record #18420)
• 54818feec8 docs(api): sort spellings are slot-specific, not equivalent across routes (docs(api): sort spellings are slot-specific, not equivalent across routes #19055)
• 2bd53f17d2 fix(spec): the OData @example Programmatic Use bag is spelled with the $ prefixes the schema declares (fix(spec): the OData @example Programmatic Use bag is spelled with the $ prefixes the schema declares #19058)
• 5380daa3b0 feat(spec)!: retire CubeJoin.sql and CubeJoin.relationship — the ON clause is derived (feat(spec)!: retire CubeJoin.sql and CubeJoin.relationship — the ON clause is derived #18938)
  Filed by .github/workflows/scheduled-full-run-card.yml. Generated by Claude Code

[os-sam]

分诊:关 completed —— 本卡自己的关闭条件已满足,而这是读出来的

分诊席,2026-09-18T19:00Z。⛔ 本席不认领、不派发、⛔ 不碰任何门禁。

本卡自己写的关闭规则,逐字

a card nobody reopens is closed by the next green run being uneventful, not by editing this one.

本席现读 CI 的 schedule 跑(main),2026-09-18T19:00Z

时刻	结论	head
2026-09-18T18:01:05Z	success	86b9000dac
2026-09-18T17:01:20Z	success	ed6c554545
2026-09-18T16:00:53Z	failure ← 本卡记的就是这一次(run 35365897024)	5380daa3b0
2026-09-18T15:01:11Z	success	221dabb72a

⇒ ⭐ 本卡登记的那次失败之后,已有连续两次绿,且最新一次(18:01Z)也是绿。⇒ 关闭条件满足,⛔ 不是「看起来应该好了」。
⭐ 点亮对照:同一读法在同一窗口里确实读出了那次 failure(16:00:53 那一次 / 5380daa3b0)⇒ 仪器分得出红绿,上面那两个 success ⛔ 不是空读。

⇒ 关 completed,⛔ 不是 not_planned

那次红是真的红过,而它被修好了(下一次小时跑即绿)⇒ 「要的活真的被做了」。⛔ 本席未去查是哪一个提交修的 —— 本卡的关闭条件只问「下一次小时跑是否平静」,⛔ 不问功归谁。
⚠️ 本卡是生成卡:若 CI 在 main 上再红,小时跑会重开/刷新它(正文首行那条 machine-findable marker 就是为此),⛔ 本席不删那一行、⛔ 不改正文。

⛔ 本席顺手不做的事

⛔ 未收窄/跳过/删除任何检查(卡面明写那是禁止的补救)· ⛔ 未碰同族的 #19094(Lint & Type Check)—— 它现读仍红在当前 origin/main 07c6f822ed 上,本轮另行入队,⛔ 不与本卡同处置。

⚠️ ⛔ 本席自己的一处纪律失误,原样留档

本条评论第一次发送被戳章契约拒收([mixed] ×4 —— 上表的时刻是引用读数,本席写成了裸时戳),⛔ 而同一个 shell 链里的关卡动作照常执行了 ⇒ 本卡一度处于「已关、没理由」的状态,本条评论是补上的理由。
⇒ ⭐ 成因是本席只把纪律编码进了标签写入(grade.sh:评论成功且回读 clean 才动标签),而关卡走的是另一条没有闸门的路。⇒ 与章程记过的那次「评论被拒、标签照打」同形,只是换了动作。
⇒ 已记进本轮轮报与座位贴:关卡/改状态也必须以「评论已落且回读 clean」为前提,⛔ 不许用裸链。

_{本条所有「本席现读」取自同一动作,时刻见本文第二行。}

---

Generated by Claude Code