docs(lint,spec): describe the field-typed arm at the registration and in the shared message's TSDoc

The rule's registration comment said it needs no resolution context; arm 2
reads the stack's objects and datasets when present. The shared refusal
wording's TSDoc said "ordering comparand"; it is now also the wording for the
field-typed equality/membership positions. The TSDoc publishes in dist/*.d.ts
(measured), so the spec change carries a patch changeset.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01T6HeZvT9wdSJD1ZxJb5Eno

Author: claude

.changeset/spec-preset-comparand-message-tsdoc.md

@@ -0,0 +1,5 @@
+---
+'@objectstack/spec': patch
+---
+
+`bareDateRangePresetComparandMessage`'s TSDoc — published in `dist/*.d.ts` — now states both moments the wording is reported at: the field-agnostic schema door in `data/filter.zod.ts` (ordering positions only: without a field type, equality on a select column is legitimate) and `@objectstack/lint`'s `filter-preset-comparand` rule, which with the field type in hand refuses every comparand position on a declared `date` / `datetime` field (#16106). The message text itself is unchanged.

packages/lint/src/authoring-rules.ts

@@ -607,13 +607,17 @@ export const AUTHORING_RULES: readonly AuthoringRule[] = [
   // no layer: the engine refuses it on a declared temporal field at query time
   // (INVALID_FILTER / 400, PR #8808), and anywhere else it compares as a
   // literal string. This is the authoring-time refusal the ruling shipped
-  // alongside the engine door, judging the filter literal in isolation —
-  // ordering positions only, all three authored filter shapes. Like
-  // `validateEmptyCombinators` it needs NO resolution context, so
-  // RUNTIME_NEEDS_FULL_SNAPSHOT does not apply and the runtime gate runs it
-  // for every filter-carrying type the gate already maps: the write path is
-  // the one door an AI author uses, and dashboards/views are where the preset
-  // vocabulary is near enough to reach for.
+  // alongside the engine door. Two arms (the rule's header is the authority):
+  // arm 1 judges the filter literal in isolation — ordering positions only,
+  // all three authored filter shapes, no resolution context; arm 2 (#16106,
+  // maintainer-ruled 1′) judges equality / membership positions WITH the field
+  // type in hand, read from the stack's own `objects` (and `datasets`, to bind
+  // a widget or report) — both collections the per-write snapshot carries —
+  // and stays silent wherever they are absent. So RUNTIME_NEEDS_FULL_SNAPSHOT
+  // still does not apply and the runtime gate runs it for every
+  // filter-carrying type the gate already maps: the write path is the one door
+  // an AI author uses, and dashboards/views are where the preset vocabulary is
+  // near enough to reach for.
   {
     name: 'validatePresetComparands',
     tier: 'gating',

packages/spec/src/data/date-range-presets.ts

@@ -99,10 +99,14 @@ export const DATE_RANGE_PRESET_MACRO_WINDOWS: Readonly<
 
 /**
  * The one refusal wording for "a declared preset name authored as a bare
- * ordering comparand", shared by the two moments it can be reported — the
- * schema door in `data/filter.zod.ts` and `@objectstack/lint`'s
- * `filter-preset-comparand` rule — so one condition keeps one wording
- * (the #5240 convention).
+ * filter comparand", shared by the moments it can be reported — the
+ * field-agnostic schema door in `data/filter.zod.ts` (ordering positions
+ * only: without a field type, equality on a select column is legitimate) and
+ * `@objectstack/lint`'s `filter-preset-comparand` rule (the same ordering
+ * positions, plus — with the field type in hand — EVERY comparand position on
+ * a declared `date` / `datetime` field: bare, `$eq` / `$ne`, `$in` / `$nin`
+ * and their view-rule and triple spellings; #16106, maintainer-ruled 1′) — so
+ * one condition keeps one wording (the #5240 convention).
  *
  * Why this is refused at all (#8690, C half, maintainer-ruled 2026-08-15):
  * `last_30_days` and its siblings are REAL declared names — but only for the