feat(platform): add activate/deactivate toggle for custom agents

[Israeltheminer]

Summary

• Add a Switch toggle component for custom agents matching the existing automation toggle pattern
• Display the toggle in both the custom agents list table and the general settings tab
• Draft agents have the toggle disabled (require full publish flow); deactivation shows a confirmation dialog

Test plan

• Verify active agents show a checked toggle in the table and settings page
• Verify archived agents show an unchecked toggle that activates on click
• Verify draft agents show a disabled toggle
• Verify deactivation shows confirmation dialog before unpublishing
• Run npm run test:ui --workspace=@tale/platform — all 235 tests pass
• Run npm run lint --workspace=@tale/platform — 0 errors

Summary by CodeRabbit

New Features

• Custom agents can now be toggled between active and inactive states from the agent table and detail pages
• Deactivating an agent requires confirmation via a dialog to prevent accidental changes
• Success and error notifications confirm the outcome of each activation or deactivation action

[coderabbitai]

📝 Walkthrough

Walkthrough

This change introduces a new CustomAgentActiveToggle component for managing the activation state of custom agents. The component includes mutation handlers for activating archived agents and deactivating active agents with confirmation dialogs. The component is integrated into the custom agents table as a new column and added to the custom agent details page under the General tab. Supporting test coverage is provided, and localized i18n strings are added for labels, dialogs, and toast notifications.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• feat: custom agents - backend, frontend, settings, webhooks, and versioning #422: The CustomAgentActiveToggle component and its integrations into the table and route are part of the broader custom agents feature implementation.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: adding an activate/deactivate toggle feature for custom agents, which is clearly the primary focus across all modified files.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

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

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/custom-agent-active-toggle

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@services/platform/app/routes/dashboard/`$id/custom-agents/$agentId/index.tsx:
- Around line 142-150: The CustomAgentActiveToggle is being passed a possibly
undefined agent from useCustomAgentVersion(), so guard rendering by checking the
agent before rendering the toggle: only render <CustomAgentActiveToggle
agent={agent} ... /> (and the helper <p>) when agent is truthy, or alternatively
render a loading/placeholder/disabled state until agent is defined; update the
JSX around CustomAgentActiveToggle and the surrounding Stack to conditionally
render based on agent (referencing the CustomAgentActiveToggle component and the
useCustomAgentVersion hook).