feat(cli): lint the record-change date-equality time anti-pattern at build (#1874)

[os-zhuang]

Refs #1874.

Framing: this targets the core problem, not the literal feature

The templates are AI-authored, and preventing AI authoring mistakes is the project's core goal. The robust capability for time-relative rules already exists (daily SCHEDULE trigger + range query), so the high-leverage fix for "renewal_alert never fires" is not a new trigger primitive — it's a build-time guardrail that catches the exact mistake the author (AI or human) keeps making, in the same "make silently-wrong metadata loud at build" vein as #1877 / #1870 / #1876.

What it does

objectstack build now emits an advisory WARNING when a record-* flow's start condition compares a date field for EQUALITY against a time function:

end_date == daysFromNow(60)      // ⚠ only fires if the record is written on that exact day
today() != record.start_date

…and points the author at the robust shape: a daily schedule trigger + a range query (get_record where end_date BETWEEN {TODAY()} and {TODAY()+N}).

Precision (low false-positive by design)

• Flags: equality (==/!=) adjacent to daysFromNow/daysAgo/today/now/date/datetime, either side, on record-* triggers; string or Expression-envelope conditions.
• Does NOT flag: range comparisons (>=/<= — the correct building block), non-time-field equality, or schedule-trigger conditions.
• Never fails the build — advisory only (mirrors the dashboard widget-binding warnings). Guides without breaking technically-legal metadata.

Tests

New lint-flow-patterns.ts + 7 unit tests (both equality forms, envelope condition; range/non-time/schedule false-positive guards). @objectstack/cli suite 383 pass; example builds clean (no spurious warnings).

Scope note

This does not implement #1874's declarative time-relative trigger (a future DX feature needing real API design — multi-threshold windows, per-record fan-out, indexed queries for scale, Studio authoring), nor the cross-repo template fixes. It's the AI-authoring guardrail, which is the part that pays off now.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
spec	Ready	Preview, Comment	Jun 15, 2026 3:11pm

[github-actions]

📓 Docs Drift Check

This PR changes 1 package(s): @objectstack/cli.

15 hand-written doc(s) reference the affected code and may need an implementation-accuracy re-verification:

• content/docs/concepts/cloud-artifact-api.mdx (via packages/cli)
• content/docs/concepts/implementation-status.mdx (via @objectstack/cli)
• content/docs/concepts/packages.mdx (via @objectstack/cli)
• content/docs/getting-started/cli.mdx (via @objectstack/cli)
• content/docs/getting-started/quick-start.mdx (via @objectstack/cli)
• content/docs/guides/authentication.mdx (via @objectstack/cli)
• content/docs/guides/client-sdk.mdx (via @objectstack/cli)
• content/docs/guides/hook-bodies.mdx (via packages/cli)
• content/docs/guides/packages.mdx (via @objectstack/cli)
• content/docs/guides/project-scoping.mdx (via @objectstack/cli)
• content/docs/guides/runtime-services/data-service.mdx (via packages/cli)
• content/docs/guides/runtime-services/index.mdx (via packages/cli)
• content/docs/guides/skills.mdx (via packages/cli)
• content/docs/protocol/objectos/plugin-spec.mdx (via @objectstack/cli)
• content/docs/protocol/objectos/realtime-protocol.mdx (via @objectstack/cli)

Advisory only. To re-verify, run the docs-accuracy-audit workflow scoped to these files:
node scripts/docs-audit/affected-docs.mjs origin/main → pass the list as args.docs.