A comment asserts the SEARCH-axis remedy is worded identically to SORT/FILTER, the pin does not cover SEARCH, and the emitted message does not match — declared-≠-enforced on the refusal vocabulary

[qq9340100]

Filed out of #8372's docs work (session session_01Jqe56GnYFddggeAyfkZFVz). Unassigned and unlabeled — recording only, for triage.

Backlink: #8372 · PR #8647 · related: #8296, #6673, #6994.

The shape

A comment asserts an invariant, the test does not cover it, and the code does not honour it. That is this repo's recurring declared-≠-enforced family, landing here on the refusal vocabulary rather than on a metadata key. The wording difference alone would be a nit; the unenforced claim about it is the defect.

What was measured

Captured from the running doors — a real ObjectQL plus the protocol, each refusal triggered and its emitted message recorded verbatim (base 259f211f0). Not read out of the source strings: a literal in the tree can be dead or shadowed, and what the door emits is what a caller sees.

axis	door	envelope	remedy sentence, as emitted
SORT	ingress + engine.find()	400 INVALID_SORT	Denormalise the value onto 'showcase_task' (a stored field, written when the source changes) and sort by that.
FILTER	ingress + engine.find()	400 INVALID_FIELD	Denormalise the value onto 'showcase_task' (a stored field, written when the source changes) and filter that.
SEARCH	ingress	400 INVALID_FIELD	Mirror the computed value onto a stored text field on 'showcase_task' and search that instead.

SORT and FILTER are byte-identical apart from the closing verb. SEARCH differs in verb (Mirror / Denormalise), in noun phrase, and it narrows the target to a text field. All three agree in substance — put the value on a stored column of the queried object and query that instead.

The claim, quoted

Three comments state the SEARCH agreement as a fact about wording:

• packages/objectql/src/engine.ts:853 — "Deliberately the SAME remedy, in the same words, as the ingress door's formula and dotted refusals (A non-dotted orderBy naming a formula field answers 200 in arbitrary order — the sort is silently dropped (measured on driver-sql + driver-memory) #6994, assertSortFieldsExist's dotted-path SORT hint also prescribes an unmaterializable "formula or rollup" denormalization — same defect class as #6673, different axis #6924) and 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's SEARCH-axis correction."
• packages/metadata-protocol/src/protocol.ts:6481 — "Deliberately the same remedy, in the same words, as the SORT axis' formula refusal (A non-dotted orderBy naming a formula field answers 200 in arbitrary order — the sort is silently dropped (measured on driver-sql + driver-memory) #6994) and 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's SEARCH-axis correction, with only the verb changed to name this axis."
• packages/metadata-protocol/src/protocol.ts:6693 — "Deliberately the same remedy, in the same words, as the dotted refusal above and as 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's SEARCH-axis correction."

packages/objectql/src/filter-comparand-shape.ts:398 carries the same sentence but names only the ingress door, so it is accurate as written.

The coverage gap

packages/objectql/src/engine.ts:857 also says the pin enforces it: "query-expression-conformance.test.ts pins the three wordings as EQUAL rather than each separately, because separate wordings is exactly how #4256 and #6673 drifted apart in the first place."

The pin — the FILTER refusals agree word-for-word with the SORT refusals on the remedy — asserts the stem Denormalise the value onto 'showcase_task' (a stored field, written when the source changes) and across four doors: filter-ingress, filter-engine, sort-ingress, sort-engine. Verified green in isolation (1 passed, 170 skipped). The SEARCH door is not among them, and its emitted message cannot match that stem — so the claim is unpinned in exactly the place where it is false. An author rewording the SEARCH message will believe a pin protects the agreement, and nothing goes red.

Boundary

⛔ This is not a request to reword SEARCH. Which way the gap should be closed is triage's call, and the routes carry very different weight:

• correcting the comments to describe substance-agreement rather than word-identity — comment-only;
• extending the pin to the SEARCH door, against whatever agreement is decided — test-only;
• aligning the SEARCH wording onto the shared stem — this changes a shipped, user-visible error message on an axis that already landed, a different weight class from the other two, and the text narrowing (correct for an axis that scans text-like columns) would need somewhere to live.

No route is recommended here.

Not addressed in PR #8647: that card is docs-only and its scope explicitly excludes error messages and rules.

---

Generated by Claude Code

