// Resolves a pasted/dropped chat attachment into a workspace-relative
// path the agent request body can carry inside `attachments[]` as a
// path-only entry.
//
// All accepted MIME types (image, PDF, DOCX, XLSX, PPTX, text/*,
// JSON, XML, YAML, TOML) round-trip through POST /api/attachments,
// which saves the file under data/attachments/YYYY/MM/<id>.<ext>
// and returns the path. PPTX uploads also yield a `.pdf` companion;
// the route returns the PDF path so the LLM is handed a document
// Claude can natively read. The data: URI form is never sent from
// the Vue UI — paths only.
//
// Background: feat/attachments-as-paths refactor (image side
// completed in plans/done/refactor-edit-images-array.md).

import type { PastedFile } from "../../types/pastedFile";
import { apiPost } from "../api";
import { API_ROUTES } from "../../config/apiRoutes";

/** A stored attachment plus the name its file had on the user's machine.
 *  The on-disk name under `path` stays the collision-proof hex id; `filename`
 *  is what the chat history and the LLM marker show instead (#2308). For a
 *  server-converted upload (PPTX → PDF) the two disagree on extension by
 *  design — `path` is the bytes that were delivered, `filename` is what the
 *  user actually handed over. */
export interface ResolvedAttachment {
  path: string;
  filename: string;
}

export type ResolveResult = { ok: true; value: ResolvedAttachment } | { ok: false; error: string };

interface UploadAttachmentResponse {
  path: string;
  originalPath: string;
  mimeType: string;
}

export async function resolvePastedAttachment(file: PastedFile): Promise<ResolveResult> {
  const upload = await apiPost<UploadAttachmentResponse>(API_ROUTES.attachments.upload, {
    dataUrl: file.dataUrl,
    filename: file.name,
  });
  if (!upload.ok) return { ok: false, error: upload.error };
  return { ok: true, value: { path: upload.data.path, filename: file.name } };
}