Inert vi.mock Specifiers

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

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 #1344

Workflow file for this run

.github/workflows/vi-mock-specifiers.yml at 92e5d3b
name: Inert vi.mock Specifiers
# Two gates over ONE population, in one home. Both read the `vi.mock` call sites
# of this tree and both catch a mock that is silently not doing what it looks
# like it is doing: `check-vi-mock-specifiers.mjs` catches a specifier that
# resolves to no file (an inert stand-in), and `check-vi-mock-inherit.mjs`
# catches a factory that hand-lists its exports (a frozen export surface,
# objectui#6849). They share the call-site pattern deliberately -- a population
# that drifted between them would be a hole neither one reports -- so they share
# a workflow rather than each registering a required context of its own.
#
# The workflow `name:` and the job `name:` are therefore BROADER than the older
# of the two gates. They are left unchanged on purpose: those two strings are
# the check-run context that branch protection and
# `scripts/dependabot-merge-gate.mjs` name, and renaming a required context
# silently un-requires it.
#
# Why this is its own workflow rather than a step in `ci.yml` or `lint.yml`: a
# module mock can be written into any package, in any shape of pull request, and
# both of those workflows decide inside the job whether the change "needs a full
# run" — with an exclusion list that skips every expensive step on a
# markdown-only or changeset-only change. This gate costs a checkout plus one
# `node` call, so there is nothing to gain by putting it behind that switch and
# a whole class of pull request to lose.
#
# Same shape and the same reasoning as `docs-links.yml`, `control-bytes.yml`,
# `skills-paths.yml`, `changeset-presence.yml` and `pre-install-import-graph.yml`,
# whose headers record the conclusion this repository has now reached five
# times: a gate that cannot see the pull request shape most likely to trip it
# "rebuilds the hole it exists to close". One gate, one home.
#
# Hence: no `paths` and no `paths-ignore` here, deliberately.
# `scripts/__tests__/check-vi-mock-specifiers.test.ts` fails if either is ever
# added, and fails too if a second workflow starts running the same script.
# Reporting on every pull request is also what makes the check requirable, and
# `scripts/dependabot-merge-gate.mjs` classifies it as a required context — an
# unclassified blocking check is one a Dependabot merge would be let past
# (objectui#6135).
#
# It needs no install and no build — a checkout plus one `node` call over ~3.7k
# tracked source files, measured at ~2.7s on this tree. Keep it that way; the
# import graph is builtins plus repo-relative modules only, which
# `pre-install-import-graph.yml` enforces (objectui#6148).
on:
pull_request:
branches: [main, develop]
push:
branches: [main, develop]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). A required check that does not report on a
# queue build stalls the queue until the ruleset's 60-minute timeout fails it,
# so an unfiltered gate that can become required subscribes here from the
# start. `types:` is named although `checks_requested` is currently the only
# activity type GitHub defines for `merge_group`.
merge_group:
types: [checks_requested]
workflow_dispatch:
concurrency:
group: vi-mock-specifiers-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
permissions:
contents: read
jobs:
vi-mock-specifiers:
name: Inert vi.mock Specifier Check
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
- name: Checkout code
uses: actions/checkout@v7
- name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# A `vi.mock` whose relative specifier resolves to no file does NOT error.
# Vitest registers the mock against a module id nothing imports, the run
# proceeds with the real module everywhere, and the suite passes —
# identically to a correct one, with no warning and no smaller assertion
# count. objectui#5646: the one known instance (PR #5645) passed even with
# the code under test reverted to the shape the suite was written to
# catch, and only an ablation leg exposed it.
#
# This gate is GREEN AT REST — there are zero unresolvable specifiers in
# the tree and there should stay zero — so it prints its census rather
# than a bare "OK", and it FAILS if the population collapses to nothing.
# A scan that silently finds nothing reads as coverage, which is this
# gate's own defect one level up.
- name: Check every relative vi.mock specifier resolves
run: node scripts/check-vi-mock-specifiers.mjs
# The sibling property of the same call sites: a factory that HAND-LISTS
# the exports it returns freezes the mock's export surface. The next
# export any module in the file's import graph reads AT MODULE SCOPE then
# kills the file during COLLECTION -- `Test Files 3 failed | 546 passed`
# with `Tests 6694 passed`, ZERO failed assertions, because the tests in
# those files never ran (objectui#6768). It reads as flake to whoever
# sees it next, and the bill lands on whoever added the export.
#
# The recogniser is SEMANTIC, never a grep for `importOriginal`: that
# spelling mis-counted eleven correct files as broken AND missed one
# broken file entirely (objectui#6849). It asks whether the factory
# OBTAINS the real module -- a callback parameter under any name, or
# `vi.importActual` of the same specifier -- and SPREADS it.
#
# Narrow by ruling: only the covered workspace specifiers in
# `COVERED_SPECIFIERS` are judged. Whole-module replacement of a local
# module is legitimate and out of scope by construction, not by exemption.
- name: Check every covered vi.mock factory inherits the real export surface
run: node scripts/check-vi-mock-inherit.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
 Inert vi.mock Specifiers

