feat(apps): split AI tool and workflow action triggers in LogicFunction manifest (#20208)

## Summary

Replaces the bolted-on `isTool` + `toolInputSchema` fields on
`LogicFunctionManifest` with two distinct, opt-in triggers that align
with the existing `cron` / `databaseEvent` / `httpRoute` trigger
pattern:

- **`toolTriggerSettings`** — exposes the function as an AI tool (chat /
MCP / function calling). Uses standard JSON Schema (the format LLMs
natively understand).
- **`workflowActionTriggerSettings`** — exposes the function as a step
in the visual workflow builder. Uses Twenty's rich `InputSchema` so the
builder can render proper `FieldMetadataType`-aware editors, variable
pickers, labels, and an optional `outputSchema`.

A function can opt into none, one, or both. Each surface gets the schema
format appropriate for it.

### Why

`isTool: true` previously exposed the function as both an AI tool AND a
workflow node, with the same JSON Schema feeding both — but the workflow
builder really wants Twenty's `InputSchema` (with `CURRENCY`,
`RELATION`, `EMAILS`, etc.) and the AI surface really wants standard
JSON Schema. Today the workflow builder hacks around this by treating
JSON Schema as `InputSchema`, which silently breaks for any
non-primitive field type. Splitting the triggers fixes that and lets
each surface evolve independently.

### Migration

- **Fast** instance command adds the two new nullable columns.
- **Slow** instance command backfills `toolTriggerSettings` +
`workflowActionTriggerSettings` from `isTool=true` rows (preserving
today's both-surfaces behaviour) then drops the legacy columns.

### Stacked

Stacked on top of #20181. Merge that first, then this.

## Test plan

- [ ] CI green (oxlint, typecheck, jest, vitest)
- [ ] Run `--include-slow` upgrade against a workspace with existing
`isTool=true` logic functions; verify both new columns populated and old
columns dropped
- [ ] Verify AI chat sees migrated tool functions (Linear create-issue,
Exa search) and can call them with the JSON Schema
- [ ] Add an AI-tool function from the Settings UI (toggles
`toolTriggerSettings`) and verify it shows up in chat
- [ ] Add a workflow-action function from the Settings UI (toggles
`workflowActionTriggerSettings`) and verify it appears in the workflow
node picker
- [ ] In the workflow builder, edit a `LOGIC_FUNCTION` step and verify
input fields render (no more JSON-Schema-as-InputSchema hack)
- [ ] Try defining a function with no triggers in the SDK and verify
`defineLogicFunction` rejects it

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: martmull <martmull@hotmail.fr>

packages/twenty-front/src/modules/logic-functions/hooks/useLogicFunctionUpdateFormState.ts

@@ -5,21 +5,22 @@ import {
   type CronTriggerSettings,
   type DatabaseEventTriggerSettings,
   type HttpRouteTriggerSettings,
+  type ToolTriggerSettings,
+  type WorkflowActionTriggerSettings,
 } from 'twenty-shared/application';
 import { type LogicFunction } from '~/generated-metadata/graphql';
 import { useGetLogicFunctionSourceCode } from '@/logic-functions/hooks/useGetLogicFunctionSourceCode';
-import { DEFAULT_TOOL_INPUT_SCHEMA } from 'twenty-shared/logic-function';
 
 export type LogicFunctionFormValues = {
   name: string;
   description: string;
-  isTool: boolean;
   timeoutSeconds: number;
   sourceHandlerCode: string;
-  toolInputSchema?: object;
   cronTriggerSettings: CronTriggerSettings | null;
   databaseEventTriggerSettings: DatabaseEventTriggerSettings | null;
   httpRouteTriggerSettings: HttpRouteTriggerSettings | null;
+  toolTriggerSettings: ToolTriggerSettings | null;
+  workflowActionTriggerSettings: WorkflowActionTriggerSettings | null;
 };
 
 type SetLogicFunctionFormValues = Dispatch<
@@ -39,13 +40,13 @@ export const useLogicFunctionUpdateFormState = ({
   const [formValues, setFormValues] = useState<LogicFunctionFormValues>({
     name: '',
     description: '',
-    isTool: false,
     sourceHandlerCode: '',
     timeoutSeconds: 300,
-    toolInputSchema: DEFAULT_TOOL_INPUT_SCHEMA,
     cronTriggerSettings: null,
     databaseEventTriggerSettings: null,
     httpRouteTriggerSettings: null,
+    toolTriggerSettings: null,
+    workflowActionTriggerSettings: null,
   });
 
   const { sourceHandlerCode, loading: logicFunctionSourceCodeLoading } =
@@ -64,15 +65,15 @@ export const useLogicFunctionUpdateFormState = ({
         ...prevState,
         name: logicFunction.name || '',
         description: logicFunction.description || '',
-        isTool: logicFunction.isTool ?? false,
         timeoutSeconds: logicFunction.timeoutSeconds ?? 300,
-        toolInputSchema:
-          logicFunction.toolInputSchema || DEFAULT_TOOL_INPUT_SCHEMA,
         cronTriggerSettings: logicFunction.cronTriggerSettings ?? null,
         databaseEventTriggerSettings:
           logicFunction.databaseEventTriggerSettings ?? null,
         httpRouteTriggerSettings:
           logicFunction.httpRouteTriggerSettings ?? null,
+        toolTriggerSettings: logicFunction.toolTriggerSettings ?? null,
+        workflowActionTriggerSettings:
+          logicFunction.workflowActionTriggerSettings ?? null,
       }));
     }
   }, [logicFunction]);