Skip to content

[finding] The published docs still describe the ADR-0061 search expansion as $or of $contains in six places — and one of them tells the reader the case-insensitivity question is "still open" when #7641 closed it #13988

Open
Open
[finding] The published docs still describe the ADR-0061 search expansion as $or of $contains in six places — and one of them tells the reader the case-insensitivity question is "still open" when #7641 closed it#13988
Labels
documentationImprovements or additions to documentationdomain:specfindingpm:queuepriority:p2Medium: important, M3

Description

@zhuangjianguo
zhuangjianguo
opened on Aug 31, 2026

Filed unassigned by the domain:engine lane PM. Recording only — no severity asserted, routing is triage's. Found by extending #13744's own thesis one hop further: that card fixed the falsehood in packages/objectql/src/engine.ts, #13984 records it in search-companion.ts, and the reason both cards exist is that "an agent trusting the docblock re-introduces the falsehood the sweep just paid to retire." The same sentence is in the published documentation, where the readers are not agents.

Measured on origin/main at 47389b35de. Every grep below ran with a firing positive control on the same corpus ($icontains returns hits in content/docs: query-syntax.mdx 12, troubleshooting.mdx 3, filter.mdx 2, releases/v17.mdx 2), so the hits are readings, not artifacts of a query that could not match.

What the implementation actually does

packages/objectql/src/search-filter.ts:23 — "[#7641] The case-insensitive operator is $icontains, NOT $contains." Source columns compile to $icontains. The one deliberate $contains is the normalized __search companion clause (search-filter.ts:137-148), which is correct and documented as correct — "Do not "align" the two."

The six published sites

A. Hand-written, same two false sentences #13744 just fixed in code

content/docs/protocol/objectql/query-syntax.mdx:970-973:

The engine expands it into an $or of $contains predicates across the object's server-resolved searchable fields (ADR-0061) and deletes search from the AST before the driver sees it — every driver already runs $or/$contains, so no driver support is needed

⇒ Structurally identical to the engine.ts docblock, including the second occurrence in the driver-capability clause — the one #13744's triage noted is "easier to miss, because it reads like a statement of fact about driver capability rather than a description of the expansion shape."

Also: content/docs/data-modeling/queries.mdx:496 ("$and-of-$or-of-$contains filter (ADR-0061)") and content/docs/data-modeling/schema-design.mdx:132-133 ("?search=apollo now expands to name $contains 'apollo' OR project_name $contains 'apollo'").

B. ⚠️ The one that is worse than a stale spelling

content/docs/protocol/objectql/query-syntax.mdx:~1026, inside a callout:

Whether the expansion should emit $icontains instead of $contains — i.e. whether search is case-insensitive by definition — remains a separate open question, and one that can now actually be answered, since both operators mean one thing everywhere.

It does not remain open.#7641 answered it, search-filter.ts:23 carries the answer, and this repo's own release notes record it (below). ⇒ This page does not merely misspell an operator — it tells a reader that an adjudicated question is unresolved and invites them to answer it. That is the shape that gets a settled ruling re-litigated by someone acting in good faith on the published text.

C. Four AUTO-GENERATED rows — ⛔ do not hand-edit these

content/docs/references/data/driver.mdx:51 and :105, driver-sql.mdx:97, driver-nosql.mdx:183, all carrying:

$search is compiled by the engine into an $or of $contains predicates over the searchable fields (ADR-0061)

These pages carry {/* ⚠️ AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. */} and name their source: packages/spec/src/data/driver.zod.ts.

