New resource: pipefy_ai_agent

[Danielmoraisg]

Summary

AI agents (instruction plus behaviors attached to pipe events) have full API CRUD: createAiAgent, updateAiAgent, deleteAiAgent, toggleAiAgentStatus, with validateAiAgentBehaviors as a preflight. Agent instructions and behaviors versioned in git get the same review treatment as any other process change.

Proposed schema

• id (computed)
• pipe_id (required, RequiresReplace; the API takes the pipe UUID, so resolve id to UUID the way the field resource's delete path does)
• name (required)
• instruction (required)
• behaviors (required, nested list): per behavior name, event_id, instruction, and actions (move_card with destination phase, update_card and create_card with pipe and field attributes)
• active (optional bool, applied via toggleAiAgentStatus)
• data_source_ids (optional list)

Notes

• In practice creation is createAiAgent followed by updateAiAgent to set behaviors; the resource should wrap both in Create.
• behaviors is nested and structured; same typed-attributes vs JSON-string decision as New resource: pipefy_field_condition #45, and typed is worth it for reviewable plans.
• Run validateAiAgentBehaviors before mutations and surface findings as diagnostics.