chore(ci): slow both dependabot channels from weekly to monthly
#1344
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 #1344
Workflow file for this run

.github/workflows/vi-mock-specifiers.yml
 at
92e5d3b
name: Inert vi.mock Specifiers
# Two gates over ONE population, in one home. Both read the `vi.mock` call sites
# of this tree and both catch a mock that is silently not doing what it looks
# like it is doing: `check-vi-mock-specifiers.mjs` catches a specifier that
# resolves to no file (an inert stand-in), and `check-vi-mock-inherit.mjs`
# catches a factory that hand-lists its exports (a frozen export surface,
# objectui#6849). They share the call-site pattern deliberately -- a population
# that drifted between them would be a hole neither one reports -- so they share
# a workflow rather than each registering a required context of its own.
#
# The workflow `name:` and the job `name:` are therefore BROADER than the older
# of the two gates. They are left unchanged on purpose: those two strings are
# the check-run context that branch protection and
# `scripts/dependabot-merge-gate.mjs` name, and renaming a required context
# silently un-requires it.
#
# Why this is its own workflow rather than a step in `ci.yml` or `lint.yml`: a
# module mock can be written into any package, in any shape of pull request, and
# both of those workflows decide inside the job whether the change "needs a full
# run" — with an exclusion list that skips every expensive step on a
# markdown-only or changeset-only change. This gate costs a checkout plus one
# `node` call, so there is nothing to gain by putting it behind that switch and
# a whole class of pull request to lose.
#
# Same shape and the same reasoning as `docs-links.yml`, `control-bytes.yml`,
# `skills-paths.yml`, `changeset-presence.yml` and `pre-install-import-graph.yml`,
# whose headers record the conclusion this repository has now reached five
# times: a gate that cannot see the pull request shape most likely to trip it
# "rebuilds the hole it exists to close". One gate, one home.
#
# Hence: no `paths` and no `paths-ignore` here, deliberately.
# `scripts/__tests__/check-vi-mock-specifiers.test.ts` fails if either is ever
# added, and fails too if a second workflow starts running the same script.
# Reporting on every pull request is also what makes the check requirable, and
# `scripts/dependabot-merge-gate.mjs` classifies it as a required context — an
# unclassified blocking check is one a Dependabot merge would be let past
# (objectui#6135).
#
# It needs no install and no build — a checkout plus one `node` call over ~3.7k
# tracked source files, measured at ~2.7s on this tree. Keep it that way; the
# import graph is builtins plus repo-relative modules only, which
# `pre-install-import-graph.yml` enforces (objectui#6148).
on:
pull_request:
branches: [main, develop]
push:
branches: [main, develop]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). A required check that does not report on a
# queue build stalls the queue until the ruleset's 60-minute timeout fails it,
# so an unfiltered gate that can become required subscribes here from the
# start. `types:` is named although `checks_requested` is currently the only
# activity type GitHub defines for `merge_group`.
merge_group:
types: [checks_requested]
workflow_dispatch:
concurrency:
group: vi-mock-specifiers-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
permissions:
contents: read
jobs:
vi-mock-specifiers:
name: Inert vi.mock Specifier Check
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
 - name: Checkout code
uses: actions/checkout@v7
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# A `vi.mock` whose relative specifier resolves to no file does NOT error.
# Vitest registers the mock against a module id nothing imports, the run
# proceeds with the real module everywhere, and the suite passes —
# identically to a correct one, with no warning and no smaller assertion
# count. objectui#5646: the one known instance (PR #5645) passed even with
# the code under test reverted to the shape the suite was written to
# catch, and only an ablation leg exposed it.
#
# This gate is GREEN AT REST — there are zero unresolvable specifiers in
# the tree and there should stay zero — so it prints its census rather
# than a bare "OK", and it FAILS if the population collapses to nothing.
# A scan that silently finds nothing reads as coverage, which is this
# gate's own defect one level up.
 - name: Check every relative vi.mock specifier resolves
run: node scripts/check-vi-mock-specifiers.mjs
# The sibling property of the same call sites: a factory that HAND-LISTS
# the exports it returns freezes the mock's export surface. The next
# export any module in the file's import graph reads AT MODULE SCOPE then
# kills the file during COLLECTION -- `Test Files 3 failed | 546 passed`
# with `Tests 6694 passed`, ZERO failed assertions, because the tests in
# those files never ran (objectui#6768). It reads as flake to whoever
# sees it next, and the bill lands on whoever added the export.
#
# The recogniser is SEMANTIC, never a grep for `importOriginal`: that
# spelling mis-counted eleven correct files as broken AND missed one
# broken file entirely (objectui#6849). It asks whether the factory
# OBTAINS the real module -- a callback parameter under any name, or
# `vi.importActual` of the same specifier -- and SPREADS it.
#
# Narrow by ruling: only the covered workspace specifiers in
# `COVERED_SPECIFIERS` are judged. Whole-module replacement of a local
# module is legitimate and out of scope by construction, not by exemption.
 - name: Check every covered vi.mock factory inherits the real export surface
run: node scripts/check-vi-mock-inherit.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
 Inert vi.mock Specifiers

