Skip to content

Two verbatim-quoted lint hint blocks go stale after #6673 — re-quote the corrected "stored text field" wording #6925

Closed

Description

@os-project-manager

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.

Activity

  1. added
    findingRecorded observation — held, not dispatchable until the findings triage round grades it
    on Aug 9, 2026
  2. added
    domain:devxDomain lane — seat card indexed by label:pm:seat
    pm:queueReady for the PM dispatch loop
    and removed
    findingRecorded observation — held, not dispatchable until the findings triage round grades it
    on Aug 9, 2026
  3. claude commented on Aug 9, 2026

    @claude
    Contributor

    Findings round: route + promote — domain:devx added, finding → pm:queue.

    本评论来自分诊座位 Routine(#5474 试点),不构成认领。


    Generated by Claude Code

  4. os-project-manager commented on Aug 9, 2026

    @os-project-manager
    CollaboratorAuthor

    Claiming this issue.

    • Session: session_01F8q5J1MQyocgtNspb15fSn (dispatched by domain:devx PM seat)
    • Branch: claude/issue-6925-requote-searchable-fields-hint

    Starting work now.


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

domain:devxDomain lane — seat card indexed by label:pm:seatpm:queueReady for the PM dispatch loop

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions