feat(backend): filter disabled workflows from OOTB listing

[jeremyeder]

Summary

• Workflows with "enabled": false in their .ambient/ambient.json are now completely excluded from the /api/workflows/ootb response
• Previously all discovered workflows were returned with enabled: true regardless of their config
• Field is optional — omitting it or setting "enabled": true preserves current behavior (backward compatible)

Test plan

• Deploy backend, verify workflows without enabled field still appear
• Set "enabled": false on a workflow's ambient.json, verify it no longer appears in API response or UI
• Set "enabled": true explicitly, verify it still appears

🤖 Generated with Claude Code

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: e53f1d12-228a-4c8e-b9f5-1a1ae0380e82

📥 Commits

Reviewing files that changed from the base of the PR and between 9ca8168 and c5251e1.

📒 Files selected for processing (1)

• components/backend/handlers/sessions.go

---

Walkthrough

The ListOOTBWorkflows handler in the sessions module now supports an optional enabled field in the ambient workflow configuration. When the field is explicitly set to false, the workflow is excluded from the returned list; otherwise, the existing behavior is maintained.

Changes

Cohort / File(s)	Summary
Ambient Workflow Configuration components/backend/handlers/sessions.go	Added optional enabled field (*bool with omitempty) to ambient config parsing. Logic now checks if enabled is explicitly false and skips adding the workflow entry to the list when that condition is met.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'feat(backend): filter disabled workflows from OOTB listing' accurately summarizes the main change: filtering out workflows marked as disabled from the OOTB workflow list.
Description check	✅ Passed	The description directly relates to the changeset by explaining the new filtering behavior for disabled workflows, the backward compatibility of the optional field, and providing a clear test plan.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}