feat(scenes): daily schedule triggers (scheduled scenes fire directly)

[mohabbis]

Summary

Implements Tier 1.2 of docs/competitive-feature-scope.md — time/schedule triggers for scenes, the most-requested automation a geofence-only model couldn't express (Home Assistant's #1 automation type).

Consent decision (yours, now logged in ROADMAP.md): scheduled scenes fire directly. Setting a scene to run at a set time is itself ahead-of-time, explicit consent — categorically different from the forbidden "auto-apply on a hunch," where Lumen infers intent. Inferred SuggestionEngine suggestions remain confirmation-gated. Every scheduled fire posts a notification for explainability/reversibility, and a grace window means a missed schedule never fires stale hours later.

What's in it

Area	Change
Domain/Models/Automation/Scene.swift	scheduleMinutesSinceMidnight: Int? (nullable → inferred lightweight migration, no schema-version bump, like Home.latitude) + scheduledTime helper
Services/Scene/ScheduleTiming.swift	Pure, calendar-injectable due-logic: fires within a grace window, never twice the same day, midnight-safe
Services/Scene/SceneService.swift	scheduleTask poller (30 s tick) → fires due scenes via the existing execute(_:) path + notification; pure scenesDue(...) routing; setSchedule(...) CRUD
Services/NotificationService.swift	"schedule" case — "… ran on schedule — you set this up. Tap to adjust."
Features/Scenes/SceneDetailView.swift	Schedule card (toggle + DatePicker) in the automation section, guarded so onAppear sync doesn't spuriously re-save
Features/RootView.swift	Starts the schedule poller next to the geofence poller
LumenTests/ScheduleTests.swift	ScheduleTiming due-logic + SceneService.scenesDue routing
ROADMAP.md	Decision log entry for the fire-directly choice

Design notes

• Mirrors the existing geofence-trigger pattern exactly: a poller + a pure routing function + a notification — geofence-triggered scenes already fired directly on a pre-authorized trigger.
• The grace window (default 120 s) keeps firing calm: a scheduled scene runs close to its time or not at all — opening the app hours later won't trigger a stale run.
• In-app poller only (like the geofence poller). True background firing via BGTaskScheduler/UNCalendarNotificationTrigger is a follow-up.

Verification

Can't compile Swift on Linux (macOS/Xcode only, per CLAUDE.md); the due-logic and routing are covered by ScheduleTests, and the surfaces mirror the proven geofence lane. Web CI test job unaffected (Swift + docs only).

Tier 1 status

With this, both Tier-1 competitive gaps are closed: non-HomeKit LAN device control (#75/#76) and rich automation triggers (this PR).

🤖 Generated with Claude Code

---

Generated by Claude Code

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
lumen-idpz	Ready	Preview, Comment	Jul 14, 2026 3:12pm

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.