Console trigger form: expose run_pipeline + insert_record actions (follow-up to #92) #134

Follow-up to #92 (shipped 9e47ee1), which added the run_pipeline and insert_record trigger actions to the backend + API + MCP.

Gap

The console trigger form (store/console/src/tabs/SettingsTab.tsx) still lists only the original four actions in its dropdown:

<option value="create_task">Create task</option>
<option value="add_knowledge">Add knowledge</option>
<option value="sync_connector">Sync folder</option>

(plus log_event). A user can create the new trigger types today via the API or MCP create_instance_trigger, but not from the console UI.

Why it wasn't done in #92

Each new action needs a dedicated config input, or the form would create a broken trigger:

• run_pipeline → a pipeline name field (config.pipeline) — ideally a dropdown of the instance's configured pipelines (config.pipelines keys).
• insert_record → a target collection field (config.collection) — ideally a dropdown of the instance's collections.

Tasks

• Extend the local TriggerActionType in SettingsTab.tsx to include run_pipeline and insert_record.
• Add the two <option>s.
• Conditionally render a pipeline-name input (for run_pipeline) and a collection input (for insert_record), mirroring how sync_connector conditionally shows the grant/folder picker.
• Validate the required field before submit (like the sync_connector syncGrantId guard).
• Pass the value through in the config object on create.

Notes

• Backend contract is already live: config.pipeline / config.collection are whitelisted in parseConfig; payload.pipeline / payload.collection also work at dispatch (webhook body can override).
• Nice-to-have: populate the pipeline dropdown from the instance's config.pipelines and the collection dropdown from list_instance_collections.