Skip to content

[finding] data-service.mdx quotes the pre-#6795 "recommended interface" sentence verbatim — stale after #6795's convergence edit #7002

Description

@os-project-manager

Spun out of #6795 (PR TBD) at implementation time — filed unassigned per that card's boundaries (packages/client was the only face in scope there; docs pages are explicitly out of it).

The fact, measured

content/docs/kernel/runtime-services/data-service.mdx quotes QueryOptionsV2's JSDoc self-description verbatim, twice, attributed to the canonical source:

  • line 60: the Canonical source still names \QueryOptionsV2` "the recommended interface for `data.find()` queries"`
  • line 101: \QueryOptionsV2` is "canonical query options using Spec protocol field names … the recommended interface for `data.find()` queries"`

#6795's convergence edit (maintainer ruling, Option A, 2026-08-09) reworded that JSDoc — packages/client/src/index.ts:164 no longer says "the recommended interface for data.find() queries"; it now says QueryOptionsV2 is "the vocabulary data.find() still accepts" and is not a recommendation. The two quotes above are therefore no longer verbatim quotes of the source they cite — same class of defect as #6925 ("Two verbatim-quoted lint hint blocks go stale after #6673 — re-quote the corrected wording"), just on a different pair of files.

Why this isn't in #6795's PR

#6795's dispatch scoped the face to packages/client + .changeset/, with docs pages explicitly called out as belonging to a separate card (two other lanes — #6923, #6893 — were working scripts//docs-drift tooling in parallel at the same time). Re-quoting is a small, mechanical fix, but it is still a content/docs/** edit outside that face.

Suggested fix

Re-quote both spots with the new sentence ("the vocabulary data.find() still accepts", or paraphrase without quote marks if exact-quote maintenance is a burden going forward). Low priority / mechanical — finding class, not a functional defect: nothing a user hits differently today, the page's surrounding prose already describes the tension accurately in its own words, only the literal quoted fragment is now stale.

Related

Unassigned, unlabeled — PM triage.

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions