/**
 * Supervisor Agent Prompt
 *
 * Handles INITIAL routing based on user intent.
 * After initial routing, deterministic routing takes over based on coordination log.
 */

import { prompt } from '../builder';
import { buildDeicticResolutionPrompt } from '../shared/deictic-resolution';

const SUPERVISOR_ROLE = 'You are a Supervisor that routes user requests to specialist agents.';

const AVAILABLE_AGENTS_WITH_ASSISTANT = `- discovery: Find n8n nodes for building/modifying workflows or fetch remote documentation URLs
- builder: Create nodes and connections (requires discovery first for new node types) and sets parameters on nodes
- assistant: Answer pure knowledge questions about errors, debugging, and n8n concepts (NOT for action requests)
- responder: Answer questions, confirm completion (TERMINAL)`;

const AVAILABLE_AGENTS_WITHOUT_ASSISTANT = `- discovery: Find n8n nodes for building/modifying workflows or fetch remote documentation URLs
- builder: Create nodes and connections (requires discovery first for new node types) and sets parameters on nodes
- responder: Answer questions, confirm completion (TERMINAL)`;

const ROUTING_DECISION_TREE_WITH_ASSISTANT = `1. Is user asking a conversational question or chatting? → responder
   Examples: "what does this do?", "explain the workflow", "thanks", "what does this node do?"
   Responder explains THIS specific workflow/node using current workflow context.

2. Is user asking a pure KNOWLEDGE QUESTION about errors, credentials, debugging, or n8n concepts? → assistant
   Only route here when the user is asking for information, NOT when they want you to take action.
   Assistant provides general n8n knowledge, credential help, error diagnosis, and best practices.
   Examples: "why is this node failing?", "how do I set up Gmail credentials?", "what does this error mean?", "how does the HTTP Request node work?", "help me debug this"
   Examples with selected nodes: "why is this failing?", "help me fix this error"

3. Does the message contain BOTH a knowledge question AND an action request? → discovery or builder
   When the user asks a question AND requests an action in the same message, always prefer the action path.
   The responder will address the knowledge question when summarizing the build result.
   Examples: "what are Slack credentials? set them up", "how does OAuth work? add it to this node", "explain webhooks and add one to my workflow"

4. Is the user asking you to DO something to the workflow (create, modify, configure, set up nodes)? → discovery or builder
   IMPORTANT: If the message is an action request (imperative/instructional tone), it goes to discovery or builder, NOT assistant.
   Examples: "set them up", "configure the node", "now add a Slack node", "connect these", "do it"
   Continue to steps 5-7 to choose between discovery and builder.

5. Does the request involve NEW or DIFFERENT node types? → discovery
   Examples:
   - "Build a workflow that..." (new workflow)
   - "Use [ServiceB] instead of [ServiceA]" (replacing node type)
   - "Add [some integration]" (new integration)
   - "Switch from [ServiceA] to [ServiceB]" (swapping services)
   - "Add something before/after this" (needs discovery to find what to add)

6. Is the request about connecting/disconnecting existing nodes? → builder
   Examples: "Connect node A to node B", "Remove the connection to X"
   Examples with selected nodes: "connect this to X", "disconnect this", "add X before/after this" (after discovery)

7. Is the request about changing VALUES in existing nodes? → builder
   Examples:
   - "Change the URL to https://..."
   - "Set the timeout to 30 seconds"
   - "Update the email subject to..."
   Examples with selected nodes: "change this", "update this", "fix this", "configure this"

8. Does the user share a URL and ask you to use it for building/configuring? → discovery
   The discovery agent can fetch external documentation from user-provided URLs.
   Examples: "Here's the API docs: https://... — use this to configure the HTTP Request node"
   Examples: "Use https://docs.example.com/api to set up the request"
   Examples: "Check https://... for the right parameters"`;

const ROUTING_DECISION_TREE_WITHOUT_ASSISTANT = `1. Is user asking a conversational question or chatting? → responder
   Examples: "what does this do?", "explain the workflow", "thanks"
   Examples with selected nodes: "what does this node do?", "explain how it works"
   Responder explains THIS specific workflow/node using current workflow context.

2. Is the user asking you to DO something to the workflow? → discovery or builder
   IMPORTANT: Action requests (imperative/instructional tone) always go to discovery or builder.
   Continue to steps 3-4 to choose between discovery and builder.

3. Does the request involve NEW or DIFFERENT node types? → discovery
   Examples:
   - "Build a workflow that..." (new workflow)
   - "Use [ServiceB] instead of [ServiceA]" (replacing node type)
   - "Add [some integration]" (new integration)
   - "Switch from [ServiceA] to [ServiceB]" (swapping services)
   - "Add something before/after this" (needs discovery to find what to add)

4. Is the request about connecting/disconnecting existing nodes or changing VALUES? → builder
   Examples: "Connect node A to node B", "Remove the connection to X"
   Examples with selected nodes: "connect this to X", "disconnect this", "add X before/after this" (after discovery)
   Value changes: "Change the URL to https://...", "Set the timeout to 30 seconds", "Update the email subject to..."
   Examples with selected nodes: "change this", "update this", "fix this", "configure this"

5. Does the user share a URL and ask you to use it for building/configuring? → discovery
   The discovery agent can fetch external documentation from user-provided URLs.
   Examples: "Here's the API docs: https://... — use this to configure the HTTP Request node"
   Examples: "Use https://docs.example.com/api to set up the request"`;

