// Decision schema (structured-output target) + encoders to InstanceAiConfirmRequest.

import { domainAccessActionSchema, instanceGatewayResourceDecisionSchema } from '@n8n/api-types';
import type { InstanceAiConfirmRequest, InstanceAiCredentialSetupHint } from '@n8n/api-types';
import { isRecord } from '@n8n/utils/is-record';
import { z } from 'zod';

// ---------------------------------------------------------------------------
// Decision schema — the structured-output shape the model fills
// ---------------------------------------------------------------------------

const answerSchema = z.object({
	questionId: z.string(),
	selectedOptions: z.array(z.string()),
	customText: z.string().optional(),
	skipped: z.boolean().optional(),
});

const answerQuestionsDecisionSchema = z.object({
	action: z.literal('answer_questions'),
	answers: z.array(answerSchema),
});

const applySetupWizardDecisionSchema = z.object({
	action: z.literal('apply_setup_wizard'),
	// JSON-encoded object mapping setup node name -> parameter map. Emitted as a string
	// because Anthropic structured output rejects nested z.record schemas.
	nodeParametersJson: z.string(),
	/**
	 * JSON-encoded object mapping setup node name -> credential type -> existing
	 * credential id to select (`{"<node>": {"<credentialType>": "<id>"}}`),
	 * e.g. from `setupRequests[].existingCredentials`. Omit/empty by default —
	 * only populate when a stage direction governing this exact card asks the
	 * user to engage with a credential slot instead of leaving it deferred.
	 */
	nodeCredentialsJson: z.string().optional(),
	/**
	 * Credential TYPES (e.g. `["slackApi"]`) the user enters a working token for
	 * on this card — the harness makes those credentials' connection test pass,
	 * so the build proceeds as it would with a real account. Per type rather than
	 * a single flag because one card can carry several credentials and a case may
	 * want one to work and another to fail. Only meaningful for a slot with no
	 * existing candidate (the harness creates the credential). Any type left out
	 * keeps the placeholder token that fails its test for real — the default, and
	 * what the honesty cases rely on.
	 */
	workingCredentialTypes: z.array(z.string()).optional(),
});

const approveOrRejectDecisionSchema = z.object({
	action: z.literal('approve_or_reject'),
	approved: z.boolean(),
	userInput: z.string().optional(),
});

const respondToDomainAccessDecisionSchema = z.object({
	action: z.literal('respond_to_domain_access'),
	response: z.enum(['allow_once', 'allow_all', 'deny']),
});

const pickResourceDecisionSchema = z.object({
	action: z.literal('pick_resource_decision'),
	decision: z.string(),
});

/**
 * Response to a standalone credential-setup card (`credentials(action='setup')`
 * suspending — TRUST-349). This action is always part of `confirmationDecisionSchema`
 * and always listed in the tool descriptions, same as `approve_or_reject` —
 * it isn't conditionally offered. What's gated is whether the *event* ever
 * reaches the model at all: the deterministic default (no pending stage
 * direction) short-circuits before the LLM is even called (see
 * `confirmation-payload.ts`'s `allowCredentialEngagement`), so in practice the
 * model only ever sees this event when a direction is already pending — `skip`
 * exists for the case where that pending direction asks the user to decline
 * rather than engage.
 *
 * A normal multi-node workflow BUILD never reaches this tool in practice — live
 * testing found the builder routes credential resolution through the workflow
 * setup wizard instead (`applySetupWizardDecisionSchema`'s `nodeCredentialsJson`
 * below). This tool *is* reached by a standalone credential-connect request with
 * no build attached (e.g. "connect my Slack account now, before I build
 * anything") — confirmed live against a real instance, all three outcomes:
 *
 * Live-captured suspend (`credentials(action='setup')` call args):
 * ```json
 * { "action": "setup", "credentials": [{ "credentialType": "slackApi", "reason": "...", "suggestedName": "Slack account" }] }
 * ```
 *
 *  - `manual` → `{kind:'credentialSelection', credentials:{[type]: id}}` — the
 *    resume payload itself is how the assistant learns the credential exists
 *    (tool State 5); no re-check round-trip. Live-captured tool result (one
 *    existing credential, auto-selected): `{success:true, credentials:{slackApi:"eg_slackapi_key"}}`.
 *    `manual` covers all three existing-credential counts for the resolved
 *    type (ticket TRUST-349):
 *      - zero  → the harness creates a real credential for it
 *        (`UserProxyConfig.credentialCreation`) and selects the new id —
 *        "user fills the New Credential modal". Falls back to decline (with a
 *        parse-failure log) if credential-creation support isn't wired in.
 *      - one   → that credential is selected automatically; `existingCredentialId`
 *        is not needed.
 *      - many  → `existingCredentialId` is required to disambiguate which one
 *        the direction names; omitting it declines (ambiguous).
 *  - `auto`   → `{kind:'credentialAutoSetup', credentialType}` — triggers an
 *    agent rebuild server-side (tool State 4). Live-captured tool result:
 *    `{success:false, needsBrowserSetup:true, credentialType:"slackApi", docsUrl:"...", requiredFields:[...]}`,
 *    followed by the assistant loading the `credential-setup-with-computer-use`
 *    skill as designed. Reachable and its shape is real, but not further
 *    implemented — the harness has no Computer Use tools attached, so a case
 *    scripting this will stall afterward. Do not push such a case to the
 *    gated CI suite.
 *  - `skip`   → `{kind:'approval', approved:false}` — tool State 2 (deferred).
 *    Live-captured tool result: `{success:true, deferred:true, reason:"User skipped credential setup for now...."}`.
 */
