mirror of
https://github.com/cpvalente/ontime.git
synced 2026-08-12 10:53:51 +00:00
Claude
fc8819cea6
The demo had automations empty and switched off, so the feature stayed invisible to exactly the users most likely to be exploring. It was also inconsistent with the blank project default, where automations are on. Three automations, none of which touch the network. Two fire: an aux timer that runs with the event, on a global trigger, and a wrap-up message on an event level trigger, which is the only way per-event triggers get found by browsing rather than by reading the docs. The third is a fully formed OSC example with no trigger attached at all, so there is something realistic to read and edit without anything being sent anywhere. OSC input stays off: never open a listening socket the user did not ask for. The ids are hand written literals and nothing in the type system checks that a trigger resolves to an automation, so a test covers that, along with the promise that nothing bound to a trigger can reach off this machine. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LpbLJVVT26tzWkduck1M9H