chore(ci): slow both dependabot channels from weekly to monthly
#1344
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 #1344
Workflow file for this run

.github/workflows/vi-mock-specifiers.yml
 at
92e5d3b
name: Inert vi.mock Specifiers
# Two gates over ONE population, in one home. Both read the `vi.mock` call sites
# of this tree and both catch a mock that is silently not doing what it looks
# like it is doing: `check-vi-mock-specifiers.mjs` catches a specifier that
# resolves to no file (an inert stand-in), and `check-vi-mock-inherit.mjs`
# catches a factory that hand-lists its exports (a frozen export surface,
# objectui#6849). They share the call-site pattern deliberately -- a population
# that drifted between them would be a hole neither one reports -- so they share
# a workflow rather than each registering a required context of its own.
#
# The workflow `name:` and the job `name:` are therefore BROADER than the older
# of the two gates. They are left unchanged on purpose: those two strings are
# the check-run context that branch protection and
# `scripts/dependabot-merge-gate.mjs` name, and renaming a required context
# silently un-requires it.
#
# Why this is its own workflow rather than a step in `ci.yml` or `lint.yml`: a
# module mock can be written into any package, in any shape of pull request, and
# both of those workflows decide inside the job whether the change "needs a full
# run" — with an exclusion list that skips every expensive step on a
# markdown-only or changeset-only change. This gate costs a checkout plus one
# `node` call, so there is nothing to gain by putting it behind that switch and
# a whole class of pull request to lose.
#
# Same shape and the same reasoning as `docs-links.yml`, `control-bytes.yml`,
# `skills-paths.yml`, `changeset-presence.yml` and `pre-install-import-graph.yml`,
# whose headers record the conclusion this repository has now reached five
# times: a gate that cannot see the pull request shape most likely to trip it
# "rebuilds the hole it exists to close". One gate, one home.
#
# Hence: no `paths` and no `paths-ignore` here, deliberately.
# `scripts/__tests__/check-vi-mock-specifiers.test.ts` fails if either is ever
# added, and fails too if a second workflow starts running the same script.
# Reporting on every pull request is also what makes the check requirable, and
# `scripts/dependabot-merge-gate.mjs` classifies it as a required context — an
# unclassified blocking check is one a Dependabot merge would be let past
# (objectui#6135).
#
# It needs no install and no build — a checkout plus one `node` call over ~3.7k
# tracked source files, measured at ~2.7s on this tree. Keep it that way; the
# import graph is builtins plus repo-relative modules only, which
# `pre-install-import-graph.yml` enforces (objectui#6148).
on:
pull_request:
branches: [main, develop]
push:
branches: [main, develop]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). A required check that does not report on a
# queue build stalls the queue until the ruleset's 60-minute timeout fails it,
# so an unfiltered gate that can become required subscribes here from the
# start. `types:` is named although `checks_requested` is currently the only
# activity type GitHub defines for `merge_group`.
merge_group:
types: [checks_requested]
workflow_dispatch:
concurrency:
group: vi-mock-specifiers-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
permissions:
contents: read
jobs:
vi-mock-specifiers:
name: Inert vi.mock Specifier Check
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
 - name: Checkout code
uses: actions/checkout@v7
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# A `vi.mock` whose relative specifier resolves to no file does NOT error.
# Vitest registers the mock against a module id nothing imports, the run
# proceeds with the real module everywhere, and the suite passes —
# identically to a correct one, with no warning and no smaller assertion
# count. objectui#5646: the one known instance (PR #5645) passed even with
# the code under test reverted to the shape the suite was written to
# catch, and only an ablation leg exposed it.
#
# This gate is GREEN AT REST — there are zero unresolvable specifiers in
# the tree and there should stay zero — so it prints its census rather
# than a bare "OK", and it FAILS if the population collapses to nothing.
# A scan that silently finds nothing reads as coverage, which is this
# gate's own defect one level up.
 - name: Check every relative vi.mock specifier resolves
run: node scripts/check-vi-mock-specifiers.mjs
# The sibling property of the same call sites: a factory that HAND-LISTS
# the exports it returns freezes the mock's export surface. The next
# export any module in the file's import graph reads AT MODULE SCOPE then
# kills the file during COLLECTION -- `Test Files 3 failed | 546 passed`
# with `Tests 6694 passed`, ZERO failed assertions, because the tests in
# those files never ran (objectui#6768). It reads as flake to whoever
# sees it next, and the bill lands on whoever added the export.
#
# The recogniser is SEMANTIC, never a grep for `importOriginal`: that
# spelling mis-counted eleven correct files as broken AND missed one
# broken file entirely (objectui#6849). It asks whether the factory
# OBTAINS the real module -- a callback parameter under any name, or
# `vi.importActual` of the same specifier -- and SPREADS it.
#
# Narrow by ruling: only the covered workspace specifiers in
# `COVERED_SPECIFIERS` are judged. Whole-module replacement of a local
# module is legitimate and out of scope by construction, not by exemption.
 - name: Check every covered vi.mock factory inherits the real export surface
run: node scripts/check-vi-mock-inherit.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
 Inert vi.mock Specifiers

