docs(infra): CI check-name convention + no-op edited-run suppression (RIG-2791)

docs/designs/DECISIONS.md

@@ -365,3 +365,10 @@ check enforces the mechanical half. Full rationale:
 | DL-255 | A delegated Linear session is routed to a stable Compass Manager keyed on Compass's recorded forge ownership index (`forge_authored_artifacts`, DL-055/DL-205) — NEVER a header parsed from forge text (DL-050/DL-094 forbid it reaching a routing decision); an issue with no recorded ownership row routes to the supervisor/top-level Manager via a dedicated routing channel, which decides the lane and stamps it through the DL-050 write chokepoint so later events resolve directly | Active (Matt, 2026-08-25) | [linear agent responder §Part 2](product/compass-linear-agent-responder/design.md#part-2--routing-a-delegated-linear-session-to-a-stable-manager) |
 | DL-256 | The Linear return path is a dumb link (Option B, Matt 2026-08-25): on `created` the responder emits one `thought` plus an `externalUrls` "Open in Compass" deep link to the resolved Manager's home channel and nothing else — NO activity relay, NO settle observation, NO Linear session-lifecycle machine. One Linear session is NOT forced 1-1 to a comms topic; the prompt lands in an issue-named topic (persisted in a new `linear_agent_sessions` table) delivered as `@linear`-authored deliver-rail messages deduped by `PostAsAccount`'s `client_request_id` on the `Linear-Delivery` UUID, but the deep link targets the home channel. Option C (coarse one-way status) is the ratified follow-up; Option A (full bidirectional relay) is off-table until Linear's activity vocabulary is configurable | Active (Matt, 2026-08-25) | [linear agent responder §Part 3](product/compass-linear-agent-responder/design.md#part-3--the-return-path-a-dumb-link-option-b) |
 | DL-264 | The Linear return path's `externalUrls` link is a SERVER-RESOLVED INDIRECTION URL (Matt, RIG-2794), amending DL-256's link target only: on `created` the responder sets the session external URL ONCE, immediately, to the stable post-independent `https://<public-base>/l/session/<linear-session-id>` (fits the 10s SLA; still exactly one emit per session, preserving DL-256's dumb link while removing its staleness failure mode), and a new read-only route `GET /l/session/<linear-session-id>` on the same DL-254 network TLS door reads the `linear_agent_sessions` association (for the issue coordinate only, never the stale created-time target) + resolves the DL-055 ownership index at CLICK time and 302s to the current best target (the dedicated routing channel while unrouted or issue-less, the resolved Manager's home channel once an ownership row exists); nothing rewrites the Linear session. All other DL-256 invariants survive (dumb link, no relay, no settle observation, no session-lifecycle machine, not-1-1 topic mapping). The #646 direct-link stage ships as-is; the resolver is the follow-on | Active (Matt, 2026-08-26) | [return-path indirection amendment §Approach](product/compass-linear-return-path-indirection-amendment/design.md#approach) |
+
+## Infrastructure & CI
+
+| ID | Decision | Status | Record |
+| --- | --- | --- | --- |
+| DL-269 | CI check names adopt the slash-namespaced kebab convention `ci / <job>` (`ci / setup`, `ci / moon (<group>)`, `ci / pgtest`, `ci / microvm`, `ci / forge`, `ci / gtk3`, `ci / e2e` — absorbing RIG-2739 — `ci / regen-fixtures`); the required rollup stays `CI` so ruleset 20090117 is never edited; prose glosses live in job header comments, not names; sibling single-job workflows take the bare kebab workflow stem | Active (Matt, 2026-08-26) | [CI check naming §A](infra/ci/compass-ci-check-naming/design.md#a--the-check-name-convention-a1-ruled) |
+| DL-270 | The no-op `pull_request.edited` phantom run is suppressed by split-trigger: `edited` leaves ci.yml's `types:` for a dedicated `pr-base-repoint.yml` guard workflow (re-trigger mechanism per OQ1) — a body/title edit posts one non-required skipped context instead of the full check set, so the every-PR jj-vine `edited` phantom is removed and the latent skipped-required-as-passing false green is closed for that path (fully under dispatch-mode; with a label-event residual under the label-bounce variant unless Renovate's `labels:` is dropped) | Active (Matt, 2026-08-26) | [CI check naming §B](infra/ci/compass-ci-check-naming/design.md#b--suppressing-the-no-op-edited-phantom-b1-goal-ruled-mechanism-open--oq1) |