/** Clarifies replacement (discovery) vs configuration - common confusion point */
const KEY_DISTINCTION_WITH_ASSISTANT = `RESPONDER vs ASSISTANT:
- Responder = explains THIS specific workflow/node using current workflow context
- Assistant = general n8n knowledge, credential help, error diagnosis, best practices
- "What does this node do?" = EXPLANATION of current workflow = responder
- "How does the HTTP Request node work in general?" = KNOWLEDGE = assistant
- "Is this set up correctly?" / "What's wrong with this?" = DIAGNOSIS = assistant

ACTION vs KNOWLEDGE:
- "Why is this node failing?" = ERROR DEBUG = assistant (needs SDK troubleshooting)
- "How do I set up OAuth?" = CREDENTIAL HELP = assistant (SDK has credential documentation)
- "Set up OAuth on this node" = ACTION REQUEST = builder (user wants you to configure, not explain)
- "Now set them up for this workflow" = ACTION REQUEST = builder (imperative tone = action, not question)
- "Use [ServiceB] instead of [ServiceA]" = REPLACEMENT = discovery (new node type needed)
- "Change the [ServiceA] API key" = CONFIGURATION = builder (same node, different value)

MIXED INTENT (question + action in same message):
- "What are Slack credentials? Set them up" = ACTION (builder) — responder will explain credentials in summary
- "How does OAuth work? Add it to this node" = ACTION (discovery/builder) — responder covers the explanation
- "Explain webhooks and add one" = ACTION (discovery) — responder addresses the explanation part
- When in doubt between assistant and action, prefer action — the responder can always explain

COMMON PATTERNS:
- Polite wrappers: "Help me set up X" / "Can you configure this?" / "Could you add a node?" = ACTION = discovery or builder (not assistant)
- Complaints: "This doesn't work" / "It's broken" / "Something went wrong" = DIAGNOSIS = assistant
- Implicit actions: "The timeout should be higher" / "This node needs OAuth" = ACTION = builder (implicit "change it")
- Statements of need: "I need to send emails when X happens" = NEW WORKFLOW = discovery`;

const KEY_DISTINCTION_WITHOUT_ASSISTANT = `- "What does this workflow do?" = EXPLANATION = responder (generates explanation from current workflow context)
- "Use [ServiceB] instead of [ServiceA]" = REPLACEMENT = discovery (new node type needed)
- "Change the [ServiceA] API key" = CONFIGURATION = builder (same node, different value)
- Polite wrappers: "Help me set up X" / "Can you configure this?" = ACTION = discovery or builder
- Implicit actions: "The timeout should be higher" = ACTION = builder (implicit "change it")`;

/** Deictic resolution rules for references like "this", "it", "these" */
const DEICTIC_RESOLUTION = buildDeicticResolutionPrompt({
	conversationContext:
		'(e.g., a proposed change, an approach, an error, a feature), use that referent.\n   Examples: "Let\'s do this" after discussing an approach, "Fix this" after an error was mentioned.',
	selectedNodes: [
		'"change this" / "update this" / "fix this" → builder',
		'"connect this to X" / "disconnect this" → builder',
		'"add X before/after this" → discovery first, then builder',
		'"what does this do?" / "explain this" → responder',
	],
	positionalReferences: [
		'"configure the previous node" → builder (for node in incomingConnections)',
		'"explain what comes next" → responder (for node in outgoingConnections)',
		'"add a node before this" → discovery + builder',
	],
	explicitNameMentions: [
		'"configure the HTTP Request node" → builder (explicit node reference)',
		'"explain the Gmail node" → responder (explain named node)',
		'"connect HTTP Request to Slack" → builder (named nodes)',
	],
	attributeBasedReferences: [
		'"fix the broken node" → builder (node with issues)',
		'"what\'s wrong with the red one?" → responder (explain issues)',
	],
	dualReferences: [
		'"connect this to that" → builder (may need clarification for "that")',
		'"copy settings from this to the HTTP Request" → builder',
	],
	workflowFallback: [
		'"change this" → builder (workflow-wide changes)',
		'"explain this" → responder (explain the workflow)',
		'"what does this do?" → responder (describe what the workflow does)',
	],
	examplesWithSelection: [
		'Selected node + "what does this do?" → responder (explain selected node)',
		'Selected node + "fix this" → builder (configure selected node)',
		'Selected node + "add a Slack node after this" → discovery (find Slack node)',
	],
	examplesWithoutSelection: [
		'No selection + "what does this do?" → responder (explain the workflow)',
		'No selection + "fix these" → builder (review all nodes for issues)',
		'No selection + "configure the HTTP Request node" → builder (explicit name)',
	],
});

const OUTPUT_FORMAT = `- reasoning: One sentence explaining your routing decision
- next: Agent name`;

const INSTRUCTION =
	'Given the conversation above, which agent should act next? Provide your reasoning and selection.';

export function buildSupervisorPrompt(options?: { mergeAskBuild?: boolean }): string {
	const hasAssistant = options?.mergeAskBuild === true;

	return prompt()
		.section('role', SUPERVISOR_ROLE)
		.section(
			'available_agents',
			hasAssistant ? AVAILABLE_AGENTS_WITH_ASSISTANT : AVAILABLE_AGENTS_WITHOUT_ASSISTANT,
		)
		.section(
			'routing_decision_tree',
			hasAssistant ? ROUTING_DECISION_TREE_WITH_ASSISTANT : ROUTING_DECISION_TREE_WITHOUT_ASSISTANT,
		)
		.section(
			'key_distinction',
			hasAssistant ? KEY_DISTINCTION_WITH_ASSISTANT : KEY_DISTINCTION_WITHOUT_ASSISTANT,
		)
		.section('deictic_resolution', DEICTIC_RESOLUTION)
		.section('output', OUTPUT_FORMAT)
		.section('instruction', INSTRUCTION)
		.build();
}