chore(ci): slow both dependabot channels from weekly to monthly
#1344
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 #1344
Workflow file for this run

.github/workflows/vi-mock-specifiers.yml
 at
92e5d3b
name: Inert vi.mock Specifiers
# Two gates over ONE population, in one home. Both read the `vi.mock` call sites
# of this tree and both catch a mock that is silently not doing what it looks
# like it is doing: `check-vi-mock-specifiers.mjs` catches a specifier that
# resolves to no file (an inert stand-in), and `check-vi-mock-inherit.mjs`
# catches a factory that hand-lists its exports (a frozen export surface,
# objectui#6849). They share the call-site pattern deliberately -- a population
# that drifted between them would be a hole neither one reports -- so they share
# a workflow rather than each registering a required context of its own.
#
# The workflow `name:` and the job `name:` are therefore BROADER than the older
# of the two gates. They are left unchanged on purpose: those two strings are
# the check-run context that branch protection and
# `scripts/dependabot-merge-gate.mjs` name, and renaming a required context
# silently un-requires it.
#
# Why this is its own workflow rather than a step in `ci.yml` or `lint.yml`: a
# module mock can be written into any package, in any shape of pull request, and
# both of those workflows decide inside the job whether the change "needs a full
# run" — with an exclusion list that skips every expensive step on a
# markdown-only or changeset-only change. This gate costs a checkout plus one
# `node` call, so there is nothing to gain by putting it behind that switch and
# a whole class of pull request to lose.
#
# Same shape and the same reasoning as `docs-links.yml`, `control-bytes.yml`,
# `skills-paths.yml`, `changeset-presence.yml` and `pre-install-import-graph.yml`,
# whose headers record the conclusion this repository has now reached five
# times: a gate that cannot see the pull request shape most likely to trip it
# "rebuilds the hole it exists to close". One gate, one home.
#
# Hence: no `paths` and no `paths-ignore` here, deliberately.
# `scripts/__tests__/check-vi-mock-specifiers.test.ts` fails if either is ever
# added, and fails too if a second workflow starts running the same script.
# Reporting on every pull request is also what makes the check requirable, and
# `scripts/dependabot-merge-gate.mjs` classifies it as a required context — an
# unclassified blocking check is one a Dependabot merge would be let past
# (objectui#6135).
#
# It needs no install and no build — a checkout plus one `node` call over ~3.7k
# tracked source files, measured at ~2.7s on this tree. Keep it that way; the
# import graph is builtins plus repo-relative modules only, which
# `pre-install-import-graph.yml` enforces (objectui#6148).
on:
pull_request:
branches: [main, develop]
push:
branches: [main, develop]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). A required check that does not report on a
# queue build stalls the queue until the ruleset's 60-minute timeout fails it,
# so an unfiltered gate that can become required subscribes here from the
# start. `types:` is named although `checks_requested` is currently the only
# activity type GitHub defines for `merge_group`.
merge_group:
types: [checks_requested]
workflow_dispatch:
concurrency:
group: vi-mock-specifiers-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
permissions:
contents: read
jobs:
vi-mock-specifiers:
name: Inert vi.mock Specifier Check
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
 - name: Checkout code
uses: actions/checkout@v7
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# A `vi.mock` whose relative specifier resolves to no file does NOT error.
# Vitest registers the mock against a module id nothing imports, the run
# proceeds with the real module everywhere, and the suite passes —
# identically to a correct one, with no warning and no smaller assertion
# count. objectui#5646: the one known instance (PR #5645) passed even with
# the code under test reverted to the shape the suite was written to
# catch, and only an ablation leg exposed it.
#
# This gate is GREEN AT REST — there are zero unresolvable specifiers in
# the tree and there should stay zero — so it prints its census rather
# than a bare "OK", and it FAILS if the population collapses to nothing.
# A scan that silently finds nothing reads as coverage, which is this
# gate's own defect one level up.
 - name: Check every relative vi.mock specifier resolves
run: node scripts/check-vi-mock-specifiers.mjs
# The sibling property of the same call sites: a factory that HAND-LISTS
# the exports it returns freezes the mock's export surface. The next
# export any module in the file's import graph reads AT MODULE SCOPE then
# kills the file during COLLECTION -- `Test Files 3 failed | 546 passed`
# with `Tests 6694 passed`, ZERO failed assertions, because the tests in
# those files never ran (objectui#6768). It reads as flake to whoever
# sees it next, and the bill lands on whoever added the export.
#
# The recogniser is SEMANTIC, never a grep for `importOriginal`: that
# spelling mis-counted eleven correct files as broken AND missed one
# broken file entirely (objectui#6849). It asks whether the factory
# OBTAINS the real module -- a callback parameter under any name, or
# `vi.importActual` of the same specifier -- and SPREADS it.
#
# Narrow by ruling: only the covered workspace specifiers in
# `COVERED_SPECIFIERS` are judged. Whole-module replacement of a local
# module is legitimate and out of scope by construction, not by exemption.
 - name: Check every covered vi.mock factory inherits the real export surface
run: node scripts/check-vi-mock-inherit.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
 Inert vi.mock Specifiers

