Single-Claim Path Guard

feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading #3405

Sign in to view logs

feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading

feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading #3405

Workflow file for this run

.github/workflows/single-claim-path-guard.yml at fe829be
# Two PRs reached green independently while shipping ONE physical change: both
# rewrote the objectui pin from the same old sha to the same new sha and both
# added the same generated changeset — a byte-identical hunk under two card
# numbers. The first entered the merge queue; the second was green and one flip
# from enqueueing behind it, where it would have conflicted on both files.
#
# The repo's Duplicate Fix Guard is not broken and is not touched by this file.
# It asks whether two open PRs claim the same CARD, and it answered correctly:
# these claimed two genuinely different, independently filed cards, neither a
# duplicate of the other as written. The duplication existed only in the diff.
# This workflow adds the second question — do two open PRs write the same
# at-most-one-writer path — and the two gates run side by side.
#
# The rule, the declared path list, the measured false-positive rates that
# forced a declared list instead of repo-wide diff intersection, and the wording
# of the failure all live in `scripts/check-single-claim-paths.mjs`; that header
# is authoritative and this file is the invocation.
#
# Sibling shape, deliberately copied rather than reinvented: the Part-of
# Closing-Keyword Guard is this repo's other single-script PR-scoped blocking
# check, and this takes its job shape, its runtime pin and its trigger set.
name: Single-Claim Path Guard
# `synchronize` is the load-bearing one here, and that is the difference from
# the two body-scoped guards this otherwise copies. Their whole input is the PR
# body, so `edited` is what they need; this one's input is the PR's CHANGED
# FILES, which move on every push. A PR that adds a claim on a listed path in
# its second commit must be judged on that commit, and one that drops the path
# again must be able to go green without being closed and reopened.
#
# `edited` is kept anyway and is not decoration: the failure text tells a reader
# to close one of the two PRs, and closing the earlier one must let the later
# one recover. That recovery arrives as an event on the SURVIVING PR only if it
# is touched — so `edited` is the cheap, no-push way back to green, exactly as
# in the sibling guards.
#
# No `merge_group:` trigger, and not by oversight: a merge-queue event carries
# no pull request, so this check has nothing to judge there. That also keeps it
# out of the required-context registry, whose entries must report on queue
# builds. Branch protection is a settings change no agent seat can make; this
# publishes a check run, and whether it becomes REQUIRED carries a maintainer
# ruling. The Duplicate Fix Guard sits in exactly the same position.
on:
pull_request:
types: [opened, edited, reopened, synchronize]
# Read-only, and that is the whole grant. This gate reports; it never closes a
# PR, comments, or edits a body. The one incident where a duplicate PR was
# closed, it was closed by a human who spotted by eye what no gate could see —
# and a gate that closed PRs by itself would be a far more expensive mistake
# than the one it prevents.
#
# `contents: read` is not optional padding: naming a `permissions:` block at all
# sets every scope NOT listed to `none`, and this job checks the repo out to get
# at the script. With only the pull-requests scope here the job dies in the
# checkout step, before the gate ever runs — a gate that is red for a reason
# that has nothing to do with what it checks.
permissions:
contents: read
pull-requests: read
concurrency:
group: single-claim-path-${{ github.event.pull_request.number }}
cancel-in-progress: true
jobs:
single-claim-path:
name: No other open PR may claim the same single-writer path
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v7
# Pinned to the same major and spelling as every other setup-node in this
# repo, for the measured reason recorded in the sibling guard's header:
# a setup-node major whose package-manager-cache default is on reads
# `packageManager` out of package.json and shells out to pnpm to find its
# store, killing the job in the SETUP step with "Unable to locate
# executable file: pnpm" — before the script runs, and naming a tool the
# workflow source never mentions. This job installs no package manager on
# purpose: the script is dependency-free and imports nothing.
- name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22'
# Everything reaches the script through `env:`, never through `${{ }}`
# inside the `run:` line. Nothing here is attacker-controlled text today
# — a PR number is a number — but the spelling is the one the sibling
# guard's self-test pins, and keeping both gates identical on this point
# is what stops a later edit from introducing the unsafe form by analogy.
#
# `PR_NUMBER` is also the witness that separates a real verdict from an
# unwired run: with it absent the script exits 2 and says it judged
# nothing, rather than exiting 0 and reading as "no violations".
#
# The token is required, not optional: this gate's question is about OTHER
# open PRs, which cannot be answered from the event payload. The read is
# short-circuited on the cheap side — when this PR touches none of the
# declared paths, which is ~99.7% of runs by measurement, the job makes a
# single API call and stops.
- name: At most one open PR may modify a declared single-writer path
env:
PR_NUMBER: ${{ github.event.pull_request.number }}
GITHUB_REPOSITORY: ${{ github.repository }}
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: node scripts/check-single-claim-paths.mjs
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
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;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} 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
 Single-Claim Path Guard

feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading
#3405
Sign in to view logs

feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading


feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading #3405
Workflow file for this run

.github/workflows/single-claim-path-guard.yml
 at
fe829be
# Two PRs reached green independently while shipping ONE physical change: both
# rewrote the objectui pin from the same old sha to the same new sha and both
# added the same generated changeset — a byte-identical hunk under two card
# numbers. The first entered the merge queue; the second was green and one flip
# from enqueueing behind it, where it would have conflicted on both files.
#
# The repo's Duplicate Fix Guard is not broken and is not touched by this file.
# It asks whether two open PRs claim the same CARD, and it answered correctly:
# these claimed two genuinely different, independently filed cards, neither a
# duplicate of the other as written. The duplication existed only in the diff.
# This workflow adds the second question — do two open PRs write the same
# at-most-one-writer path — and the two gates run side by side.
#
# The rule, the declared path list, the measured false-positive rates that
# forced a declared list instead of repo-wide diff intersection, and the wording
# of the failure all live in `scripts/check-single-claim-paths.mjs`; that header
# is authoritative and this file is the invocation.
#
# Sibling shape, deliberately copied rather than reinvented: the Part-of
# Closing-Keyword Guard is this repo's other single-script PR-scoped blocking
# check, and this takes its job shape, its runtime pin and its trigger set.
name: Single-Claim Path Guard
# `synchronize` is the load-bearing one here, and that is the difference from
# the two body-scoped guards this otherwise copies. Their whole input is the PR
# body, so `edited` is what they need; this one's input is the PR's CHANGED
# FILES, which move on every push. A PR that adds a claim on a listed path in
# its second commit must be judged on that commit, and one that drops the path
# again must be able to go green without being closed and reopened.
#
# `edited` is kept anyway and is not decoration: the failure text tells a reader
# to close one of the two PRs, and closing the earlier one must let the later
# one recover. That recovery arrives as an event on the SURVIVING PR only if it
# is touched — so `edited` is the cheap, no-push way back to green, exactly as
# in the sibling guards.
#
# No `merge_group:` trigger, and not by oversight: a merge-queue event carries
# no pull request, so this check has nothing to judge there. That also keeps it
# out of the required-context registry, whose entries must report on queue
# builds. Branch protection is a settings change no agent seat can make; this
# publishes a check run, and whether it becomes REQUIRED carries a maintainer
# ruling. The Duplicate Fix Guard sits in exactly the same position.
on:
pull_request:
types: [opened, edited, reopened, synchronize]
# Read-only, and that is the whole grant. This gate reports; it never closes a
# PR, comments, or edits a body. The one incident where a duplicate PR was
# closed, it was closed by a human who spotted by eye what no gate could see —
# and a gate that closed PRs by itself would be a far more expensive mistake
# than the one it prevents.
#
# `contents: read` is not optional padding: naming a `permissions:` block at all
# sets every scope NOT listed to `none`, and this job checks the repo out to get
# at the script. With only the pull-requests scope here the job dies in the
# checkout step, before the gate ever runs — a gate that is red for a reason
# that has nothing to do with what it checks.
permissions:
contents: read
pull-requests: read
concurrency:
group: single-claim-path-${{ github.event.pull_request.number }}
cancel-in-progress: true
jobs:
single-claim-path:
name: No other open PR may claim the same single-writer path
runs-on: ubuntu-latest
steps:
 - name: Checkout repository
uses: actions/checkout@v7
# Pinned to the same major and spelling as every other setup-node in this
# repo, for the measured reason recorded in the sibling guard's header:
# a setup-node major whose package-manager-cache default is on reads
# `packageManager` out of package.json and shells out to pnpm to find its
# store, killing the job in the SETUP step with "Unable to locate
# executable file: pnpm" — before the script runs, and naming a tool the
# workflow source never mentions. This job installs no package manager on
# purpose: the script is dependency-free and imports nothing.
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22'
# Everything reaches the script through `env:`, never through `${{ }}`
# inside the `run:` line. Nothing here is attacker-controlled text today
# — a PR number is a number — but the spelling is the one the sibling
# guard's self-test pins, and keeping both gates identical on this point
# is what stops a later edit from introducing the unsafe form by analogy.
#
# `PR_NUMBER` is also the witness that separates a real verdict from an
# unwired run: with it absent the script exits 2 and says it judged
# nothing, rather than exiting 0 and reading as "no violations".
#
# The token is required, not optional: this gate's question is about OTHER
# open PRs, which cannot be answered from the event payload. The read is
# short-circuited on the cheap side — when this PR touches none of the
# declared paths, which is ~99.7% of runs by measurement, the job makes a
# single API call and stops.
 - name: At most one open PR may modify a declared single-writer path
env:
PR_NUMBER: ${{ github.event.pull_request.number }}
GITHUB_REPOSITORY: ${{ github.repository }}
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: node scripts/check-single-claim-paths.mjs

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

Skip to content
 Single-Claim Path Guard

feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading
#3405
Sign in to view logs

feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading


feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading #3405
Workflow file for this run

.github/workflows/single-claim-path-guard.yml
 at
fe829be
# Two PRs reached green independently while shipping ONE physical change: both
# rewrote the objectui pin from the same old sha to the same new sha and both
# added the same generated changeset — a byte-identical hunk under two card
# numbers. The first entered the merge queue; the second was green and one flip
# from enqueueing behind it, where it would have conflicted on both files.
#
# The repo's Duplicate Fix Guard is not broken and is not touched by this file.
# It asks whether two open PRs claim the same CARD, and it answered correctly:
# these claimed two genuinely different, independently filed cards, neither a
# duplicate of the other as written. The duplication existed only in the diff.
# This workflow adds the second question — do two open PRs write the same
# at-most-one-writer path — and the two gates run side by side.
#
# The rule, the declared path list, the measured false-positive rates that
# forced a declared list instead of repo-wide diff intersection, and the wording
# of the failure all live in `scripts/check-single-claim-paths.mjs`; that header
# is authoritative and this file is the invocation.
#
# Sibling shape, deliberately copied rather than reinvented: the Part-of
# Closing-Keyword Guard is this repo's other single-script PR-scoped blocking
# check, and this takes its job shape, its runtime pin and its trigger set.
name: Single-Claim Path Guard
# `synchronize` is the load-bearing one here, and that is the difference from
# the two body-scoped guards this otherwise copies. Their whole input is the PR
# body, so `edited` is what they need; this one's input is the PR's CHANGED
# FILES, which move on every push. A PR that adds a claim on a listed path in
# its second commit must be judged on that commit, and one that drops the path
# again must be able to go green without being closed and reopened.
#
# `edited` is kept anyway and is not decoration: the failure text tells a reader
# to close one of the two PRs, and closing the earlier one must let the later
# one recover. That recovery arrives as an event on the SURVIVING PR only if it
# is touched — so `edited` is the cheap, no-push way back to green, exactly as
# in the sibling guards.
#
# No `merge_group:` trigger, and not by oversight: a merge-queue event carries
# no pull request, so this check has nothing to judge there. That also keeps it
# out of the required-context registry, whose entries must report on queue
# builds. Branch protection is a settings change no agent seat can make; this
# publishes a check run, and whether it becomes REQUIRED carries a maintainer
# ruling. The Duplicate Fix Guard sits in exactly the same position.
on:
pull_request:
types: [opened, edited, reopened, synchronize]
# Read-only, and that is the whole grant. This gate reports; it never closes a
# PR, comments, or edits a body. The one incident where a duplicate PR was
# closed, it was closed by a human who spotted by eye what no gate could see —
# and a gate that closed PRs by itself would be a far more expensive mistake
# than the one it prevents.
#
# `contents: read` is not optional padding: naming a `permissions:` block at all
# sets every scope NOT listed to `none`, and this job checks the repo out to get
# at the script. With only the pull-requests scope here the job dies in the
# checkout step, before the gate ever runs — a gate that is red for a reason
# that has nothing to do with what it checks.
permissions:
contents: read
pull-requests: read
concurrency:
group: single-claim-path-${{ github.event.pull_request.number }}
cancel-in-progress: true
jobs:
single-claim-path:
name: No other open PR may claim the same single-writer path
runs-on: ubuntu-latest
steps:
 - name: Checkout repository
uses: actions/checkout@v7
# Pinned to the same major and spelling as every other setup-node in this
# repo, for the measured reason recorded in the sibling guard's header:
# a setup-node major whose package-manager-cache default is on reads
# `packageManager` out of package.json and shells out to pnpm to find its
# store, killing the job in the SETUP step with "Unable to locate
# executable file: pnpm" — before the script runs, and naming a tool the
# workflow source never mentions. This job installs no package manager on
# purpose: the script is dependency-free and imports nothing.
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22'
# Everything reaches the script through `env:`, never through `${{ }}`
# inside the `run:` line. Nothing here is attacker-controlled text today
# — a PR number is a number — but the spelling is the one the sibling
# guard's self-test pins, and keeping both gates identical on this point
# is what stops a later edit from introducing the unsafe form by analogy.
#
# `PR_NUMBER` is also the witness that separates a real verdict from an
# unwired run: with it absent the script exits 2 and says it judged
# nothing, rather than exiting 0 and reading as "no violations".
#
# The token is required, not optional: this gate's question is about OTHER
# open PRs, which cannot be answered from the event payload. The read is
# short-circuited on the cheap side — when this PR touches none of the
# declared paths, which is ~99.7% of runs by measurement, the job makes a
# single API call and stops.
 - name: At most one open PR may modify a declared single-writer path
env:
PR_NUMBER: ${{ github.event.pull_request.number }}
GITHUB_REPOSITORY: ${{ github.repository }}
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: node scripts/check-single-claim-paths.mjs

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

Skip to content
 Single-Claim Path Guard

feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading
#3405
Sign in to view logs

feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading


feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading #3405
Workflow file for this run

.github/workflows/single-claim-path-guard.yml
 at
fe829be
# Two PRs reached green independently while shipping ONE physical change: both
# rewrote the objectui pin from the same old sha to the same new sha and both
# added the same generated changeset — a byte-identical hunk under two card
# numbers. The first entered the merge queue; the second was green and one flip
# from enqueueing behind it, where it would have conflicted on both files.
#
# The repo's Duplicate Fix Guard is not broken and is not touched by this file.
# It asks whether two open PRs claim the same CARD, and it answered correctly:
# these claimed two genuinely different, independently filed cards, neither a
# duplicate of the other as written. The duplication existed only in the diff.
# This workflow adds the second question — do two open PRs write the same
# at-most-one-writer path — and the two gates run side by side.
#
# The rule, the declared path list, the measured false-positive rates that
# forced a declared list instead of repo-wide diff intersection, and the wording
# of the failure all live in `scripts/check-single-claim-paths.mjs`; that header
# is authoritative and this file is the invocation.
#
# Sibling shape, deliberately copied rather than reinvented: the Part-of
# Closing-Keyword Guard is this repo's other single-script PR-scoped blocking
# check, and this takes its job shape, its runtime pin and its trigger set.
name: Single-Claim Path Guard
# `synchronize` is the load-bearing one here, and that is the difference from
# the two body-scoped guards this otherwise copies. Their whole input is the PR
# body, so `edited` is what they need; this one's input is the PR's CHANGED
# FILES, which move on every push. A PR that adds a claim on a listed path in
# its second commit must be judged on that commit, and one that drops the path
# again must be able to go green without being closed and reopened.
#
# `edited` is kept anyway and is not decoration: the failure text tells a reader
# to close one of the two PRs, and closing the earlier one must let the later
# one recover. That recovery arrives as an event on the SURVIVING PR only if it
# is touched — so `edited` is the cheap, no-push way back to green, exactly as
# in the sibling guards.
#
# No `merge_group:` trigger, and not by oversight: a merge-queue event carries
# no pull request, so this check has nothing to judge there. That also keeps it
# out of the required-context registry, whose entries must report on queue
# builds. Branch protection is a settings change no agent seat can make; this
# publishes a check run, and whether it becomes REQUIRED carries a maintainer
# ruling. The Duplicate Fix Guard sits in exactly the same position.
on:
pull_request:
types: [opened, edited, reopened, synchronize]
# Read-only, and that is the whole grant. This gate reports; it never closes a
# PR, comments, or edits a body. The one incident where a duplicate PR was
# closed, it was closed by a human who spotted by eye what no gate could see —
# and a gate that closed PRs by itself would be a far more expensive mistake
# than the one it prevents.
#
# `contents: read` is not optional padding: naming a `permissions:` block at all
# sets every scope NOT listed to `none`, and this job checks the repo out to get
# at the script. With only the pull-requests scope here the job dies in the
# checkout step, before the gate ever runs — a gate that is red for a reason
# that has nothing to do with what it checks.
permissions:
contents: read
pull-requests: read
concurrency:
group: single-claim-path-${{ github.event.pull_request.number }}
cancel-in-progress: true
jobs:
single-claim-path:
name: No other open PR may claim the same single-writer path
runs-on: ubuntu-latest
steps:
 - name: Checkout repository
uses: actions/checkout@v7
# Pinned to the same major and spelling as every other setup-node in this
# repo, for the measured reason recorded in the sibling guard's header:
# a setup-node major whose package-manager-cache default is on reads
# `packageManager` out of package.json and shells out to pnpm to find its
# store, killing the job in the SETUP step with "Unable to locate
# executable file: pnpm" — before the script runs, and naming a tool the
# workflow source never mentions. This job installs no package manager on
# purpose: the script is dependency-free and imports nothing.
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22'
# Everything reaches the script through `env:`, never through `${{ }}`
# inside the `run:` line. Nothing here is attacker-controlled text today
# — a PR number is a number — but the spelling is the one the sibling
# guard's self-test pins, and keeping both gates identical on this point
# is what stops a later edit from introducing the unsafe form by analogy.
#
# `PR_NUMBER` is also the witness that separates a real verdict from an
# unwired run: with it absent the script exits 2 and says it judged
# nothing, rather than exiting 0 and reading as "no violations".
#
# The token is required, not optional: this gate's question is about OTHER
# open PRs, which cannot be answered from the event payload. The read is
# short-circuited on the cheap side — when this PR touches none of the
# declared paths, which is ~99.7% of runs by measurement, the job makes a
# single API call and stops.
 - name: At most one open PR may modify a declared single-writer path
env:
PR_NUMBER: ${{ github.event.pull_request.number }}
GITHUB_REPOSITORY: ${{ github.repository }}
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: node scripts/check-single-claim-paths.mjs

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} 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
 Single-Claim Path Guard

feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading
#3405
Sign in to view logs

feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading


feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading #3405
Workflow file for this run

.github/workflows/single-claim-path-guard.yml
 at
fe829be
# Two PRs reached green independently while shipping ONE physical change: both
# rewrote the objectui pin from the same old sha to the same new sha and both
# added the same generated changeset — a byte-identical hunk under two card
# numbers. The first entered the merge queue; the second was green and one flip
# from enqueueing behind it, where it would have conflicted on both files.
#
# The repo's Duplicate Fix Guard is not broken and is not touched by this file.
# It asks whether two open PRs claim the same CARD, and it answered correctly:
# these claimed two genuinely different, independently filed cards, neither a
# duplicate of the other as written. The duplication existed only in the diff.
# This workflow adds the second question — do two open PRs write the same
# at-most-one-writer path — and the two gates run side by side.
#
# The rule, the declared path list, the measured false-positive rates that
# forced a declared list instead of repo-wide diff intersection, and the wording
# of the failure all live in `scripts/check-single-claim-paths.mjs`; that header
# is authoritative and this file is the invocation.
#
# Sibling shape, deliberately copied rather than reinvented: the Part-of
# Closing-Keyword Guard is this repo's other single-script PR-scoped blocking
# check, and this takes its job shape, its runtime pin and its trigger set.
name: Single-Claim Path Guard
# `synchronize` is the load-bearing one here, and that is the difference from
# the two body-scoped guards this otherwise copies. Their whole input is the PR
# body, so `edited` is what they need; this one's input is the PR's CHANGED
# FILES, which move on every push. A PR that adds a claim on a listed path in
# its second commit must be judged on that commit, and one that drops the path
# again must be able to go green without being closed and reopened.
#
# `edited` is kept anyway and is not decoration: the failure text tells a reader
# to close one of the two PRs, and closing the earlier one must let the later
# one recover. That recovery arrives as an event on the SURVIVING PR only if it
# is touched — so `edited` is the cheap, no-push way back to green, exactly as
# in the sibling guards.
#
# No `merge_group:` trigger, and not by oversight: a merge-queue event carries
# no pull request, so this check has nothing to judge there. That also keeps it
# out of the required-context registry, whose entries must report on queue
# builds. Branch protection is a settings change no agent seat can make; this
# publishes a check run, and whether it becomes REQUIRED carries a maintainer
# ruling. The Duplicate Fix Guard sits in exactly the same position.
on:
pull_request:
types: [opened, edited, reopened, synchronize]
# Read-only, and that is the whole grant. This gate reports; it never closes a
# PR, comments, or edits a body. The one incident where a duplicate PR was
# closed, it was closed by a human who spotted by eye what no gate could see —
# and a gate that closed PRs by itself would be a far more expensive mistake
# than the one it prevents.
#
# `contents: read` is not optional padding: naming a `permissions:` block at all
# sets every scope NOT listed to `none`, and this job checks the repo out to get
# at the script. With only the pull-requests scope here the job dies in the
# checkout step, before the gate ever runs — a gate that is red for a reason
# that has nothing to do with what it checks.
permissions:
contents: read
pull-requests: read
concurrency:
group: single-claim-path-${{ github.event.pull_request.number }}
cancel-in-progress: true
jobs:
single-claim-path:
name: No other open PR may claim the same single-writer path
runs-on: ubuntu-latest
steps:
 - name: Checkout repository
uses: actions/checkout@v7
# Pinned to the same major and spelling as every other setup-node in this
# repo, for the measured reason recorded in the sibling guard's header:
# a setup-node major whose package-manager-cache default is on reads
# `packageManager` out of package.json and shells out to pnpm to find its
# store, killing the job in the SETUP step with "Unable to locate
# executable file: pnpm" — before the script runs, and naming a tool the
# workflow source never mentions. This job installs no package manager on
# purpose: the script is dependency-free and imports nothing.
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22'
# Everything reaches the script through `env:`, never through `${{ }}`
# inside the `run:` line. Nothing here is attacker-controlled text today
# — a PR number is a number — but the spelling is the one the sibling
# guard's self-test pins, and keeping both gates identical on this point
# is what stops a later edit from introducing the unsafe form by analogy.
#
# `PR_NUMBER` is also the witness that separates a real verdict from an
# unwired run: with it absent the script exits 2 and says it judged
# nothing, rather than exiting 0 and reading as "no violations".
#
# The token is required, not optional: this gate's question is about OTHER
# open PRs, which cannot be answered from the event payload. The read is
# short-circuited on the cheap side — when this PR touches none of the
# declared paths, which is ~99.7% of runs by measurement, the job makes a
# single API call and stops.
 - name: At most one open PR may modify a declared single-writer path
env:
PR_NUMBER: ${{ github.event.pull_request.number }}
GITHUB_REPOSITORY: ${{ github.repository }}
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: node scripts/check-single-claim-paths.mjs

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

Skip to content
 Single-Claim Path Guard

feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading
#3405
Sign in to view logs

feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading


feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading #3405
Workflow file for this run

.github/workflows/single-claim-path-guard.yml
 at
fe829be
# Two PRs reached green independently while shipping ONE physical change: both
# rewrote the objectui pin from the same old sha to the same new sha and both
# added the same generated changeset — a byte-identical hunk under two card
# numbers. The first entered the merge queue; the second was green and one flip
# from enqueueing behind it, where it would have conflicted on both files.
#
# The repo's Duplicate Fix Guard is not broken and is not touched by this file.
# It asks whether two open PRs claim the same CARD, and it answered correctly:
# these claimed two genuinely different, independently filed cards, neither a
# duplicate of the other as written. The duplication existed only in the diff.
# This workflow adds the second question — do two open PRs write the same
# at-most-one-writer path — and the two gates run side by side.
#
# The rule, the declared path list, the measured false-positive rates that
# forced a declared list instead of repo-wide diff intersection, and the wording
# of the failure all live in `scripts/check-single-claim-paths.mjs`; that header
# is authoritative and this file is the invocation.
#
# Sibling shape, deliberately copied rather than reinvented: the Part-of
# Closing-Keyword Guard is this repo's other single-script PR-scoped blocking
# check, and this takes its job shape, its runtime pin and its trigger set.
name: Single-Claim Path Guard
# `synchronize` is the load-bearing one here, and that is the difference from
# the two body-scoped guards this otherwise copies. Their whole input is the PR
# body, so `edited` is what they need; this one's input is the PR's CHANGED
# FILES, which move on every push. A PR that adds a claim on a listed path in
# its second commit must be judged on that commit, and one that drops the path
# again must be able to go green without being closed and reopened.
#
# `edited` is kept anyway and is not decoration: the failure text tells a reader
# to close one of the two PRs, and closing the earlier one must let the later
# one recover. That recovery arrives as an event on the SURVIVING PR only if it
# is touched — so `edited` is the cheap, no-push way back to green, exactly as
# in the sibling guards.
#
# No `merge_group:` trigger, and not by oversight: a merge-queue event carries
# no pull request, so this check has nothing to judge there. That also keeps it
# out of the required-context registry, whose entries must report on queue
# builds. Branch protection is a settings change no agent seat can make; this
# publishes a check run, and whether it becomes REQUIRED carries a maintainer
# ruling. The Duplicate Fix Guard sits in exactly the same position.
on:
pull_request:
types: [opened, edited, reopened, synchronize]
# Read-only, and that is the whole grant. This gate reports; it never closes a
# PR, comments, or edits a body. The one incident where a duplicate PR was
# closed, it was closed by a human who spotted by eye what no gate could see —
# and a gate that closed PRs by itself would be a far more expensive mistake
# than the one it prevents.
#
# `contents: read` is not optional padding: naming a `permissions:` block at all
# sets every scope NOT listed to `none`, and this job checks the repo out to get
# at the script. With only the pull-requests scope here the job dies in the
# checkout step, before the gate ever runs — a gate that is red for a reason
# that has nothing to do with what it checks.
permissions:
contents: read
pull-requests: read
concurrency:
group: single-claim-path-${{ github.event.pull_request.number }}
cancel-in-progress: true
jobs:
single-claim-path:
name: No other open PR may claim the same single-writer path
runs-on: ubuntu-latest
steps:
 - name: Checkout repository
uses: actions/checkout@v7
# Pinned to the same major and spelling as every other setup-node in this
# repo, for the measured reason recorded in the sibling guard's header:
# a setup-node major whose package-manager-cache default is on reads
# `packageManager` out of package.json and shells out to pnpm to find its
# store, killing the job in the SETUP step with "Unable to locate
# executable file: pnpm" — before the script runs, and naming a tool the
# workflow source never mentions. This job installs no package manager on
# purpose: the script is dependency-free and imports nothing.
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22'
# Everything reaches the script through `env:`, never through `${{ }}`
# inside the `run:` line. Nothing here is attacker-controlled text today
# — a PR number is a number — but the spelling is the one the sibling
# guard's self-test pins, and keeping both gates identical on this point
# is what stops a later edit from introducing the unsafe form by analogy.
#
# `PR_NUMBER` is also the witness that separates a real verdict from an
# unwired run: with it absent the script exits 2 and says it judged
# nothing, rather than exiting 0 and reading as "no violations".
#
# The token is required, not optional: this gate's question is about OTHER
# open PRs, which cannot be answered from the event payload. The read is
# short-circuited on the cheap side — when this PR touches none of the
# declared paths, which is ~99.7% of runs by measurement, the job makes a
# single API call and stops.
 - name: At most one open PR may modify a declared single-writer path
env:
PR_NUMBER: ${{ github.event.pull_request.number }}
GITHUB_REPOSITORY: ${{ github.repository }}
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: node scripts/check-single-claim-paths.mjs

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

Skip to content
 Single-Claim Path Guard

feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading
#3405
Sign in to view logs

feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading


feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading #3405
Workflow file for this run

.github/workflows/single-claim-path-guard.yml
 at
fe829be
# Two PRs reached green independently while shipping ONE physical change: both
# rewrote the objectui pin from the same old sha to the same new sha and both
# added the same generated changeset — a byte-identical hunk under two card
# numbers. The first entered the merge queue; the second was green and one flip
# from enqueueing behind it, where it would have conflicted on both files.
#
# The repo's Duplicate Fix Guard is not broken and is not touched by this file.
# It asks whether two open PRs claim the same CARD, and it answered correctly:
# these claimed two genuinely different, independently filed cards, neither a
# duplicate of the other as written. The duplication existed only in the diff.
# This workflow adds the second question — do two open PRs write the same
# at-most-one-writer path — and the two gates run side by side.
#
# The rule, the declared path list, the measured false-positive rates that
# forced a declared list instead of repo-wide diff intersection, and the wording
# of the failure all live in `scripts/check-single-claim-paths.mjs`; that header
# is authoritative and this file is the invocation.
#
# Sibling shape, deliberately copied rather than reinvented: the Part-of
# Closing-Keyword Guard is this repo's other single-script PR-scoped blocking
# check, and this takes its job shape, its runtime pin and its trigger set.
name: Single-Claim Path Guard
# `synchronize` is the load-bearing one here, and that is the difference from
# the two body-scoped guards this otherwise copies. Their whole input is the PR
# body, so `edited` is what they need; this one's input is the PR's CHANGED
# FILES, which move on every push. A PR that adds a claim on a listed path in
# its second commit must be judged on that commit, and one that drops the path
# again must be able to go green without being closed and reopened.
#
# `edited` is kept anyway and is not decoration: the failure text tells a reader
# to close one of the two PRs, and closing the earlier one must let the later
# one recover. That recovery arrives as an event on the SURVIVING PR only if it
# is touched — so `edited` is the cheap, no-push way back to green, exactly as
# in the sibling guards.
#
# No `merge_group:` trigger, and not by oversight: a merge-queue event carries
# no pull request, so this check has nothing to judge there. That also keeps it
# out of the required-context registry, whose entries must report on queue
# builds. Branch protection is a settings change no agent seat can make; this
# publishes a check run, and whether it becomes REQUIRED carries a maintainer
# ruling. The Duplicate Fix Guard sits in exactly the same position.
on:
pull_request:
types: [opened, edited, reopened, synchronize]
# Read-only, and that is the whole grant. This gate reports; it never closes a
# PR, comments, or edits a body. The one incident where a duplicate PR was
# closed, it was closed by a human who spotted by eye what no gate could see —
# and a gate that closed PRs by itself would be a far more expensive mistake
# than the one it prevents.
#
# `contents: read` is not optional padding: naming a `permissions:` block at all
# sets every scope NOT listed to `none`, and this job checks the repo out to get
# at the script. With only the pull-requests scope here the job dies in the
# checkout step, before the gate ever runs — a gate that is red for a reason
# that has nothing to do with what it checks.
permissions:
contents: read
pull-requests: read
concurrency:
group: single-claim-path-${{ github.event.pull_request.number }}
cancel-in-progress: true
jobs:
single-claim-path:
name: No other open PR may claim the same single-writer path
runs-on: ubuntu-latest
steps:
 - name: Checkout repository
uses: actions/checkout@v7
# Pinned to the same major and spelling as every other setup-node in this
# repo, for the measured reason recorded in the sibling guard's header:
# a setup-node major whose package-manager-cache default is on reads
# `packageManager` out of package.json and shells out to pnpm to find its
# store, killing the job in the SETUP step with "Unable to locate
# executable file: pnpm" — before the script runs, and naming a tool the
# workflow source never mentions. This job installs no package manager on
# purpose: the script is dependency-free and imports nothing.
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22'
# Everything reaches the script through `env:`, never through `${{ }}`
# inside the `run:` line. Nothing here is attacker-controlled text today
# — a PR number is a number — but the spelling is the one the sibling
# guard's self-test pins, and keeping both gates identical on this point
# is what stops a later edit from introducing the unsafe form by analogy.
#
# `PR_NUMBER` is also the witness that separates a real verdict from an
# unwired run: with it absent the script exits 2 and says it judged
# nothing, rather than exiting 0 and reading as "no violations".
#
# The token is required, not optional: this gate's question is about OTHER
# open PRs, which cannot be answered from the event payload. The read is
# short-circuited on the cheap side — when this PR touches none of the
# declared paths, which is ~99.7% of runs by measurement, the job makes a
# single API call and stops.
 - name: At most one open PR may modify a declared single-writer path
env:
PR_NUMBER: ${{ github.event.pull_request.number }}
GITHUB_REPOSITORY: ${{ github.repository }}
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: node scripts/check-single-claim-paths.mjs

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

Skip to content
 Single-Claim Path Guard

feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading
#3405
Sign in to view logs

feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading


