Governed Surface Guard

chore(ci): slow both dependabot channels from weekly to monthly #454

Sign in to view logs

chore(ci): slow both dependabot channels from weekly to monthly

chore(ci): slow both dependabot channels from weekly to monthly #454

Workflow file for this run

.github/workflows/governed-surface-guard.yml at 92e5d3b
# The machine half of the governed-surface no-bypass rule (objectui#6596,
# maintainer ruling 2026-08-27 accepting Option C on #6325). The rule, the event
# split, the approval predicate and the exit contract all live in
# `scripts/check-governed-queue-guard.mjs`; that header is authoritative and this
# file is the invocation. Only the wiring decisions are argued here.
#
# What it is for, in one measurement: PR #6183 touched `AGENTS.md`, was correctly
# parked as a draft, and a GitHub MCP `update_pull_request` call passing only
# `reviewers` silently set `draft: false`. The pull request entered the merge
# queue and landed as `5b3290fd5` with no human approval; converting it back to a
# draft did NOT dequeue it. Nothing in this repository could have refused that —
# the whole defence was seat discipline, and the failure contained no seat
# decision at all.
name: Governed Surface Guard
on:
# BOTH legs are load-bearing and they mean DIFFERENT things — see the script
# header. `merge_group` is the leg that REFUSES: the queue build is the last
# thing between a speculative merge and `main`, and it is the path #6183 took.
# `pull_request` is an EARLY WARNING that deliberately exits 0, because a
# governed PR held as a draft for the maintainer to merge by hand is this
# regime's healthy end state, and a check that reddens on the healthy case is
# a permanently red check nobody reads.
pull_request:
# `develop` is included for the same reason every other requirable gate here
# names both: a context that does not report on a branch it could be
# required on leaves the pull request pending rather than failing it.
branches: [main, develop]
# ⚠️ Naming `types:` REPLACES GitHub's default set rather than extending it,
# so all three defaults are restated. `ready_for_review` is the addition and
# it is the point: flipping a governed draft to ready is the first move of
# the exact sequence this guard exists to interrupt, and it is not in the
# default set — without it the warning would not re-fire at the one moment a
# seat most needs to read it. `scripts/check-governed-queue-guard.mjs
# --self-test` pins this line.
types: [opened, synchronize, reopened, ready_for_review]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). This is the leg that refuses, and a
# requirable context that does not report on a queue build stalls the queue
# until the ruleset's 60-minute status-check timeout. `types:` is named
# although `checks_requested` is currently the only one GitHub defines.
merge_group:
types: [checks_requested]
# ⛔ NO `paths:` filter, on either leg, and this is not an oversight. A skipped
# job counts as SUCCESS in branch protection, so a path filter would hand the
# queue a green "Governed Surface Queue Guard" for a pull request the filter
# mis-scoped — on the one check whose entire job is to refuse. The path test
# belongs INSIDE the script, where "nothing governed" is a verdict that says so
# and costs zero API calls. (`merge_group` supports no path filter at all, so a
# filter would also make the two legs disagree about what they cover.) The
# script's `--self-test` fails if one is ever added; the same conclusion
# `control-bytes.yml` and `changeset-presence.yml` reached for themselves.
concurrency:
group: governed-surface-guard-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
# The default read scopes and nothing beyond them. `pull-requests: read` is what
# the review and head reads need; there is no write scope here, and adding one
# to let this check "fix" anything would be a widening no ruling covers.
permissions:
contents: read
pull-requests: read
jobs:
governed-surface-guard:
# ⚠️ THIS LITERAL IS THE CHECK-RUN NAME branch protection would pin, and it
# is duplicated in `CHECK_CONTEXT_NAME` in the script — deliberately, and
# pinned in both directions: the script's `--self-test` reads THIS FILE and
# fails if the two ever disagree. Renaming a job silently detaches a
# required context, and a name that lives in exactly one place is a name
# nothing can pin. It is also registered in `REQUIRED_CONTEXTS` in
# `scripts/dependabot-merge-gate.mjs`, which is this repository's own
# written-down answer to "which checks are blocking".
#
# ⛔ Making it a REQUIRED context in the live branch-protection ruleset is
# not this pull request's step and cannot be: that is a repository-settings
# surface only the maintainer can change. Until it is flipped, this job
# REPORTS on a queue build without stopping it.
name: Governed Surface Queue Guard
runs-on: ubuntu-latest
timeout-minutes: 10
steps:
- name: Checkout code
uses: actions/checkout@v7
with:
# A governed-surface question answered over a truncated history
# answers with SILENCE, and silence reads as compliance. A merge
# group's base sha can predate a shallow fetch's floor, so the whole
# history is the only depth that cannot under-report. The script
# refuses outright (exit 1) if either sha is missing, rather than
# diffing what it happens to have.
fetch-depth: 0
- name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# The self-test runs FIRST and in its own step, because it is the
# precondition for trusting the run after it: this guard's predicates
# decide whether a merge lands, so a rotted predicate must redden here
# rather than quietly wave a governed diff through. It also holds the
# wiring pins — the job name above, the triggers, `fetch-depth: 0`, the
# absent path filter, and the `REQUIRED_CONTEXTS` registration.
#
# No install and no build: the script imports node builtins and one local
# module (`scripts/invoked-as.mjs`) only, which is also what keeps it
# clear of `scripts/check-pre-install-import-graph.mjs`.
- name: Guard predicate self-test
run: node scripts/check-governed-queue-guard.mjs --self-test
# The live judgment. Everything it reads arrives through `env:` or the
# event payload on disk — no `${{ }}` interpolation into the shell line,
# so no pull-request-controlled text ever becomes part of a command.
#
# GITHUB_TOKEN is the workflow's own default token at the read scopes
# declared above; it is what makes the review read possible at all, and an
# unreadable review list is a REFUSAL with its own exit code, never a
# pass. ⛔ Fail-open is wrong in this file specifically — it exists
# because every other layer in this chain failed open.
- name: Governed surfaces may not enter the merge queue unreviewed
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: node scripts/check-governed-queue-guard.mjs
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
 Governed Surface Guard