const chooseCredentialSetupOptionDecisionSchema = z.object({
	action: z.literal('choose_credential_setup_option'),
	option: z.enum(['auto', 'manual', 'skip']),
	/** Which `credentialRequests[].credentialType` this applies to. Optional
	 *  when the card requests exactly one credential (the common case). */
	credentialType: z.string().optional(),
	/** For `manual` when the card lists more than one existing credential of
	 *  the resolved type — the `id` of the one to select (from
	 *  `credentialRequests[].existingCredentials[].id`). Required to
	 *  disambiguate when there are several; not needed for zero (created) or
	 *  one (auto-selected) candidates. */
	existingCredentialId: z.string().optional(),
});

const sendFollowUpMessageDecisionSchema = z.object({
	action: z.literal('send_follow_up_message'),
	message: z.string(),
	/**
	 * Rename the workflow this run last saved, from outside the conversation, at
	 * this turn boundary — the agent is idle and is never told. `name` is one of
	 * WORKFLOW_CHECKSUM_FIELDS, so the rename conflicts the agent's next save
	 * without touching any node, which is how a case reaches the "modified
	 * outside this conversation" path on purpose instead of by accident.
	 *
	 * Set it ONLY when a stage direction says something changed the workflow
	 * behind the user's back. The harness performs the rename; the agent sees
	 * nothing but `message`. A specific field rather than a general patch because
	 * anything richer would have the model authoring workflow JSON — and
	 * structured output cannot take a nested object here anyway (see
	 * `nodeParametersJson` above).
	 *
	 * The harness ignores it when the run has saved no workflow yet, and when
	 * that workflow already carries this name.
	 */
	renameWorkflowTo: z.string().min(1).optional(),
});

const declareDoneDecisionSchema = z.object({
	action: z.literal('declare_done'),
});

/**
 * The two moments the proxy is asked to decide, each with its own action menu:
 *  - `confirmation` — the agent paused mid-run to show a widget; the proxy must
 *    respond to that widget.
 *  - `user-turn` — the agent's run finished with nothing pending; the turn passed
 *    to the user, who either types a chat message or ends the conversation.
 * The schema handed to the model per mode IS the action menu — actions that
 * cannot function at that moment are not offered at all.
 */
export type ProxyDecisionMode = 'confirmation' | 'user-turn';

export const confirmationDecisionSchema = z.discriminatedUnion('action', [
	answerQuestionsDecisionSchema,
	applySetupWizardDecisionSchema,
	approveOrRejectDecisionSchema,
	respondToDomainAccessDecisionSchema,
	pickResourceDecisionSchema,
	chooseCredentialSetupOptionDecisionSchema,
]);

export const userTurnDecisionSchema = z.discriminatedUnion('action', [
	sendFollowUpMessageDecisionSchema,
	declareDoneDecisionSchema,
]);

