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-server/src/engine/workspace-manager/standard-objects-prefill-data/services/prefill-logic-function.service.ts

@@ -45,10 +45,8 @@ export class PrefillLogicFunctionService {
           id: definition.id,
           name: definition.name,
           description: definition.description,
-          toolInputSchema: definition.toolInputSchema,
           source: {
             sourceHandlerCode: definition.sourceHandlerCode,
-            toolInputSchema: definition.toolInputSchema,
             handlerName: 'main',
           },
         },

packages/twenty-server/src/engine/workspace-manager/standard-objects-prefill-data/utils/prefill-workflow-code-step-logic-functions.util.ts

@@ -20,42 +20,6 @@ export const getCreateCompanyWhenAddingNewPersonCodeStepLogicFunctionIds = (
   ),
 });
 
-const EXTRACT_DOMAIN_TOOL_INPUT_SCHEMA = {
-  type: 'object',
-  properties: {
-    email: {
-      type: 'string',
-    },
-  },
-  required: ['email'],
-};
-
-const IS_PERSONAL_EMAIL_TOOL_INPUT_SCHEMA = {
-  type: 'object',
-  properties: {
-    primaryEmail: {
-      type: 'string',
-    },
-  },
-  required: ['primaryEmail'],
-};
-
-const FIND_MATCHING_COMPANY_BY_DOMAIN_TOOL_INPUT_SCHEMA = {
-  type: 'object',
-  properties: {
-    companies: {
-      type: 'array',
-      items: {
-        type: 'object',
-      },
-    },
-    domain: {
-      type: 'string',
-    },
-  },
-  required: ['companies', 'domain'],
-};
-
 const EXTRACT_DOMAIN_LOGIC_FUNCTION_SOURCE = `const psl = require('psl');
 
 export const main = async (params) => {
@@ -184,7 +148,6 @@ export type PrefilledWorkflowCodeStepLogicFunctionDefinition = {
   name: string;
   description: string;
   sourceHandlerCode: string;
-  toolInputSchema: object;
 };
 
 export const getCreateCompanyWhenAddingNewPersonCodeStepLogicFunctionDefinitions =
@@ -203,7 +166,6 @@ export const getCreateCompanyWhenAddingNewPersonCodeStepLogicFunctionDefinitions
         description:
           'Extracts a normalized company domain and URL from a person email address.',
         sourceHandlerCode: EXTRACT_DOMAIN_LOGIC_FUNCTION_SOURCE,
-        toolInputSchema: EXTRACT_DOMAIN_TOOL_INPUT_SCHEMA,
       },
       {
         id: findMatchingCompanyByDomainLogicFunctionId,
@@ -212,7 +174,6 @@ export const getCreateCompanyWhenAddingNewPersonCodeStepLogicFunctionDefinitions
           'Finds an existing company whose website matches a normalized registrable domain.',
         sourceHandlerCode:
           FIND_MATCHING_COMPANY_BY_DOMAIN_LOGIC_FUNCTION_SOURCE,
-        toolInputSchema: FIND_MATCHING_COMPANY_BY_DOMAIN_TOOL_INPUT_SCHEMA,
       },
       {
         id: isPersonalEmailLogicFunctionId,
@@ -220,7 +181,6 @@ export const getCreateCompanyWhenAddingNewPersonCodeStepLogicFunctionDefinitions
         description:
           'Detects whether an email address belongs to a common personal email provider.',
         sourceHandlerCode: IS_PERSONAL_EMAIL_LOGIC_FUNCTION_SOURCE,
-        toolInputSchema: IS_PERSONAL_EMAIL_TOOL_INPUT_SCHEMA,
       },
     ];
   };