feat(scripts,adr): a published TYPE-surface narrowing gets an honest ADR-0087 disposition — the sixth category, paid for by a base-side type reading #3405
Workflow file for this run

.github/workflows/single-claim-path-guard.yml
 at
fe829be
# Two PRs reached green independently while shipping ONE physical change: both
# rewrote the objectui pin from the same old sha to the same new sha and both
# added the same generated changeset — a byte-identical hunk under two card
# numbers. The first entered the merge queue; the second was green and one flip
# from enqueueing behind it, where it would have conflicted on both files.
#
# The repo's Duplicate Fix Guard is not broken and is not touched by this file.
# It asks whether two open PRs claim the same CARD, and it answered correctly:
# these claimed two genuinely different, independently filed cards, neither a
# duplicate of the other as written. The duplication existed only in the diff.
# This workflow adds the second question — do two open PRs write the same
# at-most-one-writer path — and the two gates run side by side.
#
# The rule, the declared path list, the measured false-positive rates that
# forced a declared list instead of repo-wide diff intersection, and the wording
# of the failure all live in `scripts/check-single-claim-paths.mjs`; that header
# is authoritative and this file is the invocation.
#
# Sibling shape, deliberately copied rather than reinvented: the Part-of
# Closing-Keyword Guard is this repo's other single-script PR-scoped blocking
# check, and this takes its job shape, its runtime pin and its trigger set.
name: Single-Claim Path Guard
# `synchronize` is the load-bearing one here, and that is the difference from
# the two body-scoped guards this otherwise copies. Their whole input is the PR
# body, so `edited` is what they need; this one's input is the PR's CHANGED
# FILES, which move on every push. A PR that adds a claim on a listed path in
# its second commit must be judged on that commit, and one that drops the path
# again must be able to go green without being closed and reopened.
#
# `edited` is kept anyway and is not decoration: the failure text tells a reader
# to close one of the two PRs, and closing the earlier one must let the later
# one recover. That recovery arrives as an event on the SURVIVING PR only if it
# is touched — so `edited` is the cheap, no-push way back to green, exactly as
# in the sibling guards.
#
# No `merge_group:` trigger, and not by oversight: a merge-queue event carries
# no pull request, so this check has nothing to judge there. That also keeps it
# out of the required-context registry, whose entries must report on queue
# builds. Branch protection is a settings change no agent seat can make; this
# publishes a check run, and whether it becomes REQUIRED carries a maintainer
# ruling. The Duplicate Fix Guard sits in exactly the same position.
on:
pull_request:
types: [opened, edited, reopened, synchronize]
# Read-only, and that is the whole grant. This gate reports; it never closes a
# PR, comments, or edits a body. The one incident where a duplicate PR was
# closed, it was closed by a human who spotted by eye what no gate could see —
# and a gate that closed PRs by itself would be a far more expensive mistake
# than the one it prevents.
#
# `contents: read` is not optional padding: naming a `permissions:` block at all
# sets every scope NOT listed to `none`, and this job checks the repo out to get
# at the script. With only the pull-requests scope here the job dies in the
# checkout step, before the gate ever runs — a gate that is red for a reason
# that has nothing to do with what it checks.
permissions:
contents: read
pull-requests: read
concurrency:
group: single-claim-path-${{ github.event.pull_request.number }}
cancel-in-progress: true
jobs:
single-claim-path:
name: No other open PR may claim the same single-writer path
runs-on: ubuntu-latest
steps:
 - name: Checkout repository
uses: actions/checkout@v7
# Pinned to the same major and spelling as every other setup-node in this
# repo, for the measured reason recorded in the sibling guard's header:
# a setup-node major whose package-manager-cache default is on reads
# `packageManager` out of package.json and shells out to pnpm to find its
# store, killing the job in the SETUP step with "Unable to locate
# executable file: pnpm" — before the script runs, and naming a tool the
# workflow source never mentions. This job installs no package manager on
# purpose: the script is dependency-free and imports nothing.
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22'
# Everything reaches the script through `env:`, never through `${{ }}`
# inside the `run:` line. Nothing here is attacker-controlled text today
# — a PR number is a number — but the spelling is the one the sibling
# guard's self-test pins, and keeping both gates identical on this point
# is what stops a later edit from introducing the unsafe form by analogy.
#
# `PR_NUMBER` is also the witness that separates a real verdict from an
# unwired run: with it absent the script exits 2 and says it judged
# nothing, rather than exiting 0 and reading as "no violations".
#
# The token is required, not optional: this gate's question is about OTHER
# open PRs, which cannot be answered from the event payload. The read is
# short-circuited on the cheap side — when this PR touches none of the
# declared paths, which is ~99.7% of runs by measurement, the job makes a
# single API call and stops.
 - name: At most one open PR may modify a declared single-writer path
env:
PR_NUMBER: ${{ github.event.pull_request.number }}
GITHUB_REPOSITORY: ${{ github.repository }}
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: node scripts/check-single-claim-paths.mjs