/** Full union — the type every decision consumer handles. Agents are only ever
 *  offered the mode-scoped subsets above. */
export const decisionSchema = z.discriminatedUnion('action', [
	answerQuestionsDecisionSchema,
	applySetupWizardDecisionSchema,
	approveOrRejectDecisionSchema,
	respondToDomainAccessDecisionSchema,
	pickResourceDecisionSchema,
	chooseCredentialSetupOptionDecisionSchema,
	sendFollowUpMessageDecisionSchema,
	declareDoneDecisionSchema,
]);

export type Decision = z.infer<typeof decisionSchema>;

export interface SetupWizardParseContext {
	nodes: Array<{
		nodeId?: string;
		nodeName: string;
		parameterNames: string[];
		/**
		 * Credential types this node still needs (workflow setup wizard shows one
		 * `setupRequests[]` entry per (node, credentialType) combo), each with its
		 * existing-credential pick list — mirrors `CredentialSetupParseContext`
		 * below but scoped per node, since a wizard card can list several nodes.
		 */
		credentialRequests: Array<{
			credentialType: string;
			existingCredentials: Array<{ id: string; name: string }>;
			/** Simplified Custom Auth's recipe (template + placeholders) for minting
			 *  the credential — only present for `httpTemplatedCustomAuth` requests. */
			setupHint?: InstanceAiCredentialSetupHint;
		}>;
	}>;
}

/**
 * The credential-setup card's `credentialRequests[]`, carried through so
 * `manual`/`auto` can resolve a `credentialType` (and, for `manual`, an
 * existing credential id already visible under the thread's eval allowlist —
 * see `EvalThreadCredentialAllowlistService` — to select) without re-deriving
 * it from the model's free-form answer.
 */
export interface CredentialSetupParseContext {
	requests: Array<{
		credentialType: string;
		existingCredentials: Array<{ id: string; name: string }>;
	}>;
}

// ---------------------------------------------------------------------------
// Tool descriptions — bundled with the prompt so the model picks the right action
// ---------------------------------------------------------------------------

export const CONFIRMATION_TOOL_DESCRIPTIONS = `Available actions — confirmation responses. A widget is on screen: the agent paused mid-run and is waiting for the user to respond to the event shown in this prompt. Pick the action that matches the widget:

- answer_questions(answers[]): The agent fired an ask-user confirmation (inputType=questions). Answer every question with a plausible value — stated → implied → invented. Invent rather than skip. Set skipped=true only when the question has no plausible answer of any shape, OR when a [stage direction] in the script tells the user to decline or withhold that value — in that case you MUST set skipped=true with an empty selectedOptions and pick NO option (not even one that looks standard or obvious); picking a value defeats the test.

- apply_setup_wizard(nodeParametersJson, nodeCredentialsJson?, workingCredentialTypes?): The agent fired a setup-wizard / "configure your workflow" setup card with placeholder parameters and/or credential slots (the event's payload has \`setupRequests\`). \`nodeParametersJson\` decodes to { "<setup node name>": { "<paramName>": <value>, ... }, ... } — fill every non-credential placeholder with a plausible value (stated → implied → invented). Credential slots (a request entry with \`credentialType\`) stay unset by default — omit \`nodeCredentialsJson\` or leave that node/type out of it — UNLESS a stage direction governing this exact card tells the user to engage; then set \`nodeCredentialsJson\` to { "<setup node name>": { "<credentialType>": "<id>" } }. What \`<id>\` should be depends on that request's \`existingCredentials\`: zero entries → put any placeholder string, a real credential will be created for you; exactly one → put its \`id\`; two or more → put the \`id\` of the one the direction names (match by its \`name\`). This is the ONLY correct way to fill a setup card — do NOT answer it with answer_questions. To deliberately leave a value unset (e.g. a stage direction says the user skips it), dismiss the whole card with approve_or_reject(approved=false) instead of filling it. Whenever you fill a credential slot, list that slot's credential type in \`workingCredentialTypes\` — completing a setup card means the credential the user entered authenticates, which is what the real product requires before it will let the card be applied. Leave a type out ONLY when a stage direction says that particular credential is invalid, expired, revoked or otherwise won't authenticate; with several credentials on one card a direction may make one work and another fail, so list exactly the working ones.

- approve_or_reject(approved, userInput?): A plan-review or free-text confirmation widget is on screen (the event's inputType is plan-review or text). Approve if the plan matches user intent; reject with reason if it diverges. This action only exists as a response to such a widget.

- respond_to_domain_access(response): The agent is asking permission to reach the network — either a specific domain (fetch-url) or a web search. Pick allow_once, allow_all, or deny. Default to allow_all; pick deny ONLY when a [stage direction] tells the user to refuse this kind of access.

- pick_resource_decision(decision): The agent is asking the user to pick a gateway resource access option. Pick the option the user would choose.

- choose_credential_setup_option(option, credentialType?, existingCredentialId?): The agent opened a standalone credential setup card (the event's payload has \`credentialRequests\`, not \`setupRequests\`). You are only ever shown this action when a stage direction governs this exact moment — outside that, credentials stay deferred automatically and you never see this event. Follow the direction: \`manual\` fills the card the way a user filling the form would — check \`credentialRequests[].existingCredentials\` for the resolved type: zero entries → a real credential is created for you automatically, no \`existingCredentialId\` needed; exactly one → it's selected automatically, no \`existingCredentialId\` needed; two or more → set \`existingCredentialId\` to the \`id\` of the one the direction names (match by its \`name\`). \`auto\` hands off to automatic browser-based setup (shape-only — the harness cannot actually drive that flow, so only script this in a throwaway local check, never in a case meant for the gated suite). \`skip\` if the direction says to decline. Never pick this action on your own initiative — only in response to a direction that explicitly asks for credential engagement.`;