chore(ci): slow both dependabot channels from weekly to monthly
#1344
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 #1344
Workflow file for this run

.github/workflows/vi-mock-specifiers.yml
 at
92e5d3b
name: Inert vi.mock Specifiers
# Two gates over ONE population, in one home. Both read the `vi.mock` call sites
# of this tree and both catch a mock that is silently not doing what it looks
# like it is doing: `check-vi-mock-specifiers.mjs` catches a specifier that
# resolves to no file (an inert stand-in), and `check-vi-mock-inherit.mjs`
# catches a factory that hand-lists its exports (a frozen export surface,
# objectui#6849). They share the call-site pattern deliberately -- a population
# that drifted between them would be a hole neither one reports -- so they share
# a workflow rather than each registering a required context of its own.
#
# The workflow `name:` and the job `name:` are therefore BROADER than the older
# of the two gates. They are left unchanged on purpose: those two strings are
# the check-run context that branch protection and
# `scripts/dependabot-merge-gate.mjs` name, and renaming a required context
# silently un-requires it.
#
# Why this is its own workflow rather than a step in `ci.yml` or `lint.yml`: a
# module mock can be written into any package, in any shape of pull request, and
# both of those workflows decide inside the job whether the change "needs a full
# run" — with an exclusion list that skips every expensive step on a
# markdown-only or changeset-only change. This gate costs a checkout plus one
# `node` call, so there is nothing to gain by putting it behind that switch and
# a whole class of pull request to lose.
#
# Same shape and the same reasoning as `docs-links.yml`, `control-bytes.yml`,
# `skills-paths.yml`, `changeset-presence.yml` and `pre-install-import-graph.yml`,
# whose headers record the conclusion this repository has now reached five
# times: a gate that cannot see the pull request shape most likely to trip it
# "rebuilds the hole it exists to close". One gate, one home.
#
# Hence: no `paths` and no `paths-ignore` here, deliberately.
# `scripts/__tests__/check-vi-mock-specifiers.test.ts` fails if either is ever
# added, and fails too if a second workflow starts running the same script.
# Reporting on every pull request is also what makes the check requirable, and
# `scripts/dependabot-merge-gate.mjs` classifies it as a required context — an
# unclassified blocking check is one a Dependabot merge would be let past
# (objectui#6135).
#
# It needs no install and no build — a checkout plus one `node` call over ~3.7k
# tracked source files, measured at ~2.7s on this tree. Keep it that way; the
# import graph is builtins plus repo-relative modules only, which
# `pre-install-import-graph.yml` enforces (objectui#6148).
on:
pull_request:
branches: [main, develop]
push:
branches: [main, develop]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). A required check that does not report on a
# queue build stalls the queue until the ruleset's 60-minute timeout fails it,
# so an unfiltered gate that can become required subscribes here from the
# start. `types:` is named although `checks_requested` is currently the only
# activity type GitHub defines for `merge_group`.
merge_group:
types: [checks_requested]
workflow_dispatch:
concurrency:
group: vi-mock-specifiers-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
permissions:
contents: read
jobs:
vi-mock-specifiers:
name: Inert vi.mock Specifier Check
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
 - name: Checkout code
uses: actions/checkout@v7
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# A `vi.mock` whose relative specifier resolves to no file does NOT error.
# Vitest registers the mock against a module id nothing imports, the run
# proceeds with the real module everywhere, and the suite passes —
# identically to a correct one, with no warning and no smaller assertion
# count. objectui#5646: the one known instance (PR #5645) passed even with
# the code under test reverted to the shape the suite was written to
# catch, and only an ablation leg exposed it.
#
# This gate is GREEN AT REST — there are zero unresolvable specifiers in
# the tree and there should stay zero — so it prints its census rather
# than a bare "OK", and it FAILS if the population collapses to nothing.
# A scan that silently finds nothing reads as coverage, which is this
# gate's own defect one level up.
 - name: Check every relative vi.mock specifier resolves
run: node scripts/check-vi-mock-specifiers.mjs
# The sibling property of the same call sites: a factory that HAND-LISTS
# the exports it returns freezes the mock's export surface. The next
# export any module in the file's import graph reads AT MODULE SCOPE then
# kills the file during COLLECTION -- `Test Files 3 failed | 546 passed`
# with `Tests 6694 passed`, ZERO failed assertions, because the tests in
# those files never ran (objectui#6768). It reads as flake to whoever
# sees it next, and the bill lands on whoever added the export.
#
# The recogniser is SEMANTIC, never a grep for `importOriginal`: that
# spelling mis-counted eleven correct files as broken AND missed one
# broken file entirely (objectui#6849). It asks whether the factory
# OBTAINS the real module -- a callback parameter under any name, or
# `vi.importActual` of the same specifier -- and SPREADS it.
#
# Narrow by ruling: only the covered workspace specifiers in
# `COVERED_SPECIFIERS` are judged. Whole-module replacement of a local
# module is legitimate and out of scope by construction, not by exemption.
 - name: Check every covered vi.mock factory inherits the real export surface
run: node scripts/check-vi-mock-inherit.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
 Inert vi.mock Specifiers

