lsm / neokai / 25411292878

64%

push

github

Add ability to disable workflows (#1802)

* Add ability to disable workflows

- Add `disabled` boolean field to SpaceWorkflow model and DB schema
- Add migration 117 to add `disabled` column to existing databases
- Update repository to persist and read `disabled` field
- Filter disabled workflows from runtime selection (resolveWorkflowForRun,
  attachStandaloneTasksToWorkflows, preferredWorkflowId fallback)
- Thread `disabled` through export/import bundle format
- Add disabled toggle checkbox to visual workflow editor
- Show "Disabled" badge and greyed-out styling in workflow list
- Update serialization layer to preserve disabled state

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Fix review: preserve disabled flag through import pipeline

- Add `disabled: z.boolean().optional()` to `exportedWorkflowBaseSchema`
  so validation no longer strips the field on import.
- Add export→import round-trip test verifying a disabled workflow
  stays disabled after re-import.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Fix review: block disabled workflows from all start paths

- Add defense-in-depth check in SpaceRuntime.startWorkflowRun() rejecting
  disabled workflows with a clear error message.
- Filter disabled workflows from spaceWorkflowRun.start auto-select path.
- Reject explicit disabled workflowId in spaceWorkflowRun.start.
- Reject disabled target workflow in change_plan agent tool.
- Filter disabled workflows from suggest_workflow agent tool.
- Include `disabled` field in list_space_workflows MCP tool response.
- Add tests for RPC start and change_plan with disabled workflows.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

* Add defense-in-depth test for startWorkflowRun with disabled workflow

Adds a test verifying SpaceRuntime.startWorkflowRun() rejects
workflows marked as disabled.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

8041 of 11158 branches covered (72.06%)

Branch coverage included in aggregate %.

41 of 43 new or added lines in 10 files covered. (95.35%)

64708 of 90508 relevant lines covered (71.49%)

250.85 hits per line