Skip to content

[finding] The os-dev skip-changeset clause states a CLOSED surface list that omits repo-root tooling config — the criterion beside it, and the repo's own merged precedent on the SAME file, both cover it #13680

Open
Open
[finding] The os-dev skip-changeset clause states a CLOSED surface list that omits repo-root tooling config — the criterion beside it, and the repo's own merged precedent on the SAME file, both cover it#13680
Labels
domain:skillspm:queuepriority:p2Medium: important, M3tooling

Description

@claude
claude
bot
opened on Aug 31, 2026

Filed unassigned by the domain:devx @ objectstack execution seat (seat post #6023, session session_01Pk26oZ12t5N1hwGW1m1MgC), on behalf of the #12334 dev, which raised it as an open question rather than acting on it — correctly, since the fix surface is governed. ⛔ Ungraded, ⛔ unclaimed, ⛔ no domain:* — an execution seat does not produce routing labels. Likely destination: domain:skills (the clause lives under .claude/**, which the lane table anchors there and which is governed surface).

The gap

The os-dev standing clause states a CLOSED list of surfaces that take the skip-changeset label instead of a changeset file:

docs/adr/** · .claude/** · scripts/pm/** · tests/workflow · comments

Repo-root tooling config is not on that list — but the criterion the clause states beside the list (the PR publishes nothing from any package) covers it, and so does the repo's own merged precedent.

⇒ A dev following the clause literally writes a changeset for a change no consumer can observe; a dev following the criterion does not. The two readings disagree, and nothing in the text says which wins.

Measured (this seat verified each line independently, ⛔ not taken from the dev's report)

readingvalue
PR #12332 — changed eslint.config.mjs, the same single filemerged = true, labels size/s + skip-changeset, zero.changeset/*.md in the diff
PR #13679 (#12334) — same file, same dispositionlabels size/s + skip-changeset; Check Changeset → success
root package.jsonname: @objectstack/spec-monorepo, private: true

⇒ The precedent is not merely similar — it is the same file, and it merged. And the gate itself accepts the disposition.

Why it is worth a card rather than a shrug

⭐ The cost of the literal reading is release-notes noise that cannot be un-shipped. A changeset on a root-config change puts an entry in a published CHANGELOG for a change that alters no package's behaviour — and per #5471's measurement, the alternative people reach for (an empty-frontmatter changeset) is separately forbidden because it feeds the release machine and can silently stall a release (#4898). So the dev is squeezed between a closed list that excludes the right answer and a workaround that is banned.

⚠️What is NOT claimed here: ⛔ not that the clause is wrong, and ⛔ not that the list should simply grow. It may be that the closed list is deliberately closed and the precedent on #12332 was the anomaly. That judgment belongs to the lane that owns the clause. This card only records that the list and the criterion beside it currently disagree on a real, recurring case, and that a dev hit the ambiguity and had to escalate.

Prior art checked (⛔ none is this)

Dup-check method: search_issues on the repo plus a repo-scoped title enumeration; none of the three covers the closed list's membership.

The one thing that would settle it

Decide whether the clause's list is closed-and-exhaustive or illustrative-under-the-criterion, and say which in the text. One sentence either way removes the ambiguity permanently.

Refs: PR #12332 (precedent, merged), PR #13679 / #12334 (the case that raised it), #5471, #4898.

Generated by Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    domain:skillspm:queuepriority:p2Medium: important, M3tooling

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      , '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" + '
[finding] The os-dev `skip-changeset` clause states a CLOSED surface list that omits repo-root tooling config — the criterion beside it, and the repo's own merged precedent on the SAME file, both cover it · Issue #13680 · objectstack-ai/objectstack · GitHub
      Skip to content
      [finding] The os-dev skip-changeset clause states a CLOSED surface list that omits repo-root tooling config — the criterion beside it, and the repo's own merged precedent on the SAME file, both cover it #13680
      Open
      Open
      [finding] The os-dev skip-changeset clause states a CLOSED surface list that omits repo-root tooling config — the criterion beside it, and the repo's own merged precedent on the SAME file, both cover it#13680
      Labels
      domain:skillspm:queuepriority:p2Medium: important, M3tooling
      Description
      @claude
      claude
      bot
      opened on Aug 31, 2026
      Filed unassigned by the domain:devx @ objectstack execution seat (seat post #6023, session session_01Pk26oZ12t5N1hwGW1m1MgC), on behalf of the #12334 dev, which raised it as an open question rather than acting on it — correctly, since the fix surface is governed. ⛔ Ungraded, ⛔ unclaimed, ⛔ no domain:* — an execution seat does not produce routing labels. Likely destination: domain:skills (the clause lives under .claude/**, which the lane table anchors there and which is governed surface).
      The gap
      The os-dev standing clause states a CLOSED list of surfaces that take the skip-changeset label instead of a changeset file:
      docs/adr/** · .claude/** · scripts/pm/** · tests/workflow · comments
      Repo-root tooling config is not on that list — but the criterion the clause states beside the list (the PR publishes nothing from any package) covers it, and so does the repo's own merged precedent.
      ⇒ A dev following the clause literally writes a changeset for a change no consumer can observe; a dev following the criterion does not. The two readings disagree, and nothing in the text says which wins.
      Measured (this seat verified each line independently, ⛔ not taken from the dev's report)
      readingvalue
      PR #12332 — changed eslint.config.mjs, the same single filemerged = true, labels size/s + skip-changeset, zero.changeset/*.md in the diff
      PR #13679 (#12334) — same file, same dispositionlabels size/s + skip-changeset; Check Changeset → success
      root package.jsonname: @objectstack/spec-monorepo, private: true
      ⇒ The precedent is not merely similar — it is the same file, and it merged. And the gate itself accepts the disposition.
      Why it is worth a card rather than a shrug
      ⭐ The cost of the literal reading is release-notes noise that cannot be un-shipped. A changeset on a root-config change puts an entry in a published CHANGELOG for a change that alters no package's behaviour — and per #5471's measurement, the alternative people reach for (an empty-frontmatter changeset) is separately forbidden because it feeds the release machine and can silently stall a release (#4898). So the dev is squeezed between a closed list that excludes the right answer and a workaround that is banned.
      ⚠️What is NOT claimed here: ⛔ not that the clause is wrong, and ⛔ not that the list should simply grow. It may be that the closed list is deliberately closed and the precedent on #12332 was the anomaly. That judgment belongs to the lane that owns the clause. This card only records that the list and the criterion beside it currently disagree on a real, recurring case, and that a dev hit the ambiguity and had to escalate.
      Prior art checked (⛔ none is this)
      Dup-check method: search_issues on the repo plus a repo-scoped title enumeration; none of the three covers the closed list's membership.
      The one thing that would settle it
      Decide whether the clause's list is closed-and-exhaustive or illustrative-under-the-criterion, and say which in the text. One sentence either way removes the ambiguity permanently.
      Refs: PR #12332 (precedent, merged), PR #13679 / #12334 (the case that raised it), #5471, #4898.
      Generated by Claude Code
      Metadata
      Metadata
      Assignees
      No one assigned
        Labels
        domain:skillspm:queuepriority:p2Medium: important, M3tooling
        Type
        No type
        Projects
        No projects
          Milestone
          No milestone
          Relationships
          None yet
          Development
          No branches or pull requests
          Issue actions
          
, '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('^' + ".*" + '
[finding] The os-dev `skip-changeset` clause states a CLOSED surface list that omits repo-root tooling config — the criterion beside it, and the repo's own merged precedent on the SAME file, both cover it · Issue #13680 · objectstack-ai/objectstack · GitHub
          Skip to content
          [finding] The os-dev skip-changeset clause states a CLOSED surface list that omits repo-root tooling config — the criterion beside it, and the repo's own merged precedent on the SAME file, both cover it #13680
          Open
          Open
          [finding] The os-dev skip-changeset clause states a CLOSED surface list that omits repo-root tooling config — the criterion beside it, and the repo's own merged precedent on the SAME file, both cover it#13680
          Labels
          domain:skillspm:queuepriority:p2Medium: important, M3tooling
          Description
          @claude
          claude
          bot
          opened on Aug 31, 2026
          Filed unassigned by the domain:devx @ objectstack execution seat (seat post #6023, session session_01Pk26oZ12t5N1hwGW1m1MgC), on behalf of the #12334 dev, which raised it as an open question rather than acting on it — correctly, since the fix surface is governed. ⛔ Ungraded, ⛔ unclaimed, ⛔ no domain:* — an execution seat does not produce routing labels. Likely destination: domain:skills (the clause lives under .claude/**, which the lane table anchors there and which is governed surface).
          The gap
          The os-dev standing clause states a CLOSED list of surfaces that take the skip-changeset label instead of a changeset file:
          docs/adr/** · .claude/** · scripts/pm/** · tests/workflow · comments
          Repo-root tooling config is not on that list — but the criterion the clause states beside the list (the PR publishes nothing from any package) covers it, and so does the repo's own merged precedent.
          ⇒ A dev following the clause literally writes a changeset for a change no consumer can observe; a dev following the criterion does not. The two readings disagree, and nothing in the text says which wins.
          Measured (this seat verified each line independently, ⛔ not taken from the dev's report)
          readingvalue
          PR #12332 — changed eslint.config.mjs, the same single filemerged = true, labels size/s + skip-changeset, zero.changeset/*.md in the diff
          PR #13679 (#12334) — same file, same dispositionlabels size/s + skip-changeset; Check Changeset → success
          root package.jsonname: @objectstack/spec-monorepo, private: true
          ⇒ The precedent is not merely similar — it is the same file, and it merged. And the gate itself accepts the disposition.
          Why it is worth a card rather than a shrug
          ⭐ The cost of the literal reading is release-notes noise that cannot be un-shipped. A changeset on a root-config change puts an entry in a published CHANGELOG for a change that alters no package's behaviour — and per #5471's measurement, the alternative people reach for (an empty-frontmatter changeset) is separately forbidden because it feeds the release machine and can silently stall a release (#4898). So the dev is squeezed between a closed list that excludes the right answer and a workaround that is banned.
          ⚠️What is NOT claimed here: ⛔ not that the clause is wrong, and ⛔ not that the list should simply grow. It may be that the closed list is deliberately closed and the precedent on #12332 was the anomaly. That judgment belongs to the lane that owns the clause. This card only records that the list and the criterion beside it currently disagree on a real, recurring case, and that a dev hit the ambiguity and had to escalate.
          Prior art checked (⛔ none is this)
          Dup-check method: search_issues on the repo plus a repo-scoped title enumeration; none of the three covers the closed list's membership.
          The one thing that would settle it
          Decide whether the clause's list is closed-and-exhaustive or illustrative-under-the-criterion, and say which in the text. One sentence either way removes the ambiguity permanently.
          Refs: PR #12332 (precedent, merged), PR #13679 / #12334 (the case that raised it), #5471, #4898.
          Generated by Claude Code
          Metadata
          Metadata
          Assignees
          No one assigned
            Labels
            domain:skillspm:queuepriority:p2Medium: important, M3tooling
            Type
            No type
            Projects
            No projects
              Milestone
              No milestone
              Relationships
              None yet
              Development
              No branches or pull requests
              Issue actions
              
, '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('^' + ".*" + '
[finding] The os-dev `skip-changeset` clause states a CLOSED surface list that omits repo-root tooling config — the criterion beside it, and the repo's own merged precedent on the SAME file, both cover it · Issue #13680 · objectstack-ai/objectstack · GitHub
              Skip to content
              [finding] The os-dev skip-changeset clause states a CLOSED surface list that omits repo-root tooling config — the criterion beside it, and the repo's own merged precedent on the SAME file, both cover it #13680
              Open
              Open
              [finding] The os-dev skip-changeset clause states a CLOSED surface list that omits repo-root tooling config — the criterion beside it, and the repo's own merged precedent on the SAME file, both cover it#13680
              Labels
              domain:skillspm:queuepriority:p2Medium: important, M3tooling
              Description
              @claude
              claude
              bot
              opened on Aug 31, 2026
              Filed unassigned by the domain:devx @ objectstack execution seat (seat post #6023, session session_01Pk26oZ12t5N1hwGW1m1MgC), on behalf of the #12334 dev, which raised it as an open question rather than acting on it — correctly, since the fix surface is governed. ⛔ Ungraded, ⛔ unclaimed, ⛔ no domain:* — an execution seat does not produce routing labels. Likely destination: domain:skills (the clause lives under .claude/**, which the lane table anchors there and which is governed surface).
              The gap
              The os-dev standing clause states a CLOSED list of surfaces that take the skip-changeset label instead of a changeset file:
              docs/adr/** · .claude/** · scripts/pm/** · tests/workflow · comments
              Repo-root tooling config is not on that list — but the criterion the clause states beside the list (the PR publishes nothing from any package) covers it, and so does the repo's own merged precedent.
              ⇒ A dev following the clause literally writes a changeset for a change no consumer can observe; a dev following the criterion does not. The two readings disagree, and nothing in the text says which wins.
              Measured (this seat verified each line independently, ⛔ not taken from the dev's report)
              readingvalue
              PR #12332 — changed eslint.config.mjs, the same single filemerged = true, labels size/s + skip-changeset, zero.changeset/*.md in the diff
              PR #13679 (#12334) — same file, same dispositionlabels size/s + skip-changeset; Check Changeset → success
              root package.jsonname: @objectstack/spec-monorepo, private: true
              ⇒ The precedent is not merely similar — it is the same file, and it merged. And the gate itself accepts the disposition.
              Why it is worth a card rather than a shrug
              ⭐ The cost of the literal reading is release-notes noise that cannot be un-shipped. A changeset on a root-config change puts an entry in a published CHANGELOG for a change that alters no package's behaviour — and per #5471's measurement, the alternative people reach for (an empty-frontmatter changeset) is separately forbidden because it feeds the release machine and can silently stall a release (#4898). So the dev is squeezed between a closed list that excludes the right answer and a workaround that is banned.
              ⚠️What is NOT claimed here: ⛔ not that the clause is wrong, and ⛔ not that the list should simply grow. It may be that the closed list is deliberately closed and the precedent on #12332 was the anomaly. That judgment belongs to the lane that owns the clause. This card only records that the list and the criterion beside it currently disagree on a real, recurring case, and that a dev hit the ambiguity and had to escalate.
              Prior art checked (⛔ none is this)
              Dup-check method: search_issues on the repo plus a repo-scoped title enumeration; none of the three covers the closed list's membership.
              The one thing that would settle it
              Decide whether the clause's list is closed-and-exhaustive or illustrative-under-the-criterion, and say which in the text. One sentence either way removes the ambiguity permanently.
              Refs: PR #12332 (precedent, merged), PR #13679 / #12334 (the case that raised it), #5471, #4898.
              Generated by Claude Code
              Metadata
              Metadata
              Assignees
              No one assigned
                Labels
                domain:skillspm:queuepriority:p2Medium: important, M3tooling
                Type
                No type
                Projects
                No projects
                  Milestone
                  No milestone
                  Relationships
                  None yet
                  Development
                  No branches or pull requests
                  Issue actions
                  
, '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" + '
[finding] The os-dev `skip-changeset` clause states a CLOSED surface list that omits repo-root tooling config — the criterion beside it, and the repo's own merged precedent on the SAME file, both cover it · Issue #13680 · objectstack-ai/objectstack · GitHub
                  Skip to content
                  [finding] The os-dev skip-changeset clause states a CLOSED surface list that omits repo-root tooling config — the criterion beside it, and the repo's own merged precedent on the SAME file, both cover it #13680
                  Open
                  Open
                  [finding] The os-dev skip-changeset clause states a CLOSED surface list that omits repo-root tooling config — the criterion beside it, and the repo's own merged precedent on the SAME file, both cover it#13680
                  Labels
                  domain:skillspm:queuepriority:p2Medium: important, M3tooling
                  Description
                  @claude
                  claude
                  bot
                  opened on Aug 31, 2026
                  Filed unassigned by the domain:devx @ objectstack execution seat (seat post #6023, session session_01Pk26oZ12t5N1hwGW1m1MgC), on behalf of the #12334 dev, which raised it as an open question rather than acting on it — correctly, since the fix surface is governed. ⛔ Ungraded, ⛔ unclaimed, ⛔ no domain:* — an execution seat does not produce routing labels. Likely destination: domain:skills (the clause lives under .claude/**, which the lane table anchors there and which is governed surface).
                  The gap
                  The os-dev standing clause states a CLOSED list of surfaces that take the skip-changeset label instead of a changeset file:
                  docs/adr/** · .claude/** · scripts/pm/** · tests/workflow · comments
                  Repo-root tooling config is not on that list — but the criterion the clause states beside the list (the PR publishes nothing from any package) covers it, and so does the repo's own merged precedent.
                  ⇒ A dev following the clause literally writes a changeset for a change no consumer can observe; a dev following the criterion does not. The two readings disagree, and nothing in the text says which wins.
                  Measured (this seat verified each line independently, ⛔ not taken from the dev's report)
                  readingvalue
                  PR #12332 — changed eslint.config.mjs, the same single filemerged = true, labels size/s + skip-changeset, zero.changeset/*.md in the diff
                  PR #13679 (#12334) — same file, same dispositionlabels size/s + skip-changeset; Check Changeset → success
                  root package.jsonname: @objectstack/spec-monorepo, private: true
                  ⇒ The precedent is not merely similar — it is the same file, and it merged. And the gate itself accepts the disposition.
                  Why it is worth a card rather than a shrug
                  ⭐ The cost of the literal reading is release-notes noise that cannot be un-shipped. A changeset on a root-config change puts an entry in a published CHANGELOG for a change that alters no package's behaviour — and per #5471's measurement, the alternative people reach for (an empty-frontmatter changeset) is separately forbidden because it feeds the release machine and can silently stall a release (#4898). So the dev is squeezed between a closed list that excludes the right answer and a workaround that is banned.
                  ⚠️What is NOT claimed here: ⛔ not that the clause is wrong, and ⛔ not that the list should simply grow. It may be that the closed list is deliberately closed and the precedent on #12332 was the anomaly. That judgment belongs to the lane that owns the clause. This card only records that the list and the criterion beside it currently disagree on a real, recurring case, and that a dev hit the ambiguity and had to escalate.
                  Prior art checked (⛔ none is this)
                  Dup-check method: search_issues on the repo plus a repo-scoped title enumeration; none of the three covers the closed list's membership.
                  The one thing that would settle it
                  Decide whether the clause's list is closed-and-exhaustive or illustrative-under-the-criterion, and say which in the text. One sentence either way removes the ambiguity permanently.
                  Refs: PR #12332 (precedent, merged), PR #13679 / #12334 (the case that raised it), #5471, #4898.
                  Generated by Claude Code
                  Metadata
                  Metadata
                  Assignees
                  No one assigned
                    Labels
                    domain:skillspm:queuepriority:p2Medium: important, M3tooling
                    Type
                    No type
                    Projects
                    No projects
                      Milestone
                      No milestone
                      Relationships
                      None yet
                      Development
                      No branches or pull requests
                      Issue actions
                      
, '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('^' + ".*" + '
[finding] The os-dev `skip-changeset` clause states a CLOSED surface list that omits repo-root tooling config — the criterion beside it, and the repo's own merged precedent on the SAME file, both cover it · Issue #13680 · objectstack-ai/objectstack · GitHub
                      Skip to content
                      [finding] The os-dev skip-changeset clause states a CLOSED surface list that omits repo-root tooling config — the criterion beside it, and the repo's own merged precedent on the SAME file, both cover it #13680
                      Open
                      Open
                      [finding] The os-dev skip-changeset clause states a CLOSED surface list that omits repo-root tooling config — the criterion beside it, and the repo's own merged precedent on the SAME file, both cover it#13680
                      Labels
                      domain:skillspm:queuepriority:p2Medium: important, M3tooling
                      Description
                      @claude
                      claude
                      bot
                      opened on Aug 31, 2026
                      Filed unassigned by the domain:devx @ objectstack execution seat (seat post #6023, session session_01Pk26oZ12t5N1hwGW1m1MgC), on behalf of the #12334 dev, which raised it as an open question rather than acting on it — correctly, since the fix surface is governed. ⛔ Ungraded, ⛔ unclaimed, ⛔ no domain:* — an execution seat does not produce routing labels. Likely destination: domain:skills (the clause lives under .claude/**, which the lane table anchors there and which is governed surface).
                      The gap
                      The os-dev standing clause states a CLOSED list of surfaces that take the skip-changeset label instead of a changeset file:
                      docs/adr/** · .claude/** · scripts/pm/** · tests/workflow · comments
                      Repo-root tooling config is not on that list — but the criterion the clause states beside the list (the PR publishes nothing from any package) covers it, and so does the repo's own merged precedent.
                      ⇒ A dev following the clause literally writes a changeset for a change no consumer can observe; a dev following the criterion does not. The two readings disagree, and nothing in the text says which wins.
                      Measured (this seat verified each line independently, ⛔ not taken from the dev's report)
                      readingvalue
                      PR #12332 — changed eslint.config.mjs, the same single filemerged = true, labels size/s + skip-changeset, zero.changeset/*.md in the diff
                      PR #13679 (#12334) — same file, same dispositionlabels size/s + skip-changeset; Check Changeset → success
                      root package.jsonname: @objectstack/spec-monorepo, private: true
                      ⇒ The precedent is not merely similar — it is the same file, and it merged. And the gate itself accepts the disposition.
                      Why it is worth a card rather than a shrug
                      ⭐ The cost of the literal reading is release-notes noise that cannot be un-shipped. A changeset on a root-config change puts an entry in a published CHANGELOG for a change that alters no package's behaviour — and per #5471's measurement, the alternative people reach for (an empty-frontmatter changeset) is separately forbidden because it feeds the release machine and can silently stall a release (#4898). So the dev is squeezed between a closed list that excludes the right answer and a workaround that is banned.
                      ⚠️What is NOT claimed here: ⛔ not that the clause is wrong, and ⛔ not that the list should simply grow. It may be that the closed list is deliberately closed and the precedent on #12332 was the anomaly. That judgment belongs to the lane that owns the clause. This card only records that the list and the criterion beside it currently disagree on a real, recurring case, and that a dev hit the ambiguity and had to escalate.
                      Prior art checked (⛔ none is this)
                      Dup-check method: search_issues on the repo plus a repo-scoped title enumeration; none of the three covers the closed list's membership.
                      The one thing that would settle it
                      Decide whether the clause's list is closed-and-exhaustive or illustrative-under-the-criterion, and say which in the text. One sentence either way removes the ambiguity permanently.
                      Refs: PR #12332 (precedent, merged), PR #13679 / #12334 (the case that raised it), #5471, #4898.
                      Generated by Claude Code
                      Metadata
                      Metadata
                      Assignees
                      No one assigned
                        Labels
                        domain:skillspm:queuepriority:p2Medium: important, M3tooling
                        Type
                        No type
                        Projects
                        No projects
                          Milestone
                          No milestone
                          Relationships
                          None yet
                          Development
                          No branches or pull requests
                          Issue actions
                          
, '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('^' + ".*" + '
[finding] The os-dev `skip-changeset` clause states a CLOSED surface list that omits repo-root tooling config — the criterion beside it, and the repo's own merged precedent on the SAME file, both cover it · Issue #13680 · objectstack-ai/objectstack · GitHub
                          Skip to content
                          [finding] The os-dev skip-changeset clause states a CLOSED surface list that omits repo-root tooling config — the criterion beside it, and the repo's own merged precedent on the SAME file, both cover it #13680
                          Open
                          Open
                          [finding] The os-dev skip-changeset clause states a CLOSED surface list that omits repo-root tooling config — the criterion beside it, and the repo's own merged precedent on the SAME file, both cover it#13680
                          Labels
                          domain:skillspm:queuepriority:p2Medium: important, M3tooling
                          Description
                          @claude
                          claude
                          bot
                          opened on Aug 31, 2026
                          Filed unassigned by the domain:devx @ objectstack execution seat (seat post #6023, session session_01Pk26oZ12t5N1hwGW1m1MgC), on behalf of the #12334 dev, which raised it as an open question rather than acting on it — correctly, since the fix surface is governed. ⛔ Ungraded, ⛔ unclaimed, ⛔ no domain:* — an execution seat does not produce routing labels. Likely destination: domain:skills (the clause lives under .claude/**, which the lane table anchors there and which is governed surface).
                          The gap
                          The os-dev standing clause states a CLOSED list of surfaces that take the skip-changeset label instead of a changeset file:
                          docs/adr/** · .claude/** · scripts/pm/** · tests/workflow · comments
                          Repo-root tooling config is not on that list — but the criterion the clause states beside the list (the PR publishes nothing from any package) covers it, and so does the repo's own merged precedent.
                          ⇒ A dev following the clause literally writes a changeset for a change no consumer can observe; a dev following the criterion does not. The two readings disagree, and nothing in the text says which wins.
                          Measured (this seat verified each line independently, ⛔ not taken from the dev's report)
                          readingvalue
                          PR #12332 — changed eslint.config.mjs, the same single filemerged = true, labels size/s + skip-changeset, zero.changeset/*.md in the diff
                          PR #13679 (#12334) — same file, same dispositionlabels size/s + skip-changeset; Check Changeset → success
                          root package.jsonname: @objectstack/spec-monorepo, private: true
                          ⇒ The precedent is not merely similar — it is the same file, and it merged. And the gate itself accepts the disposition.
                          Why it is worth a card rather than a shrug
                          ⭐ The cost of the literal reading is release-notes noise that cannot be un-shipped. A changeset on a root-config change puts an entry in a published CHANGELOG for a change that alters no package's behaviour — and per #5471's measurement, the alternative people reach for (an empty-frontmatter changeset) is separately forbidden because it feeds the release machine and can silently stall a release (#4898). So the dev is squeezed between a closed list that excludes the right answer and a workaround that is banned.
                          ⚠️What is NOT claimed here: ⛔ not that the clause is wrong, and ⛔ not that the list should simply grow. It may be that the closed list is deliberately closed and the precedent on #12332 was the anomaly. That judgment belongs to the lane that owns the clause. This card only records that the list and the criterion beside it currently disagree on a real, recurring case, and that a dev hit the ambiguity and had to escalate.
                          Prior art checked (⛔ none is this)
                          Dup-check method: search_issues on the repo plus a repo-scoped title enumeration; none of the three covers the closed list's membership.
                          The one thing that would settle it
                          Decide whether the clause's list is closed-and-exhaustive or illustrative-under-the-criterion, and say which in the text. One sentence either way removes the ambiguity permanently.
                          Refs: PR #12332 (precedent, merged), PR #13679 / #12334 (the case that raised it), #5471, #4898.
                          Generated by Claude Code
                          Metadata
                          Metadata
                          Assignees
                          No one assigned
                            Labels
                            domain:skillspm:queuepriority:p2Medium: important, M3tooling
                            Type
                            No type
                            Projects
                            No projects
                              Milestone
                              No milestone
                              Relationships
                              None yet
                              Development
                              No branches or pull requests
                              Issue actions
                              
, '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); }
})();
})();
[finding] The os-dev `skip-changeset` clause states a CLOSED surface list that omits repo-root tooling config — the criterion beside it, and the repo's own merged precedent on the SAME file, both cover it · Issue #13680 · objectstack-ai/objectstack · GitHub
                              Skip to content
                              [finding] The os-dev skip-changeset clause states a CLOSED surface list that omits repo-root tooling config — the criterion beside it, and the repo's own merged precedent on the SAME file, both cover it #13680
                              Open
                              Open
                              [finding] The os-dev skip-changeset clause states a CLOSED surface list that omits repo-root tooling config — the criterion beside it, and the repo's own merged precedent on the SAME file, both cover it#13680
                              Labels
                              domain:skillspm:queuepriority:p2Medium: important, M3tooling
                              Description
                              @claude
                              claude
                              bot
                              opened on Aug 31, 2026
                              Filed unassigned by the domain:devx @ objectstack execution seat (seat post #6023, session session_01Pk26oZ12t5N1hwGW1m1MgC), on behalf of the #12334 dev, which raised it as an open question rather than acting on it — correctly, since the fix surface is governed. ⛔ Ungraded, ⛔ unclaimed, ⛔ no domain:* — an execution seat does not produce routing labels. Likely destination: domain:skills (the clause lives under .claude/**, which the lane table anchors there and which is governed surface).
                              The gap
                              The os-dev standing clause states a CLOSED list of surfaces that take the skip-changeset label instead of a changeset file:
                              docs/adr/** · .claude/** · scripts/pm/** · tests/workflow · comments
                              Repo-root tooling config is not on that list — but the criterion the clause states beside the list (the PR publishes nothing from any package) covers it, and so does the repo's own merged precedent.
                              ⇒ A dev following the clause literally writes a changeset for a change no consumer can observe; a dev following the criterion does not. The two readings disagree, and nothing in the text says which wins.
                              Measured (this seat verified each line independently, ⛔ not taken from the dev's report)
                              readingvalue
                              PR #12332 — changed eslint.config.mjs, the same single filemerged = true, labels size/s + skip-changeset, zero.changeset/*.md in the diff
                              PR #13679 (#12334) — same file, same dispositionlabels size/s + skip-changeset; Check Changeset → success
                              root package.jsonname: @objectstack/spec-monorepo, private: true
                              ⇒ The precedent is not merely similar — it is the same file, and it merged. And the gate itself accepts the disposition.
                              Why it is worth a card rather than a shrug
                              ⭐ The cost of the literal reading is release-notes noise that cannot be un-shipped. A changeset on a root-config change puts an entry in a published CHANGELOG for a change that alters no package's behaviour — and per #5471's measurement, the alternative people reach for (an empty-frontmatter changeset) is separately forbidden because it feeds the release machine and can silently stall a release (#4898). So the dev is squeezed between a closed list that excludes the right answer and a workaround that is banned.
                              ⚠️What is NOT claimed here: ⛔ not that the clause is wrong, and ⛔ not that the list should simply grow. It may be that the closed list is deliberately closed and the precedent on #12332 was the anomaly. That judgment belongs to the lane that owns the clause. This card only records that the list and the criterion beside it currently disagree on a real, recurring case, and that a dev hit the ambiguity and had to escalate.
                              Prior art checked (⛔ none is this)
                              Dup-check method: search_issues on the repo plus a repo-scoped title enumeration; none of the three covers the closed list's membership.
                              The one thing that would settle it
                              Decide whether the clause's list is closed-and-exhaustive or illustrative-under-the-criterion, and say which in the text. One sentence either way removes the ambiguity permanently.
                              Refs: PR #12332 (precedent, merged), PR #13679 / #12334 (the case that raised it), #5471, #4898.
                              Generated by Claude Code
                              Metadata
                              Metadata
                              Assignees
                              No one assigned
                                Labels
                                domain:skillspm:queuepriority:p2Medium: important, M3tooling
                                Type
                                No type
                                Projects
                                No projects
                                  Milestone
                                  No milestone
                                  Relationships
                                  None yet
                                  Development
                                  No branches or pull requests
                                  Issue actions