ci: push runs on main use the affected set; an hourly scheduled run keeps the full list and files a card on red (maintainer-directed)

[claude]

Filed by the skills lane seat (session session_019RfFHiRCSs3JXLK4cwcfox, os-steve) on the maintainer's direction, 2026-09-07T02:5xZ. Surface owner stays domain:devx.

Authority (maintainer, verbatim, live PM chat 2026-09-07): 「同意你的建议，你负责执行派发所有可行的优化」, after the seat explained the hourly full run.

What

push runs on main compute the Test Core package set with --affected against the previous main commit (github.event.before), and a scheduled run every hour (schedule, minute 0) plus workflow_dispatch runs the full list. A red hourly full run opens or updates one card naming the merges since the last green hourly run.

Measured

• Every merge triggers a full push run on main that re-tests the tree the merge group just verified; of the last 60 push runs, 36 were cancelled by cancel-in-progress and the mean was 39 shard-minutes — so today's push runs cost ~90 machine-hours a day and rarely complete during busy hours, which means "main is green" is mostly unknown exactly when it matters.
• Runner wait inside merge-group runs is ~0, so this card does not speed the queue; it recovers cost and gives one complete full run per hour.

Ruling

1. The push branch of the selection script (extracted by ci: the merge queue runs the affected package set, not the full list (maintainer-directed, part A of the test-cost programme) #16453) takes github.event.before as the base; a zero sha (first push, force-push) falls back to the full list loudly.
2. schedule: '0 * * * *' and workflow_dispatch trigger the same workflow with the full list; the selection script treats schedule/workflow_dispatch as full.
3. On a red scheduled run, one card (fixed title prefix, deduplicated) with the run link and git log between the previous green scheduled run's sha and this one; the same idiom as ci: e2e and live tiers move to a nightly run on main; PR and queue runs keep unit, integration and conformance (maintainer-directed, part B tiering) #16455's nightly card.
4. The timings refresh (CI: the shard-timings file is stale for the CLI package — 672s predicted vs 28m46s measured against a 30-minute timeout, so Test Core shard 1/6 is one slow run from being killed on any PR touching the CLI #16173's command and the scheduled refresh) reads the hourly run's artifacts; say so in the workflow comment.

Serial

Blocked behind #16453 (V): same step, same script. Dispatched when V merges.

Refs #16173, #16453.

---

Generated by Claude Code

[claude]

Blocked-by: #16453

Same step and script as flight V; dispatched when V merges. Skills lane seat, 2026-09-07T02:5xZ.

---

Generated by Claude Code

[claude]

Scope gap recorded from #16496 / PR #16754 (contract review, patch round 1): this card's hourly full run must explicitly include .github/workflows/lint.yml, not only ci.yml / Test Core.

Measured on main at 5e53d73d:

• lint.yml has no schedule: trigger — its on: is push → main, pull_request, merge_group. ci(lint): Lint & Repo Gates is the merge-group critical path after #16453; run each gate family only on the paths it reads (PM dispatch-gates self-test 518 s first) #16496's card ruling 1 says "push on main and the hourly full run (ci: push runs on main use the affected set; an hourly scheduled run keeps the full list and files a card on red (maintainer-directed) #16467) keep the full battery", but no hourly run of Lint & Type Check exists today.
• The push-on-main run of Lint & Type Check is the only post-merge full-battery run of the families ci(lint): run each scoped Lint & Repo Gates family only on the paths it reads #16754 scopes on merge groups (PM dispatch-gates self-test, both ratchets, verify-lock self-test, comment-mask corpus), and it is cancel-in-progress — this card's own measurement has 36 of 60 push runs cancelled.
• No workflow consumes a red push-main run of Lint & Type Check: merge-queue-triage.yml listens to workflows: [CI] only. A scoped family that goes red on main after a group skipped it has no filer.

What #16754 does about it: the selector runs every family for any event other than merge_group / pull_request, so the moment lint.yml gains a schedule: trigger the full battery runs there with no further change. What this card owes, so #16496's acceptance item 3 ("a scoped family that goes red on the hourly full run files the same deduplicated card shape #16455's nightly uses") is reachable: the hourly schedule on lint.yml as well as ci.yml, and a red-run card filer that watches Lint & Type Check as well as CI.

⛔ Nothing on this card was changed by this note beyond the record; the ruling on how to fold lint.yml in stays with the PM.

---

Generated by Claude Code