chore(ci): slow both dependabot channels from weekly to monthly
#454
Sign in to view logs

chore(ci): slow both dependabot channels from weekly to monthly


chore(ci): slow both dependabot channels from weekly to monthly #454
Workflow file for this run

.github/workflows/governed-surface-guard.yml
 at
92e5d3b
# The machine half of the governed-surface no-bypass rule (objectui#6596,
# maintainer ruling 2026-08-27 accepting Option C on #6325). The rule, the event
# split, the approval predicate and the exit contract all live in
# `scripts/check-governed-queue-guard.mjs`; that header is authoritative and this
# file is the invocation. Only the wiring decisions are argued here.
#
# What it is for, in one measurement: PR #6183 touched `AGENTS.md`, was correctly
# parked as a draft, and a GitHub MCP `update_pull_request` call passing only
# `reviewers` silently set `draft: false`. The pull request entered the merge
# queue and landed as `5b3290fd5` with no human approval; converting it back to a
# draft did NOT dequeue it. Nothing in this repository could have refused that —
# the whole defence was seat discipline, and the failure contained no seat
# decision at all.
name: Governed Surface Guard
on:
# BOTH legs are load-bearing and they mean DIFFERENT things — see the script
# header. `merge_group` is the leg that REFUSES: the queue build is the last
# thing between a speculative merge and `main`, and it is the path #6183 took.
# `pull_request` is an EARLY WARNING that deliberately exits 0, because a
# governed PR held as a draft for the maintainer to merge by hand is this
# regime's healthy end state, and a check that reddens on the healthy case is
# a permanently red check nobody reads.
pull_request:
# `develop` is included for the same reason every other requirable gate here
# names both: a context that does not report on a branch it could be
# required on leaves the pull request pending rather than failing it.
branches: [main, develop]
# ⚠️ Naming `types:` REPLACES GitHub's default set rather than extending it,
# so all three defaults are restated. `ready_for_review` is the addition and
# it is the point: flipping a governed draft to ready is the first move of
# the exact sequence this guard exists to interrupt, and it is not in the
# default set — without it the warning would not re-fire at the one moment a
# seat most needs to read it. `scripts/check-governed-queue-guard.mjs
# --self-test` pins this line.
types: [opened, synchronize, reopened, ready_for_review]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). This is the leg that refuses, and a
# requirable context that does not report on a queue build stalls the queue
# until the ruleset's 60-minute status-check timeout. `types:` is named
# although `checks_requested` is currently the only one GitHub defines.
merge_group:
types: [checks_requested]
# ⛔ NO `paths:` filter, on either leg, and this is not an oversight. A skipped
# job counts as SUCCESS in branch protection, so a path filter would hand the
# queue a green "Governed Surface Queue Guard" for a pull request the filter
# mis-scoped — on the one check whose entire job is to refuse. The path test
# belongs INSIDE the script, where "nothing governed" is a verdict that says so
# and costs zero API calls. (`merge_group` supports no path filter at all, so a
# filter would also make the two legs disagree about what they cover.) The
# script's `--self-test` fails if one is ever added; the same conclusion
# `control-bytes.yml` and `changeset-presence.yml` reached for themselves.
concurrency:
group: governed-surface-guard-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
# The default read scopes and nothing beyond them. `pull-requests: read` is what
# the review and head reads need; there is no write scope here, and adding one
# to let this check "fix" anything would be a widening no ruling covers.
permissions:
contents: read
pull-requests: read
jobs:
governed-surface-guard:
# ⚠️ THIS LITERAL IS THE CHECK-RUN NAME branch protection would pin, and it
# is duplicated in `CHECK_CONTEXT_NAME` in the script — deliberately, and
# pinned in both directions: the script's `--self-test` reads THIS FILE and
# fails if the two ever disagree. Renaming a job silently detaches a
# required context, and a name that lives in exactly one place is a name
# nothing can pin. It is also registered in `REQUIRED_CONTEXTS` in
# `scripts/dependabot-merge-gate.mjs`, which is this repository's own
# written-down answer to "which checks are blocking".
#
# ⛔ Making it a REQUIRED context in the live branch-protection ruleset is
# not this pull request's step and cannot be: that is a repository-settings
# surface only the maintainer can change. Until it is flipped, this job
# REPORTS on a queue build without stopping it.
name: Governed Surface Queue Guard
runs-on: ubuntu-latest
timeout-minutes: 10
steps:
 - name: Checkout code
uses: actions/checkout@v7
with:
# A governed-surface question answered over a truncated history
# answers with SILENCE, and silence reads as compliance. A merge
# group's base sha can predate a shallow fetch's floor, so the whole
# history is the only depth that cannot under-report. The script
# refuses outright (exit 1) if either sha is missing, rather than
# diffing what it happens to have.
fetch-depth: 0
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# The self-test runs FIRST and in its own step, because it is the
# precondition for trusting the run after it: this guard's predicates
# decide whether a merge lands, so a rotted predicate must redden here
# rather than quietly wave a governed diff through. It also holds the
# wiring pins — the job name above, the triggers, `fetch-depth: 0`, the
# absent path filter, and the `REQUIRED_CONTEXTS` registration.
#
# No install and no build: the script imports node builtins and one local
# module (`scripts/invoked-as.mjs`) only, which is also what keeps it
# clear of `scripts/check-pre-install-import-graph.mjs`.
 - name: Guard predicate self-test
run: node scripts/check-governed-queue-guard.mjs --self-test
# The live judgment. Everything it reads arrives through `env:` or the
# event payload on disk — no `${{ }}` interpolation into the shell line,
# so no pull-request-controlled text ever becomes part of a command.
#
# GITHUB_TOKEN is the workflow's own default token at the read scopes
# declared above; it is what makes the review read possible at all, and an
# unreadable review list is a REFUSAL with its own exit code, never a
# pass. ⛔ Fail-open is wrong in this file specifically — it exists
# because every other layer in this chain failed open.
 - name: Governed surfaces may not enter the merge queue unreviewed
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: node scripts/check-governed-queue-guard.mjs

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
 Governed Surface Guard

