Scott Werner e87130ae23 Require a server-managed environment for automations ... Automations now store an environment_id that must reference an enabled Docker or Daytona environment. Each trigger fire resolves the current environment definition and snapshots its settings into the run, and deleting an environment still referenced by an automation is rejected with a conflict. Existing automations are backfilled conservatively: a compatible environment named default is selected when present, otherwise the sole compatible environment. Anything ambiguous is left incomplete and cannot run until an operator selects an environment in the web UI. Scheduler failures are recorded on the automation as last_error and cleared after the next successful scheduled run. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>		2026-08-30 09:58:13 -04:00
..
client-sdks.mdx	refactor: organize crates into three layers	2026-07-23 17:59:34 -04:00
fabro-api.yaml	Require a server-managed environment for automations	2026-08-30 09:58:13 -04:00
overview.mdx	docs: refresh product documentation	2026-08-24 09:53:09 -04:00