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:
-
content/docs/data-modeling/schema-design.mdx:163-175:
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.
Why not fixed in #6673 directly
#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.
Refs: #6673, PR #6670, PR #6921, PR #6898.
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-unknownhint verbatim, with an inline caveat noting the quoted wording was loose:content/docs/data-modeling/schema-design.mdx:163-175: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.
Why not fixed in #6673 directly
#6673's dispatch explicitly scoped to the hint strings in
packages/lint+packages/metadata-protocoland 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.Refs: #6673, PR #6670, PR #6921, PR #6898.