chore(ci): slow both dependabot channels from weekly to monthly
#454
Sign in to view logs

chore(ci): slow both dependabot channels from weekly to monthly


chore(ci): slow both dependabot channels from weekly to monthly #454
Workflow file for this run

.github/workflows/governed-surface-guard.yml
 at
92e5d3b
# The machine half of the governed-surface no-bypass rule (objectui#6596,
# maintainer ruling 2026-08-27 accepting Option C on #6325). The rule, the event
# split, the approval predicate and the exit contract all live in
# `scripts/check-governed-queue-guard.mjs`; that header is authoritative and this
# file is the invocation. Only the wiring decisions are argued here.
#
# What it is for, in one measurement: PR #6183 touched `AGENTS.md`, was correctly
# parked as a draft, and a GitHub MCP `update_pull_request` call passing only
# `reviewers` silently set `draft: false`. The pull request entered the merge
# queue and landed as `5b3290fd5` with no human approval; converting it back to a
# draft did NOT dequeue it. Nothing in this repository could have refused that —
# the whole defence was seat discipline, and the failure contained no seat
# decision at all.
name: Governed Surface Guard
on:
# BOTH legs are load-bearing and they mean DIFFERENT things — see the script
# header. `merge_group` is the leg that REFUSES: the queue build is the last
# thing between a speculative merge and `main`, and it is the path #6183 took.
# `pull_request` is an EARLY WARNING that deliberately exits 0, because a
# governed PR held as a draft for the maintainer to merge by hand is this
# regime's healthy end state, and a check that reddens on the healthy case is
# a permanently red check nobody reads.
pull_request:
# `develop` is included for the same reason every other requirable gate here
# names both: a context that does not report on a branch it could be
# required on leaves the pull request pending rather than failing it.
branches: [main, develop]
# ⚠️ Naming `types:` REPLACES GitHub's default set rather than extending it,
# so all three defaults are restated. `ready_for_review` is the addition and
# it is the point: flipping a governed draft to ready is the first move of
# the exact sequence this guard exists to interrupt, and it is not in the
# default set — without it the warning would not re-fire at the one moment a
# seat most needs to read it. `scripts/check-governed-queue-guard.mjs
# --self-test` pins this line.
types: [opened, synchronize, reopened, ready_for_review]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). This is the leg that refuses, and a
# requirable context that does not report on a queue build stalls the queue
# until the ruleset's 60-minute status-check timeout. `types:` is named
# although `checks_requested` is currently the only one GitHub defines.
merge_group:
types: [checks_requested]
# ⛔ NO `paths:` filter, on either leg, and this is not an oversight. A skipped
# job counts as SUCCESS in branch protection, so a path filter would hand the
# queue a green "Governed Surface Queue Guard" for a pull request the filter
# mis-scoped — on the one check whose entire job is to refuse. The path test
# belongs INSIDE the script, where "nothing governed" is a verdict that says so
# and costs zero API calls. (`merge_group` supports no path filter at all, so a
# filter would also make the two legs disagree about what they cover.) The
# script's `--self-test` fails if one is ever added; the same conclusion
# `control-bytes.yml` and `changeset-presence.yml` reached for themselves.
concurrency:
group: governed-surface-guard-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
# The default read scopes and nothing beyond them. `pull-requests: read` is what
# the review and head reads need; there is no write scope here, and adding one
# to let this check "fix" anything would be a widening no ruling covers.
permissions:
contents: read
pull-requests: read
jobs:
governed-surface-guard:
# ⚠️ THIS LITERAL IS THE CHECK-RUN NAME branch protection would pin, and it
# is duplicated in `CHECK_CONTEXT_NAME` in the script — deliberately, and
# pinned in both directions: the script's `--self-test` reads THIS FILE and
# fails if the two ever disagree. Renaming a job silently detaches a
# required context, and a name that lives in exactly one place is a name
# nothing can pin. It is also registered in `REQUIRED_CONTEXTS` in
# `scripts/dependabot-merge-gate.mjs`, which is this repository's own
# written-down answer to "which checks are blocking".
#
# ⛔ Making it a REQUIRED context in the live branch-protection ruleset is
# not this pull request's step and cannot be: that is a repository-settings
# surface only the maintainer can change. Until it is flipped, this job
# REPORTS on a queue build without stopping it.
name: Governed Surface Queue Guard
runs-on: ubuntu-latest
timeout-minutes: 10
steps:
 - name: Checkout code
uses: actions/checkout@v7
with:
# A governed-surface question answered over a truncated history
# answers with SILENCE, and silence reads as compliance. A merge
# group's base sha can predate a shallow fetch's floor, so the whole
# history is the only depth that cannot under-report. The script
# refuses outright (exit 1) if either sha is missing, rather than
# diffing what it happens to have.
fetch-depth: 0
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# The self-test runs FIRST and in its own step, because it is the
# precondition for trusting the run after it: this guard's predicates
# decide whether a merge lands, so a rotted predicate must redden here
# rather than quietly wave a governed diff through. It also holds the
# wiring pins — the job name above, the triggers, `fetch-depth: 0`, the
# absent path filter, and the `REQUIRED_CONTEXTS` registration.
#
# No install and no build: the script imports node builtins and one local
# module (`scripts/invoked-as.mjs`) only, which is also what keeps it
# clear of `scripts/check-pre-install-import-graph.mjs`.
 - name: Guard predicate self-test
run: node scripts/check-governed-queue-guard.mjs --self-test
# The live judgment. Everything it reads arrives through `env:` or the
# event payload on disk — no `${{ }}` interpolation into the shell line,
# so no pull-request-controlled text ever becomes part of a command.
#
# GITHUB_TOKEN is the workflow's own default token at the read scopes
# declared above; it is what makes the review read possible at all, and an
# unreadable review list is a REFUSAL with its own exit code, never a
# pass. ⛔ Fail-open is wrong in this file specifically — it exists
# because every other layer in this chain failed open.
 - name: Governed surfaces may not enter the merge queue unreviewed
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: node scripts/check-governed-queue-guard.mjs

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
 Governed Surface Guard