chore(ci): slow both dependabot channels from weekly to monthly
#1344
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 #1344
Workflow file for this run

.github/workflows/vi-mock-specifiers.yml
 at
92e5d3b
name: Inert vi.mock Specifiers
# Two gates over ONE population, in one home. Both read the `vi.mock` call sites
# of this tree and both catch a mock that is silently not doing what it looks
# like it is doing: `check-vi-mock-specifiers.mjs` catches a specifier that
# resolves to no file (an inert stand-in), and `check-vi-mock-inherit.mjs`
# catches a factory that hand-lists its exports (a frozen export surface,
# objectui#6849). They share the call-site pattern deliberately -- a population
# that drifted between them would be a hole neither one reports -- so they share
# a workflow rather than each registering a required context of its own.
#
# The workflow `name:` and the job `name:` are therefore BROADER than the older
# of the two gates. They are left unchanged on purpose: those two strings are
# the check-run context that branch protection and
# `scripts/dependabot-merge-gate.mjs` name, and renaming a required context
# silently un-requires it.
#
# Why this is its own workflow rather than a step in `ci.yml` or `lint.yml`: a
# module mock can be written into any package, in any shape of pull request, and
# both of those workflows decide inside the job whether the change "needs a full
# run" — with an exclusion list that skips every expensive step on a
# markdown-only or changeset-only change. This gate costs a checkout plus one
# `node` call, so there is nothing to gain by putting it behind that switch and
# a whole class of pull request to lose.
#
# Same shape and the same reasoning as `docs-links.yml`, `control-bytes.yml`,
# `skills-paths.yml`, `changeset-presence.yml` and `pre-install-import-graph.yml`,
# whose headers record the conclusion this repository has now reached five
# times: a gate that cannot see the pull request shape most likely to trip it
# "rebuilds the hole it exists to close". One gate, one home.
#
# Hence: no `paths` and no `paths-ignore` here, deliberately.
# `scripts/__tests__/check-vi-mock-specifiers.test.ts` fails if either is ever
# added, and fails too if a second workflow starts running the same script.
# Reporting on every pull request is also what makes the check requirable, and
# `scripts/dependabot-merge-gate.mjs` classifies it as a required context — an
# unclassified blocking check is one a Dependabot merge would be let past
# (objectui#6135).
#
# It needs no install and no build — a checkout plus one `node` call over ~3.7k
# tracked source files, measured at ~2.7s on this tree. Keep it that way; the
# import graph is builtins plus repo-relative modules only, which
# `pre-install-import-graph.yml` enforces (objectui#6148).
on:
pull_request:
branches: [main, develop]
push:
branches: [main, develop]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). A required check that does not report on a
# queue build stalls the queue until the ruleset's 60-minute timeout fails it,
# so an unfiltered gate that can become required subscribes here from the
# start. `types:` is named although `checks_requested` is currently the only
# activity type GitHub defines for `merge_group`.
merge_group:
types: [checks_requested]
workflow_dispatch:
concurrency:
group: vi-mock-specifiers-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
permissions:
contents: read
jobs:
vi-mock-specifiers:
name: Inert vi.mock Specifier Check
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
 - name: Checkout code
uses: actions/checkout@v7
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# A `vi.mock` whose relative specifier resolves to no file does NOT error.
# Vitest registers the mock against a module id nothing imports, the run
# proceeds with the real module everywhere, and the suite passes —
# identically to a correct one, with no warning and no smaller assertion
# count. objectui#5646: the one known instance (PR #5645) passed even with
# the code under test reverted to the shape the suite was written to
# catch, and only an ablation leg exposed it.
#
# This gate is GREEN AT REST — there are zero unresolvable specifiers in
# the tree and there should stay zero — so it prints its census rather
# than a bare "OK", and it FAILS if the population collapses to nothing.
# A scan that silently finds nothing reads as coverage, which is this
# gate's own defect one level up.
 - name: Check every relative vi.mock specifier resolves
run: node scripts/check-vi-mock-specifiers.mjs
# The sibling property of the same call sites: a factory that HAND-LISTS
# the exports it returns freezes the mock's export surface. The next
# export any module in the file's import graph reads AT MODULE SCOPE then
# kills the file during COLLECTION -- `Test Files 3 failed | 546 passed`
# with `Tests 6694 passed`, ZERO failed assertions, because the tests in
# those files never ran (objectui#6768). It reads as flake to whoever
# sees it next, and the bill lands on whoever added the export.
#
# The recogniser is SEMANTIC, never a grep for `importOriginal`: that
# spelling mis-counted eleven correct files as broken AND missed one
# broken file entirely (objectui#6849). It asks whether the factory
# OBTAINS the real module -- a callback parameter under any name, or
# `vi.importActual` of the same specifier -- and SPREADS it.
#
# Narrow by ruling: only the covered workspace specifiers in
# `COVERED_SPECIFIERS` are judged. Whole-module replacement of a local
# module is legitimate and out of scope by construction, not by exemption.
 - name: Check every covered vi.mock factory inherits the real export surface
run: node scripts/check-vi-mock-inherit.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
 Inert vi.mock Specifiers

