import { AGENT_ROLE_LABELS, type AgentRole } from "@paperclipai/shared";

/**
 * The name the wizard offers before the customer picks a role. It is a job
 * title rather than a role label because it reads as a person on the very
 * first screen where the agent appears.
 */
/**
 * The role every onboarding hire is filed under.
 *
 * The arc asks for a name, not a role: someone naming their first agent is
 * describing what it should do, and the placeholder carries the range of
 * answers that fit. `general` is the honest filing for that — it claims
 * nothing the customer did not say — and the role can be set later, in the
 * app, where the agent's work gives the choice meaning.
 */
export const DEFAULT_AGENT_ROLE = "general" as const;

export const DEFAULT_AGENT_NAME = "Chief of staff";

/**
 * Names the wizard put there itself, and may therefore replace. Anything the
 * customer typed is theirs and survives a role change.
 *
 * The prototype's version of this step simply overwrote the name whenever the
 * role changed, which is fine in a mock with no real input to lose. Here it
 * would silently discard a name someone chose deliberately, and the loss is
 * invisible: the field still has *a* plausible name in it afterwards.
 */
const WIZARD_SUPPLIED_NAMES: ReadonlySet<string> = new Set([
  DEFAULT_AGENT_NAME,
  ...Object.values(AGENT_ROLE_LABELS),
]);

/**
 * The name to show after a role change — the new role's label when the field
 * still holds something the wizard supplied, otherwise the customer's own text.
 */
export function nextAgentNameForRole(params: {
  currentName: string;
  nextRole: AgentRole;
}): string {
  const current = params.currentName.trim();
  if (current === "" || WIZARD_SUPPLIED_NAMES.has(current)) {
    return AGENT_ROLE_LABELS[params.nextRole];
  }
  return params.currentName;
}