chore(ci): slow both dependabot channels from weekly to monthly
#454
Sign in to view logs

chore(ci): slow both dependabot channels from weekly to monthly


chore(ci): slow both dependabot channels from weekly to monthly #454
Workflow file for this run

.github/workflows/governed-surface-guard.yml
 at
92e5d3b
# The machine half of the governed-surface no-bypass rule (objectui#6596,
# maintainer ruling 2026-08-27 accepting Option C on #6325). The rule, the event
# split, the approval predicate and the exit contract all live in
# `scripts/check-governed-queue-guard.mjs`; that header is authoritative and this
# file is the invocation. Only the wiring decisions are argued here.
#
# What it is for, in one measurement: PR #6183 touched `AGENTS.md`, was correctly
# parked as a draft, and a GitHub MCP `update_pull_request` call passing only
# `reviewers` silently set `draft: false`. The pull request entered the merge
# queue and landed as `5b3290fd5` with no human approval; converting it back to a
# draft did NOT dequeue it. Nothing in this repository could have refused that —
# the whole defence was seat discipline, and the failure contained no seat
# decision at all.
name: Governed Surface Guard
on:
# BOTH legs are load-bearing and they mean DIFFERENT things — see the script
# header. `merge_group` is the leg that REFUSES: the queue build is the last
# thing between a speculative merge and `main`, and it is the path #6183 took.
# `pull_request` is an EARLY WARNING that deliberately exits 0, because a
# governed PR held as a draft for the maintainer to merge by hand is this
# regime's healthy end state, and a check that reddens on the healthy case is
# a permanently red check nobody reads.
pull_request:
# `develop` is included for the same reason every other requirable gate here
# names both: a context that does not report on a branch it could be
# required on leaves the pull request pending rather than failing it.
branches: [main, develop]
# ⚠️ Naming `types:` REPLACES GitHub's default set rather than extending it,
# so all three defaults are restated. `ready_for_review` is the addition and
# it is the point: flipping a governed draft to ready is the first move of
# the exact sequence this guard exists to interrupt, and it is not in the
# default set — without it the warning would not re-fire at the one moment a
# seat most needs to read it. `scripts/check-governed-queue-guard.mjs
# --self-test` pins this line.
types: [opened, synchronize, reopened, ready_for_review]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). This is the leg that refuses, and a
# requirable context that does not report on a queue build stalls the queue
# until the ruleset's 60-minute status-check timeout. `types:` is named
# although `checks_requested` is currently the only one GitHub defines.
merge_group:
types: [checks_requested]
# ⛔ NO `paths:` filter, on either leg, and this is not an oversight. A skipped
# job counts as SUCCESS in branch protection, so a path filter would hand the
# queue a green "Governed Surface Queue Guard" for a pull request the filter
# mis-scoped — on the one check whose entire job is to refuse. The path test
# belongs INSIDE the script, where "nothing governed" is a verdict that says so
# and costs zero API calls. (`merge_group` supports no path filter at all, so a
# filter would also make the two legs disagree about what they cover.) The
# script's `--self-test` fails if one is ever added; the same conclusion
# `control-bytes.yml` and `changeset-presence.yml` reached for themselves.
concurrency:
group: governed-surface-guard-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
# The default read scopes and nothing beyond them. `pull-requests: read` is what
# the review and head reads need; there is no write scope here, and adding one
# to let this check "fix" anything would be a widening no ruling covers.
permissions:
contents: read
pull-requests: read
jobs:
governed-surface-guard:
# ⚠️ THIS LITERAL IS THE CHECK-RUN NAME branch protection would pin, and it
# is duplicated in `CHECK_CONTEXT_NAME` in the script — deliberately, and
# pinned in both directions: the script's `--self-test` reads THIS FILE and
# fails if the two ever disagree. Renaming a job silently detaches a
# required context, and a name that lives in exactly one place is a name
# nothing can pin. It is also registered in `REQUIRED_CONTEXTS` in
# `scripts/dependabot-merge-gate.mjs`, which is this repository's own
# written-down answer to "which checks are blocking".
#
# ⛔ Making it a REQUIRED context in the live branch-protection ruleset is
# not this pull request's step and cannot be: that is a repository-settings
# surface only the maintainer can change. Until it is flipped, this job
# REPORTS on a queue build without stopping it.
name: Governed Surface Queue Guard
runs-on: ubuntu-latest
timeout-minutes: 10
steps:
 - name: Checkout code
uses: actions/checkout@v7
with:
# A governed-surface question answered over a truncated history
# answers with SILENCE, and silence reads as compliance. A merge
# group's base sha can predate a shallow fetch's floor, so the whole
# history is the only depth that cannot under-report. The script
# refuses outright (exit 1) if either sha is missing, rather than
# diffing what it happens to have.
fetch-depth: 0
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# The self-test runs FIRST and in its own step, because it is the
# precondition for trusting the run after it: this guard's predicates
# decide whether a merge lands, so a rotted predicate must redden here
# rather than quietly wave a governed diff through. It also holds the
# wiring pins — the job name above, the triggers, `fetch-depth: 0`, the
# absent path filter, and the `REQUIRED_CONTEXTS` registration.
#
# No install and no build: the script imports node builtins and one local
# module (`scripts/invoked-as.mjs`) only, which is also what keeps it
# clear of `scripts/check-pre-install-import-graph.mjs`.
 - name: Guard predicate self-test
run: node scripts/check-governed-queue-guard.mjs --self-test
# The live judgment. Everything it reads arrives through `env:` or the
# event payload on disk — no `${{ }}` interpolation into the shell line,
# so no pull-request-controlled text ever becomes part of a command.
#
# GITHUB_TOKEN is the workflow's own default token at the read scopes
# declared above; it is what makes the review read possible at all, and an
# unreadable review list is a REFUSAL with its own exit code, never a
# pass. ⛔ Fail-open is wrong in this file specifically — it exists
# because every other layer in this chain failed open.
 - name: Governed surfaces may not enter the merge queue unreviewed
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: node scripts/check-governed-queue-guard.mjs

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
 Governed Surface Guard

