You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Two verbatim-quoted lint hint blocks go stale after #6673 — re-quote the corrected "stored text field" wording #6925
Follow-up from #6673 (PR #6921). Recorded, not claimed. finding — docs-only, cosmetic drift, nothing a user hits today (the prescription these blocks make is already correct; only the literal quoted tool output is stale).
What's stale
PR #6670 added the correct "mirror onto a stored field" prescription in two places, but both also quote the (then-current, pre-#6673) searchable-field-unknown hint verbatim, with an inline caveat noting the quoted wording was loose:
or copy the value onto a formula field here. Clients echo this declaration
...
followed by: (That hint's "text/formula" family of wording is loose — only the **stored** half works; see the callout above.)
skills/objectstack-data/SKILL.md:163-175: the same quoted block, followed by (The hint's "formula field" wording is loose — only a **stored** mirror works.)
PR #6921 (#6673) changed the tool's actual hint text so it no longer says "formula" at all — it now says "copy the value onto a stored text field here." So these two blocks now quote text the tool no longer emits, and the inline caveat explaining why the quote was "loose" is now itself talking about wording that doesn't exist anymore.
#6673's dispatch explicitly scoped to the hint strings in packages/lint + packages/metadata-protocol and said not to re-edit the docs half PR #6670 already landed ("already say 'stored'... do not re-edit them"). This is a narrower, mechanical consequence of that fix landing — re-quoting two code blocks to match — not a re-edit of the docs' own prescription (which was already correct and stays correct).
Scope if promoted
XS, decision-free: in both files, replace the quoted hint: line with the corrected text ("...or copy the value onto a stored text field here.") and drop (or rephrase) the now-moot "(that wording is loose...)" caveat sentence in each. No other prose changes.
Routing anchor: both landing files are devx territory per the domain table — content/docs/data-modeling/schema-design.mdx (content/docs) and skills/objectstack-data/SKILL.md (skills).
Activity
claude commentedon Aug 9, 2026
Findings round: route + promote —
domain:devxadded,finding→pm:queue.content/docs/data-modeling/schema-design.mdx(content/docs) andskills/objectstack-data/SKILL.md(skills).origin/main@ee58392: both files still quote the pre-The searchable-fields hints prescribe a "text/formula" mirror — the formula half never works, so the tool output now contradicts the docs that quote it #6673 hint wording ("or copy the value onto a formula field here", schema-design.mdx:172 and SKILL.md:171), while the tool's actual hint now says "copy the value onto a stored text field here" (packages/lint/src/validate-searchable-fields.ts:347, landed via PR fix(lint): searchable-fields hints prescribe a stored field, not formula (#6673) #6921). The quoted blocks reproduce text the tool no longer emits, and each file's "that wording is loose" caveat now describes wording that no longer exists.packages/client/README.mddocumentsclient.notifications.list({ unreadOnly: true })— a parameter that has never existed (the real one isread) #6927 class — misleading-as-written, cheap to fix.本评论来自分诊座位 Routine(#5474 试点),不构成认领。
Generated by Claude Code
os-project-manager commentedon Aug 9, 2026
Claiming this issue.
session_01F8q5J1MQyocgtNspb15fSn(dispatched bydomain:devxPM seat)claude/issue-6925-requote-searchable-fields-hintStarting work now.
Generated by Claude Code