You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 497bda8
Browse filesBrowse the repository at this point in the historyBrowse files
feat(automation): honor flow status for enable/disable + expose runtime enable/bound state
The engine bound and ran every registered flow, ignoring the persisted `status`
— an author couldn't turn an automation off or tell whether one was live.
- registerFlow honors `status`: `obsolete`/`invalid` → disabled (trigger not
bound, execute() refuses). `draft`/`active`/legacy-no-status → enabled, so
existing flows are unaffected (zero regression). This persists the Studio's
on/off switch via the existing `status` field (applied on publish rebind); a
flip back out of a disabled status re-enables on re-register; a runtime
toggleFlow() override on a still-enabled flow is preserved.
- New getFlowRuntimeStates() + GET /api/v1/automation/_status → [{name, enabled,
bound}] for every flow — the truth behind the Studio's status badges.
Tests: draft/active bind+enable, obsolete neither binds nor enables + execute
refuses, obsolete→active re-enables+re-binds, _status route shape. Endpoint
runtime-verified on the showcase (20 flows; screen/manual flows correctly
bound:false, all enabled).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
0 commit comments