docs(infra): CI check-name convention + no-op edited-run suppression (RIG-2791) - #663
Merged
Merged
Conversation
rigel-mintaka
force-pushed
the
compass-repo/rig-2791-ci-check-naming
branch
from
August 27, 2026 02:33
b79542f to
dff5f4b
Compare
|
Compass engineering docs preview: https://compass-repo-rig-2791-ci-che.compass-eng-docs.pages.dev Deployed from Changed pages: |
rigel-mintaka
force-pushed
the
compass-repo/rig-2791-ci-check-naming
branch
from
August 27, 2026 18:09
dff5f4b to
53b816a
Compare
…(RIG-2791) Design record for RIG-2791, ruling Matt's two-part ask on PR #591: - A (ruled A1): a slash-namespaced kebab check-name convention — every ci.yml gate job renames to `ci / <job>`; the required `CI` rollup stays `CI` so ruleset 20090117 is untouched; sibling single-job workflows take the bare kebab stem. Absorbs RIG-2739 (dogfood-e2e -> e2e). - B (goal ruled B1; mechanism open): suppress the no-op `pull_request.edited` phantom run jj-vine fires on every PR. A triggered run cannot post zero contexts, so `edited` must leave ci.yml's `types:` behind a dedicated guard workflow. The re-trigger mechanism is the one load-bearing Open Question (OQ1) — dispatch-mode recommended after a red-team surfaced two blockers in the label-bounce path (the GITHUB_TOKEN no-trigger rule; and Renovate labelling every dependency PR). Diagnosis grounded in #591's check-runs: affected detection is NOT broken — the real run ran the full TS battery green. The phantom is the second, self-skipped `edited` run double-listing contexts (incl. a raw `Moon battery (${{ matrix.group }})` and a `skipped` `CI`), a cosmetic artifact today with a latent skipped-required-as-passing false-green. Ledger-impact: adds DL-277 (naming convention) and DL-278 (edited-run suppression) under a new `## Infrastructure & CI` section. Ids are provisional against concurrent ledger appends; reconciled at merge. Co-authored-by: Matt Wilkinson <matt@rigel.build>
rigel-mintaka
force-pushed
the
compass-repo/rig-2791-ci-check-naming
branch
from
August 27, 2026 18:24
53b816a to
e104116
Compare
mattwilkinsonn
approved these changes
Aug 27, 2026
rigel-mintaka
added a commit
that referenced
this pull request
Aug 27, 2026
…ppression (RIG-2791) Implements the frozen design record `docs/designs/infra/ci/compass-ci-check-naming/design.md` (#663), ruling A1 + B1/OQ1-option-3. ## A — check-name convention Every ci.yml gate job renames to the slash-namespaced kebab form `ci / <job>`: `ci / setup`, `ci / moon (<group>)`, `ci / pgtest`, `ci / microvm`, `ci / forge`, `ci / gtk3`, `ci / e2e`, `ci / regen-fixtures`. The required `CI` rollup keeps its name, so ruleset 20090117 is untouched — branch protection still requires exactly one check. The `dogfood-e2e` job **id** renames to `e2e` (absorbing RIG-2739); the rollup's `needs:` and `needs.e2e.result` read move with it. Sibling single-job workflows take the bare kebab stem: `renovate` gains `name: renovate`, `publish` → `publish-agent-image`, `deploy` gains `name: eng-docs-deploy`. ## B — suppress the no-op `edited` phantom (OQ1 = dispatch-mode) `edited` leaves ci.yml's `types:` (now `[opened, synchronize, reopened]`), so jj-vine's every-PR body edit no longer fires a phantom run that self-skips and double-lists every check (closing the latent skipped-required-as-passing false green). The one thing `edited` bought — a fresh run on a stacked PR's base re-point — moves to a dedicated guard, `.github/workflows/pr-base-repoint.yml`: it listens to `edited`, guards on `changes.base != null` (+ same-repo head), and re-triggers ci.yml via `workflow_dispatch` carrying the PR number, then verifies a fresh run actually started (fails red if not — "loud to a log" is not loud to the gate). Dispatch-mode (OQ1 option 3) needs **no minted credential**: a default `GITHUB_TOKEN` event triggers no workflow, but `workflow_dispatch` is exempt. ci.yml gains a `workflow_dispatch.inputs.pr` input; a non-empty `pr` is the base-re-point re-trigger (gate jobs run the full battery against the recomputed `refs/pull/<pr>/merge`, which a fresh run picks up per actions/checkout#919), an empty `pr` is the existing operator-only fixture-regen lane. Every gate job's guard, its checkout `ref:`, the forge oracle's tri-event `if:`, the dogfood image-affected seed (builds from the merge tree on a re-point, never a stale `:latest`), the `CI` rollup, and the regen guard are all disambiguated on that input. ## Validation `moon ci` green (markdownlint, app-bundle build, eng-docs, ref-gates); `actionlint` clean on both workflows (zero new findings — the 9 shellcheck advisories are pre-existing bootstrap-script notes identical to main). Live gate behavior (names render once, no-op edit produces one guard context, a real base re-point produces a fresh full run) validates on this PR — T5. Spec-impact: none. Refs RIG-2791 Co-authored-by: Matt Wilkinson <matt@rigel.build>
rigel-mintaka
added a commit
that referenced
this pull request
Aug 27, 2026
…ppression (RIG-2791) Implements the frozen design record `docs/designs/infra/ci/compass-ci-check-naming/design.md` (#663), ruling A1 + B1/OQ1-option-3. ## A — check-name convention Every ci.yml gate job renames to the slash-namespaced kebab form `ci / <job>`: `ci / setup`, `ci / moon (<group>)`, `ci / pgtest`, `ci / microvm`, `ci / forge`, `ci / gtk3`, `ci / e2e`, `ci / regen-fixtures`. The required `CI` rollup keeps its name, so ruleset 20090117 is untouched — branch protection still requires exactly one check. The `dogfood-e2e` job **id** renames to `e2e` (absorbing RIG-2739); the rollup's `needs:` and `needs.e2e.result` read move with it. Sibling single-job workflows take the bare kebab stem: `renovate` gains `name: renovate`, `publish` → `publish-agent-image`, `deploy` gains `name: eng-docs-deploy`. ## B — suppress the no-op `edited` phantom (OQ1 = dispatch-mode) `edited` leaves ci.yml's `types:` (now `[opened, synchronize, reopened]`), so jj-vine's every-PR body edit no longer fires a phantom run that self-skips and double-lists every check (closing the latent skipped-required-as-passing false green). The one thing `edited` bought — a fresh run on a stacked PR's base re-point — moves to a dedicated guard, `.github/workflows/pr-base-repoint.yml`: it listens to `edited`, guards on `changes.base != null` (+ same-repo head), and re-triggers ci.yml via `workflow_dispatch` carrying the PR number, then verifies a fresh run actually started (fails red if not — "loud to a log" is not loud to the gate). Dispatch-mode (OQ1 option 3) needs **no minted credential**: a default `GITHUB_TOKEN` event triggers no workflow, but `workflow_dispatch` is exempt. ci.yml gains a `workflow_dispatch.inputs.pr` input; a non-empty `pr` is the base-re-point re-trigger (gate jobs run the full battery against the recomputed `refs/pull/<pr>/merge`, which a fresh run picks up per actions/checkout#919), an empty `pr` is the existing operator-only fixture-regen lane. Every gate job's guard, its checkout `ref:`, the forge oracle's tri-event `if:`, the dogfood image-affected seed (builds from the merge tree on a re-point, never a stale `:latest`), the `CI` rollup, and the regen guard are all disambiguated on that input. ## Validation `moon ci` green (markdownlint, app-bundle build, eng-docs, ref-gates); `actionlint` clean on both workflows (zero new findings — the 9 shellcheck advisories are pre-existing bootstrap-script notes identical to main). Live gate behavior (names render once, no-op edit produces one guard context, a real base re-point produces a fresh full run) validates on this PR — T5. Spec-impact: none. Refs RIG-2791 Co-authored-by: Matt Wilkinson <matt@rigel.build>
rigel-mintaka
added a commit
that referenced
this pull request
Aug 28, 2026
…ppression (RIG-2791) Implements the frozen design record `docs/designs/infra/ci/compass-ci-check-naming/design.md` (#663), ruling A1 + B1/OQ1-option-3. ## A — check-name convention Every ci.yml gate job renames to the slash-namespaced kebab form `ci / <job>`: `ci / setup`, `ci / moon (<group>)`, `ci / pgtest`, `ci / microvm`, `ci / forge`, `ci / gtk3`, `ci / e2e`, `ci / regen-fixtures`. The required `CI` rollup keeps its name, so ruleset 20090117 is untouched — branch protection still requires exactly one check. The `dogfood-e2e` job **id** renames to `e2e` (absorbing RIG-2739); the rollup's `needs:` and `needs.e2e.result` read move with it. Sibling single-job workflows take the bare kebab stem: `renovate` gains `name: renovate`, `publish` → `publish-agent-image`, `deploy` gains `name: eng-docs-deploy`. ## B — suppress the no-op `edited` phantom (OQ1 = dispatch-mode) `edited` leaves ci.yml's `types:` (now `[opened, synchronize, reopened]`), so jj-vine's every-PR body edit no longer fires a phantom run that self-skips and double-lists every check (closing the latent skipped-required-as-passing false green). The one thing `edited` bought — a fresh run on a stacked PR's base re-point — moves to a dedicated guard, `.github/workflows/pr-base-repoint.yml`: it listens to `edited`, guards on `changes.base != null` (+ same-repo head), and re-triggers ci.yml via `workflow_dispatch` carrying the PR number, then verifies a fresh run actually started (fails red if not — "loud to a log" is not loud to the gate). Dispatch-mode (OQ1 option 3) needs **no minted credential**: a default `GITHUB_TOKEN` event triggers no workflow, but `workflow_dispatch` is exempt. ci.yml gains a `workflow_dispatch.inputs.pr` input; a non-empty `pr` is the base-re-point re-trigger (gate jobs run the full battery against the recomputed `refs/pull/<pr>/merge`, which a fresh run picks up per actions/checkout#919), an empty `pr` is the existing operator-only fixture-regen lane. Every gate job's guard, its checkout `ref:`, the forge oracle's tri-event `if:`, the dogfood image-affected seed (builds from the merge tree on a re-point, never a stale `:latest`), the `CI` rollup, and the regen guard are all disambiguated on that input. ## Validation `moon ci` green (markdownlint, app-bundle build, eng-docs, ref-gates); `actionlint` clean on both workflows (zero new findings — the 9 shellcheck advisories are pre-existing bootstrap-script notes identical to main). Live gate behavior (names render once, no-op edit produces one guard context, a real base re-point produces a fresh full run) validates on this PR — T5. Spec-impact: none. Refs RIG-2791 Co-authored-by: Matt Wilkinson <matt@rigel.build>
rigel-mintaka
added a commit
that referenced
this pull request
Aug 28, 2026
…on (RIG-2791) Implements the frozen design record `docs/designs/infra/ci/compass-ci-check-naming/design.md` (#663), rulings A1 + B1/OQ1-option-3, plus the A4 contingency the record named. A — check-name convention (A1 + A4). GitHub renders each Actions check as `<workflow name> / <job name>`, so an embedded `ci /` job prefix under the workflow named `CI` double-rendered (`CI / ci / moon (go)`). Per the record's §A verification step, that forces A4: the workflow itself is renamed `CI` -> `ci` and every gate job takes a bare kebab name (`setup`, `moon (${{ matrix.group }})`, `pgtest`, `microvm`, `forge`, `gtk4`, `e2e`, `regen-fixtures`), rendering `ci / <job>` natively. The rollup — the sole required check — is renamed key and name `CI` -> `rollup` (rendering `ci / rollup`); nothing `needs:` it, so the key rename is inert to the graph. The `dogfood-e2e` job id becomes `e2e` (absorbs RIG-2739). Sibling workflows normalize to `<kebab workflow> / <kebab job>`: `eng-docs`/`deploy`, `agent-image`/`publish`, `renovate`/`run`, and pr-base-repoint's job to bare `guard`. The matching ruleset flip (required context `CI` -> `rollup`) ships in orion IaC (RigelBuild/orion#1907) as a coordinated cutover. B — suppress the no-op `edited` phantom (OQ1 = dispatch-mode). `edited` leaves ci.yml's `types:` (now `[opened, synchronize, reopened]`), so jj-vine's per-PR body edit no longer fires a phantom run that self-skips and double-lists every check (closing the latent skipped-required-as-passing false green). The base-re-point coverage `edited` bought moves to a dedicated guard, `.github/workflows/pr-base-repoint.yml`: it listens to `edited`, guards on `changes.base != null` (+ same-repo head), re-triggers ci.yml via `workflow_dispatch` carrying the PR number, then verifies a fresh run actually started (anchored to a pre-dispatch timestamp so a pre-existing queued run can't satisfy it). Dispatch-mode needs no minted credential: a default `GITHUB_TOKEN` event triggers no workflow, but `workflow_dispatch` is exempt. Every gate job's guard, its checkout `ref:`, the forge oracle's tri-event `if:`, the dogfood image-affected seed (builds from the merge tree on a re-point, never a stale `:latest`), the rollup, and the regen guard are disambiguated on `inputs.pr` (non-empty = base-re-point, empty = operator fixture-regen). Rebased onto #684's gtk3 -> gtk4 migration: the gtk job keeps #684's `gtk4-e2e` key / weston+xvfb two-backend gate / closure-input affected detection, with the A4 bare name (`gtk4`) and the dispatch-mode guard + checkout arm layered on; the rollup's `needs:` and shell carry both renames (`e2e` and `gtk4-e2e`). Refs RIG-2791 Co-authored-by: Matt Wilkinson <matt@rigel.build>
rigel-mintaka
added a commit
that referenced
this pull request
Aug 28, 2026
…on (RIG-2791) Implements the frozen design record `docs/designs/infra/ci/compass-ci-check-naming/design.md` (#663), rulings A1 + B1/OQ1-option-3, plus the A4 contingency the record named. A — check-name convention (A1 + A4). GitHub renders each Actions check as `<workflow name> / <job name>`, so an embedded `ci /` job prefix under the workflow named `CI` double-rendered (`CI / ci / moon (go)`). Per the record's §A verification step, that forces A4: the workflow itself is renamed `CI` -> `ci` and every gate job takes a bare kebab name (`setup`, `moon (${{ matrix.group }})`, `pgtest`, `microvm`, `forge`, `gtk4`, `e2e`, `regen-fixtures`), rendering `ci / <job>` natively. The rollup — the sole required check — is renamed key and name `CI` -> `rollup` (rendering `ci / rollup`); nothing `needs:` it, so the key rename is inert to the graph. The `dogfood-e2e` job id becomes `e2e` (absorbs RIG-2739). Sibling workflows normalize to `<kebab workflow> / <kebab job>`: `eng-docs`/`deploy`, `agent-image`/`publish`, `renovate`/`run`, and pr-base-repoint's job to bare `guard`. The matching ruleset flip (required context `CI` -> `rollup`) ships in orion IaC (RigelBuild/orion#1907) as a coordinated cutover. B — suppress the no-op `edited` phantom (OQ1 = dispatch-mode). `edited` leaves ci.yml's `types:` (now `[opened, synchronize, reopened]`), so jj-vine's per-PR body edit no longer fires a phantom run that self-skips and double-lists every check (closing the latent skipped-required-as-passing false green). The base-re-point coverage `edited` bought moves to a dedicated guard, `.github/workflows/pr-base-repoint.yml`: it listens to `edited`, guards on `changes.base != null` (+ same-repo head), re-triggers ci.yml via `workflow_dispatch` carrying the PR number, then verifies a fresh run actually started (anchored to a pre-dispatch timestamp so a pre-existing queued run can't satisfy it). Dispatch-mode needs no minted credential: a default `GITHUB_TOKEN` event triggers no workflow, but `workflow_dispatch` is exempt. Every gate job's guard, its checkout `ref:`, the forge oracle's tri-event `if:`, the dogfood image-affected seed (builds from the merge tree on a re-point, never a stale `:latest`), the rollup, and the regen guard are disambiguated on `inputs.pr` (non-empty = base-re-point, empty = operator fixture-regen). Rebased onto #684's gtk3 -> gtk4 migration: the gtk job keeps #684's `gtk4-e2e` key / weston+xvfb two-backend gate / closure-input affected detection, with the A4 bare name (`gtk4`) and the dispatch-mode guard + checkout arm layered on; the rollup's `needs:` and shell carry both renames (`e2e` and `gtk4-e2e`). Refs RIG-2791 Co-authored-by: Matt Wilkinson <matt@rigel.build>
rigel-mintaka
added a commit
that referenced
this pull request
Aug 28, 2026
…on (RIG-2791) Implements the frozen design record `docs/designs/infra/ci/compass-ci-check-naming/design.md` (#663), rulings A1 + B1/OQ1-option-3, plus the A4 contingency the record named. A — check-name convention (A1 + A4). GitHub renders each Actions check as `<workflow name> / <job name>`, so an embedded `ci /` job prefix under the workflow named `CI` double-rendered (`CI / ci / moon (go)`). Per the record's §A verification step, that forces A4: the workflow itself is renamed `CI` -> `ci` and every gate job takes a bare kebab name (`setup`, `moon (${{ matrix.group }})`, `pgtest`, `microvm`, `forge`, `gtk4`, `e2e`, `regen-fixtures`), rendering `ci / <job>` natively. The rollup — the sole required check — is renamed key and name `CI` -> `rollup` (rendering `ci / rollup`); nothing `needs:` it, so the key rename is inert to the graph. The `dogfood-e2e` job id becomes `e2e` (absorbs RIG-2739). Sibling workflows normalize to `<kebab workflow> / <kebab job>`: `eng-docs`/`deploy`, `agent-image`/`publish`, `renovate`/`run`, and pr-base-repoint's job to bare `guard`. The matching ruleset flip (required context `CI` -> `rollup`) ships in orion IaC (RigelBuild/orion#1907) as a coordinated cutover. B — suppress the no-op `edited` phantom (OQ1 = dispatch-mode). `edited` leaves ci.yml's `types:` (now `[opened, synchronize, reopened]`), so jj-vine's per-PR body edit no longer fires a phantom run that self-skips and double-lists every check (closing the latent skipped-required-as-passing false green). The base-re-point coverage `edited` bought moves to a dedicated guard, `.github/workflows/pr-base-repoint.yml`: it listens to `edited`, guards on `changes.base != null` (+ same-repo head), re-triggers ci.yml via `workflow_dispatch` carrying the PR number, then verifies a fresh run actually started (anchored to a pre-dispatch timestamp so a pre-existing queued run can't satisfy it). Dispatch-mode needs no minted credential: a default `GITHUB_TOKEN` event triggers no workflow, but `workflow_dispatch` is exempt. Every gate job's guard, its checkout `ref:`, the forge oracle's tri-event `if:`, the dogfood image-affected seed (builds from the merge tree on a re-point, never a stale `:latest`), the rollup, and the regen guard are disambiguated on `inputs.pr` (non-empty = base-re-point, empty = operator fixture-regen). Rebased onto #684's gtk3 -> gtk4 migration: the gtk job keeps #684's `gtk4-e2e` key / weston+xvfb two-backend gate / closure-input affected detection, with the A4 bare name (`gtk4`) and the dispatch-mode guard + checkout arm layered on; the rollup's `needs:` and shell carry both renames (`e2e` and `gtk4-e2e`). Refs RIG-2791 Co-authored-by: Matt Wilkinson <matt@rigel.build>
mattwilkinsonn
added a commit
that referenced
this pull request
Aug 28, 2026
…on (RIG-2791) (#686) * ci(infra): check-name convention + dispatch-mode edited-run suppression (RIG-2791) Implements the frozen design record `docs/designs/infra/ci/compass-ci-check-naming/design.md` (#663), rulings A1 + B1/OQ1-option-3, plus the A4 contingency the record named. A — check-name convention (A1 + A4). GitHub renders each Actions check as `<workflow name> / <job name>`, so an embedded `ci /` job prefix under the workflow named `CI` double-rendered (`CI / ci / moon (go)`). Per the record's §A verification step, that forces A4: the workflow itself is renamed `CI` -> `ci` and every gate job takes a bare kebab name (`setup`, `moon (${{ matrix.group }})`, `pgtest`, `microvm`, `forge`, `gtk4`, `e2e`, `regen-fixtures`), rendering `ci / <job>` natively. The rollup — the sole required check — is renamed key and name `CI` -> `rollup` (rendering `ci / rollup`); nothing `needs:` it, so the key rename is inert to the graph. The `dogfood-e2e` job id becomes `e2e` (absorbs RIG-2739). Sibling workflows normalize to `<kebab workflow> / <kebab job>`: `eng-docs`/`deploy`, `agent-image`/`publish`, `renovate`/`run`, and pr-base-repoint's job to bare `guard`. The matching ruleset flip (required context `CI` -> `rollup`) ships in orion IaC (RigelBuild/orion#1907) as a coordinated cutover. B — suppress the no-op `edited` phantom (OQ1 = dispatch-mode). `edited` leaves ci.yml's `types:` (now `[opened, synchronize, reopened]`), so jj-vine's per-PR body edit no longer fires a phantom run that self-skips and double-lists every check (closing the latent skipped-required-as-passing false green). The base-re-point coverage `edited` bought moves to a dedicated guard, `.github/workflows/pr-base-repoint.yml`: it listens to `edited`, guards on `changes.base != null` (+ same-repo head), re-triggers ci.yml via `workflow_dispatch` carrying the PR number, then verifies a fresh run actually started (anchored to a pre-dispatch timestamp so a pre-existing queued run can't satisfy it). Dispatch-mode needs no minted credential: a default `GITHUB_TOKEN` event triggers no workflow, but `workflow_dispatch` is exempt. Every gate job's guard, its checkout `ref:`, the forge oracle's tri-event `if:`, the dogfood image-affected seed (builds from the merge tree on a re-point, never a stale `:latest`), the rollup, and the regen guard are disambiguated on `inputs.pr` (non-empty = base-re-point, empty = operator fixture-regen). Rebased onto #684's gtk3 -> gtk4 migration: the gtk job keeps #684's `gtk4-e2e` key / weston+xvfb two-backend gate / closure-input affected detection, with the A4 bare name (`gtk4`) and the dispatch-mode guard + checkout arm layered on; the rollup's `needs:` and shell carry both renames (`e2e` and `gtk4-e2e`). Refs RIG-2791 Co-authored-by: Matt Wilkinson <matt@rigel.build> * fix(ci): restore gtk4-e2e job-level guard dropped in the #684 rebase (RIG-2791) The 7-conflict rebase onto #684's gtk3->gtk4 migration correctly merged the two renames everywhere except the gtk4-e2e job header, where the conflict hunk spanned both the job comment and the `if:`/`timeout-minutes:`/`env:` block and the resolution re-supplied only the comment — dropping the job-level guard entirely. Restore it in the dispatch-aware form the sibling gate jobs use (pgtest/microvm/forge-oracle): the affected gate keyed on `needs.setup.outputs.gtk4_affected`, the `timeout-minutes: 30` ceiling, and `env: TMPDIR: /tmp` (the 108-byte AF_UNIX sun_path budget the multi-window e2e needs). Without it the leg ran on every pull_request (a cost regression, not a false green — the in-step guard + the rollup's fail-closed require_gated kept correctness), had no 30m ceiling, and inherited a long TMPDIR. Refs RIG-2791 Co-authored-by: Matt Wilkinson <matt@rigel.build> --------- Co-authored-by: Matt Wilkinson <matt@rigel.build>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Design record for RIG-2791, ruling Matt's two-part ask on PR #591:
gate job renames to
ci / <job>; the requiredCIrollup staysCIsoruleset 20090117 is untouched; sibling single-job workflows take the bare
kebab stem. Absorbs RIG-2739 (dogfood-e2e -> e2e).
pull_request.editedphantom run jj-vine fires on every PR. A triggered run cannot post zero
contexts, so
editedmust leave ci.yml'stypes:behind a dedicatedguard workflow. The re-trigger mechanism is the one load-bearing Open
Question (OQ1) — dispatch-mode recommended after a red-team surfaced two
blockers in the label-bounce path (the GITHUB_TOKEN no-trigger rule; and
Renovate labelling every dependency PR).
Diagnosis grounded in #591's check-runs: affected detection is NOT broken —
the real run ran the full TS battery green. The phantom is the second,
self-skipped
editedrun double-listing contexts (incl. a rawMoon battery (${{ matrix.group }})and askippedCI), a cosmeticartifact today with a latent skipped-required-as-passing false-green.
Ledger-impact: adds DL-264 (naming convention) and DL-265 (edited-run
suppression) under a new
## Infrastructure & CIsection.Co-authored-by: Matt Wilkinson matt@rigel.build