chore(ci): slow both dependabot channels from weekly to monthly
#454
Sign in to view logs

chore(ci): slow both dependabot channels from weekly to monthly


chore(ci): slow both dependabot channels from weekly to monthly #454
Workflow file for this run

.github/workflows/governed-surface-guard.yml
 at
92e5d3b
# The machine half of the governed-surface no-bypass rule (objectui#6596,
# maintainer ruling 2026-08-27 accepting Option C on #6325). The rule, the event
# split, the approval predicate and the exit contract all live in
# `scripts/check-governed-queue-guard.mjs`; that header is authoritative and this
# file is the invocation. Only the wiring decisions are argued here.
#
# What it is for, in one measurement: PR #6183 touched `AGENTS.md`, was correctly
# parked as a draft, and a GitHub MCP `update_pull_request` call passing only
# `reviewers` silently set `draft: false`. The pull request entered the merge
# queue and landed as `5b3290fd5` with no human approval; converting it back to a
# draft did NOT dequeue it. Nothing in this repository could have refused that —
# the whole defence was seat discipline, and the failure contained no seat
# decision at all.
name: Governed Surface Guard
on:
# BOTH legs are load-bearing and they mean DIFFERENT things — see the script
# header. `merge_group` is the leg that REFUSES: the queue build is the last
# thing between a speculative merge and `main`, and it is the path #6183 took.
# `pull_request` is an EARLY WARNING that deliberately exits 0, because a
# governed PR held as a draft for the maintainer to merge by hand is this
# regime's healthy end state, and a check that reddens on the healthy case is
# a permanently red check nobody reads.
pull_request:
# `develop` is included for the same reason every other requirable gate here
# names both: a context that does not report on a branch it could be
# required on leaves the pull request pending rather than failing it.
branches: [main, develop]
# ⚠️ Naming `types:` REPLACES GitHub's default set rather than extending it,
# so all three defaults are restated. `ready_for_review` is the addition and
# it is the point: flipping a governed draft to ready is the first move of
# the exact sequence this guard exists to interrupt, and it is not in the
# default set — without it the warning would not re-fire at the one moment a
# seat most needs to read it. `scripts/check-governed-queue-guard.mjs
# --self-test` pins this line.
types: [opened, synchronize, reopened, ready_for_review]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). This is the leg that refuses, and a
# requirable context that does not report on a queue build stalls the queue
# until the ruleset's 60-minute status-check timeout. `types:` is named
# although `checks_requested` is currently the only one GitHub defines.
merge_group:
types: [checks_requested]
# ⛔ NO `paths:` filter, on either leg, and this is not an oversight. A skipped
# job counts as SUCCESS in branch protection, so a path filter would hand the
# queue a green "Governed Surface Queue Guard" for a pull request the filter
# mis-scoped — on the one check whose entire job is to refuse. The path test
# belongs INSIDE the script, where "nothing governed" is a verdict that says so
# and costs zero API calls. (`merge_group` supports no path filter at all, so a
# filter would also make the two legs disagree about what they cover.) The
# script's `--self-test` fails if one is ever added; the same conclusion
# `control-bytes.yml` and `changeset-presence.yml` reached for themselves.
concurrency:
group: governed-surface-guard-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
# The default read scopes and nothing beyond them. `pull-requests: read` is what
# the review and head reads need; there is no write scope here, and adding one
# to let this check "fix" anything would be a widening no ruling covers.
permissions:
contents: read
pull-requests: read
jobs:
governed-surface-guard:
# ⚠️ THIS LITERAL IS THE CHECK-RUN NAME branch protection would pin, and it
# is duplicated in `CHECK_CONTEXT_NAME` in the script — deliberately, and
# pinned in both directions: the script's `--self-test` reads THIS FILE and
# fails if the two ever disagree. Renaming a job silently detaches a
# required context, and a name that lives in exactly one place is a name
# nothing can pin. It is also registered in `REQUIRED_CONTEXTS` in
# `scripts/dependabot-merge-gate.mjs`, which is this repository's own
# written-down answer to "which checks are blocking".
#
# ⛔ Making it a REQUIRED context in the live branch-protection ruleset is
# not this pull request's step and cannot be: that is a repository-settings
# surface only the maintainer can change. Until it is flipped, this job
# REPORTS on a queue build without stopping it.
name: Governed Surface Queue Guard
runs-on: ubuntu-latest
timeout-minutes: 10
steps:
 - name: Checkout code
uses: actions/checkout@v7
with:
# A governed-surface question answered over a truncated history
# answers with SILENCE, and silence reads as compliance. A merge
# group's base sha can predate a shallow fetch's floor, so the whole
# history is the only depth that cannot under-report. The script
# refuses outright (exit 1) if either sha is missing, rather than
# diffing what it happens to have.
fetch-depth: 0
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# The self-test runs FIRST and in its own step, because it is the
# precondition for trusting the run after it: this guard's predicates
# decide whether a merge lands, so a rotted predicate must redden here
# rather than quietly wave a governed diff through. It also holds the
# wiring pins — the job name above, the triggers, `fetch-depth: 0`, the
# absent path filter, and the `REQUIRED_CONTEXTS` registration.
#
# No install and no build: the script imports node builtins and one local
# module (`scripts/invoked-as.mjs`) only, which is also what keeps it
# clear of `scripts/check-pre-install-import-graph.mjs`.
 - name: Guard predicate self-test
run: node scripts/check-governed-queue-guard.mjs --self-test
# The live judgment. Everything it reads arrives through `env:` or the
# event payload on disk — no `${{ }}` interpolation into the shell line,
# so no pull-request-controlled text ever becomes part of a command.
#
# GITHUB_TOKEN is the workflow's own default token at the read scopes
# declared above; it is what makes the review read possible at all, and an
# unreadable review list is a REFUSAL with its own exit code, never a
# pass. ⛔ Fail-open is wrong in this file specifically — it exists
# because every other layer in this chain failed open.
 - name: Governed surfaces may not enter the merge queue unreviewed
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: node scripts/check-governed-queue-guard.mjs

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
 Governed Surface Guard