export const USER_TURN_TOOL_DESCRIPTIONS = `Available actions — it is the user's turn. The agent finished its run, no widget is on screen, and the chat input is waiting. The user either types a message or ends the conversation:

- send_follow_up_message(message, renameWorkflowTo?): Send the user's next chat message. Everything the user wants to say right now goes here — including answering a question the agent asked in plain text, and approving or rejecting a plan the agent presented in plain text ("No — two changes first: …" or "Yes, go ahead." ARE follow-up messages). Set \`renameWorkflowTo\` ONLY when a [stage direction] says the workflow was changed outside this conversation — e.g. renamed in another tab, or edited by a colleague. The harness renames the last saved workflow for real at this exact moment, and the agent is told nothing about it; \`message\` must NOT mention the rename, because the whole point is that the agent discovers the conflict on its next save. Leave it unset on every other turn.

- declare_done(): The user got what they wanted (or has nothing left to say) and walks away; the conversation ends. Never pick this while the agent is waiting for an answer.`;

// ---------------------------------------------------------------------------
// Decision → InstanceAiConfirmRequest encoders
// ---------------------------------------------------------------------------

/** Creates a real credential of the given type for the "manual, zero existing"
 *  case — see `UserProxyConfig.credentialCreation` in `user-proxy/index.ts`. */
export type CreateCredentialFn = (
	credentialType: string,
	options?: { works?: boolean; setupHint?: InstanceAiCredentialSetupHint },
) => Promise<{ id: string; name: string }>;

/**
 * Shared safety net around `createCredential`: missing config and a thrown
 * creation error (bad type, network failure, ...) both decline-and-log rather
 * than crash the run — a failed credential creation is no different from any
 * other unresolvable manual selection from the caller's point of view.
 */
async function tryCreateCredential(
	createCredential: CreateCredentialFn | undefined,
	credentialType: string,
	actionLabel: string,
	onFailure?: (raw: string, error: unknown) => void,
	options?: { works?: boolean; setupHint?: InstanceAiCredentialSetupHint },
): Promise<{ id: string; name: string } | undefined> {
	if (!createCredential) {
		onFailure?.(
			actionLabel,
			new Error(
				`no existing credential for type "${credentialType}" and no credential-creation support wired in`,
			),
		);
		return undefined;
	}
	try {
		return await createCredential(credentialType, options);
	} catch (error) {
		onFailure?.(actionLabel, error);
		return undefined;
	}
}

/**
 * Encode a confirmation-response action into an InstanceAiConfirmRequest.
 * Returns null for user-turn actions (send_follow_up_message, declare_done),
 * which the caller routes separately.
 */
export async function encodeConfirmationDecision(
	decision: Decision,
	onParseFailure?: (raw: string, error: unknown) => void,
	setupContext?: SetupWizardParseContext,
	credentialSetupContext?: CredentialSetupParseContext,
	createCredential?: CreateCredentialFn,
): Promise<InstanceAiConfirmRequest | null> {
	switch (decision.action) {
		case 'answer_questions':
			return { kind: 'questions', answers: decision.answers };

		case 'apply_setup_wizard': {
			const nodeCredentials = decision.nodeCredentialsJson
				? await parseNodeCredentialsJson(
						decision.nodeCredentialsJson,
						onParseFailure,
						setupContext,
						createCredential,
						new Set(decision.workingCredentialTypes ?? []),
					)
				: undefined;
			return {
				kind: 'setupWorkflowApply',
				nodeParameters: parseNodeParametersJson(
					decision.nodeParametersJson,
					onParseFailure,
					setupContext,
				),
				...(nodeCredentials && Object.keys(nodeCredentials).length > 0 ? { nodeCredentials } : {}),
			};
		}

		case 'approve_or_reject':
			return {
				kind: 'approval',
				approved: decision.approved,
				...(decision.userInput ? { userInput: decision.userInput } : {}),
			};

		case 'respond_to_domain_access': {
			if (decision.response === 'deny') return { kind: 'domainAccessDeny' };
			const parsed = domainAccessActionSchema.safeParse(decision.response);
			return {
				kind: 'domainAccessApprove',
				domainAccessAction: parsed.success ? parsed.data : 'allow_once',
			};
		}

		case 'pick_resource_decision': {
			const parsed = instanceGatewayResourceDecisionSchema.safeParse(decision.decision);
			return {
				kind: 'resourceDecision',
				resourceDecision: parsed.success ? parsed.data : 'allowOnce',
			};
		}

		case 'choose_credential_setup_option':
			return await encodeCredentialSetupDecision(
				decision,
				onParseFailure,
				credentialSetupContext,
				createCredential,
			);

		case 'send_follow_up_message':
		case 'declare_done':
			return null;
	}
}

async function encodeCredentialSetupDecision(
	decision: Extract<Decision, { action: 'choose_credential_setup_option' }>,
	onParseFailure?: (raw: string, error: unknown) => void,
	credentialSetupContext?: CredentialSetupParseContext,
	createCredential?: CreateCredentialFn,
): Promise<InstanceAiConfirmRequest> {
	if (decision.option === 'skip') return { kind: 'approval', approved: false };

	const request = resolveCredentialRequest(decision.credentialType, credentialSetupContext);

	if (decision.option === 'auto') {
		// When the card told us which credentials it wants, only one of those is a
		// valid target: falling back to the model's free-form string would launch
		// automatic setup for a type the card never asked about. Without context
		// the model's answer is the only source we have.
		const credentialType = credentialSetupContext
			? request?.credentialType
			: decision.credentialType;
		if (!credentialType) {
			onParseFailure?.(
				decision.action,
				new Error(
					`auto setup chosen with no resolvable credentialType${
						decision.credentialType ? ` (card does not list "${decision.credentialType}")` : ''
					}`,
				),
			);
			return { kind: 'approval', approved: false };
		}
		return { kind: 'credentialAutoSetup', credentialType };
	}

	// manual — covers all three existing-credential counts for the resolved type.
	return await resolveManualCredentialSelection(
		decision,
		request,
		onParseFailure,
		createCredential,
	);
}

/**
 * `manual`'s three-way behavior (TRUST-349): zero existing credentials of the
 * resolved type → create one for real; exactly one → auto-select it;
 * several → `existingCredentialId` must disambiguate which one.
 */
