Skip to content

Commit cf492d7

Browse files
committed
wip: instruction surfaces and ci.yml prose follow the Dogfood Regression Gate row
Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017ihL2ebbZkr2QAEG1x7UC8
1 parent 529c4de commit cf492d7

4 files changed

Lines changed: 19 additions & 21 deletions

File tree

‎.claude/skills/pm-dispatch/references/platform-readings.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -385,9 +385,9 @@
385385
- 强制档不因临缺授权降档:临缺非退役,退役唯维护者裁;不达档起隔离达档子代理或等档。
386386
- 本车道强制多是过宽的回忆:`dispatch-gates.mjs --tier PATH` 逐路径现推,路径线是下限非放行。
387387
- 该脚本只答自己那棵树:姊妹仓路径回 absent from this tree,姊妹仓的档位与条款②只能手推。
388-
- required checks 的名单是每仓事实,objectstack 十个:
389-
`TypeScript Type Check` · `Lint & Repo Gates` · `Test Core` · `Build Core` · `Lint UI` ·
390-
`Governed Surface Queue Guard` · `Type Check UI` · `Test UI` · `Build & E2E UI` · `Live E2E UI`。
388+
- required checks 的名单是每仓事实,objectstack 十一个:
389+
`TypeScript Type Check` · `Lint & Repo Gates` · `Test Core` · `Build Core` · `Lint UI` · `Test UI` ·
390+
`Governed Surface Queue Guard` · `Type Check UI` · `Build & E2E UI` · `Live E2E UI` · `Dogfood Regression Gate`。
391391
- ⭐ 本表的 `mustName` 声明 `statesTheSet` ⇒ 必须逐字等于注册表,加注册行不跟改本表即红。
392392
- ⇒ 门绿即名单逐字齐全的读数;⛔ 但数量词未钉:实测 七→六 照绿,只能手跟改。
393393
- ⛔ 聚合命令同样不作判定:`check:type-check-debt` 可在包级 typecheck 绿时红。

‎.github/workflows/ci.yml‎

Lines changed: 10 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -122,9 +122,8 @@ concurrency:
122122
# github.event_name != 'pull_request'
123123
#
124124
# in its `if:`, so a dogfood red shows on the queue build of the entry that
125-
# carries it rather than first on `main`'s push run after it. It is advisory
126-
# there: the context is outside the required set (below), so the queue may
127-
# merge the entry before or despite the shards.
125+
# carries it rather than first on `main`'s push run after it, and the red
126+
# ejects that entry: the context is in the required set again (below).
128127
# `main`'s 4-hourly `schedule` run, its `push` runs and an on-demand
129128
# `workflow_dispatch` carry the FULL BATTERY: all of that plus the three jobs
130129
# below that spell
@@ -139,9 +138,9 @@ concurrency:
139138
# `scripts/ci/scheduled-full-run.mjs --release-gate`). ⛔ No affected-only
140139
# dogfood filter on the queue: the shards run on every entry, through the
141140
# `core` output, which is 'true' on `merge_group` (letter C was not ruled).
142-
# The queue enforces only the ruleset's required set, and `Dogfood Regression
143-
# Gate` is outside it since #22998 (check:required-contexts' tombstone); this
144-
# file does not decide whether it rejoins.
141+
# The queue enforces only the ruleset's required set. `Dogfood Regression
142+
# Gate` left it by #22998 and rejoined it by the #30461 follow-up ruling
143+
# (ruling record 6669982756); check:required-contexts pins its row.
145144
#
146145
# Spelled as a DENY-list of the per-PR events on purpose — the filter
147146
# contract's half 1 below, applied to events: a trigger added to `on:` later
@@ -2724,8 +2723,8 @@ jobs:
27242723
overwrite: true
27252724