chore(ci): slow both dependabot channels from weekly to monthly
#454
Sign in to view logs

chore(ci): slow both dependabot channels from weekly to monthly


chore(ci): slow both dependabot channels from weekly to monthly #454
Workflow file for this run

.github/workflows/governed-surface-guard.yml
 at
92e5d3b
# The machine half of the governed-surface no-bypass rule (objectui#6596,
# maintainer ruling 2026-08-27 accepting Option C on #6325). The rule, the event
# split, the approval predicate and the exit contract all live in
# `scripts/check-governed-queue-guard.mjs`; that header is authoritative and this
# file is the invocation. Only the wiring decisions are argued here.
#
# What it is for, in one measurement: PR #6183 touched `AGENTS.md`, was correctly
# parked as a draft, and a GitHub MCP `update_pull_request` call passing only
# `reviewers` silently set `draft: false`. The pull request entered the merge
# queue and landed as `5b3290fd5` with no human approval; converting it back to a
# draft did NOT dequeue it. Nothing in this repository could have refused that —
# the whole defence was seat discipline, and the failure contained no seat
# decision at all.
name: Governed Surface Guard
on:
# BOTH legs are load-bearing and they mean DIFFERENT things — see the script
# header. `merge_group` is the leg that REFUSES: the queue build is the last
# thing between a speculative merge and `main`, and it is the path #6183 took.
# `pull_request` is an EARLY WARNING that deliberately exits 0, because a
# governed PR held as a draft for the maintainer to merge by hand is this
# regime's healthy end state, and a check that reddens on the healthy case is
# a permanently red check nobody reads.
pull_request:
# `develop` is included for the same reason every other requirable gate here
# names both: a context that does not report on a branch it could be
# required on leaves the pull request pending rather than failing it.
branches: [main, develop]
# ⚠️ Naming `types:` REPLACES GitHub's default set rather than extending it,
# so all three defaults are restated. `ready_for_review` is the addition and
# it is the point: flipping a governed draft to ready is the first move of
# the exact sequence this guard exists to interrupt, and it is not in the
# default set — without it the warning would not re-fire at the one moment a
# seat most needs to read it. `scripts/check-governed-queue-guard.mjs
# --self-test` pins this line.
types: [opened, synchronize, reopened, ready_for_review]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). This is the leg that refuses, and a
# requirable context that does not report on a queue build stalls the queue
# until the ruleset's 60-minute status-check timeout. `types:` is named
# although `checks_requested` is currently the only one GitHub defines.
merge_group:
types: [checks_requested]
# ⛔ NO `paths:` filter, on either leg, and this is not an oversight. A skipped
# job counts as SUCCESS in branch protection, so a path filter would hand the
# queue a green "Governed Surface Queue Guard" for a pull request the filter
# mis-scoped — on the one check whose entire job is to refuse. The path test
# belongs INSIDE the script, where "nothing governed" is a verdict that says so
# and costs zero API calls. (`merge_group` supports no path filter at all, so a
# filter would also make the two legs disagree about what they cover.) The
# script's `--self-test` fails if one is ever added; the same conclusion
# `control-bytes.yml` and `changeset-presence.yml` reached for themselves.
concurrency:
group: governed-surface-guard-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
# The default read scopes and nothing beyond them. `pull-requests: read` is what
# the review and head reads need; there is no write scope here, and adding one
# to let this check "fix" anything would be a widening no ruling covers.
permissions:
contents: read
pull-requests: read
jobs:
governed-surface-guard:
# ⚠️ THIS LITERAL IS THE CHECK-RUN NAME branch protection would pin, and it
# is duplicated in `CHECK_CONTEXT_NAME` in the script — deliberately, and
# pinned in both directions: the script's `--self-test` reads THIS FILE and
# fails if the two ever disagree. Renaming a job silently detaches a
# required context, and a name that lives in exactly one place is a name
# nothing can pin. It is also registered in `REQUIRED_CONTEXTS` in
# `scripts/dependabot-merge-gate.mjs`, which is this repository's own
# written-down answer to "which checks are blocking".
#
# ⛔ Making it a REQUIRED context in the live branch-protection ruleset is
# not this pull request's step and cannot be: that is a repository-settings
# surface only the maintainer can change. Until it is flipped, this job
# REPORTS on a queue build without stopping it.
name: Governed Surface Queue Guard
runs-on: ubuntu-latest
timeout-minutes: 10
steps:
 - name: Checkout code
uses: actions/checkout@v7
with:
# A governed-surface question answered over a truncated history
# answers with SILENCE, and silence reads as compliance. A merge
# group's base sha can predate a shallow fetch's floor, so the whole
# history is the only depth that cannot under-report. The script
# refuses outright (exit 1) if either sha is missing, rather than
# diffing what it happens to have.
fetch-depth: 0
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# The self-test runs FIRST and in its own step, because it is the
# precondition for trusting the run after it: this guard's predicates
# decide whether a merge lands, so a rotted predicate must redden here
# rather than quietly wave a governed diff through. It also holds the
# wiring pins — the job name above, the triggers, `fetch-depth: 0`, the
# absent path filter, and the `REQUIRED_CONTEXTS` registration.
#
# No install and no build: the script imports node builtins and one local
# module (`scripts/invoked-as.mjs`) only, which is also what keeps it
# clear of `scripts/check-pre-install-import-graph.mjs`.
 - name: Guard predicate self-test
run: node scripts/check-governed-queue-guard.mjs --self-test
# The live judgment. Everything it reads arrives through `env:` or the
# event payload on disk — no `${{ }}` interpolation into the shell line,
# so no pull-request-controlled text ever becomes part of a command.
#
# GITHUB_TOKEN is the workflow's own default token at the read scopes
# declared above; it is what makes the review read possible at all, and an
# unreadable review list is a REFUSAL with its own exit code, never a
# pass. ⛔ Fail-open is wrong in this file specifically — it exists
# because every other layer in this chain failed open.
 - name: Governed surfaces may not enter the merge queue unreviewed
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: node scripts/check-governed-queue-guard.mjs

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
 Governed Surface Guard

