plugin-flow-builder: create utils folder and split in diferent files

[Iru89]

Description

This PR refactors the internal architecture of botonic-plugin-flow-builder by reorganising utility helpers into a dedicated utils/ folder, splitting the monolithic action orchestration logic into smaller focused modules, and replacing ActionRequest with BotContext across the board. It also introduces an abstract processContent method on every content field so that side effects (tracking, handoff, bot actions, AI agent resolution) are encapsulated inside each content type rather than centralised in FlowBuilderAction.

Context

The previous code mixed orchestration (which content to fetch) with rendering side effects (tracking events, executing handoffs, resolving AI agent responses) inside action/index.tsx. This made it hard to follow the execution flow, reuse individual pieces, and unit-test them in isolation. Additionally, helper functions were scattered across helpers.ts and ad-hoc files with no clear grouping strategy. The refactor creates a clean separation of concerns aligned with the existing content-field model.

Approach taken / Explain the design

1. New src/utils/ folder

Four focused utility modules replace the old helpers.ts catch-all:

File	Responsibility
utils/get-flow-builder-plugin.ts	Retrieves the BotonicPluginFlowBuilder instance from the plugin registry. Previously lived in helpers.ts.
utils/ai-agent.ts	splitAiAgentContents() helper + HubtypeAssistantContent adapter class that converts FlowContent objects to plain-text strings for AI assistant context.
utils/input.ts	Input-type guards (inputHasTextOrTranscript, getTextOrTranscript) and NLU shadowing checks (isKeywordsAllowed, isSmartIntentsAllowed, isKnowledgeBasesAllowed).
utils/token.ts	resolveGetAccessToken() — selects the correct token-retrieval strategy depending on NODE_ENV.

2. action/context.ts — shared context object

Extracts the FlowBuilderContext interface (cmsApi, flowBuilderPlugin, request, resolvedLocale, contentID) and its factory function getFlowBuilderActionContext() into a standalone module. Every action module now receives a typed context instead of constructing it inline.

3. action/get-contents.ts — content-routing orchestrator

Moves the getContents() routing logic (first interaction, payload, AI agent, knowledge base, fallback) out of action/index.tsx into its own module. FlowBuilderAction.botonicInit now simply delegates to getContents() + prepareContentsToRender().

4. action/ai-agent-from-user-input.ts — replaces action/ai-agent/index.ts

The old getContentsByAiAgent function (and its internal structured-output wiring) is replaced by a thin getContentsByAiAgentFromUserInput that delegates the heavy lifting to the FlowAiAgent content field directly. The deleted folder action/ai-agent/ is no longer needed.

5. Abstract processContent on ContentFieldsBase

A new abstract method processContent(botContext: BotContext): Promise<void> is added to the base class. Each content field implements it to perform its own side effects (track event, execute handoff, run bot action, resolve AI agent response). FlowBuilderAction.prepareContentsToRender now iterates over filtered contents and calls content.processContent(), making trackAllContents and doHandoffAndBotActions unnecessary.

6. FlowAiAgent becomes self-contained

All AI agent inference logic previously scattered in action/ai-agent/index.ts is moved into FlowAiAgent:

• resolveAIAgentResponse(botContext, previousContents?) — orchestrates inference, tracking, message parsing, and JSX generation.
• getAIAgentResponse(botContext, previousContents?) — calls the underlying inference API.
• Internal state changed from a single responses array to aiAgentResponse, messages, and jsxElements for clearer lifecycle semantics.

7. ActionRequest → BotContext

Throughout ContentFieldsBase, FlowBuilderAction, and every content field, ActionRequest (from @botonic/react) is replaced by BotContext (from @botonic/core) to reduce the dependency on the React layer in pure-logic modules.

8. WhatsApp Button List — toBotonic rename

toBotonic functions in flow-whatsapp-button-list-section.tsx and flow-whatsapp-button-list-row.tsx are renamed to be consistent with the rest of the content field naming convention, and a new whatsapp-button-list/index.ts barrel is added.

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.