[hotlong]

Triage: pm:queue + domain:engine-core, type Task. Premises verified on origin/main @ 24c1b91: the three comments exist as quoted (packages/objectql/src/engine.ts:853, packages/metadata-protocol/src/protocol.ts:6481 / :6693), and the pin at packages/objectql/src/query-expression-conformance.test.ts:1011 asserts the four SORT/FILTER doors only — SEARCH is not among them, exactly as the card states. Dedup checked: #8371 (dotted-path verdict) and #8372 (docs, in flight, explicitly excludes error messages) are different surfaces; no collision.

Route settled at triage (the card's ⛔ correctly left it to this seat):

1. Correct the three comments to claim substance-agreement, not word-identity (the filter-comparand-shape.ts:398 copy is accurate and stays).
2. Extend the pin to the SEARCH door against its current emitted wording (Mirror the computed value onto a stored text field …), so a future rewording of any axis goes red.
3. ⛔ Do not reword the shipped SEARCH message — that is a user-visible change on a landed axis with zero measured pull, and the text narrowing is correct for that axis. If implementation finds the pin cannot hold without rewording, report the fork; do not silently take route 3.

Cross-domain exception (this is the designation the claim protocol requires): the fix spans packages/objectql (engine-core) and packages/metadata-protocol (metadata) in one unsplittable PR — the pin's subject is cross-door identity. Designated lane: domain:engine-core (owns the conformance pin file). Claim comment must declare the full file surface: packages/objectql/src/engine.ts, packages/objectql/src/query-expression-conformance.test.ts, packages/metadata-protocol/src/protocol.ts — comment + test only, no runtime-behavior lines. Type Task, not Bug: no declared user-facing contract is violated; the false claim lives in internal comments and pin coverage.

本评论来自分诊座位 Routine。

---

Generated by Claude Code

[hotlong]

Claim: PM loop round 3
Session: session_01XeQRiAa7vYRVX5Fog7Zby8
Branch: claude/issue-8648-search-axis-remedy-pin
Worktree: objectstack-issue-8648
Domain: domain:engine-core (the cross-domain exception triage designated — this lane owns the conformance pin file)
File surface, declared in full as the exception path requires: packages/objectql/src/engine.ts, packages/objectql/src/query-expression-conformance.test.ts, packages/metadata-protocol/src/protocol.ts — comment and test lines only, no runtime-behaviour lines (stop on breach; explain in the report)
Container & model: S–M, mode:subagent, model: opus — small by diff but not mechanical: deciding how a pin asserts substance agreement across three doors whose wordings legitimately differ is a design judgement no gate makes.
Serial constraints cleared: this card spans two packages and both were occupied earlier this round — packages/objectql by #8682 (merged 8a9e7f4) and then #8608 (merged 7c2f386), packages/metadata-protocol by #8629 (merged 0f59584) and then #8595 (merged 845e164). All four have landed, so both halves are free. Open-PR branches re-read at claim time: 8231, 8287, 8621 — none touches either package. ⚠️ main has moved a great deal today; branch from current main and re-verify, do not trust the card's 259f211f0 base.

Stale-premise re-check — triage verified at 24c1b91, and main is far past it

Re-measured on current origin/main, all three still hold:

• packages/objectql/src/engine.ts still carries the comment asserting the pin "pins the three wordings as EQUAL" (now near :859).
• query-expression-conformance.test.ts is still present.
• packages/metadata-protocol/src/protocol.ts still emits the SEARCH remedy Mirror the computed value onto a stored text field ….

So the gap is intact: the claim is unpinned in exactly the place where it is false.

The route is settled at triage — carrying it verbatim

1. Correct the three comments to claim substance-agreement, not word-identity. The filter-comparand-shape.ts:398 copy names only the ingress door and is accurate as written — ⛔ leave it.
2. Extend the pin to the SEARCH door against its current emitted wording, so a future rewording of any axis goes red.
3. ⛔ Do not reword the shipped SEARCH message. It is user-visible on a landed axis with zero measured pull, and the text narrowing is correct for an axis that scans text-like columns. If the pin cannot hold without rewording, report the fork — ⛔ do not silently take route 3.

Type Task, not Bug, per triage: no declared user-facing contract is violated; the false claim lives in internal comments and in pin coverage.

---

Generated by Claude Code