docs(spec): the filter-preset-ordering-comparand-refused entry's replacement names the closed last_30_days window; the changeset carries lint and verify

Claude-Session: https://claude.ai/code/session_012uFegdfR6K6uqvLzt7XsdZ
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

.changeset/23170-rolling-presets-close-on-today.md

@@ -1,6 +1,8 @@
 ---
 '@objectstack/spec': patch
 '@objectstack/core': patch
+'@objectstack/lint': patch
+'@objectstack/verify': patch
 ---
 
 fix(spec,core): the rolling `last_7_days`, `last_30_days` and `last_90_days` presets close on today, at the spec's prescription table, the save door's refusal and the analytics preset arm
@@ -12,5 +14,6 @@ The three rolling windows were the open arm of `DATE_RANGE_PRESET_MACRO_WINDOWS`
 - `DATE_RANGE_PRESET_MACRO_WINDOWS` now closes every rolling window on `{today}`: `last_7_days` is `['{7_days_ago}', '{today}']`, and `last_30_days` and `last_90_days` follow the same shape. That is the inclusive last-day end every calendar preset already uses, and the extent the console's lowering already selects. The table's declared type narrows to match, `readonly [start: string, end: string]` (it was `end: string | null`). A reader that compared `end` with `null` still compiles; that branch can no longer be taken.
 - The save door's refusal of a bare preset comparand (`bareDateRangePresetComparandMessage`, and the `filter-preset-comparand` lint verdict that quotes it) now prescribes the closed window. For `last_30_days` it says: write `{ $between: ['{30_days_ago}', '{today}'] }`, where it used to say `{ $gte: '{30_days_ago}' }`.
 - `@objectstack/core`'s `resolveAnalyticsDateRangePreset`, the preset arm behind `timeDimensions[].dateRange`, selects the same extent. A rolling window now stops before tomorrow begins in the reference timezone, exactly as `today` does, with `endExclusive: true`. It used to end at the reference instant, so it dropped rows stamped later today. Its ends keep this module's own "the day the window stops before" spelling (`tomorrow`). Every preset this resolver returns is now `endExclusive: true`, and a caller's explicit `[a, b]` window keeps its inclusive reading, as before.
+- The semantic migration entry `filter-preset-ordering-comparand-refused`, which `spec-changes.json` and `os migrate meta` carry, now names `{ $between: ["{30_days_ago}", "{today}"] }` as the window for `last_30_days` in its replacement, where it named `{ $gte: "{30_days_ago}" }`.
 
 If you followed the old refusal and authored `{ $gte: '{N_days_ago}' }` for a rolling preset, add `$lte: '{today}'`, or write the `$between` pair above, to stop counting future-dated rows.

packages/spec/src/migrations/entries/semantic/18.filter-preset-ordering-comparand-refused.ts

@@ -28,7 +28,7 @@ export const entry: SemanticMigration = {
     + 'flow CRUD node\'s config.filter). The lint is likewise what refuses a preset in an '
     + 'ordering filter triple wherever its walk meets one',
   replacement:
-    'the date-macro window the preset already means — { $gte: "{30_days_ago}" } for '
+    'the date-macro window the preset already means — { $between: ["{30_days_ago}", "{today}"] } for '
     + 'last_30_days, { $between: ["{week_start}", "{week_end}"] } for this_week, and so on '
     + '(the rejection names the exact window per preset; DATE_RANGE_PRESET_MACRO_WINDOWS in '
     + '@objectstack/spec/data is the table) — or an ISO date such as 2026-01-15. The preset '