docs(references): regenerate automation reference for TimeRelativeTrigger (#1874)

Auto-generated from the new TimeRelativeTriggerSchema (packages/spec).
content/docs/references/ is generated by build-docs.ts and gated by the
`check:docs` CI job — this adds the missing automation/time-relative-trigger.mdx
and updates the automation index/meta.

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

Author: claude

content/docs/references/automation/index.mdx

@@ -15,6 +15,7 @@ This section contains all protocol schemas for the automation layer of ObjectSta
   <Card href="/docs/references/automation/node-executor" title="Node Executor" description="Source: packages/spec/src/automation/node-executor.zod.ts" />
   <Card href="/docs/references/automation/state-machine" title="State Machine" description="Source: packages/spec/src/automation/state-machine.zod.ts" />
   <Card href="/docs/references/automation/sync" title="Sync" description="Source: packages/spec/src/automation/sync.zod.ts" />
+  <Card href="/docs/references/automation/time-relative-trigger" title="Time Relative Trigger" description="Source: packages/spec/src/automation/time-relative-trigger.zod.ts" />
   <Card href="/docs/references/automation/trigger-registry" title="Trigger Registry" description="Source: packages/spec/src/automation/trigger-registry.zod.ts" />
   <Card href="/docs/references/automation/webhook" title="Webhook" description="Source: packages/spec/src/automation/webhook.zod.ts" />
 </Cards>

content/docs/references/automation/meta.json

@@ -13,6 +13,7 @@
     "offline",
     "state-machine",
     "sync",
+    "time-relative-trigger",
     "trigger-registry",
     "webhook"
   ]

content/docs/references/automation/time-relative-trigger.mdx

@@ -0,0 +1,129 @@
+---
+title: Time Relative Trigger
+description: Time Relative Trigger protocol schemas
+---
+
+{/* ⚠️  AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs live in the module folders under content/docs/. */}
+
+Time-Relative Trigger Protocol
+
+A **declarative** trigger for time-relative business rules — "act on records
+
+whose date field is coming up (or overdue) relative to today" — without the
+
+author hand-writing a cron job + range query, and without the fragile
+
+date-equality-on-record-change anti-pattern (#1874).
+
+## The anti-pattern it replaces
+
+Authors used to express "alert 60 days before `end_date`" as a `record_change`
+
+flow gated on `end_date == daysFromNow(60)`. That predicate is only evaluated
+
+when the record *happens to change*, so it fires only if the record is edited
+
+on exactly that day — i.e. almost never, unattended. The robust alternative
+
+was a hand-written `schedule` flow that queries a date range every day, which
+
+every author re-implemented (contracts `renewal_alert`, hr
+
+`document_expiring_soon`, procurement `po_overdue`, …).
+
+## What this declares instead
+
+A `time_relative` trigger sweeps an object on a schedule (daily by default)
+
+and launches the flow **once per matching record**, with that record in the
+
+automation context (so `\{record.<field>\}` interpolation and the start-node
+
+`condition` gate work exactly as they do for record-change flows). The
+
+descriptor is carried on the flow's start node as `config.timeRelative`.
+
+@example T-minus renewal reminders (fires on the day a contract is 60/30/7 days out)
+
+```ts
+
+// flow start node
+
+config: \{
+
+timeRelative: \{
+
+object: 'contracts',
+
+dateField: 'end_date',
+
+offsetDays: [60, 30, 7],
+
+filter: \{ status: 'active' \},
+
+\},
+
+// optional sweep cadence — defaults to daily at 08:00 UTC
+
+schedule: \{ type: 'cron', expression: '0 8 * * *' \},
+
+\}
+
+```
+
+@example "Expiring soon" range (fires every day a document is within 30 days of expiry)
+
+```ts
+
+config: \{
+
+timeRelative: \{ object: 'hr_document', dateField: 'expires_on', withinDays: 30 \},
+
+\}
+
+```
+
+@example Overdue sweep (fires for POs up to 14 days past due)
+
+```ts
+
+config: \{
+
+timeRelative: \{ object: 'purchase_order', dateField: 'due_date', withinDays: -14, filter: \{ status: 'open' \} \},
+
+\}
+
+```
+
+<Callout type="info">
+**Source:** `packages/spec/src/automation/time-relative-trigger.zod.ts`
+</Callout>
+
+## TypeScript Usage
+
+```typescript
+import { TimeRelativeTrigger } from '@objectstack/spec/automation';
+import type { TimeRelativeTrigger } from '@objectstack/spec/automation';
+
+// Validate data
+const result = TimeRelativeTrigger.parse(data);
+```
+
+---
+
+## TimeRelativeTrigger
+
+### Properties
+
+| Property | Type | Required | Description |
+| :--- | :--- | :--- | :--- |
+| **object** | `string` | ✅ | Object (machine name) to sweep, e.g. "contracts". |
+| **dateField** | `string` | ✅ | Date or datetime field evaluated relative to today, e.g. "end_date". |
+| **withinDays** | `integer` | optional | Range mode: fire while dateField is within N days of today. Positive = upcoming, negative = overdue lookback, 0 = today. |
+| **offsetDays** | `integer[]` | optional | Offset mode: fire when dateField is exactly today + each offset (e.g. [60, 30, 7]). |
+| **filter** | `Record<string, any>` | optional | Extra ObjectQL where-map ANDed with the date window (e.g. `{ status: "active" }`). |
+| **maxRecords** | `integer` | optional | Max records launched per sweep (default 1000). The sweep logs when it clamps. |
+
+
+---
+