docs(ci): the queue-build dogfood red is advisory, and the stale wall-time figure is the measured median

Contract-review should-fixes on the dogfood merge_group change: THE TWO
SPEEDS no longer says a dogfood red shows "before the merge" (the context is
outside the required set, so the queue may merge first); the
check-required-contexts tombstone names the follow-up ruling's two-step path
back into the required set; the discipline doc's "10 minutes of wall per queue
entry" becomes the measured ~20 minute median.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017ihL2ebbZkr2QAEG1x7UC8

Author: claude

.github/workflows/ci.yml

@@ -122,7 +122,9 @@ concurrency:
 #     github.event_name != 'pull_request'
 #
 # in its `if:`, so a dogfood red shows on the queue build of the entry that
-# carries it, before the merge rather than on `main`'s push run after it.
+# carries it rather than first on `main`'s push run after it. It is advisory
+# there: the context is outside the required set (below), so the queue may
+# merge the entry before or despite the shards.
 # `main`'s 4-hourly `schedule` run, its `push` runs and an on-demand
 # `workflow_dispatch` carry the FULL BATTERY: all of that plus the three jobs
 # below that spell

docs/agents/multi-agent-discipline.md

@@ -130,11 +130,11 @@ A check outside those ten is advisory and rides through, and an advisory red
 
 ← [`AGENTS.md` › Multi-agent working discipline](../../AGENTS.md#multi-agent-working-discipline)
 
-**Two speeds** (ruling record 6120820653): PR and queue runs carry the fast set, 10 minutes of
-   wall per queue entry; `main`'s scheduled (4-hourly) and push runs carry the full battery — dogfood, e2e,
-   `Temporal Conformance (live PG + MySQL)` — read by the publish lane before
+**Two speeds** (ruling record 6120820653): PR and queue runs carry the fast set, about 20 minutes
+   of wall per queue entry (median, 2026-11-05); `main`'s scheduled (4-hourly) and push runs
+   carry the full battery — dogfood, e2e, `Temporal Conformance (live PG + MySQL)` — read by the publish lane before
    any approval. Queue runs also carry the three `Dogfood Regression Gate` shards (ruling record
-   6663883327), so a dogfood red shows on the queue build before the merge; `Dogfood Verify CLI`,
+   6663883327), so a dogfood red shows on the queue build, advisory only; `Dogfood Verify CLI`,
    Temporal Conformance and `UI Published Artifacts` stay full-battery only. The `Dogfood Regression
    Gate` context is outside the required set, so the queue does not hold an entry on it.
 

scripts/check-required-contexts.mjs

@@ -384,11 +384,14 @@ const UNATTRIBUTED_BATTERY = '(no battery open)';
  * RETIRED_CONTEXT_NAMES row, for the reason the `Build Docs` / `Console Pin
  * Gate` tombstone above gives: neither name is dead — both jobs still publish
  * these check-runs on every full-battery run, and the instruction files name
- * them correctly as full-battery jobs.
+ * where each runs.
  * Since #30461 (ruling record 6663883327, letter B) the three dogfood shards
  * also run on `merge_group`, so a queue build publishes `Dogfood Regression
- * Gate` over their credentials; the context stays out of this registry and
- * of the ruleset until a ruling puts it back, which that ruling did not do.
+ * Gate` over their credentials; `Temporal Conformance` stays full-battery
+ * only. The context stays out of this registry and of the ruleset for now: the
+ * follow-up ruling on #30461 (A, in two steps, 6669982756) puts it back only
+ * after a clean 24-hour reading of the queue builds, the row here landing
+ * first and the ruleset edit after it.
  */
 export const REQUIRED_CONTEXTS = [
   {