ld-morning-updates

Read upcoming events with the plow-gog calendar CLI, compose a message of 115 characters or fewer anchored in a specific family event, write it to the fixed handoff file, then run the post_message.py helper which delivers it to the kiosk endpoint.

Keep the command argv byte-identical on every run so Latch always-allow rules match it, and use relative flags like --days=3 instead of computed dates. Avoid shell wrappers, heredocs, or interpreter one-liners since cron runs have no user to approve flagged commands.

Yes, one plow-gog call covers every source by comma-joining all calendar_id values under a single account. Each calendar is addressed by its globally-unique id, and including shared family calendars is required so their events appear in the kiosk message.

Latch injects its own safety flags and refuses any caller-supplied duplicates, so adding --readonly or --wrap-untrusted makes every run fail before it starts. Pass only the exact documented argv with config-supplied account and calendar values.

The skill skips the calendar read for that run and composes the affirmation from an abstract fallback instead. The message still posts to the kiosk, just without event-specific grounding.

The post_message.py helper reads the endpoint from DASHBOARD_ENDPOINT_URL and the token from DASHBOARD_TOKEN environment variables loaded from a mode-600 .env file. Credentials never appear in argv, and the handoff file path is fixed so injected input cannot steer the post.