chore(ci): slow both dependabot channels from weekly to monthly
#454
Sign in to view logs

chore(ci): slow both dependabot channels from weekly to monthly


chore(ci): slow both dependabot channels from weekly to monthly #454
Workflow file for this run

.github/workflows/governed-surface-guard.yml
 at
92e5d3b
# The machine half of the governed-surface no-bypass rule (objectui#6596,
# maintainer ruling 2026-08-27 accepting Option C on #6325). The rule, the event
# split, the approval predicate and the exit contract all live in
# `scripts/check-governed-queue-guard.mjs`; that header is authoritative and this
# file is the invocation. Only the wiring decisions are argued here.
#
# What it is for, in one measurement: PR #6183 touched `AGENTS.md`, was correctly
# parked as a draft, and a GitHub MCP `update_pull_request` call passing only
# `reviewers` silently set `draft: false`. The pull request entered the merge
# queue and landed as `5b3290fd5` with no human approval; converting it back to a
# draft did NOT dequeue it. Nothing in this repository could have refused that —
# the whole defence was seat discipline, and the failure contained no seat
# decision at all.
name: Governed Surface Guard
on:
# BOTH legs are load-bearing and they mean DIFFERENT things — see the script
# header. `merge_group` is the leg that REFUSES: the queue build is the last
# thing between a speculative merge and `main`, and it is the path #6183 took.
# `pull_request` is an EARLY WARNING that deliberately exits 0, because a
# governed PR held as a draft for the maintainer to merge by hand is this
# regime's healthy end state, and a check that reddens on the healthy case is
# a permanently red check nobody reads.
pull_request:
# `develop` is included for the same reason every other requirable gate here
# names both: a context that does not report on a branch it could be
# required on leaves the pull request pending rather than failing it.
branches: [main, develop]
# ⚠️ Naming `types:` REPLACES GitHub's default set rather than extending it,
# so all three defaults are restated. `ready_for_review` is the addition and
# it is the point: flipping a governed draft to ready is the first move of
# the exact sequence this guard exists to interrupt, and it is not in the
# default set — without it the warning would not re-fire at the one moment a
# seat most needs to read it. `scripts/check-governed-queue-guard.mjs
# --self-test` pins this line.
types: [opened, synchronize, reopened, ready_for_review]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). This is the leg that refuses, and a
# requirable context that does not report on a queue build stalls the queue
# until the ruleset's 60-minute status-check timeout. `types:` is named
# although `checks_requested` is currently the only one GitHub defines.
merge_group:
types: [checks_requested]
# ⛔ NO `paths:` filter, on either leg, and this is not an oversight. A skipped
# job counts as SUCCESS in branch protection, so a path filter would hand the
# queue a green "Governed Surface Queue Guard" for a pull request the filter
# mis-scoped — on the one check whose entire job is to refuse. The path test
# belongs INSIDE the script, where "nothing governed" is a verdict that says so
# and costs zero API calls. (`merge_group` supports no path filter at all, so a
# filter would also make the two legs disagree about what they cover.) The
# script's `--self-test` fails if one is ever added; the same conclusion
# `control-bytes.yml` and `changeset-presence.yml` reached for themselves.
concurrency:
group: governed-surface-guard-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
# The default read scopes and nothing beyond them. `pull-requests: read` is what
# the review and head reads need; there is no write scope here, and adding one
# to let this check "fix" anything would be a widening no ruling covers.
permissions:
contents: read
pull-requests: read
jobs:
governed-surface-guard:
# ⚠️ THIS LITERAL IS THE CHECK-RUN NAME branch protection would pin, and it
# is duplicated in `CHECK_CONTEXT_NAME` in the script — deliberately, and
# pinned in both directions: the script's `--self-test` reads THIS FILE and
# fails if the two ever disagree. Renaming a job silently detaches a
# required context, and a name that lives in exactly one place is a name
# nothing can pin. It is also registered in `REQUIRED_CONTEXTS` in
# `scripts/dependabot-merge-gate.mjs`, which is this repository's own
# written-down answer to "which checks are blocking".
#
# ⛔ Making it a REQUIRED context in the live branch-protection ruleset is
# not this pull request's step and cannot be: that is a repository-settings
# surface only the maintainer can change. Until it is flipped, this job
# REPORTS on a queue build without stopping it.
name: Governed Surface Queue Guard
runs-on: ubuntu-latest
timeout-minutes: 10
steps:
 - name: Checkout code
uses: actions/checkout@v7
with:
# A governed-surface question answered over a truncated history
# answers with SILENCE, and silence reads as compliance. A merge
# group's base sha can predate a shallow fetch's floor, so the whole
# history is the only depth that cannot under-report. The script
# refuses outright (exit 1) if either sha is missing, rather than
# diffing what it happens to have.
fetch-depth: 0
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# The self-test runs FIRST and in its own step, because it is the
# precondition for trusting the run after it: this guard's predicates
# decide whether a merge lands, so a rotted predicate must redden here
# rather than quietly wave a governed diff through. It also holds the
# wiring pins — the job name above, the triggers, `fetch-depth: 0`, the
# absent path filter, and the `REQUIRED_CONTEXTS` registration.
#
# No install and no build: the script imports node builtins and one local
# module (`scripts/invoked-as.mjs`) only, which is also what keeps it
# clear of `scripts/check-pre-install-import-graph.mjs`.
 - name: Guard predicate self-test
run: node scripts/check-governed-queue-guard.mjs --self-test
# The live judgment. Everything it reads arrives through `env:` or the
# event payload on disk — no `${{ }}` interpolation into the shell line,
# so no pull-request-controlled text ever becomes part of a command.
#
# GITHUB_TOKEN is the workflow's own default token at the read scopes
# declared above; it is what makes the review read possible at all, and an
# unreadable review list is a REFUSAL with its own exit code, never a
# pass. ⛔ Fail-open is wrong in this file specifically — it exists
# because every other layer in this chain failed open.
 - name: Governed surfaces may not enter the merge queue unreviewed
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: node scripts/check-governed-queue-guard.mjs

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
 Governed Surface Guard