chore(ci): slow both dependabot channels from weekly to monthly
#1344
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 #1344
Workflow file for this run

.github/workflows/vi-mock-specifiers.yml
 at
92e5d3b
name: Inert vi.mock Specifiers
# Two gates over ONE population, in one home. Both read the `vi.mock` call sites
# of this tree and both catch a mock that is silently not doing what it looks
# like it is doing: `check-vi-mock-specifiers.mjs` catches a specifier that
# resolves to no file (an inert stand-in), and `check-vi-mock-inherit.mjs`
# catches a factory that hand-lists its exports (a frozen export surface,
# objectui#6849). They share the call-site pattern deliberately -- a population
# that drifted between them would be a hole neither one reports -- so they share
# a workflow rather than each registering a required context of its own.
#
# The workflow `name:` and the job `name:` are therefore BROADER than the older
# of the two gates. They are left unchanged on purpose: those two strings are
# the check-run context that branch protection and
# `scripts/dependabot-merge-gate.mjs` name, and renaming a required context
# silently un-requires it.
#
# Why this is its own workflow rather than a step in `ci.yml` or `lint.yml`: a
# module mock can be written into any package, in any shape of pull request, and
# both of those workflows decide inside the job whether the change "needs a full
# run" — with an exclusion list that skips every expensive step on a
# markdown-only or changeset-only change. This gate costs a checkout plus one
# `node` call, so there is nothing to gain by putting it behind that switch and
# a whole class of pull request to lose.
#
# Same shape and the same reasoning as `docs-links.yml`, `control-bytes.yml`,
# `skills-paths.yml`, `changeset-presence.yml` and `pre-install-import-graph.yml`,
# whose headers record the conclusion this repository has now reached five
# times: a gate that cannot see the pull request shape most likely to trip it
# "rebuilds the hole it exists to close". One gate, one home.
#
# Hence: no `paths` and no `paths-ignore` here, deliberately.
# `scripts/__tests__/check-vi-mock-specifiers.test.ts` fails if either is ever
# added, and fails too if a second workflow starts running the same script.
# Reporting on every pull request is also what makes the check requirable, and
# `scripts/dependabot-merge-gate.mjs` classifies it as a required context — an
# unclassified blocking check is one a Dependabot merge would be let past
# (objectui#6135).
#
# It needs no install and no build — a checkout plus one `node` call over ~3.7k
# tracked source files, measured at ~2.7s on this tree. Keep it that way; the
# import graph is builtins plus repo-relative modules only, which
# `pre-install-import-graph.yml` enforces (objectui#6148).
on:
pull_request:
branches: [main, develop]
push:
branches: [main, develop]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). A required check that does not report on a
# queue build stalls the queue until the ruleset's 60-minute timeout fails it,
# so an unfiltered gate that can become required subscribes here from the
# start. `types:` is named although `checks_requested` is currently the only
# activity type GitHub defines for `merge_group`.
merge_group:
types: [checks_requested]
workflow_dispatch:
concurrency:
group: vi-mock-specifiers-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
permissions:
contents: read
jobs:
vi-mock-specifiers:
name: Inert vi.mock Specifier Check
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
 - name: Checkout code
uses: actions/checkout@v7
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# A `vi.mock` whose relative specifier resolves to no file does NOT error.
# Vitest registers the mock against a module id nothing imports, the run
# proceeds with the real module everywhere, and the suite passes —
# identically to a correct one, with no warning and no smaller assertion
# count. objectui#5646: the one known instance (PR #5645) passed even with
# the code under test reverted to the shape the suite was written to
# catch, and only an ablation leg exposed it.
#
# This gate is GREEN AT REST — there are zero unresolvable specifiers in
# the tree and there should stay zero — so it prints its census rather
# than a bare "OK", and it FAILS if the population collapses to nothing.
# A scan that silently finds nothing reads as coverage, which is this
# gate's own defect one level up.
 - name: Check every relative vi.mock specifier resolves
run: node scripts/check-vi-mock-specifiers.mjs
# The sibling property of the same call sites: a factory that HAND-LISTS
# the exports it returns freezes the mock's export surface. The next
# export any module in the file's import graph reads AT MODULE SCOPE then
# kills the file during COLLECTION -- `Test Files 3 failed | 546 passed`
# with `Tests 6694 passed`, ZERO failed assertions, because the tests in
# those files never ran (objectui#6768). It reads as flake to whoever
# sees it next, and the bill lands on whoever added the export.
#
# The recogniser is SEMANTIC, never a grep for `importOriginal`: that
# spelling mis-counted eleven correct files as broken AND missed one
# broken file entirely (objectui#6849). It asks whether the factory
# OBTAINS the real module -- a callback parameter under any name, or
# `vi.importActual` of the same specifier -- and SPREADS it.
#
# Narrow by ruling: only the covered workspace specifiers in
# `COVERED_SPECIFIERS` are judged. Whole-module replacement of a local
# module is legitimate and out of scope by construction, not by exemption.
 - name: Check every covered vi.mock factory inherits the real export surface
run: node scripts/check-vi-mock-inherit.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
 Inert vi.mock Specifiers