27262725
dogfood-gate:
2727-
# Stable check name for a SHARDED job (#3622 follow-up). Since #22998 the
2728-
# context is outside the required set (THE TWO SPEEDS above `jobs:`). On a
2726+
# Stable check name for a SHARDED job (#3622 follow-up). A required context
2727+
# again since #30461 (THE TWO SPEEDS above `jobs:`). On a
27292728
# PR both legs skip and this gate counts zero expected attestations; on a
27302729
# queue build (since #30461) the three dogfood shards run and are counted,
27312730
# while `dogfood-verify` skips and is judged with zero expected; the full
@@ -2738,10 +2737,9 @@ jobs:
27382737
# EVERY pull request in the repo sat permanently BLOCKED (mergeable, all
27392738
# checks green, merge button dead). #3622's own comment called for updating
27402739
# branch protection; keeping the contract HERE instead means a future
2741-
# shard-count change cannot deadlock the repo a second time. From #6865
2742-
# until #22998 the bare name was pinned by `check:required-contexts`; it
2743-
# left that registry with the required set, so a rename now falsifies the
2744-
# prose that names it without reddening anything — treat it as contract.
2740+
# shard-count change cannot deadlock the repo a second time. The bare name
2741+
# is pinned by `check:required-contexts` (since #6865; out of that registry
2742+
# from #22998 until #30461) — treat it as contract.
27452743
#
27462744
# Also aggregates dogfood-verify (the CLI pass that used to ride shard 1),
27472745
# so the one context still covers everything it covered before the split.

‎AGENTS.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -505,11 +505,11 @@ Even inside your own worktree, operate defensively:
505505
yet"; `in_progress` is not a pass, and arming a red PR hides it
506506
([why](docs/agents/multi-agent-discipline.md#arming-a-red-pr-hides-it)). Always read *two* things:
507507
the queue branch **and** `origin/main`. And **the queue enforces only the required
508-
set** — ten contexts block: `Lint & Repo Gates` (all `check:*` gates), `TypeScript Type Check`,
508+
set** — eleven contexts block: `Lint & Repo Gates` (all `check:*` gates), `TypeScript Type Check`,
509509
`Test Core`, `Build Core`, `Governed Surface Queue Guard`, `Lint UI`, `Type Check UI`, `Test UI`,
510-
`Build & E2E UI` and `Live E2E UI`; a check outside those ten is advisory
510+
`Build & E2E UI`, `Live E2E UI` and `Dogfood Regression Gate`; a check outside those eleven is advisory
511511
([why that matters](docs/agents/multi-agent-discipline.md#advisory-checks-ride-through)). A required context is
512-
matched by check-run name, so a rename detaches its gate silently — treat those ten names as contract.
512+
matched by check-run name, so a rename detaches its gate silently — treat those eleven names as contract.
513513
**Two speeds** — PR runs carry the fast set, queue runs add the dogfood shards; `main`'s scheduled and push runs
514514
carry the full battery ([detail](docs/agents/multi-agent-discipline.md#two-speeds-which-runs-carry-which-battery)).
515515
**Main-red:** a full-battery red is its lane's first work — triage files it under

‎docs/agents/multi-agent-discipline.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -123,7 +123,7 @@ Arming a red PR does not queue it, it hides it:
123123

124124
← [`AGENTS.md` › Multi-agent working discipline](../../AGENTS.md#multi-agent-working-discipline)
125125

126-
A check outside those ten is advisory and rides through, and an advisory red
126+
A check outside those eleven is advisory and rides through, and an advisory red
127127
that lands rides `main`'s merge ref into every later PR until stanched.
128128

129129
## Two speeds: which runs carry which battery
@@ -134,9 +134,9 @@ A check outside those ten is advisory and rides through, and an advisory red
134134
of wall per queue entry (median, 2026-11-05); `main`'s scheduled (4-hourly) and push runs
135135
carry the full battery — dogfood, e2e, `Temporal Conformance (live PG + MySQL)` — read by the publish lane before
136136
any approval. Queue runs also carry the three `Dogfood Regression Gate` shards (ruling record
137-
6663883327), so a dogfood red shows on the queue build, advisory only; `Dogfood Verify CLI`,
137+
6663883327), so a dogfood red shows on the queue build; `Dogfood Verify CLI`,
138138
Temporal Conformance and `UI Published Artifacts` stay full-battery only. The `Dogfood Regression
139-
Gate` context is outside the required set, so the queue does not hold an entry on it.
139+
Gate` context is in the required set again (ruling record 6669982756), so a dogfood red ejects the entry.
140140

141141
## Re-arm awareness
142142

0 commit comments

Comments
 (0)