chore(ci): slow both dependabot channels from weekly to monthly
#454
Sign in to view logs

chore(ci): slow both dependabot channels from weekly to monthly


chore(ci): slow both dependabot channels from weekly to monthly #454
Workflow file for this run

.github/workflows/governed-surface-guard.yml
 at
92e5d3b
# The machine half of the governed-surface no-bypass rule (objectui#6596,
# maintainer ruling 2026-08-27 accepting Option C on #6325). The rule, the event
# split, the approval predicate and the exit contract all live in
# `scripts/check-governed-queue-guard.mjs`; that header is authoritative and this
# file is the invocation. Only the wiring decisions are argued here.
#
# What it is for, in one measurement: PR #6183 touched `AGENTS.md`, was correctly
# parked as a draft, and a GitHub MCP `update_pull_request` call passing only
# `reviewers` silently set `draft: false`. The pull request entered the merge
# queue and landed as `5b3290fd5` with no human approval; converting it back to a
# draft did NOT dequeue it. Nothing in this repository could have refused that —
# the whole defence was seat discipline, and the failure contained no seat
# decision at all.
name: Governed Surface Guard
on:
# BOTH legs are load-bearing and they mean DIFFERENT things — see the script
# header. `merge_group` is the leg that REFUSES: the queue build is the last
# thing between a speculative merge and `main`, and it is the path #6183 took.
# `pull_request` is an EARLY WARNING that deliberately exits 0, because a
# governed PR held as a draft for the maintainer to merge by hand is this
# regime's healthy end state, and a check that reddens on the healthy case is
# a permanently red check nobody reads.
pull_request:
# `develop` is included for the same reason every other requirable gate here
# names both: a context that does not report on a branch it could be
# required on leaves the pull request pending rather than failing it.
branches: [main, develop]
# ⚠️ Naming `types:` REPLACES GitHub's default set rather than extending it,
# so all three defaults are restated. `ready_for_review` is the addition and
# it is the point: flipping a governed draft to ready is the first move of
# the exact sequence this guard exists to interrupt, and it is not in the
# default set — without it the warning would not re-fire at the one moment a
# seat most needs to read it. `scripts/check-governed-queue-guard.mjs
# --self-test` pins this line.
types: [opened, synchronize, reopened, ready_for_review]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). This is the leg that refuses, and a
# requirable context that does not report on a queue build stalls the queue
# until the ruleset's 60-minute status-check timeout. `types:` is named
# although `checks_requested` is currently the only one GitHub defines.
merge_group:
types: [checks_requested]
# ⛔ NO `paths:` filter, on either leg, and this is not an oversight. A skipped
# job counts as SUCCESS in branch protection, so a path filter would hand the
# queue a green "Governed Surface Queue Guard" for a pull request the filter
# mis-scoped — on the one check whose entire job is to refuse. The path test
# belongs INSIDE the script, where "nothing governed" is a verdict that says so
# and costs zero API calls. (`merge_group` supports no path filter at all, so a
# filter would also make the two legs disagree about what they cover.) The
# script's `--self-test` fails if one is ever added; the same conclusion
# `control-bytes.yml` and `changeset-presence.yml` reached for themselves.
concurrency:
group: governed-surface-guard-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
# The default read scopes and nothing beyond them. `pull-requests: read` is what
# the review and head reads need; there is no write scope here, and adding one
# to let this check "fix" anything would be a widening no ruling covers.
permissions:
contents: read
pull-requests: read
jobs:
governed-surface-guard:
# ⚠️ THIS LITERAL IS THE CHECK-RUN NAME branch protection would pin, and it
# is duplicated in `CHECK_CONTEXT_NAME` in the script — deliberately, and
# pinned in both directions: the script's `--self-test` reads THIS FILE and
# fails if the two ever disagree. Renaming a job silently detaches a
# required context, and a name that lives in exactly one place is a name
# nothing can pin. It is also registered in `REQUIRED_CONTEXTS` in
# `scripts/dependabot-merge-gate.mjs`, which is this repository's own
# written-down answer to "which checks are blocking".
#
# ⛔ Making it a REQUIRED context in the live branch-protection ruleset is
# not this pull request's step and cannot be: that is a repository-settings
# surface only the maintainer can change. Until it is flipped, this job
# REPORTS on a queue build without stopping it.
name: Governed Surface Queue Guard
runs-on: ubuntu-latest
timeout-minutes: 10
steps:
 - name: Checkout code
uses: actions/checkout@v7
with:
# A governed-surface question answered over a truncated history
# answers with SILENCE, and silence reads as compliance. A merge
# group's base sha can predate a shallow fetch's floor, so the whole
# history is the only depth that cannot under-report. The script
# refuses outright (exit 1) if either sha is missing, rather than
# diffing what it happens to have.
fetch-depth: 0
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# The self-test runs FIRST and in its own step, because it is the
# precondition for trusting the run after it: this guard's predicates
# decide whether a merge lands, so a rotted predicate must redden here
# rather than quietly wave a governed diff through. It also holds the
# wiring pins — the job name above, the triggers, `fetch-depth: 0`, the
# absent path filter, and the `REQUIRED_CONTEXTS` registration.
#
# No install and no build: the script imports node builtins and one local
# module (`scripts/invoked-as.mjs`) only, which is also what keeps it
# clear of `scripts/check-pre-install-import-graph.mjs`.
 - name: Guard predicate self-test
run: node scripts/check-governed-queue-guard.mjs --self-test
# The live judgment. Everything it reads arrives through `env:` or the
# event payload on disk — no `${{ }}` interpolation into the shell line,
# so no pull-request-controlled text ever becomes part of a command.
#
# GITHUB_TOKEN is the workflow's own default token at the read scopes
# declared above; it is what makes the review read possible at all, and an
# unreadable review list is a REFUSAL with its own exit code, never a
# pass. ⛔ Fail-open is wrong in this file specifically — it exists
# because every other layer in this chain failed open.
 - name: Governed surfaces may not enter the merge queue unreviewed
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: node scripts/check-governed-queue-guard.mjs