A gate script that quotes example code in a message string reads as a real SDK call site to the envelope-caller census — it masks comments, never string literals #13874

Description

@os-project-manager

What was measured

packages/client/src/envelope-caller-census.test.ts walks every .ts / .tsx / .js / .mjs / .cjs file in the workspace looking for four SDK spellings — analytics.query, analytics.meta, analytics.explain, automation.trigger — and blanks comments only, through the house scanner scripts/js-comment-mask.mjs (maskComments). String literals are left intact, and deliberately so: the file's own header explains that a naive stripper which also blanked literals would open a phantom comment on any block-comment opener inside a string and shrink the census in silence.

The consequence is that example code quoted inside a string literal is counted as a real SDK call site. Gate scripts under scripts/** are full of exactly such strings: refusal messages that show the author what to write instead, fixtures that embed a synthetic changeset body, usage banners.

Measured on PR #13596, running the census's own four patterns through the repo's own maskComments over each file that PR changes:

patternorigin/mainthat PR's branchdelta
analytics.query02+2
analytics.meta000
analytics.explain000
automation.trigger000

Both occurrences sat inside one string literal — a fixture's migration table in scripts/check-adr-0087-registration.mjs. The census went red (expected 21 to be 19) and the merge queue ejected the PR. The two comment mentions that same PR adds were masked correctly and contributed nothing, which is what isolates the mechanism to literals.

Why this is worth a card and not only the one fix

That PR has been fixed on its own terms: its fixture now demonstrates the symbol the fixture itself names, which is what it should have demonstrated anyway. The general shape is untouched, and it is a trap for the next gate author:

  • the failure lands in a different package from the edit (packages/client) and names a ledger the author has never read;
  • it is invisible to every local gate family a path derivation produces for a scripts/** edit — nothing in that family reads the census;
  • it surfaces in the merge queue, i.e. after review, at the most expensive point;
  • the diagnostic is a bare count mismatch, which says nothing about strings, masking, or gate scripts.

Which way it should be resolved is not obvious, and is left to triage. A sketch of the space, with no recommendation attached:

  1. Do nothing — accept it as a known cost, and let each gate author learn it once, in the merge queue.
  2. Make the census's own diagnostic self-explaining: when a counted site falls inside a string-literal span, say so in the failure text.
  3. Teach the census a defensible literal/context distinction — weighed against the measured reason literals are NOT masked today.
  4. Move the burden to gate authors (a convention for how example code is spelled inside author-facing messages), with the standing objection that a convention no instrument enforces is not a mechanism.

⛔ Nothing here proposes weakening, skipping or exempting the census, and nothing here proposes registering fixture prose in its ledger. The ledger's whole purpose is to be true; prose booked as call sites would be false data in it.

Context — surfaced while fixing the merge-queue ejection on #13596 (card #13080). The census is #13079's instrument. Neither is changed by this card, and this card asks for no change to either as a precondition.

Generated by Claude Code

Metadata

Metadata

Assignees

No one assigned

    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" + '
      
      Skip to content

      A gate script that quotes example code in a message string reads as a real SDK call site to the envelope-caller census — it masks comments, never string literals #13874

      Description

      @os-project-manager

      What was measured

      packages/client/src/envelope-caller-census.test.ts walks every .ts / .tsx / .js / .mjs / .cjs file in the workspace looking for four SDK spellings — analytics.query, analytics.meta, analytics.explain, automation.trigger — and blanks comments only, through the house scanner scripts/js-comment-mask.mjs (maskComments). String literals are left intact, and deliberately so: the file's own header explains that a naive stripper which also blanked literals would open a phantom comment on any block-comment opener inside a string and shrink the census in silence.

      The consequence is that example code quoted inside a string literal is counted as a real SDK call site. Gate scripts under scripts/** are full of exactly such strings: refusal messages that show the author what to write instead, fixtures that embed a synthetic changeset body, usage banners.

      Measured on PR #13596, running the census's own four patterns through the repo's own maskComments over each file that PR changes:

      patternorigin/mainthat PR's branchdelta
      analytics.query02+2
      analytics.meta000
      analytics.explain000
      automation.trigger000

      Both occurrences sat inside one string literal — a fixture's migration table in scripts/check-adr-0087-registration.mjs. The census went red (expected 21 to be 19) and the merge queue ejected the PR. The two comment mentions that same PR adds were masked correctly and contributed nothing, which is what isolates the mechanism to literals.

      Why this is worth a card and not only the one fix

      That PR has been fixed on its own terms: its fixture now demonstrates the symbol the fixture itself names, which is what it should have demonstrated anyway. The general shape is untouched, and it is a trap for the next gate author:

      • the failure lands in a different package from the edit (packages/client) and names a ledger the author has never read;
      • it is invisible to every local gate family a path derivation produces for a scripts/** edit — nothing in that family reads the census;
      • it surfaces in the merge queue, i.e. after review, at the most expensive point;
      • the diagnostic is a bare count mismatch, which says nothing about strings, masking, or gate scripts.

      Which way it should be resolved is not obvious, and is left to triage. A sketch of the space, with no recommendation attached:

      1. Do nothing — accept it as a known cost, and let each gate author learn it once, in the merge queue.
      2. Make the census's own diagnostic self-explaining: when a counted site falls inside a string-literal span, say so in the failure text.
      3. Teach the census a defensible literal/context distinction — weighed against the measured reason literals are NOT masked today.
      4. Move the burden to gate authors (a convention for how example code is spelled inside author-facing messages), with the standing objection that a convention no instrument enforces is not a mechanism.

      ⛔ Nothing here proposes weakening, skipping or exempting the census, and nothing here proposes registering fixture prose in its ledger. The ledger's whole purpose is to be true; prose booked as call sites would be false data in it.

      Context — surfaced while fixing the merge-queue ejection on #13596 (card #13080). The census is #13079's instrument. Neither is changed by this card, and this card asks for no change to either as a precondition.

      Generated by Claude Code

      Metadata

      Metadata

      Assignees

      No one assigned

        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('^' + ".*" + '
          Skip to content

          A gate script that quotes example code in a message string reads as a real SDK call site to the envelope-caller census — it masks comments, never string literals #13874

          Description

          @os-project-manager

          What was measured

          packages/client/src/envelope-caller-census.test.ts walks every .ts / .tsx / .js / .mjs / .cjs file in the workspace looking for four SDK spellings — analytics.query, analytics.meta, analytics.explain, automation.trigger — and blanks comments only, through the house scanner scripts/js-comment-mask.mjs (maskComments). String literals are left intact, and deliberately so: the file's own header explains that a naive stripper which also blanked literals would open a phantom comment on any block-comment opener inside a string and shrink the census in silence.

          The consequence is that example code quoted inside a string literal is counted as a real SDK call site. Gate scripts under scripts/** are full of exactly such strings: refusal messages that show the author what to write instead, fixtures that embed a synthetic changeset body, usage banners.

          Measured on PR #13596, running the census's own four patterns through the repo's own maskComments over each file that PR changes:

          patternorigin/mainthat PR's branchdelta
          analytics.query02+2
          analytics.meta000
          analytics.explain000
          automation.trigger000

          Both occurrences sat inside one string literal — a fixture's migration table in scripts/check-adr-0087-registration.mjs. The census went red (expected 21 to be 19) and the merge queue ejected the PR. The two comment mentions that same PR adds were masked correctly and contributed nothing, which is what isolates the mechanism to literals.

          Why this is worth a card and not only the one fix

          That PR has been fixed on its own terms: its fixture now demonstrates the symbol the fixture itself names, which is what it should have demonstrated anyway. The general shape is untouched, and it is a trap for the next gate author:

          • the failure lands in a different package from the edit (packages/client) and names a ledger the author has never read;
          • it is invisible to every local gate family a path derivation produces for a scripts/** edit — nothing in that family reads the census;
          • it surfaces in the merge queue, i.e. after review, at the most expensive point;
          • the diagnostic is a bare count mismatch, which says nothing about strings, masking, or gate scripts.

          Which way it should be resolved is not obvious, and is left to triage. A sketch of the space, with no recommendation attached:

          1. Do nothing — accept it as a known cost, and let each gate author learn it once, in the merge queue.
          2. Make the census's own diagnostic self-explaining: when a counted site falls inside a string-literal span, say so in the failure text.
          3. Teach the census a defensible literal/context distinction — weighed against the measured reason literals are NOT masked today.
          4. Move the burden to gate authors (a convention for how example code is spelled inside author-facing messages), with the standing objection that a convention no instrument enforces is not a mechanism.

          ⛔ Nothing here proposes weakening, skipping or exempting the census, and nothing here proposes registering fixture prose in its ledger. The ledger's whole purpose is to be true; prose booked as call sites would be false data in it.

          Context — surfaced while fixing the merge-queue ejection on #13596 (card #13080). The census is #13079's instrument. Neither is changed by this card, and this card asks for no change to either as a precondition.

          Generated by Claude Code

          Metadata

          Metadata

          Assignees

          No one assigned

            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('^' + ".*" + '
              Skip to content

              A gate script that quotes example code in a message string reads as a real SDK call site to the envelope-caller census — it masks comments, never string literals #13874

              Description

              @os-project-manager

              What was measured

              packages/client/src/envelope-caller-census.test.ts walks every .ts / .tsx / .js / .mjs / .cjs file in the workspace looking for four SDK spellings — analytics.query, analytics.meta, analytics.explain, automation.trigger — and blanks comments only, through the house scanner scripts/js-comment-mask.mjs (maskComments). String literals are left intact, and deliberately so: the file's own header explains that a naive stripper which also blanked literals would open a phantom comment on any block-comment opener inside a string and shrink the census in silence.

              The consequence is that example code quoted inside a string literal is counted as a real SDK call site. Gate scripts under scripts/** are full of exactly such strings: refusal messages that show the author what to write instead, fixtures that embed a synthetic changeset body, usage banners.

              Measured on PR #13596, running the census's own four patterns through the repo's own maskComments over each file that PR changes:

              patternorigin/mainthat PR's branchdelta
              analytics.query02+2
              analytics.meta000
              analytics.explain000
              automation.trigger000

              Both occurrences sat inside one string literal — a fixture's migration table in scripts/check-adr-0087-registration.mjs. The census went red (expected 21 to be 19) and the merge queue ejected the PR. The two comment mentions that same PR adds were masked correctly and contributed nothing, which is what isolates the mechanism to literals.

              Why this is worth a card and not only the one fix

              That PR has been fixed on its own terms: its fixture now demonstrates the symbol the fixture itself names, which is what it should have demonstrated anyway. The general shape is untouched, and it is a trap for the next gate author:

              • the failure lands in a different package from the edit (packages/client) and names a ledger the author has never read;
              • it is invisible to every local gate family a path derivation produces for a scripts/** edit — nothing in that family reads the census;
              • it surfaces in the merge queue, i.e. after review, at the most expensive point;
              • the diagnostic is a bare count mismatch, which says nothing about strings, masking, or gate scripts.

              Which way it should be resolved is not obvious, and is left to triage. A sketch of the space, with no recommendation attached:

              1. Do nothing — accept it as a known cost, and let each gate author learn it once, in the merge queue.
              2. Make the census's own diagnostic self-explaining: when a counted site falls inside a string-literal span, say so in the failure text.
              3. Teach the census a defensible literal/context distinction — weighed against the measured reason literals are NOT masked today.
              4. Move the burden to gate authors (a convention for how example code is spelled inside author-facing messages), with the standing objection that a convention no instrument enforces is not a mechanism.

              ⛔ Nothing here proposes weakening, skipping or exempting the census, and nothing here proposes registering fixture prose in its ledger. The ledger's whole purpose is to be true; prose booked as call sites would be false data in it.

              Context — surfaced while fixing the merge-queue ejection on #13596 (card #13080). The census is #13079's instrument. Neither is changed by this card, and this card asks for no change to either as a precondition.

              Generated by Claude Code

              Metadata

              Metadata

              Assignees

              No one assigned

                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" + '
                  Skip to content

                  A gate script that quotes example code in a message string reads as a real SDK call site to the envelope-caller census — it masks comments, never string literals #13874

                  Description

                  @os-project-manager

                  What was measured

                  packages/client/src/envelope-caller-census.test.ts walks every .ts / .tsx / .js / .mjs / .cjs file in the workspace looking for four SDK spellings — analytics.query, analytics.meta, analytics.explain, automation.trigger — and blanks comments only, through the house scanner scripts/js-comment-mask.mjs (maskComments). String literals are left intact, and deliberately so: the file's own header explains that a naive stripper which also blanked literals would open a phantom comment on any block-comment opener inside a string and shrink the census in silence.

                  The consequence is that example code quoted inside a string literal is counted as a real SDK call site. Gate scripts under scripts/** are full of exactly such strings: refusal messages that show the author what to write instead, fixtures that embed a synthetic changeset body, usage banners.

                  Measured on PR #13596, running the census's own four patterns through the repo's own maskComments over each file that PR changes:

                  patternorigin/mainthat PR's branchdelta
                  analytics.query02+2
                  analytics.meta000
                  analytics.explain000
                  automation.trigger000

                  Both occurrences sat inside one string literal — a fixture's migration table in scripts/check-adr-0087-registration.mjs. The census went red (expected 21 to be 19) and the merge queue ejected the PR. The two comment mentions that same PR adds were masked correctly and contributed nothing, which is what isolates the mechanism to literals.

                  Why this is worth a card and not only the one fix

                  That PR has been fixed on its own terms: its fixture now demonstrates the symbol the fixture itself names, which is what it should have demonstrated anyway. The general shape is untouched, and it is a trap for the next gate author:

                  • the failure lands in a different package from the edit (packages/client) and names a ledger the author has never read;
                  • it is invisible to every local gate family a path derivation produces for a scripts/** edit — nothing in that family reads the census;
                  • it surfaces in the merge queue, i.e. after review, at the most expensive point;
                  • the diagnostic is a bare count mismatch, which says nothing about strings, masking, or gate scripts.

                  Which way it should be resolved is not obvious, and is left to triage. A sketch of the space, with no recommendation attached:

                  1. Do nothing — accept it as a known cost, and let each gate author learn it once, in the merge queue.
                  2. Make the census's own diagnostic self-explaining: when a counted site falls inside a string-literal span, say so in the failure text.
                  3. Teach the census a defensible literal/context distinction — weighed against the measured reason literals are NOT masked today.
                  4. Move the burden to gate authors (a convention for how example code is spelled inside author-facing messages), with the standing objection that a convention no instrument enforces is not a mechanism.

                  ⛔ Nothing here proposes weakening, skipping or exempting the census, and nothing here proposes registering fixture prose in its ledger. The ledger's whole purpose is to be true; prose booked as call sites would be false data in it.

                  Context — surfaced while fixing the merge-queue ejection on #13596 (card #13080). The census is #13079's instrument. Neither is changed by this card, and this card asks for no change to either as a precondition.

                  Generated by Claude Code

                  Metadata

                  Metadata

                  Assignees

                  No one assigned

                    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('^' + ".*" + '
                      Skip to content

                      A gate script that quotes example code in a message string reads as a real SDK call site to the envelope-caller census — it masks comments, never string literals #13874

                      Description

                      @os-project-manager

                      What was measured

                      packages/client/src/envelope-caller-census.test.ts walks every .ts / .tsx / .js / .mjs / .cjs file in the workspace looking for four SDK spellings — analytics.query, analytics.meta, analytics.explain, automation.trigger — and blanks comments only, through the house scanner scripts/js-comment-mask.mjs (maskComments). String literals are left intact, and deliberately so: the file's own header explains that a naive stripper which also blanked literals would open a phantom comment on any block-comment opener inside a string and shrink the census in silence.

                      The consequence is that example code quoted inside a string literal is counted as a real SDK call site. Gate scripts under scripts/** are full of exactly such strings: refusal messages that show the author what to write instead, fixtures that embed a synthetic changeset body, usage banners.

                      Measured on PR #13596, running the census's own four patterns through the repo's own maskComments over each file that PR changes:

                      patternorigin/mainthat PR's branchdelta
                      analytics.query02+2
                      analytics.meta000
                      analytics.explain000
                      automation.trigger000

                      Both occurrences sat inside one string literal — a fixture's migration table in scripts/check-adr-0087-registration.mjs. The census went red (expected 21 to be 19) and the merge queue ejected the PR. The two comment mentions that same PR adds were masked correctly and contributed nothing, which is what isolates the mechanism to literals.

                      Why this is worth a card and not only the one fix

                      That PR has been fixed on its own terms: its fixture now demonstrates the symbol the fixture itself names, which is what it should have demonstrated anyway. The general shape is untouched, and it is a trap for the next gate author:

                      • the failure lands in a different package from the edit (packages/client) and names a ledger the author has never read;
                      • it is invisible to every local gate family a path derivation produces for a scripts/** edit — nothing in that family reads the census;
                      • it surfaces in the merge queue, i.e. after review, at the most expensive point;
                      • the diagnostic is a bare count mismatch, which says nothing about strings, masking, or gate scripts.

                      Which way it should be resolved is not obvious, and is left to triage. A sketch of the space, with no recommendation attached:

                      1. Do nothing — accept it as a known cost, and let each gate author learn it once, in the merge queue.
                      2. Make the census's own diagnostic self-explaining: when a counted site falls inside a string-literal span, say so in the failure text.
                      3. Teach the census a defensible literal/context distinction — weighed against the measured reason literals are NOT masked today.
                      4. Move the burden to gate authors (a convention for how example code is spelled inside author-facing messages), with the standing objection that a convention no instrument enforces is not a mechanism.

                      ⛔ Nothing here proposes weakening, skipping or exempting the census, and nothing here proposes registering fixture prose in its ledger. The ledger's whole purpose is to be true; prose booked as call sites would be false data in it.

                      Context — surfaced while fixing the merge-queue ejection on #13596 (card #13080). The census is #13079's instrument. Neither is changed by this card, and this card asks for no change to either as a precondition.

                      Generated by Claude Code

                      Metadata

                      Metadata

                      Assignees

                      No one assigned

                        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('^' + ".*" + '
                          Skip to content

                          A gate script that quotes example code in a message string reads as a real SDK call site to the envelope-caller census — it masks comments, never string literals #13874

                          Description

                          @os-project-manager

                          What was measured

                          packages/client/src/envelope-caller-census.test.ts walks every .ts / .tsx / .js / .mjs / .cjs file in the workspace looking for four SDK spellings — analytics.query, analytics.meta, analytics.explain, automation.trigger — and blanks comments only, through the house scanner scripts/js-comment-mask.mjs (maskComments). String literals are left intact, and deliberately so: the file's own header explains that a naive stripper which also blanked literals would open a phantom comment on any block-comment opener inside a string and shrink the census in silence.

                          The consequence is that example code quoted inside a string literal is counted as a real SDK call site. Gate scripts under scripts/** are full of exactly such strings: refusal messages that show the author what to write instead, fixtures that embed a synthetic changeset body, usage banners.

                          Measured on PR #13596, running the census's own four patterns through the repo's own maskComments over each file that PR changes:

                          patternorigin/mainthat PR's branchdelta
                          analytics.query02+2
                          analytics.meta000
                          analytics.explain000
                          automation.trigger000

                          Both occurrences sat inside one string literal — a fixture's migration table in scripts/check-adr-0087-registration.mjs. The census went red (expected 21 to be 19) and the merge queue ejected the PR. The two comment mentions that same PR adds were masked correctly and contributed nothing, which is what isolates the mechanism to literals.

                          Why this is worth a card and not only the one fix

                          That PR has been fixed on its own terms: its fixture now demonstrates the symbol the fixture itself names, which is what it should have demonstrated anyway. The general shape is untouched, and it is a trap for the next gate author:

                          • the failure lands in a different package from the edit (packages/client) and names a ledger the author has never read;
                          • it is invisible to every local gate family a path derivation produces for a scripts/** edit — nothing in that family reads the census;
                          • it surfaces in the merge queue, i.e. after review, at the most expensive point;
                          • the diagnostic is a bare count mismatch, which says nothing about strings, masking, or gate scripts.

                          Which way it should be resolved is not obvious, and is left to triage. A sketch of the space, with no recommendation attached:

                          1. Do nothing — accept it as a known cost, and let each gate author learn it once, in the merge queue.
                          2. Make the census's own diagnostic self-explaining: when a counted site falls inside a string-literal span, say so in the failure text.
                          3. Teach the census a defensible literal/context distinction — weighed against the measured reason literals are NOT masked today.
                          4. Move the burden to gate authors (a convention for how example code is spelled inside author-facing messages), with the standing objection that a convention no instrument enforces is not a mechanism.

                          ⛔ Nothing here proposes weakening, skipping or exempting the census, and nothing here proposes registering fixture prose in its ledger. The ledger's whole purpose is to be true; prose booked as call sites would be false data in it.

                          Context — surfaced while fixing the merge-queue ejection on #13596 (card #13080). The census is #13079's instrument. Neither is changed by this card, and this card asks for no change to either as a precondition.

                          Generated by Claude Code

                          Metadata

                          Metadata

                          Assignees

                          No one assigned

                            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); } })(); })();
                              Skip to content

                              A gate script that quotes example code in a message string reads as a real SDK call site to the envelope-caller census — it masks comments, never string literals #13874

                              Description

                              @os-project-manager

                              What was measured

                              packages/client/src/envelope-caller-census.test.ts walks every .ts / .tsx / .js / .mjs / .cjs file in the workspace looking for four SDK spellings — analytics.query, analytics.meta, analytics.explain, automation.trigger — and blanks comments only, through the house scanner scripts/js-comment-mask.mjs (maskComments). String literals are left intact, and deliberately so: the file's own header explains that a naive stripper which also blanked literals would open a phantom comment on any block-comment opener inside a string and shrink the census in silence.

                              The consequence is that example code quoted inside a string literal is counted as a real SDK call site. Gate scripts under scripts/** are full of exactly such strings: refusal messages that show the author what to write instead, fixtures that embed a synthetic changeset body, usage banners.

                              Measured on PR #13596, running the census's own four patterns through the repo's own maskComments over each file that PR changes:

                              patternorigin/mainthat PR's branchdelta
                              analytics.query02+2
                              analytics.meta000
                              analytics.explain000
                              automation.trigger000

                              Both occurrences sat inside one string literal — a fixture's migration table in scripts/check-adr-0087-registration.mjs. The census went red (expected 21 to be 19) and the merge queue ejected the PR. The two comment mentions that same PR adds were masked correctly and contributed nothing, which is what isolates the mechanism to literals.

                              Why this is worth a card and not only the one fix

                              That PR has been fixed on its own terms: its fixture now demonstrates the symbol the fixture itself names, which is what it should have demonstrated anyway. The general shape is untouched, and it is a trap for the next gate author:

                              • the failure lands in a different package from the edit (packages/client) and names a ledger the author has never read;
                              • it is invisible to every local gate family a path derivation produces for a scripts/** edit — nothing in that family reads the census;
                              • it surfaces in the merge queue, i.e. after review, at the most expensive point;
                              • the diagnostic is a bare count mismatch, which says nothing about strings, masking, or gate scripts.

                              Which way it should be resolved is not obvious, and is left to triage. A sketch of the space, with no recommendation attached:

                              1. Do nothing — accept it as a known cost, and let each gate author learn it once, in the merge queue.
                              2. Make the census's own diagnostic self-explaining: when a counted site falls inside a string-literal span, say so in the failure text.
                              3. Teach the census a defensible literal/context distinction — weighed against the measured reason literals are NOT masked today.
                              4. Move the burden to gate authors (a convention for how example code is spelled inside author-facing messages), with the standing objection that a convention no instrument enforces is not a mechanism.

                              ⛔ Nothing here proposes weakening, skipping or exempting the census, and nothing here proposes registering fixture prose in its ledger. The ledger's whole purpose is to be true; prose booked as call sites would be false data in it.

                              Context — surfaced while fixing the merge-queue ejection on #13596 (card #13080). The census is #13079's instrument. Neither is changed by this card, and this card asks for no change to either as a precondition.

                              Generated by Claude Code

                              Metadata

                              Metadata

                              Assignees

                              No one assigned

                                Type

                                Projects

                                No projects

                                  Milestone

                                  No milestone

                                  Relationships

                                  None yet

                                  Development

                                  No branches or pull requests

                                  Issue actions