async function resolveManualCredentialSelection(
	decision: Extract<Decision, { action: 'choose_credential_setup_option' }>,
	request: CredentialSetupParseContext['requests'][number] | undefined,
	onParseFailure?: (raw: string, error: unknown) => void,
	createCredential?: CreateCredentialFn,
): Promise<InstanceAiConfirmRequest> {
	const credentialType = request?.credentialType ?? decision.credentialType;

	if (request && request.existingCredentials.length === 0) {
		const created = await tryCreateCredential(
			createCredential,
			request.credentialType,
			decision.action,
			onParseFailure,
		);
		if (!created) return { kind: 'approval', approved: false };
		return { kind: 'credentialSelection', credentials: { [request.credentialType]: created.id } };
	}

	const existingId = request
		? resolveExistingCredentialId(request, decision.existingCredentialId)
		: undefined;
	if (!request || !existingId) {
		onParseFailure?.(
			decision.action,
			new Error(
				`manual credential selection: no existing credential found for type "${credentialType ?? ''}"` +
					(decision.existingCredentialId ? ` matching id "${decision.existingCredentialId}"` : ''),
			),
		);
		return { kind: 'approval', approved: false };
	}
	return { kind: 'credentialSelection', credentials: { [request.credentialType]: existingId } };
}

/**
 * Which existing credential to select for `manual` when at least one exists.
 * When the card lists more than one candidate for the resolved type,
 * `existingCredentialId` disambiguates (matched against `existingCredentials[].id`);
 * with a single candidate it's optional and that one is used regardless.
 */
function resolveExistingCredentialId(
	request: CredentialSetupParseContext['requests'][number],
	existingCredentialId: string | undefined,
): string | undefined {
	if (existingCredentialId) {
		return request.existingCredentials.find((c) => c.id === existingCredentialId)?.id;
	}
	return request.existingCredentials.length === 1 ? request.existingCredentials[0].id : undefined;
}

function resolveCredentialRequest(
	credentialType: string | undefined,
	context: CredentialSetupParseContext | undefined,
): CredentialSetupParseContext['requests'][number] | undefined {
	if (!context || context.requests.length === 0) return undefined;
	if (credentialType) {
		return context.requests.find((r) => r.credentialType === credentialType);
	}
	// No type specified — fine when the card only asked for one credential.
	return context.requests.length === 1 ? context.requests[0] : undefined;
}

/**
 * Parse+validate `nodeCredentialsJson` against the wizard's parse context:
 * every node key must be a known setup node, and every credential type must be
 * one that node actually requested. Same three-way `manual` behavior as the
 * standalone tool (TRUST-349): a (node, type) with existing candidates must
 * name a real one from `existingCredentials` (auto-accepted when there's only
 * one, regardless of the id string given, since there's nothing else it could
 * be); zero candidates creates a real credential instead — the model has
 * nothing to reference there, so any value in that slot signals intent to
 * engage, not a specific id. Invalid/unresolvable entries are dropped with a
 * parse-failure log rather than silently sending a bogus id through.
 */
async function parseNodeCredentialsJson(
	json: string,
	onFailure?: (raw: string, error: unknown) => void,
	setupContext?: SetupWizardParseContext,
	createCredential?: CreateCredentialFn,
	workingCredentialTypes?: ReadonlySet<string>,
): Promise<Record<string, Record<string, string>>> {
	let parsed: unknown;
	try {
		parsed = JSON.parse(json);
	} catch (error) {
		onFailure?.(json, error);
		return {};
	}
	if (!isRecord(parsed)) {
		onFailure?.(json, new Error('parsed nodeCredentialsJson is not a plain object'));
		return {};
	}
	if (!setupContext || setupContext.nodes.length === 0) {
		onFailure?.(json, new Error('nodeCredentialsJson supplied with no setup-wizard context'));
		return {};
	}

	const nodeByAcceptedKey = new Map<string, (typeof setupContext.nodes)[number]>();
	for (const node of setupContext.nodes) {
		nodeByAcceptedKey.set(node.nodeName, node);
		if (node.nodeId) nodeByAcceptedKey.set(node.nodeId, node);
	}

	const result: Record<string, Record<string, string>> = {};
	for (const [key, credsByType] of Object.entries(parsed)) {
		const node = nodeByAcceptedKey.get(key);
		if (!node || !isRecord(credsByType)) {
			onFailure?.(json, new Error(`nodeCredentialsJson: unknown setup node "${key}"`));
			continue;
		}
		for (const [credentialType, credentialId] of Object.entries(credsByType)) {
			const request = node.credentialRequests.find((r) => r.credentialType === credentialType);
			if (!request) {
				onFailure?.(
					json,
					new Error(
						`nodeCredentialsJson: node "${key}" did not request credential type "${credentialType}"`,
					),
				);
				continue;
			}

			if (request.existingCredentials.length === 0) {
				const created = await tryCreateCredential(
					createCredential,
					credentialType,
					'apply_setup_wizard',
					onFailure,
					{
						works: workingCredentialTypes?.has(credentialType) === true,
						setupHint: request.setupHint,
					},
				);
				if (created) (result[node.nodeName] ??= {})[credentialType] = created.id;
				continue;
			}

			const match =
				request.existingCredentials.length === 1
					? request.existingCredentials[0]
					: request.existingCredentials.find((c) => c.id === credentialId);
			if (!match) {
				onFailure?.(
					json,
					new Error(
						`nodeCredentialsJson: no existing credential "${String(credentialId)}" of type "${credentialType}" for node "${key}"`,
					),
				);
				continue;
			}
			(result[node.nodeName] ??= {})[credentialType] = match.id;
		}
	}
	return result;
}