⚠️ Two consequences whoever takes this must not discover late:

  1. The fix lands in the .describe() string in the spec, then regenerates — ⛔ not in the .mdx. (This is the exact trap fix(metadata-protocol): refuse the quoted-empty If-Match entity-tag at ingress (#13576) #13870 hit: the PM told a seat to hand-edit references/api/protocol.mdx, and the seat correctly found the generated source instead. The hand edit would have been wiped by the next gen:docs.)
  2. ⇒ The diff would touch packages/spec/src/**, so clause ②'s path limb FIRES for that part of the work, even though the content is a description string. Sites A and B alone would not.

The docs already contradict each other, and the right answer is already published

content/docs/releases/v17.mdx:3186:

like / ilike stop being folded onto $contains at the wire (#7536), and $search compiles to $icontains so textual search is actually case-insensitive.

⇒ The release notes are correct; the protocol page, the two guides and the four generated rows are not. ⛔ Nothing to do in releases/ — it is release-owned, read-only, and not falsified.

What this does NOT claim

⚠️ Routing — the anchor is genuinely split, so I am not guessing it

Sites A and B land in content/docs/** (hand-written); site C lands in packages/spec/src/data/driver.zod.ts. The anchoring rule says the domain follows where the fix lands, and this one lands in two places. ⇒ Triage should decide whether it is one card or two; ⛔ I am not attaching a domain:* label on a reading I have not measured to a single package.

Refs: #13744 (the engine.ts half, landing now) · #13984 (search-companion.ts) · #7641 / #6520 / #6682 (the adjudication chain) · #7850 (a closed earlier sweep of this same family — "Three more copies of the $search case declaration are self-contradictory … they name $contains" — which suggests the published docs were outside that sweep's scope, or have re-drifted since) · PR #13740 (the published-skill correction).

Metadata

Metadata

Assignees

No one assigned

    Labels

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      , 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
       blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
[finding] The published docs still describe the ADR-0061 search expansion as `$or` of `$contains` in six places — and one of them tells the reader the case-insensitivity question is "still open" when #7641 closed it · Issue #13988 · objectstack-ai/objectstack · GitHub
      Skip to content
      [finding] The published docs still describe the ADR-0061 search expansion as $or of $contains in six places — and one of them tells the reader the case-insensitivity question is "still open" when #7641 closed it #13988
      Open
      Open
      [finding] The published docs still describe the ADR-0061 search expansion as $or of $contains in six places — and one of them tells the reader the case-insensitivity question is "still open" when #7641 closed it#13988
      Labels
      documentationImprovements or additions to documentationdomain:specfindingpm:queuepriority:p2Medium: important, M3
      Description
      @zhuangjianguo
      zhuangjianguo
      opened on Aug 31, 2026
      Filed unassigned by the domain:engine lane PM. Recording only — no severity asserted, routing is triage's. Found by extending #13744's own thesis one hop further: that card fixed the falsehood in packages/objectql/src/engine.ts, #13984 records it in search-companion.ts, and the reason both cards exist is that "an agent trusting the docblock re-introduces the falsehood the sweep just paid to retire." The same sentence is in the published documentation, where the readers are not agents.
      Measured on origin/main at 47389b35de. Every grep below ran with a firing positive control on the same corpus ($icontains returns hits in content/docs: query-syntax.mdx 12, troubleshooting.mdx 3, filter.mdx 2, releases/v17.mdx 2), so the hits are readings, not artifacts of a query that could not match.
      What the implementation actually does
      packages/objectql/src/search-filter.ts:23 — "[#7641] The case-insensitive operator is $icontains, NOT $contains." Source columns compile to $icontains. The one deliberate $contains is the normalized __search companion clause (search-filter.ts:137-148), which is correct and documented as correct — "Do not "align" the two."
      The six published sites
      A. Hand-written, same two false sentences #13744 just fixed in code
      content/docs/protocol/objectql/query-syntax.mdx:970-973:
      The engine expands it into an $or of $contains predicates across the object's server-resolved searchable fields (ADR-0061) and deletes search from the AST before the driver sees it — every driver already runs $or/$contains, so no driver support is needed
      ⇒ Structurally identical to the engine.ts docblock, including the second occurrence in the driver-capability clause — the one #13744's triage noted is "easier to miss, because it reads like a statement of fact about driver capability rather than a description of the expansion shape."
      Also: content/docs/data-modeling/queries.mdx:496 ("$and-of-$or-of-$contains filter (ADR-0061)") and content/docs/data-modeling/schema-design.mdx:132-133 ("?search=apollo now expands to name $contains 'apollo' OR project_name $contains 'apollo'").
      B. ⚠️ The one that is worse than a stale spelling
      content/docs/protocol/objectql/query-syntax.mdx:~1026, inside a callout:
      Whether the expansion should emit $icontains instead of $contains — i.e. whether search is case-insensitive by definition — remains a separate open question, and one that can now actually be answered, since both operators mean one thing everywhere.
      It does not remain open.#7641 answered it, search-filter.ts:23 carries the answer, and this repo's own release notes record it (below). ⇒ This page does not merely misspell an operator — it tells a reader that an adjudicated question is unresolved and invites them to answer it. That is the shape that gets a settled ruling re-litigated by someone acting in good faith on the published text.
      C. Four AUTO-GENERATED rows — ⛔ do not hand-edit these
      content/docs/references/data/driver.mdx:51 and :105, driver-sql.mdx:97, driver-nosql.mdx:183, all carrying:
      $search is compiled by the engine into an $or of $contains predicates over the searchable fields (ADR-0061)
      These pages carry {/* ⚠️ AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. */} and name their source: packages/spec/src/data/driver.zod.ts.
      ⚠️ Two consequences whoever takes this must not discover late:
      1. The fix lands in the .describe() string in the spec, then regenerates — ⛔ not in the .mdx. (This is the exact trap fix(metadata-protocol): refuse the quoted-empty If-Match entity-tag at ingress (#13576) #13870 hit: the PM told a seat to hand-edit references/api/protocol.mdx, and the seat correctly found the generated source instead. The hand edit would have been wiped by the next gen:docs.)
      2. ⇒ The diff would touch packages/spec/src/**, so clause ②'s path limb FIRES for that part of the work, even though the content is a description string. Sites A and B alone would not.
      The docs already contradict each other, and the right answer is already published
      content/docs/releases/v17.mdx:3186:
      like / ilike stop being folded onto $contains at the wire (#7536), and $search compiles to $icontains so textual search is actually case-insensitive.
      ⇒ The release notes are correct; the protocol page, the two guides and the four generated rows are not. ⛔ Nothing to do in releases/ — it is release-owned, read-only, and not falsified.
      What this does NOT claim
      ⚠️ Routing — the anchor is genuinely split, so I am not guessing it
      Sites A and B land in content/docs/** (hand-written); site C lands in packages/spec/src/data/driver.zod.ts. The anchoring rule says the domain follows where the fix lands, and this one lands in two places. ⇒ Triage should decide whether it is one card or two; ⛔ I am not attaching a domain:* label on a reading I have not measured to a single package.
      Refs: #13744 (the engine.ts half, landing now) · #13984 (search-companion.ts) · #7641 / #6520 / #6682 (the adjudication chain) · #7850 (a closed earlier sweep of this same family — "Three more copies of the $search case declaration are self-contradictory … they name $contains" — which suggests the published docs were outside that sweep's scope, or have re-drifted since) · PR #13740 (the published-skill correction).
      Metadata
      Metadata
      Assignees
      No one assigned
        Labels
        documentationImprovements or additions to documentationdomain:specfindingpm:queuepriority:p2Medium: important, M3
        Type
        No type
        Projects
        No projects
          Milestone
          No milestone
          Relationships
          None yet
          Development
          No branches or pull requests
          Issue actions
          
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
[finding] The published docs still describe the ADR-0061 search expansion as `$or` of `$contains` in six places — and one of them tells the reader the case-insensitivity question is "still open" when #7641 closed it · Issue #13988 · objectstack-ai/objectstack · GitHub
          Skip to content
          [finding] The published docs still describe the ADR-0061 search expansion as $or of $contains in six places — and one of them tells the reader the case-insensitivity question is "still open" when #7641 closed it #13988
          Open
          Open
          [finding] The published docs still describe the ADR-0061 search expansion as $or of $contains in six places — and one of them tells the reader the case-insensitivity question is "still open" when #7641 closed it#13988
          Labels
          documentationImprovements or additions to documentationdomain:specfindingpm:queuepriority:p2Medium: important, M3
          Description
          @zhuangjianguo
          zhuangjianguo
          opened on Aug 31, 2026
          Filed unassigned by the domain:engine lane PM. Recording only — no severity asserted, routing is triage's. Found by extending #13744's own thesis one hop further: that card fixed the falsehood in packages/objectql/src/engine.ts, #13984 records it in search-companion.ts, and the reason both cards exist is that "an agent trusting the docblock re-introduces the falsehood the sweep just paid to retire." The same sentence is in the published documentation, where the readers are not agents.
          Measured on origin/main at 47389b35de. Every grep below ran with a firing positive control on the same corpus ($icontains returns hits in content/docs: query-syntax.mdx 12, troubleshooting.mdx 3, filter.mdx 2, releases/v17.mdx 2), so the hits are readings, not artifacts of a query that could not match.
          What the implementation actually does
          packages/objectql/src/search-filter.ts:23 — "[#7641] The case-insensitive operator is $icontains, NOT $contains." Source columns compile to $icontains. The one deliberate $contains is the normalized __search companion clause (search-filter.ts:137-148), which is correct and documented as correct — "Do not "align" the two."
          The six published sites
          A. Hand-written, same two false sentences #13744 just fixed in code
          content/docs/protocol/objectql/query-syntax.mdx:970-973:
          The engine expands it into an $or of $contains predicates across the object's server-resolved searchable fields (ADR-0061) and deletes search from the AST before the driver sees it — every driver already runs $or/$contains, so no driver support is needed
          ⇒ Structurally identical to the engine.ts docblock, including the second occurrence in the driver-capability clause — the one #13744's triage noted is "easier to miss, because it reads like a statement of fact about driver capability rather than a description of the expansion shape."
          Also: content/docs/data-modeling/queries.mdx:496 ("$and-of-$or-of-$contains filter (ADR-0061)") and content/docs/data-modeling/schema-design.mdx:132-133 ("?search=apollo now expands to name $contains 'apollo' OR project_name $contains 'apollo'").
          B. ⚠️ The one that is worse than a stale spelling
          content/docs/protocol/objectql/query-syntax.mdx:~1026, inside a callout:
          Whether the expansion should emit $icontains instead of $contains — i.e. whether search is case-insensitive by definition — remains a separate open question, and one that can now actually be answered, since both operators mean one thing everywhere.
          It does not remain open.#7641 answered it, search-filter.ts:23 carries the answer, and this repo's own release notes record it (below). ⇒ This page does not merely misspell an operator — it tells a reader that an adjudicated question is unresolved and invites them to answer it. That is the shape that gets a settled ruling re-litigated by someone acting in good faith on the published text.
          C. Four AUTO-GENERATED rows — ⛔ do not hand-edit these
          content/docs/references/data/driver.mdx:51 and :105, driver-sql.mdx:97, driver-nosql.mdx:183, all carrying:
          $search is compiled by the engine into an $or of $contains predicates over the searchable fields (ADR-0061)
          These pages carry {/* ⚠️ AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. */} and name their source: packages/spec/src/data/driver.zod.ts.
          ⚠️ Two consequences whoever takes this must not discover late:
          1. The fix lands in the .describe() string in the spec, then regenerates — ⛔ not in the .mdx. (This is the exact trap fix(metadata-protocol): refuse the quoted-empty If-Match entity-tag at ingress (#13576) #13870 hit: the PM told a seat to hand-edit references/api/protocol.mdx, and the seat correctly found the generated source instead. The hand edit would have been wiped by the next gen:docs.)
          2. ⇒ The diff would touch packages/spec/src/**, so clause ②'s path limb FIRES for that part of the work, even though the content is a description string. Sites A and B alone would not.
          The docs already contradict each other, and the right answer is already published
          content/docs/releases/v17.mdx:3186:
          like / ilike stop being folded onto $contains at the wire (#7536), and $search compiles to $icontains so textual search is actually case-insensitive.
          ⇒ The release notes are correct; the protocol page, the two guides and the four generated rows are not. ⛔ Nothing to do in releases/ — it is release-owned, read-only, and not falsified.
          What this does NOT claim
          ⚠️ Routing — the anchor is genuinely split, so I am not guessing it
          Sites A and B land in content/docs/** (hand-written); site C lands in packages/spec/src/data/driver.zod.ts. The anchoring rule says the domain follows where the fix lands, and this one lands in two places. ⇒ Triage should decide whether it is one card or two; ⛔ I am not attaching a domain:* label on a reading I have not measured to a single package.
          Refs: #13744 (the engine.ts half, landing now) · #13984 (search-companion.ts) · #7641 / #6520 / #6682 (the adjudication chain) · #7850 (a closed earlier sweep of this same family — "Three more copies of the $search case declaration are self-contradictory … they name $contains" — which suggests the published docs were outside that sweep's scope, or have re-drifted since) · PR #13740 (the published-skill correction).
          Metadata
          Metadata
          Assignees
          No one assigned
            Labels
            documentationImprovements or additions to documentationdomain:specfindingpm:queuepriority:p2Medium: important, M3
            Type
            No type
            Projects
            No projects
              Milestone
              No milestone
              Relationships
              None yet
              Development
              No branches or pull requests
              Issue actions
              
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
[finding] The published docs still describe the ADR-0061 search expansion as `$or` of `$contains` in six places — and one of them tells the reader the case-insensitivity question is "still open" when #7641 closed it · Issue #13988 · objectstack-ai/objectstack · GitHub
              Skip to content
              [finding] The published docs still describe the ADR-0061 search expansion as $or of $contains in six places — and one of them tells the reader the case-insensitivity question is "still open" when #7641 closed it #13988
              Open
              Open
              [finding] The published docs still describe the ADR-0061 search expansion as $or of $contains in six places — and one of them tells the reader the case-insensitivity question is "still open" when #7641 closed it#13988
              Labels
              documentationImprovements or additions to documentationdomain:specfindingpm:queuepriority:p2Medium: important, M3
              Description
              @zhuangjianguo
              zhuangjianguo
              opened on Aug 31, 2026
              Filed unassigned by the domain:engine lane PM. Recording only — no severity asserted, routing is triage's. Found by extending #13744's own thesis one hop further: that card fixed the falsehood in packages/objectql/src/engine.ts, #13984 records it in search-companion.ts, and the reason both cards exist is that "an agent trusting the docblock re-introduces the falsehood the sweep just paid to retire." The same sentence is in the published documentation, where the readers are not agents.
              Measured on origin/main at 47389b35de. Every grep below ran with a firing positive control on the same corpus ($icontains returns hits in content/docs: query-syntax.mdx 12, troubleshooting.mdx 3, filter.mdx 2, releases/v17.mdx 2), so the hits are readings, not artifacts of a query that could not match.
              What the implementation actually does
              packages/objectql/src/search-filter.ts:23 — "[#7641] The case-insensitive operator is $icontains, NOT $contains." Source columns compile to $icontains. The one deliberate $contains is the normalized __search companion clause (search-filter.ts:137-148), which is correct and documented as correct — "Do not "align" the two."
              The six published sites
              A. Hand-written, same two false sentences #13744 just fixed in code
              content/docs/protocol/objectql/query-syntax.mdx:970-973:
              The engine expands it into an $or of $contains predicates across the object's server-resolved searchable fields (ADR-0061) and deletes search from the AST before the driver sees it — every driver already runs $or/$contains, so no driver support is needed
              ⇒ Structurally identical to the engine.ts docblock, including the second occurrence in the driver-capability clause — the one #13744's triage noted is "easier to miss, because it reads like a statement of fact about driver capability rather than a description of the expansion shape."
              Also: content/docs/data-modeling/queries.mdx:496 ("$and-of-$or-of-$contains filter (ADR-0061)") and content/docs/data-modeling/schema-design.mdx:132-133 ("?search=apollo now expands to name $contains 'apollo' OR project_name $contains 'apollo'").
              B. ⚠️ The one that is worse than a stale spelling
              content/docs/protocol/objectql/query-syntax.mdx:~1026, inside a callout:
              Whether the expansion should emit $icontains instead of $contains — i.e. whether search is case-insensitive by definition — remains a separate open question, and one that can now actually be answered, since both operators mean one thing everywhere.
              It does not remain open.#7641 answered it, search-filter.ts:23 carries the answer, and this repo's own release notes record it (below). ⇒ This page does not merely misspell an operator — it tells a reader that an adjudicated question is unresolved and invites them to answer it. That is the shape that gets a settled ruling re-litigated by someone acting in good faith on the published text.
              C. Four AUTO-GENERATED rows — ⛔ do not hand-edit these
              content/docs/references/data/driver.mdx:51 and :105, driver-sql.mdx:97, driver-nosql.mdx:183, all carrying:
              $search is compiled by the engine into an $or of $contains predicates over the searchable fields (ADR-0061)
              These pages carry {/* ⚠️ AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. */} and name their source: packages/spec/src/data/driver.zod.ts.
              ⚠️ Two consequences whoever takes this must not discover late:
              1. The fix lands in the .describe() string in the spec, then regenerates — ⛔ not in the .mdx. (This is the exact trap fix(metadata-protocol): refuse the quoted-empty If-Match entity-tag at ingress (#13576) #13870 hit: the PM told a seat to hand-edit references/api/protocol.mdx, and the seat correctly found the generated source instead. The hand edit would have been wiped by the next gen:docs.)
              2. ⇒ The diff would touch packages/spec/src/**, so clause ②'s path limb FIRES for that part of the work, even though the content is a description string. Sites A and B alone would not.
              The docs already contradict each other, and the right answer is already published
              content/docs/releases/v17.mdx:3186:
              like / ilike stop being folded onto $contains at the wire (#7536), and $search compiles to $icontains so textual search is actually case-insensitive.
              ⇒ The release notes are correct; the protocol page, the two guides and the four generated rows are not. ⛔ Nothing to do in releases/ — it is release-owned, read-only, and not falsified.
              What this does NOT claim
              ⚠️ Routing — the anchor is genuinely split, so I am not guessing it
              Sites A and B land in content/docs/** (hand-written); site C lands in packages/spec/src/data/driver.zod.ts. The anchoring rule says the domain follows where the fix lands, and this one lands in two places. ⇒ Triage should decide whether it is one card or two; ⛔ I am not attaching a domain:* label on a reading I have not measured to a single package.
              Refs: #13744 (the engine.ts half, landing now) · #13984 (search-companion.ts) · #7641 / #6520 / #6682 (the adjudication chain) · #7850 (a closed earlier sweep of this same family — "Three more copies of the $search case declaration are self-contradictory … they name $contains" — which suggests the published docs were outside that sweep's scope, or have re-drifted since) · PR #13740 (the published-skill correction).
              Metadata
              Metadata
              Assignees
              No one assigned
                Labels
                documentationImprovements or additions to documentationdomain:specfindingpm:queuepriority:p2Medium: important, M3
                Type
                No type
                Projects
                No projects
                  Milestone
                  No milestone
                  Relationships
                  None yet
                  Development
                  No branches or pull requests
                  Issue actions
                  
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '
[finding] The published docs still describe the ADR-0061 search expansion as `$or` of `$contains` in six places — and one of them tells the reader the case-insensitivity question is "still open" when #7641 closed it · Issue #13988 · objectstack-ai/objectstack · GitHub
                  Skip to content
                  [finding] The published docs still describe the ADR-0061 search expansion as $or of $contains in six places — and one of them tells the reader the case-insensitivity question is "still open" when #7641 closed it #13988
                  Open
                  Open
                  [finding] The published docs still describe the ADR-0061 search expansion as $or of $contains in six places — and one of them tells the reader the case-insensitivity question is "still open" when #7641 closed it#13988
                  Labels
                  documentationImprovements or additions to documentationdomain:specfindingpm:queuepriority:p2Medium: important, M3
                  Description
                  @zhuangjianguo
                  zhuangjianguo
                  opened on Aug 31, 2026
                  Filed unassigned by the domain:engine lane PM. Recording only — no severity asserted, routing is triage's. Found by extending #13744's own thesis one hop further: that card fixed the falsehood in packages/objectql/src/engine.ts, #13984 records it in search-companion.ts, and the reason both cards exist is that "an agent trusting the docblock re-introduces the falsehood the sweep just paid to retire." The same sentence is in the published documentation, where the readers are not agents.
                  Measured on origin/main at 47389b35de. Every grep below ran with a firing positive control on the same corpus ($icontains returns hits in content/docs: query-syntax.mdx 12, troubleshooting.mdx 3, filter.mdx 2, releases/v17.mdx 2), so the hits are readings, not artifacts of a query that could not match.
                  What the implementation actually does
                  packages/objectql/src/search-filter.ts:23 — "[#7641] The case-insensitive operator is $icontains, NOT $contains." Source columns compile to $icontains. The one deliberate $contains is the normalized __search companion clause (search-filter.ts:137-148), which is correct and documented as correct — "Do not "align" the two."
                  The six published sites
                  A. Hand-written, same two false sentences #13744 just fixed in code
                  content/docs/protocol/objectql/query-syntax.mdx:970-973:
                  The engine expands it into an $or of $contains predicates across the object's server-resolved searchable fields (ADR-0061) and deletes search from the AST before the driver sees it — every driver already runs $or/$contains, so no driver support is needed
                  ⇒ Structurally identical to the engine.ts docblock, including the second occurrence in the driver-capability clause — the one #13744's triage noted is "easier to miss, because it reads like a statement of fact about driver capability rather than a description of the expansion shape."
                  Also: content/docs/data-modeling/queries.mdx:496 ("$and-of-$or-of-$contains filter (ADR-0061)") and content/docs/data-modeling/schema-design.mdx:132-133 ("?search=apollo now expands to name $contains 'apollo' OR project_name $contains 'apollo'").
                  B. ⚠️ The one that is worse than a stale spelling
                  content/docs/protocol/objectql/query-syntax.mdx:~1026, inside a callout:
                  Whether the expansion should emit $icontains instead of $contains — i.e. whether search is case-insensitive by definition — remains a separate open question, and one that can now actually be answered, since both operators mean one thing everywhere.
                  It does not remain open.#7641 answered it, search-filter.ts:23 carries the answer, and this repo's own release notes record it (below). ⇒ This page does not merely misspell an operator — it tells a reader that an adjudicated question is unresolved and invites them to answer it. That is the shape that gets a settled ruling re-litigated by someone acting in good faith on the published text.
                  C. Four AUTO-GENERATED rows — ⛔ do not hand-edit these
                  content/docs/references/data/driver.mdx:51 and :105, driver-sql.mdx:97, driver-nosql.mdx:183, all carrying:
                  $search is compiled by the engine into an $or of $contains predicates over the searchable fields (ADR-0061)
                  These pages carry {/* ⚠️ AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. */} and name their source: packages/spec/src/data/driver.zod.ts.
                  ⚠️ Two consequences whoever takes this must not discover late:
                  1. The fix lands in the .describe() string in the spec, then regenerates — ⛔ not in the .mdx. (This is the exact trap fix(metadata-protocol): refuse the quoted-empty If-Match entity-tag at ingress (#13576) #13870 hit: the PM told a seat to hand-edit references/api/protocol.mdx, and the seat correctly found the generated source instead. The hand edit would have been wiped by the next gen:docs.)
                  2. ⇒ The diff would touch packages/spec/src/**, so clause ②'s path limb FIRES for that part of the work, even though the content is a description string. Sites A and B alone would not.
                  The docs already contradict each other, and the right answer is already published
                  content/docs/releases/v17.mdx:3186:
                  like / ilike stop being folded onto $contains at the wire (#7536), and $search compiles to $icontains so textual search is actually case-insensitive.
                  ⇒ The release notes are correct; the protocol page, the two guides and the four generated rows are not. ⛔ Nothing to do in releases/ — it is release-owned, read-only, and not falsified.
                  What this does NOT claim
                  ⚠️ Routing — the anchor is genuinely split, so I am not guessing it
                  Sites A and B land in content/docs/** (hand-written); site C lands in packages/spec/src/data/driver.zod.ts. The anchoring rule says the domain follows where the fix lands, and this one lands in two places. ⇒ Triage should decide whether it is one card or two; ⛔ I am not attaching a domain:* label on a reading I have not measured to a single package.
                  Refs: #13744 (the engine.ts half, landing now) · #13984 (search-companion.ts) · #7641 / #6520 / #6682 (the adjudication chain) · #7850 (a closed earlier sweep of this same family — "Three more copies of the $search case declaration are self-contradictory … they name $contains" — which suggests the published docs were outside that sweep's scope, or have re-drifted since) · PR #13740 (the published-skill correction).
                  Metadata
                  Metadata
                  Assignees
                  No one assigned
                    Labels
                    documentationImprovements or additions to documentationdomain:specfindingpm:queuepriority:p2Medium: important, M3
                    Type
                    No type
                    Projects
                    No projects
                      Milestone
                      No milestone
                      Relationships
                      None yet
                      Development
                      No branches or pull requests
                      Issue actions
                      
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
[finding] The published docs still describe the ADR-0061 search expansion as `$or` of `$contains` in six places — and one of them tells the reader the case-insensitivity question is "still open" when #7641 closed it · Issue #13988 · objectstack-ai/objectstack · GitHub
                      Skip to content
                      [finding] The published docs still describe the ADR-0061 search expansion as $or of $contains in six places — and one of them tells the reader the case-insensitivity question is "still open" when #7641 closed it #13988
                      Open
                      Open
                      [finding] The published docs still describe the ADR-0061 search expansion as $or of $contains in six places — and one of them tells the reader the case-insensitivity question is "still open" when #7641 closed it#13988
                      Labels
                      documentationImprovements or additions to documentationdomain:specfindingpm:queuepriority:p2Medium: important, M3
                      Description
                      @zhuangjianguo
                      zhuangjianguo
                      opened on Aug 31, 2026
                      Filed unassigned by the domain:engine lane PM. Recording only — no severity asserted, routing is triage's. Found by extending #13744's own thesis one hop further: that card fixed the falsehood in packages/objectql/src/engine.ts, #13984 records it in search-companion.ts, and the reason both cards exist is that "an agent trusting the docblock re-introduces the falsehood the sweep just paid to retire." The same sentence is in the published documentation, where the readers are not agents.
                      Measured on origin/main at 47389b35de. Every grep below ran with a firing positive control on the same corpus ($icontains returns hits in content/docs: query-syntax.mdx 12, troubleshooting.mdx 3, filter.mdx 2, releases/v17.mdx 2), so the hits are readings, not artifacts of a query that could not match.
                      What the implementation actually does
                      packages/objectql/src/search-filter.ts:23 — "[#7641] The case-insensitive operator is $icontains, NOT $contains." Source columns compile to $icontains. The one deliberate $contains is the normalized __search companion clause (search-filter.ts:137-148), which is correct and documented as correct — "Do not "align" the two."
                      The six published sites
                      A. Hand-written, same two false sentences #13744 just fixed in code
                      content/docs/protocol/objectql/query-syntax.mdx:970-973:
                      The engine expands it into an $or of $contains predicates across the object's server-resolved searchable fields (ADR-0061) and deletes search from the AST before the driver sees it — every driver already runs $or/$contains, so no driver support is needed
                      ⇒ Structurally identical to the engine.ts docblock, including the second occurrence in the driver-capability clause — the one #13744's triage noted is "easier to miss, because it reads like a statement of fact about driver capability rather than a description of the expansion shape."
                      Also: content/docs/data-modeling/queries.mdx:496 ("$and-of-$or-of-$contains filter (ADR-0061)") and content/docs/data-modeling/schema-design.mdx:132-133 ("?search=apollo now expands to name $contains 'apollo' OR project_name $contains 'apollo'").
                      B. ⚠️ The one that is worse than a stale spelling
                      content/docs/protocol/objectql/query-syntax.mdx:~1026, inside a callout:
                      Whether the expansion should emit $icontains instead of $contains — i.e. whether search is case-insensitive by definition — remains a separate open question, and one that can now actually be answered, since both operators mean one thing everywhere.
                      It does not remain open.#7641 answered it, search-filter.ts:23 carries the answer, and this repo's own release notes record it (below). ⇒ This page does not merely misspell an operator — it tells a reader that an adjudicated question is unresolved and invites them to answer it. That is the shape that gets a settled ruling re-litigated by someone acting in good faith on the published text.
                      C. Four AUTO-GENERATED rows — ⛔ do not hand-edit these
                      content/docs/references/data/driver.mdx:51 and :105, driver-sql.mdx:97, driver-nosql.mdx:183, all carrying:
                      $search is compiled by the engine into an $or of $contains predicates over the searchable fields (ADR-0061)
                      These pages carry {/* ⚠️ AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. */} and name their source: packages/spec/src/data/driver.zod.ts.
                      ⚠️ Two consequences whoever takes this must not discover late:
                      1. The fix lands in the .describe() string in the spec, then regenerates — ⛔ not in the .mdx. (This is the exact trap fix(metadata-protocol): refuse the quoted-empty If-Match entity-tag at ingress (#13576) #13870 hit: the PM told a seat to hand-edit references/api/protocol.mdx, and the seat correctly found the generated source instead. The hand edit would have been wiped by the next gen:docs.)
                      2. ⇒ The diff would touch packages/spec/src/**, so clause ②'s path limb FIRES for that part of the work, even though the content is a description string. Sites A and B alone would not.
                      The docs already contradict each other, and the right answer is already published
                      content/docs/releases/v17.mdx:3186:
                      like / ilike stop being folded onto $contains at the wire (#7536), and $search compiles to $icontains so textual search is actually case-insensitive.
                      ⇒ The release notes are correct; the protocol page, the two guides and the four generated rows are not. ⛔ Nothing to do in releases/ — it is release-owned, read-only, and not falsified.
                      What this does NOT claim
                      ⚠️ Routing — the anchor is genuinely split, so I am not guessing it
                      Sites A and B land in content/docs/** (hand-written); site C lands in packages/spec/src/data/driver.zod.ts. The anchoring rule says the domain follows where the fix lands, and this one lands in two places. ⇒ Triage should decide whether it is one card or two; ⛔ I am not attaching a domain:* label on a reading I have not measured to a single package.
                      Refs: #13744 (the engine.ts half, landing now) · #13984 (search-companion.ts) · #7641 / #6520 / #6682 (the adjudication chain) · #7850 (a closed earlier sweep of this same family — "Three more copies of the $search case declaration are self-contradictory … they name $contains" — which suggests the published docs were outside that sweep's scope, or have re-drifted since) · PR #13740 (the published-skill correction).
                      Metadata
                      Metadata
                      Assignees
                      No one assigned
                        Labels
                        documentationImprovements or additions to documentationdomain:specfindingpm:queuepriority:p2Medium: important, M3
                        Type
                        No type
                        Projects
                        No projects
                          Milestone
                          No milestone
                          Relationships
                          None yet
                          Development
                          No branches or pull requests
                          Issue actions
                          
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
[finding] The published docs still describe the ADR-0061 search expansion as `$or` of `$contains` in six places — and one of them tells the reader the case-insensitivity question is "still open" when #7641 closed it · Issue #13988 · objectstack-ai/objectstack · GitHub
                          Skip to content
                          [finding] The published docs still describe the ADR-0061 search expansion as $or of $contains in six places — and one of them tells the reader the case-insensitivity question is "still open" when #7641 closed it #13988
                          Open
                          Open
                          [finding] The published docs still describe the ADR-0061 search expansion as $or of $contains in six places — and one of them tells the reader the case-insensitivity question is "still open" when #7641 closed it#13988
                          Labels
                          documentationImprovements or additions to documentationdomain:specfindingpm:queuepriority:p2Medium: important, M3
                          Description
                          @zhuangjianguo
                          zhuangjianguo
                          opened on Aug 31, 2026
                          Filed unassigned by the domain:engine lane PM. Recording only — no severity asserted, routing is triage's. Found by extending #13744's own thesis one hop further: that card fixed the falsehood in packages/objectql/src/engine.ts, #13984 records it in search-companion.ts, and the reason both cards exist is that "an agent trusting the docblock re-introduces the falsehood the sweep just paid to retire." The same sentence is in the published documentation, where the readers are not agents.
                          Measured on origin/main at 47389b35de. Every grep below ran with a firing positive control on the same corpus ($icontains returns hits in content/docs: query-syntax.mdx 12, troubleshooting.mdx 3, filter.mdx 2, releases/v17.mdx 2), so the hits are readings, not artifacts of a query that could not match.
                          What the implementation actually does
                          packages/objectql/src/search-filter.ts:23 — "[#7641] The case-insensitive operator is $icontains, NOT $contains." Source columns compile to $icontains. The one deliberate $contains is the normalized __search companion clause (search-filter.ts:137-148), which is correct and documented as correct — "Do not "align" the two."
                          The six published sites
                          A. Hand-written, same two false sentences #13744 just fixed in code
                          content/docs/protocol/objectql/query-syntax.mdx:970-973:
                          The engine expands it into an $or of $contains predicates across the object's server-resolved searchable fields (ADR-0061) and deletes search from the AST before the driver sees it — every driver already runs $or/$contains, so no driver support is needed
                          ⇒ Structurally identical to the engine.ts docblock, including the second occurrence in the driver-capability clause — the one #13744's triage noted is "easier to miss, because it reads like a statement of fact about driver capability rather than a description of the expansion shape."
                          Also: content/docs/data-modeling/queries.mdx:496 ("$and-of-$or-of-$contains filter (ADR-0061)") and content/docs/data-modeling/schema-design.mdx:132-133 ("?search=apollo now expands to name $contains 'apollo' OR project_name $contains 'apollo'").
                          B. ⚠️ The one that is worse than a stale spelling
                          content/docs/protocol/objectql/query-syntax.mdx:~1026, inside a callout:
                          Whether the expansion should emit $icontains instead of $contains — i.e. whether search is case-insensitive by definition — remains a separate open question, and one that can now actually be answered, since both operators mean one thing everywhere.
                          It does not remain open.#7641 answered it, search-filter.ts:23 carries the answer, and this repo's own release notes record it (below). ⇒ This page does not merely misspell an operator — it tells a reader that an adjudicated question is unresolved and invites them to answer it. That is the shape that gets a settled ruling re-litigated by someone acting in good faith on the published text.
                          C. Four AUTO-GENERATED rows — ⛔ do not hand-edit these
                          content/docs/references/data/driver.mdx:51 and :105, driver-sql.mdx:97, driver-nosql.mdx:183, all carrying:
                          $search is compiled by the engine into an $or of $contains predicates over the searchable fields (ADR-0061)
                          These pages carry {/* ⚠️ AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. */} and name their source: packages/spec/src/data/driver.zod.ts.
                          ⚠️ Two consequences whoever takes this must not discover late:
                          1. The fix lands in the .describe() string in the spec, then regenerates — ⛔ not in the .mdx. (This is the exact trap fix(metadata-protocol): refuse the quoted-empty If-Match entity-tag at ingress (#13576) #13870 hit: the PM told a seat to hand-edit references/api/protocol.mdx, and the seat correctly found the generated source instead. The hand edit would have been wiped by the next gen:docs.)
                          2. ⇒ The diff would touch packages/spec/src/**, so clause ②'s path limb FIRES for that part of the work, even though the content is a description string. Sites A and B alone would not.
                          The docs already contradict each other, and the right answer is already published
                          content/docs/releases/v17.mdx:3186:
                          like / ilike stop being folded onto $contains at the wire (#7536), and $search compiles to $icontains so textual search is actually case-insensitive.
                          ⇒ The release notes are correct; the protocol page, the two guides and the four generated rows are not. ⛔ Nothing to do in releases/ — it is release-owned, read-only, and not falsified.
                          What this does NOT claim
                          ⚠️ Routing — the anchor is genuinely split, so I am not guessing it
                          Sites A and B land in content/docs/** (hand-written); site C lands in packages/spec/src/data/driver.zod.ts. The anchoring rule says the domain follows where the fix lands, and this one lands in two places. ⇒ Triage should decide whether it is one card or two; ⛔ I am not attaching a domain:* label on a reading I have not measured to a single package.
                          Refs: #13744 (the engine.ts half, landing now) · #13984 (search-companion.ts) · #7641 / #6520 / #6682 (the adjudication chain) · #7850 (a closed earlier sweep of this same family — "Three more copies of the $search case declaration are self-contradictory … they name $contains" — which suggests the published docs were outside that sweep's scope, or have re-drifted since) · PR #13740 (the published-skill correction).
                          Metadata
                          Metadata
                          Assignees
                          No one assigned
                            Labels
                            documentationImprovements or additions to documentationdomain:specfindingpm:queuepriority:p2Medium: important, M3
                            Type
                            No type
                            Projects
                            No projects
                              Milestone
                              No milestone
                              Relationships
                              None yet
                              Development
                              No branches or pull requests
                              Issue actions
                              
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Universal Dark Mode - works on any site
(function() {
var enabled = true;
function applyDarkMode() {
if (!enabled) return;
// Create style element if it doesn't exist
var style = document.getElementById('universal-dark-mode-style');
if (!style) {
style = document.createElement('style');
style.id = 'universal-dark-mode-style';
document.head.appendChild(style);
}
// Dark mode CSS - inverts colors but preserves images/video
style.textContent = '
/* Invert everything except media */
html {
filter: invert(1) hue-rotate(180deg) !important;
background: #1a1a2e !important;
}
/* Restore images, videos, iframes, canvas */
img, video, iframe, canvas, svg, picture, [style*="background-image"] {
filter: invert(1) hue-rotate(180deg) !important;
}
/* Preserve specific elements that should not be inverted */
.no-dark-mode, .no-dark-mode *,
[data-theme="light"], [data-theme="light"],
.ace_editor, .ace_editor *,
.CodeMirror, .CodeMirror *,
.monaco-editor, .monaco-editor *,
.markdown-body pre, .markdown-body pre *,
.highlight, .highlight *,
pre code, pre code * {
filter: none !important;
}
/* Fix common UI elements */
.modal, .popup, .dropdown-menu, .tooltip, .popover {
filter: invert(1) hue-rotate(180deg) !important;
background: #2d2d44 !important;
border-color: #444 !important;
}
/* Scrollbars */
::-webkit-scrollbar { background: #1a1a2e !important; }
::-webkit-scrollbar-thumb { background: #444 !important; }
::-webkit-scrollbar-thumb:hover { background: #555 !important; }
/* Selection */
::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
';
}
function removeDarkMode() {
var style = document.getElementById('universal-dark-mode-style');
if (style) style.remove();
}
// Toggle with Alt+Shift+D
document.addEventListener('keydown', function(e) {
if (e.altKey && e.shiftKey && e.key === 'D') {
e.preventDefault();
enabled = !enabled;
if (enabled) {
applyDarkMode();
console.log('[Universal Dark Mode] Enabled');
} else {
removeDarkMode();
console.log('[Universal Dark Mode] Disabled');
}
}
});
// Apply on load
applyDarkMode();
// Re-apply on dynamic content
var observer = new MutationObserver(function(mutations) {
if (enabled && !document.getElementById('universal-dark-mode-style')) {
applyDarkMode();
}
});
observer.observe(document.head, { childList: true });
console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');
})();
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();
[finding] The published docs still describe the ADR-0061 search expansion as `$or` of `$contains` in six places — and one of them tells the reader the case-insensitivity question is "still open" when #7641 closed it · Issue #13988 · objectstack-ai/objectstack · GitHub
                              Skip to content
                              [finding] The published docs still describe the ADR-0061 search expansion as $or of $contains in six places — and one of them tells the reader the case-insensitivity question is "still open" when #7641 closed it #13988
                              Open
                              Open
                              [finding] The published docs still describe the ADR-0061 search expansion as $or of $contains in six places — and one of them tells the reader the case-insensitivity question is "still open" when #7641 closed it#13988
                              Labels
                              documentationImprovements or additions to documentationdomain:specfindingpm:queuepriority:p2Medium: important, M3
                              Description
                              @zhuangjianguo
                              zhuangjianguo
                              opened on Aug 31, 2026
                              Filed unassigned by the domain:engine lane PM. Recording only — no severity asserted, routing is triage's. Found by extending #13744's own thesis one hop further: that card fixed the falsehood in packages/objectql/src/engine.ts, #13984 records it in search-companion.ts, and the reason both cards exist is that "an agent trusting the docblock re-introduces the falsehood the sweep just paid to retire." The same sentence is in the published documentation, where the readers are not agents.
                              Measured on origin/main at 47389b35de. Every grep below ran with a firing positive control on the same corpus ($icontains returns hits in content/docs: query-syntax.mdx 12, troubleshooting.mdx 3, filter.mdx 2, releases/v17.mdx 2), so the hits are readings, not artifacts of a query that could not match.
                              What the implementation actually does
                              packages/objectql/src/search-filter.ts:23 — "[#7641] The case-insensitive operator is $icontains, NOT $contains." Source columns compile to $icontains. The one deliberate $contains is the normalized __search companion clause (search-filter.ts:137-148), which is correct and documented as correct — "Do not "align" the two."
                              The six published sites
                              A. Hand-written, same two false sentences #13744 just fixed in code
                              content/docs/protocol/objectql/query-syntax.mdx:970-973:
                              The engine expands it into an $or of $contains predicates across the object's server-resolved searchable fields (ADR-0061) and deletes search from the AST before the driver sees it — every driver already runs $or/$contains, so no driver support is needed
                              ⇒ Structurally identical to the engine.ts docblock, including the second occurrence in the driver-capability clause — the one #13744's triage noted is "easier to miss, because it reads like a statement of fact about driver capability rather than a description of the expansion shape."
                              Also: content/docs/data-modeling/queries.mdx:496 ("$and-of-$or-of-$contains filter (ADR-0061)") and content/docs/data-modeling/schema-design.mdx:132-133 ("?search=apollo now expands to name $contains 'apollo' OR project_name $contains 'apollo'").
                              B. ⚠️ The one that is worse than a stale spelling
                              content/docs/protocol/objectql/query-syntax.mdx:~1026, inside a callout:
                              Whether the expansion should emit $icontains instead of $contains — i.e. whether search is case-insensitive by definition — remains a separate open question, and one that can now actually be answered, since both operators mean one thing everywhere.
                              It does not remain open.#7641 answered it, search-filter.ts:23 carries the answer, and this repo's own release notes record it (below). ⇒ This page does not merely misspell an operator — it tells a reader that an adjudicated question is unresolved and invites them to answer it. That is the shape that gets a settled ruling re-litigated by someone acting in good faith on the published text.
                              C. Four AUTO-GENERATED rows — ⛔ do not hand-edit these
                              content/docs/references/data/driver.mdx:51 and :105, driver-sql.mdx:97, driver-nosql.mdx:183, all carrying:
                              $search is compiled by the engine into an $or of $contains predicates over the searchable fields (ADR-0061)
                              These pages carry {/* ⚠️ AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. */} and name their source: packages/spec/src/data/driver.zod.ts.
                              ⚠️ Two consequences whoever takes this must not discover late:
                              1. The fix lands in the .describe() string in the spec, then regenerates — ⛔ not in the .mdx. (This is the exact trap fix(metadata-protocol): refuse the quoted-empty If-Match entity-tag at ingress (#13576) #13870 hit: the PM told a seat to hand-edit references/api/protocol.mdx, and the seat correctly found the generated source instead. The hand edit would have been wiped by the next gen:docs.)
                              2. ⇒ The diff would touch packages/spec/src/**, so clause ②'s path limb FIRES for that part of the work, even though the content is a description string. Sites A and B alone would not.
                              The docs already contradict each other, and the right answer is already published
                              content/docs/releases/v17.mdx:3186:
                              like / ilike stop being folded onto $contains at the wire (#7536), and $search compiles to $icontains so textual search is actually case-insensitive.
                              ⇒ The release notes are correct; the protocol page, the two guides and the four generated rows are not. ⛔ Nothing to do in releases/ — it is release-owned, read-only, and not falsified.
                              What this does NOT claim
                              ⚠️ Routing — the anchor is genuinely split, so I am not guessing it
                              Sites A and B land in content/docs/** (hand-written); site C lands in packages/spec/src/data/driver.zod.ts. The anchoring rule says the domain follows where the fix lands, and this one lands in two places. ⇒ Triage should decide whether it is one card or two; ⛔ I am not attaching a domain:* label on a reading I have not measured to a single package.
                              Refs: #13744 (the engine.ts half, landing now) · #13984 (search-companion.ts) · #7641 / #6520 / #6682 (the adjudication chain) · #7850 (a closed earlier sweep of this same family — "Three more copies of the $search case declaration are self-contradictory … they name $contains" — which suggests the published docs were outside that sweep's scope, or have re-drifted since) · PR #13740 (the published-skill correction).
                              Metadata
                              Metadata
                              Assignees
                              No one assigned
                                Labels
                                documentationImprovements or additions to documentationdomain:specfindingpm:queuepriority:p2Medium: important, M3
                                Type
                                No type
                                Projects
                                No projects
                                  Milestone
                                  No milestone
                                  Relationships
                                  None yet
                                  Development
                                  No branches or pull requests
                                  Issue actions