… range support

A new :date-range property type lets users attach temporal metadata at
varying granularities — a full year ("2026"), a month ("May 2026"), or a
specific day ("May 13, 2026") — and optionally pair any two of those into
a start/end range.

Storage
-------
Each value is a lightweight DataScript entity (no :block/uuid) with three
new schema attributes:
  :logseq.property.date/precision  — keyword :year | :month | :day
  :logseq.property.date/start      — YYYYMMDD integer
  :logseq.property.date/end        — YYYYMMDD integer (absent for single-point dates)

The entity type is identified in malli_schema/entity-dispatch-key by the
presence of :logseq.property.date/precision, and validated by the new
date-range-value malli schema.

Type system changes
-------------------
  • :date-range added to user-built-in-property-types (after :date in UI order)
  • :date-range added to cardinality-property-types (supports :many)
  • :date-range added to user-ref-property-types (value stored as DB ref)
  • date-range? predicate added to built-in-validation-schemas
  • :date-range added to property-types-with-db (validation needs DB)
  • "logseq.property.date" added to logseq-property-namespaces

UI
--
  • New frontend.components.date-range-picker namespace with:
      - format-label  — human-readable display string
      - year-picker   — ‹ year › navigation
      - month-grid    — 4×3 month grid with year navigation
      - day-calendar  — delegates to existing ui/nlp-calendar
      - endpoint-picker  — single-date picker (switches on precision)
      - date-range-picker-inner — full popup with precision chips and
                                  "Add end" / "Single date" toggle
  • date-range-picker-trigger wired into property-value-date-picker
  • <find-or-create-date-range-entity! handles entity dedup/creation
  • property.cljs and value.css updated to treat :date-range like :date
    (inline layout, cursor-pointer, calendar-range icon)
  • en.edn: :property/type-date-range "Date range"
  • property/config.cljs: property-type-label case for :date-range

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Year-precision start values were stored as yyyy0101 and month-precision
as yyyymm01, requiring the sort code to compensate. Store them directly
in the canonical form (yyyy0000, yyyymm00) so sort keys equal stored
values, and simplify view.cljs sort-val accordingly. Update all tests
to match the new storage format.

- Add precision-from-int helper; derive display format from the integer
  encoding (yyyy0000/yyyymm00/yyyymmdd) so :precision key is no longer
  required by format-label
- Replace single ::precision atom with ::start-precision / ::end-precision
  so start and end dates can have independent Year/Month/Day precision;
  each endpoint column now has its own precision-button row
- set-start-precision! / set-end-precision! adjust the draft integer to
  the new precision and update the text box immediately (fix for month
  switch from year: use (max m 1) to avoid collapsing to yyyy0000 format)
- endpoint-picker uses fixed height: 330px (not min-height) so the
  pop-over never resizes when switching precision or toggling range mode
- Start label kept in DOM via visibility:hidden when not in range mode,
  preventing height drop on "Remove end"
- Live-parse on-change: fix prev-text sentinel so clearing the box when
  the picker opens onto an existing range correctly collapses range mode;
  restore " -" → show end calendar behaviour (blank p2 no longer hides it)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>