Skip to content

os i18n check --help under-counts what it reports by 9 of 14 key kinds — the CLI-side twin of a skill falsehood corrected in #13833 #13837

Open
Bug
Open
os i18n check --help under-counts what it reports by 9 of 14 key kinds — the CLI-side twin of a skill falsehood corrected in #13833#13837
Bug
Labels
documentationImprovements or additions to documentationdomain:clipm:queuepriority:p2Medium: important, M3

Description

@huangyiirene
huangyiirene
opened on Aug 31, 2026

Filed out-of-scope by the flight-⑧ sweep of skills/objectstack-i18n/** (#13815 / #13658), which corrected the same false sentence in the published skill. This is the upstream twin: fixing only the skill leaves the CLI's own --help teaching the same thing, and --help is what a user reads at the moment they run the command.

The claim

packages/cli/src/commands/i18n/check.ts:

staticoverridedescription='Detect missing translation keys (object/field/option/view/action labels) across all configured locales';

What it actually reports

CoverageIssue.source in packages/cli/src/utils/i18n-coverage.ts is a 14-member union:

object · field · option · section · view · action · globalAction · app ·
navigation · dashboard · widget · page · flow · metadataForm

and computeI18nCoverage passes key.source straight through from collectExpectedEntries, so every one of those reaches the report. Measured by driving the real walker and detector over a small fixture (one object, one app, one dashboard, one page with a filter-preset tab, one screen flow, one global action):

=== os i18n check reported source kinds ===
action, app, dashboard, field, globalAction, metadataForm, navigation,
object, option, page, view, widget (12 kinds, one fixture)
totals: expectedKeys 783, issues 783

The parenthetical names 5 of the 14. The nine it omits are not edge cases — metadataForm alone was 769 of the 783 issues on that fixture, and app / navigation / dashboard / widget / page / flow / globalAction / section are all surfaces a real app has.

Why it matters beyond tidiness

The under-count reads as a scoping statement, and it is the reason a reader reaches for a second tool: someone who wants app navigation or dashboard widgets checked is told by --help that this command does objects and fields, so they conclude the gate does not cover them and either skip the check or go looking for one that does. The capability is shipped and hidden by its own description — the "deader-than-real" direction the sweep programme (#13658, comment 5475032239 item 2) measured as the majority direction.

Suggested fix

Restate the description in terms of the surface set rather than a five-item sample, e.g. "Detect missing translation keys across every translatable surface (objects and their fields, options, views, sections, tabs, actions and params; global actions, apps, navigation, dashboards, widgets, pages, flow screens, metadata forms) for all configured locales" — or, if that is too long for a one-line oclif description, drop the parenthetical entirely rather than keep a sample that reads as a boundary.

Worth considering in the same pass: deriving the phrase from the CoverageIssue.source union so the two cannot drift again. That is the mechanism half; the wording fix stands on its own without it.

os i18n extract's description was checked in the same pass and is accurate.

Generated by Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationdomain:clipm:queuepriority:p2Medium: important, M3

    Type

    Bug

    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" + '
`os i18n check --help` under-counts what it reports by 9 of 14 key kinds — the CLI-side twin of a skill falsehood corrected in #13833 · Issue #13837 · objectstack-ai/objectstack · GitHub
      Skip to content
      os i18n check --help under-counts what it reports by 9 of 14 key kinds — the CLI-side twin of a skill falsehood corrected in #13833 #13837
      Open
      Bug
      Open
      os i18n check --help under-counts what it reports by 9 of 14 key kinds — the CLI-side twin of a skill falsehood corrected in #13833#13837
      Bug
      Labels
      documentationImprovements or additions to documentationdomain:clipm:queuepriority:p2Medium: important, M3
      Description
      @huangyiirene
      huangyiirene
      opened on Aug 31, 2026
      Filed out-of-scope by the flight-⑧ sweep of skills/objectstack-i18n/** (#13815 / #13658), which corrected the same false sentence in the published skill. This is the upstream twin: fixing only the skill leaves the CLI's own --help teaching the same thing, and --help is what a user reads at the moment they run the command.
      The claim
      packages/cli/src/commands/i18n/check.ts:
      staticoverridedescription='Detect missing translation keys (object/field/option/view/action labels) across all configured locales';
      What it actually reports
      CoverageIssue.source in packages/cli/src/utils/i18n-coverage.ts is a 14-member union:
      object · field · option · section · view · action · globalAction · app ·
navigation · dashboard · widget · page · flow · metadataForm

      and computeI18nCoverage passes key.source straight through from collectExpectedEntries, so every one of those reaches the report. Measured by driving the real walker and detector over a small fixture (one object, one app, one dashboard, one page with a filter-preset tab, one screen flow, one global action):
      === os i18n check reported source kinds ===
action, app, dashboard, field, globalAction, metadataForm, navigation,
object, option, page, view, widget (12 kinds, one fixture)
totals: expectedKeys 783, issues 783

      The parenthetical names 5 of the 14. The nine it omits are not edge cases — metadataForm alone was 769 of the 783 issues on that fixture, and app / navigation / dashboard / widget / page / flow / globalAction / section are all surfaces a real app has.
      Why it matters beyond tidiness
      The under-count reads as a scoping statement, and it is the reason a reader reaches for a second tool: someone who wants app navigation or dashboard widgets checked is told by --help that this command does objects and fields, so they conclude the gate does not cover them and either skip the check or go looking for one that does. The capability is shipped and hidden by its own description — the "deader-than-real" direction the sweep programme (#13658, comment 5475032239 item 2) measured as the majority direction.
      Suggested fix
      Restate the description in terms of the surface set rather than a five-item sample, e.g. "Detect missing translation keys across every translatable surface (objects and their fields, options, views, sections, tabs, actions and params; global actions, apps, navigation, dashboards, widgets, pages, flow screens, metadata forms) for all configured locales" — or, if that is too long for a one-line oclif description, drop the parenthetical entirely rather than keep a sample that reads as a boundary.
      Worth considering in the same pass: deriving the phrase from the CoverageIssue.source union so the two cannot drift again. That is the mechanism half; the wording fix stands on its own without it.
      os i18n extract's description was checked in the same pass and is accurate.
      Generated by Claude Code
      Metadata
      Metadata
      Assignees
      No one assigned
        Labels
        documentationImprovements or additions to documentationdomain:clipm:queuepriority:p2Medium: important, M3
        Type
        Bug
        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('^' + ".*" + '
`os i18n check --help` under-counts what it reports by 9 of 14 key kinds — the CLI-side twin of a skill falsehood corrected in #13833 · Issue #13837 · objectstack-ai/objectstack · GitHub
          Skip to content
          os i18n check --help under-counts what it reports by 9 of 14 key kinds — the CLI-side twin of a skill falsehood corrected in #13833 #13837
          Open
          Bug
          Open
          os i18n check --help under-counts what it reports by 9 of 14 key kinds — the CLI-side twin of a skill falsehood corrected in #13833#13837
          Bug
          Labels
          documentationImprovements or additions to documentationdomain:clipm:queuepriority:p2Medium: important, M3
          Description
          @huangyiirene
          huangyiirene
          opened on Aug 31, 2026
          Filed out-of-scope by the flight-⑧ sweep of skills/objectstack-i18n/** (#13815 / #13658), which corrected the same false sentence in the published skill. This is the upstream twin: fixing only the skill leaves the CLI's own --help teaching the same thing, and --help is what a user reads at the moment they run the command.
          The claim
          packages/cli/src/commands/i18n/check.ts:
          staticoverridedescription='Detect missing translation keys (object/field/option/view/action labels) across all configured locales';
          What it actually reports
          CoverageIssue.source in packages/cli/src/utils/i18n-coverage.ts is a 14-member union:
          object · field · option · section · view · action · globalAction · app ·
navigation · dashboard · widget · page · flow · metadataForm

          and computeI18nCoverage passes key.source straight through from collectExpectedEntries, so every one of those reaches the report. Measured by driving the real walker and detector over a small fixture (one object, one app, one dashboard, one page with a filter-preset tab, one screen flow, one global action):
          === os i18n check reported source kinds ===
action, app, dashboard, field, globalAction, metadataForm, navigation,
object, option, page, view, widget (12 kinds, one fixture)
totals: expectedKeys 783, issues 783

          The parenthetical names 5 of the 14. The nine it omits are not edge cases — metadataForm alone was 769 of the 783 issues on that fixture, and app / navigation / dashboard / widget / page / flow / globalAction / section are all surfaces a real app has.
          Why it matters beyond tidiness
          The under-count reads as a scoping statement, and it is the reason a reader reaches for a second tool: someone who wants app navigation or dashboard widgets checked is told by --help that this command does objects and fields, so they conclude the gate does not cover them and either skip the check or go looking for one that does. The capability is shipped and hidden by its own description — the "deader-than-real" direction the sweep programme (#13658, comment 5475032239 item 2) measured as the majority direction.
          Suggested fix
          Restate the description in terms of the surface set rather than a five-item sample, e.g. "Detect missing translation keys across every translatable surface (objects and their fields, options, views, sections, tabs, actions and params; global actions, apps, navigation, dashboards, widgets, pages, flow screens, metadata forms) for all configured locales" — or, if that is too long for a one-line oclif description, drop the parenthetical entirely rather than keep a sample that reads as a boundary.
          Worth considering in the same pass: deriving the phrase from the CoverageIssue.source union so the two cannot drift again. That is the mechanism half; the wording fix stands on its own without it.
          os i18n extract's description was checked in the same pass and is accurate.
          Generated by Claude Code
          Metadata
          Metadata
          Assignees
          No one assigned
            Labels
            documentationImprovements or additions to documentationdomain:clipm:queuepriority:p2Medium: important, M3
            Type
            Bug
            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('^' + ".*" + '
`os i18n check --help` under-counts what it reports by 9 of 14 key kinds — the CLI-side twin of a skill falsehood corrected in #13833 · Issue #13837 · objectstack-ai/objectstack · GitHub
              Skip to content
              os i18n check --help under-counts what it reports by 9 of 14 key kinds — the CLI-side twin of a skill falsehood corrected in #13833 #13837
              Open
              Bug
              Open
              os i18n check --help under-counts what it reports by 9 of 14 key kinds — the CLI-side twin of a skill falsehood corrected in #13833#13837
              Bug
              Labels
              documentationImprovements or additions to documentationdomain:clipm:queuepriority:p2Medium: important, M3
              Description
              @huangyiirene
              huangyiirene
              opened on Aug 31, 2026
              Filed out-of-scope by the flight-⑧ sweep of skills/objectstack-i18n/** (#13815 / #13658), which corrected the same false sentence in the published skill. This is the upstream twin: fixing only the skill leaves the CLI's own --help teaching the same thing, and --help is what a user reads at the moment they run the command.
              The claim
              packages/cli/src/commands/i18n/check.ts:
              staticoverridedescription='Detect missing translation keys (object/field/option/view/action labels) across all configured locales';
              What it actually reports
              CoverageIssue.source in packages/cli/src/utils/i18n-coverage.ts is a 14-member union:
              object · field · option · section · view · action · globalAction · app ·
navigation · dashboard · widget · page · flow · metadataForm

              and computeI18nCoverage passes key.source straight through from collectExpectedEntries, so every one of those reaches the report. Measured by driving the real walker and detector over a small fixture (one object, one app, one dashboard, one page with a filter-preset tab, one screen flow, one global action):
              === os i18n check reported source kinds ===
action, app, dashboard, field, globalAction, metadataForm, navigation,
object, option, page, view, widget (12 kinds, one fixture)
totals: expectedKeys 783, issues 783

              The parenthetical names 5 of the 14. The nine it omits are not edge cases — metadataForm alone was 769 of the 783 issues on that fixture, and app / navigation / dashboard / widget / page / flow / globalAction / section are all surfaces a real app has.
              Why it matters beyond tidiness
              The under-count reads as a scoping statement, and it is the reason a reader reaches for a second tool: someone who wants app navigation or dashboard widgets checked is told by --help that this command does objects and fields, so they conclude the gate does not cover them and either skip the check or go looking for one that does. The capability is shipped and hidden by its own description — the "deader-than-real" direction the sweep programme (#13658, comment 5475032239 item 2) measured as the majority direction.
              Suggested fix
              Restate the description in terms of the surface set rather than a five-item sample, e.g. "Detect missing translation keys across every translatable surface (objects and their fields, options, views, sections, tabs, actions and params; global actions, apps, navigation, dashboards, widgets, pages, flow screens, metadata forms) for all configured locales" — or, if that is too long for a one-line oclif description, drop the parenthetical entirely rather than keep a sample that reads as a boundary.
              Worth considering in the same pass: deriving the phrase from the CoverageIssue.source union so the two cannot drift again. That is the mechanism half; the wording fix stands on its own without it.
              os i18n extract's description was checked in the same pass and is accurate.
              Generated by Claude Code
              Metadata
              Metadata
              Assignees
              No one assigned
                Labels
                documentationImprovements or additions to documentationdomain:clipm:queuepriority:p2Medium: important, M3
                Type
                Bug
                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" + '
`os i18n check --help` under-counts what it reports by 9 of 14 key kinds — the CLI-side twin of a skill falsehood corrected in #13833 · Issue #13837 · objectstack-ai/objectstack · GitHub
                  Skip to content
                  os i18n check --help under-counts what it reports by 9 of 14 key kinds — the CLI-side twin of a skill falsehood corrected in #13833 #13837
                  Open
                  Bug
                  Open
                  os i18n check --help under-counts what it reports by 9 of 14 key kinds — the CLI-side twin of a skill falsehood corrected in #13833#13837
                  Bug
                  Labels
                  documentationImprovements or additions to documentationdomain:clipm:queuepriority:p2Medium: important, M3
                  Description
                  @huangyiirene
                  huangyiirene
                  opened on Aug 31, 2026
                  Filed out-of-scope by the flight-⑧ sweep of skills/objectstack-i18n/** (#13815 / #13658), which corrected the same false sentence in the published skill. This is the upstream twin: fixing only the skill leaves the CLI's own --help teaching the same thing, and --help is what a user reads at the moment they run the command.
                  The claim
                  packages/cli/src/commands/i18n/check.ts:
                  staticoverridedescription='Detect missing translation keys (object/field/option/view/action labels) across all configured locales';
                  What it actually reports
                  CoverageIssue.source in packages/cli/src/utils/i18n-coverage.ts is a 14-member union:
                  object · field · option · section · view · action · globalAction · app ·
navigation · dashboard · widget · page · flow · metadataForm

                  and computeI18nCoverage passes key.source straight through from collectExpectedEntries, so every one of those reaches the report. Measured by driving the real walker and detector over a small fixture (one object, one app, one dashboard, one page with a filter-preset tab, one screen flow, one global action):
                  === os i18n check reported source kinds ===
action, app, dashboard, field, globalAction, metadataForm, navigation,
object, option, page, view, widget (12 kinds, one fixture)
totals: expectedKeys 783, issues 783

                  The parenthetical names 5 of the 14. The nine it omits are not edge cases — metadataForm alone was 769 of the 783 issues on that fixture, and app / navigation / dashboard / widget / page / flow / globalAction / section are all surfaces a real app has.
                  Why it matters beyond tidiness
                  The under-count reads as a scoping statement, and it is the reason a reader reaches for a second tool: someone who wants app navigation or dashboard widgets checked is told by --help that this command does objects and fields, so they conclude the gate does not cover them and either skip the check or go looking for one that does. The capability is shipped and hidden by its own description — the "deader-than-real" direction the sweep programme (#13658, comment 5475032239 item 2) measured as the majority direction.
                  Suggested fix
                  Restate the description in terms of the surface set rather than a five-item sample, e.g. "Detect missing translation keys across every translatable surface (objects and their fields, options, views, sections, tabs, actions and params; global actions, apps, navigation, dashboards, widgets, pages, flow screens, metadata forms) for all configured locales" — or, if that is too long for a one-line oclif description, drop the parenthetical entirely rather than keep a sample that reads as a boundary.
                  Worth considering in the same pass: deriving the phrase from the CoverageIssue.source union so the two cannot drift again. That is the mechanism half; the wording fix stands on its own without it.
                  os i18n extract's description was checked in the same pass and is accurate.
                  Generated by Claude Code
                  Metadata
                  Metadata
                  Assignees
                  No one assigned
                    Labels
                    documentationImprovements or additions to documentationdomain:clipm:queuepriority:p2Medium: important, M3
                    Type
                    Bug
                    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('^' + ".*" + '
`os i18n check --help` under-counts what it reports by 9 of 14 key kinds — the CLI-side twin of a skill falsehood corrected in #13833 · Issue #13837 · objectstack-ai/objectstack · GitHub
                      Skip to content
                      os i18n check --help under-counts what it reports by 9 of 14 key kinds — the CLI-side twin of a skill falsehood corrected in #13833 #13837
                      Open
                      Bug
                      Open
                      os i18n check --help under-counts what it reports by 9 of 14 key kinds — the CLI-side twin of a skill falsehood corrected in #13833#13837
                      Bug
                      Labels
                      documentationImprovements or additions to documentationdomain:clipm:queuepriority:p2Medium: important, M3
                      Description
                      @huangyiirene
                      huangyiirene
                      opened on Aug 31, 2026
                      Filed out-of-scope by the flight-⑧ sweep of skills/objectstack-i18n/** (#13815 / #13658), which corrected the same false sentence in the published skill. This is the upstream twin: fixing only the skill leaves the CLI's own --help teaching the same thing, and --help is what a user reads at the moment they run the command.
                      The claim
                      packages/cli/src/commands/i18n/check.ts:
                      staticoverridedescription='Detect missing translation keys (object/field/option/view/action labels) across all configured locales';
                      What it actually reports
                      CoverageIssue.source in packages/cli/src/utils/i18n-coverage.ts is a 14-member union:
                      object · field · option · section · view · action · globalAction · app ·
navigation · dashboard · widget · page · flow · metadataForm

                      and computeI18nCoverage passes key.source straight through from collectExpectedEntries, so every one of those reaches the report. Measured by driving the real walker and detector over a small fixture (one object, one app, one dashboard, one page with a filter-preset tab, one screen flow, one global action):
                      === os i18n check reported source kinds ===
action, app, dashboard, field, globalAction, metadataForm, navigation,
object, option, page, view, widget (12 kinds, one fixture)
totals: expectedKeys 783, issues 783

                      The parenthetical names 5 of the 14. The nine it omits are not edge cases — metadataForm alone was 769 of the 783 issues on that fixture, and app / navigation / dashboard / widget / page / flow / globalAction / section are all surfaces a real app has.
                      Why it matters beyond tidiness
                      The under-count reads as a scoping statement, and it is the reason a reader reaches for a second tool: someone who wants app navigation or dashboard widgets checked is told by --help that this command does objects and fields, so they conclude the gate does not cover them and either skip the check or go looking for one that does. The capability is shipped and hidden by its own description — the "deader-than-real" direction the sweep programme (#13658, comment 5475032239 item 2) measured as the majority direction.
                      Suggested fix
                      Restate the description in terms of the surface set rather than a five-item sample, e.g. "Detect missing translation keys across every translatable surface (objects and their fields, options, views, sections, tabs, actions and params; global actions, apps, navigation, dashboards, widgets, pages, flow screens, metadata forms) for all configured locales" — or, if that is too long for a one-line oclif description, drop the parenthetical entirely rather than keep a sample that reads as a boundary.
                      Worth considering in the same pass: deriving the phrase from the CoverageIssue.source union so the two cannot drift again. That is the mechanism half; the wording fix stands on its own without it.
                      os i18n extract's description was checked in the same pass and is accurate.
                      Generated by Claude Code
                      Metadata
                      Metadata
                      Assignees
                      No one assigned
                        Labels
                        documentationImprovements or additions to documentationdomain:clipm:queuepriority:p2Medium: important, M3
                        Type
                        Bug
                        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('^' + ".*" + '
`os i18n check --help` under-counts what it reports by 9 of 14 key kinds — the CLI-side twin of a skill falsehood corrected in #13833 · Issue #13837 · objectstack-ai/objectstack · GitHub
                          Skip to content
                          os i18n check --help under-counts what it reports by 9 of 14 key kinds — the CLI-side twin of a skill falsehood corrected in #13833 #13837
                          Open
                          Bug
                          Open
                          os i18n check --help under-counts what it reports by 9 of 14 key kinds — the CLI-side twin of a skill falsehood corrected in #13833#13837
                          Bug
                          Labels
                          documentationImprovements or additions to documentationdomain:clipm:queuepriority:p2Medium: important, M3
                          Description
                          @huangyiirene
                          huangyiirene
                          opened on Aug 31, 2026
                          Filed out-of-scope by the flight-⑧ sweep of skills/objectstack-i18n/** (#13815 / #13658), which corrected the same false sentence in the published skill. This is the upstream twin: fixing only the skill leaves the CLI's own --help teaching the same thing, and --help is what a user reads at the moment they run the command.
                          The claim
                          packages/cli/src/commands/i18n/check.ts:
                          staticoverridedescription='Detect missing translation keys (object/field/option/view/action labels) across all configured locales';
                          What it actually reports
                          CoverageIssue.source in packages/cli/src/utils/i18n-coverage.ts is a 14-member union:
                          object · field · option · section · view · action · globalAction · app ·
navigation · dashboard · widget · page · flow · metadataForm

                          and computeI18nCoverage passes key.source straight through from collectExpectedEntries, so every one of those reaches the report. Measured by driving the real walker and detector over a small fixture (one object, one app, one dashboard, one page with a filter-preset tab, one screen flow, one global action):
                          === os i18n check reported source kinds ===
action, app, dashboard, field, globalAction, metadataForm, navigation,
object, option, page, view, widget (12 kinds, one fixture)
totals: expectedKeys 783, issues 783

                          The parenthetical names 5 of the 14. The nine it omits are not edge cases — metadataForm alone was 769 of the 783 issues on that fixture, and app / navigation / dashboard / widget / page / flow / globalAction / section are all surfaces a real app has.
                          Why it matters beyond tidiness
                          The under-count reads as a scoping statement, and it is the reason a reader reaches for a second tool: someone who wants app navigation or dashboard widgets checked is told by --help that this command does objects and fields, so they conclude the gate does not cover them and either skip the check or go looking for one that does. The capability is shipped and hidden by its own description — the "deader-than-real" direction the sweep programme (#13658, comment 5475032239 item 2) measured as the majority direction.
                          Suggested fix
                          Restate the description in terms of the surface set rather than a five-item sample, e.g. "Detect missing translation keys across every translatable surface (objects and their fields, options, views, sections, tabs, actions and params; global actions, apps, navigation, dashboards, widgets, pages, flow screens, metadata forms) for all configured locales" — or, if that is too long for a one-line oclif description, drop the parenthetical entirely rather than keep a sample that reads as a boundary.
                          Worth considering in the same pass: deriving the phrase from the CoverageIssue.source union so the two cannot drift again. That is the mechanism half; the wording fix stands on its own without it.
                          os i18n extract's description was checked in the same pass and is accurate.
                          Generated by Claude Code
                          Metadata
                          Metadata
                          Assignees
                          No one assigned
                            Labels
                            documentationImprovements or additions to documentationdomain:clipm:queuepriority:p2Medium: important, M3
                            Type
                            Bug
                            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); }
})();
})();
`os i18n check --help` under-counts what it reports by 9 of 14 key kinds — the CLI-side twin of a skill falsehood corrected in #13833 · Issue #13837 · objectstack-ai/objectstack · GitHub
                              Skip to content
                              os i18n check --help under-counts what it reports by 9 of 14 key kinds — the CLI-side twin of a skill falsehood corrected in #13833 #13837
                              Open
                              Bug
                              Open
                              os i18n check --help under-counts what it reports by 9 of 14 key kinds — the CLI-side twin of a skill falsehood corrected in #13833#13837
                              Bug
                              Labels
                              documentationImprovements or additions to documentationdomain:clipm:queuepriority:p2Medium: important, M3
                              Description
                              @huangyiirene
                              huangyiirene
                              opened on Aug 31, 2026
                              Filed out-of-scope by the flight-⑧ sweep of skills/objectstack-i18n/** (#13815 / #13658), which corrected the same false sentence in the published skill. This is the upstream twin: fixing only the skill leaves the CLI's own --help teaching the same thing, and --help is what a user reads at the moment they run the command.
                              The claim
                              packages/cli/src/commands/i18n/check.ts:
                              staticoverridedescription='Detect missing translation keys (object/field/option/view/action labels) across all configured locales';
                              What it actually reports
                              CoverageIssue.source in packages/cli/src/utils/i18n-coverage.ts is a 14-member union:
                              object · field · option · section · view · action · globalAction · app ·
navigation · dashboard · widget · page · flow · metadataForm

                              and computeI18nCoverage passes key.source straight through from collectExpectedEntries, so every one of those reaches the report. Measured by driving the real walker and detector over a small fixture (one object, one app, one dashboard, one page with a filter-preset tab, one screen flow, one global action):
                              === os i18n check reported source kinds ===
action, app, dashboard, field, globalAction, metadataForm, navigation,
object, option, page, view, widget (12 kinds, one fixture)
totals: expectedKeys 783, issues 783

                              The parenthetical names 5 of the 14. The nine it omits are not edge cases — metadataForm alone was 769 of the 783 issues on that fixture, and app / navigation / dashboard / widget / page / flow / globalAction / section are all surfaces a real app has.
                              Why it matters beyond tidiness
                              The under-count reads as a scoping statement, and it is the reason a reader reaches for a second tool: someone who wants app navigation or dashboard widgets checked is told by --help that this command does objects and fields, so they conclude the gate does not cover them and either skip the check or go looking for one that does. The capability is shipped and hidden by its own description — the "deader-than-real" direction the sweep programme (#13658, comment 5475032239 item 2) measured as the majority direction.
                              Suggested fix
                              Restate the description in terms of the surface set rather than a five-item sample, e.g. "Detect missing translation keys across every translatable surface (objects and their fields, options, views, sections, tabs, actions and params; global actions, apps, navigation, dashboards, widgets, pages, flow screens, metadata forms) for all configured locales" — or, if that is too long for a one-line oclif description, drop the parenthetical entirely rather than keep a sample that reads as a boundary.
                              Worth considering in the same pass: deriving the phrase from the CoverageIssue.source union so the two cannot drift again. That is the mechanism half; the wording fix stands on its own without it.
                              os i18n extract's description was checked in the same pass and is accurate.
                              Generated by Claude Code
                              Metadata
                              Metadata
                              Assignees
                              No one assigned
                                Labels
                                documentationImprovements or additions to documentationdomain:clipm:queuepriority:p2Medium: important, M3
                                Type
                                Bug
                                Projects
                                No projects
                                  Milestone
                                  No milestone
                                  Relationships
                                  None yet
                                  Development
                                  No branches or pull requests
                                  Issue actions