function parseNodeParametersJson(
	json: string,
	onFailure?: (raw: string, error: unknown) => void,
	setupContext?: SetupWizardParseContext,
): Record<string, Record<string, unknown>> {
	try {
		const parsed: unknown = JSON.parse(json);
		if (isRecord(parsed)) {
			return normalizeNodeParameters(parsed, json, onFailure, setupContext);
		}
		onFailure?.(json, new Error('parsed value is not a plain object'));
	} catch (error) {
		onFailure?.(json, error);
	}
	return {};
}

function normalizeNodeParameters(
	parsed: Record<string, unknown>,
	rawJson: string,
	onFailure?: (raw: string, error: unknown) => void,
	setupContext?: SetupWizardParseContext,
): Record<string, Record<string, unknown>> {
	if (!setupContext || setupContext.nodes.length === 0) {
		return coerceRecordOfRecords(parsed, rawJson, onFailure);
	}

	const nodeByAcceptedKey = new Map<string, string>();
	for (const node of setupContext.nodes) {
		nodeByAcceptedKey.set(node.nodeName, node.nodeName);
		if (node.nodeId) nodeByAcceptedKey.set(node.nodeId, node.nodeName);
	}

	const normalized: Record<string, Record<string, unknown>> = {};
	const unknownKeys: string[] = [];

	for (const [key, value] of Object.entries(parsed)) {
		const nodeName = nodeByAcceptedKey.get(key);
		if (!nodeName) {
			unknownKeys.push(key);
			continue;
		}
		if (!isRecord(value)) {
			onFailure?.(rawJson, new Error(`setup node "${key}" did not contain a parameter map`));
			return {};
		}
		normalized[nodeName] = value;
	}

	if (Object.keys(normalized).length > 0) {
		if (unknownKeys.length > 0) {
			onFailure?.(
				rawJson,
				new Error(`setup parameters included unknown node keys: ${unknownKeys.join(', ')}`),
			);
			return {};
		}
		return normalized;
	}

	const fillableNodes = setupContext.nodes.filter((node) => node.parameterNames.length > 0);
	if (fillableNodes.length === 1) {
		const [node] = fillableNodes;
		const parameterNames = new Set(node.parameterNames);
		const containsKnownParameter = Object.keys(parsed).some((key) => parameterNames.has(key));
		if (containsKnownParameter) {
			return { [node.nodeName]: parsed };
		}
	}

	onFailure?.(
		rawJson,
		new Error(`setup parameters did not match requested setup nodes: ${unknownKeys.join(', ')}`),
	);
	return {};
}

function coerceRecordOfRecords(
	parsed: Record<string, unknown>,
	rawJson: string,
	onFailure?: (raw: string, error: unknown) => void,
): Record<string, Record<string, unknown>> {
	const result: Record<string, Record<string, unknown>> = {};
	for (const [nodeName, params] of Object.entries(parsed)) {
		if (!isRecord(params)) {
			onFailure?.(rawJson, new Error(`setup node "${nodeName}" did not contain a parameter map`));
			return {};
		}
		result[nodeName] = params;
	}
	return result;
}