chore(ci): slow both dependabot channels from weekly to monthly
#1344
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 #1344
Workflow file for this run

.github/workflows/vi-mock-specifiers.yml
 at
92e5d3b
name: Inert vi.mock Specifiers
# Two gates over ONE population, in one home. Both read the `vi.mock` call sites
# of this tree and both catch a mock that is silently not doing what it looks
# like it is doing: `check-vi-mock-specifiers.mjs` catches a specifier that
# resolves to no file (an inert stand-in), and `check-vi-mock-inherit.mjs`
# catches a factory that hand-lists its exports (a frozen export surface,
# objectui#6849). They share the call-site pattern deliberately -- a population
# that drifted between them would be a hole neither one reports -- so they share
# a workflow rather than each registering a required context of its own.
#
# The workflow `name:` and the job `name:` are therefore BROADER than the older
# of the two gates. They are left unchanged on purpose: those two strings are
# the check-run context that branch protection and
# `scripts/dependabot-merge-gate.mjs` name, and renaming a required context
# silently un-requires it.
#
# Why this is its own workflow rather than a step in `ci.yml` or `lint.yml`: a
# module mock can be written into any package, in any shape of pull request, and
# both of those workflows decide inside the job whether the change "needs a full
# run" — with an exclusion list that skips every expensive step on a
# markdown-only or changeset-only change. This gate costs a checkout plus one
# `node` call, so there is nothing to gain by putting it behind that switch and
# a whole class of pull request to lose.
#
# Same shape and the same reasoning as `docs-links.yml`, `control-bytes.yml`,
# `skills-paths.yml`, `changeset-presence.yml` and `pre-install-import-graph.yml`,
# whose headers record the conclusion this repository has now reached five
# times: a gate that cannot see the pull request shape most likely to trip it
# "rebuilds the hole it exists to close". One gate, one home.
#
# Hence: no `paths` and no `paths-ignore` here, deliberately.
# `scripts/__tests__/check-vi-mock-specifiers.test.ts` fails if either is ever
# added, and fails too if a second workflow starts running the same script.
# Reporting on every pull request is also what makes the check requirable, and
# `scripts/dependabot-merge-gate.mjs` classifies it as a required context — an
# unclassified blocking check is one a Dependabot merge would be let past
# (objectui#6135).
#
# It needs no install and no build — a checkout plus one `node` call over ~3.7k
# tracked source files, measured at ~2.7s on this tree. Keep it that way; the
# import graph is builtins plus repo-relative modules only, which
# `pre-install-import-graph.yml` enforces (objectui#6148).
on:
pull_request:
branches: [main, develop]
push:
branches: [main, develop]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). A required check that does not report on a
# queue build stalls the queue until the ruleset's 60-minute timeout fails it,
# so an unfiltered gate that can become required subscribes here from the
# start. `types:` is named although `checks_requested` is currently the only
# activity type GitHub defines for `merge_group`.
merge_group:
types: [checks_requested]
workflow_dispatch:
concurrency:
group: vi-mock-specifiers-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
permissions:
contents: read
jobs:
vi-mock-specifiers:
name: Inert vi.mock Specifier Check
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
 - name: Checkout code
uses: actions/checkout@v7
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# A `vi.mock` whose relative specifier resolves to no file does NOT error.
# Vitest registers the mock against a module id nothing imports, the run
# proceeds with the real module everywhere, and the suite passes —
# identically to a correct one, with no warning and no smaller assertion
# count. objectui#5646: the one known instance (PR #5645) passed even with
# the code under test reverted to the shape the suite was written to
# catch, and only an ablation leg exposed it.
#
# This gate is GREEN AT REST — there are zero unresolvable specifiers in
# the tree and there should stay zero — so it prints its census rather
# than a bare "OK", and it FAILS if the population collapses to nothing.
# A scan that silently finds nothing reads as coverage, which is this
# gate's own defect one level up.
 - name: Check every relative vi.mock specifier resolves
run: node scripts/check-vi-mock-specifiers.mjs
# The sibling property of the same call sites: a factory that HAND-LISTS
# the exports it returns freezes the mock's export surface. The next
# export any module in the file's import graph reads AT MODULE SCOPE then
# kills the file during COLLECTION -- `Test Files 3 failed | 546 passed`
# with `Tests 6694 passed`, ZERO failed assertions, because the tests in
# those files never ran (objectui#6768). It reads as flake to whoever
# sees it next, and the bill lands on whoever added the export.
#
# The recogniser is SEMANTIC, never a grep for `importOriginal`: that
# spelling mis-counted eleven correct files as broken AND missed one
# broken file entirely (objectui#6849). It asks whether the factory
# OBTAINS the real module -- a callback parameter under any name, or
# `vi.importActual` of the same specifier -- and SPREADS it.
#
# Narrow by ruling: only the covered workspace specifiers in
# `COVERED_SPECIFIERS` are judged. Whole-module replacement of a local
# module is legitimate and out of scope by construction, not by exemption.
 - name: Check every covered vi.mock factory inherits the real export surface
run: node scripts/check-vi-mock-inherit.mjs