diff --git a/.planning/phases/14-crm-attio-style-fix/14-REVIEW.md b/.planning/phases/14-crm-attio-style-fix/14-REVIEW.md
new file mode 100644
index 0000000..1d9d746
--- /dev/null
+++ b/.planning/phases/14-crm-attio-style-fix/14-REVIEW.md
@@ -0,0 +1,291 @@
+---
+phase: 14-crm-attio-style-fix
+reviewed: 2026-06-14T11:35:00Z
+depth: standard
+files_reviewed: 11
+files_reviewed_list:
+  - src/app/admin/leads/[id]/page.tsx
+  - src/app/admin/leads/LeadsSearch.tsx
+  - src/app/admin/leads/actions.ts
+  - src/app/admin/leads/page.tsx
+  - src/components/admin/dashboard/FollowUpWidget.tsx
+  - src/components/admin/leads/LeadDetail.tsx
+  - src/components/admin/leads/LeadForm.tsx
+  - src/components/admin/leads/LeadTable.tsx
+  - src/components/admin/leads/SendQuoteModal.tsx
+  - src/components/ui/form.tsx
+  - src/lib/admin-queries.ts
+status: issues_found
+---
+
+# Phase 14: Code Review Report
+
+**Reviewed:** 2026-06-14T11:35:00Z
+**Depth:** standard
+**Files Reviewed:** 11
+**Status:** issues_found
+
+## Summary
+
+Reviewed the Phase 14 CRM Attio-style redesign of `/admin/leads`: the new data layer (`getLeadsWithTags`, `getLeadFieldOptions`, `updateLeadField`, lead-tag CRUD in `actions.ts`), the rewritten `LeadTable`/`LeadsSearch`/`LeadDetail`, and the 14-03 cleanup of `FollowUpWidget`, `LeadForm`, and `SendQuoteModal`.
+
+The new inline-edit / tag CRUD layer (14-01) is generally sound and follows the established `OptionMultiSelect`/`EditableCell` patterns from Phase 11. However, there are real correctness gaps:
+
+- A stale-UI bug affects every non-inline-edit mutation path (`EditLeadModal`, `SendQuoteModal`, `LogActivityModal`) — none of them call `router.refresh()`, so `revalidatePath` alone does not update the already-rendered client tree, leaving the lead detail page showing stale data after a successful save.
+- `renameLeadTag` can throw an unhandled Postgres unique-constraint violation when the new name collides with an existing tag on the same lead, and that raw DB error message is surfaced directly to the admin UI.
+- `updateLeadField("email", ...)` bypasses the email-format validation that `createLeadSchema`/`updateLeadSchema` enforce elsewhere, so inline edits can store invalid email strings.
+- Authorization (`requireAdmin()`) was added only to the new Phase 14 actions; the pre-existing `createLead`/`updateLead`/`deleteLead`/`logActivity`/`assignQuoteToLead` actions remain unguarded, which is now an inconsistent pattern within the same file.
+- Leftover dead code from the 14-03 "remove dead onSubmit branch" fix: the `generate_new` branch in `assignQuoteToLead` (actions.ts) is now unreachable, and `SendQuoteModal`'s local duplicate `assignQuoteSchema` plus `useForm<any>` were not cleaned up to match the stated fix description.
+
+## Critical Issues
+
+None found at Critical severity — the issues above are functional/UX correctness bugs and inconsistent authorization, not exploitable from outside the admin session boundary as currently scoped. See Warnings for details and required fixes.
+
+## Warnings
+
+### WR-01: Stale UI after EditLeadModal / SendQuoteModal / LogActivityModal saves — missing router.refresh()
+
+**File:** `src/components/admin/leads/LeadForm.tsx:214-226` (EditLeadModal `onSubmit`), `src/components/admin/leads/SendQuoteModal.tsx:48-65` (`onSubmit`), `src/components/admin/leads/LogActivityModal.tsx:51-69` (`onSubmit`)
+
+**Issue:** All three modals call a server action that internally calls `revalidatePath(...)`, then on success simply `setOpen(false)` (and `form.reset()` where applicable). None of them call `router.refresh()`. `revalidatePath` invalidates the Next.js Router Cache for that path, but it does **not** force the currently-mounted client component tree to refetch — that requires an explicit `router.refresh()` (as `LeadTable`'s and `LeadDetail`'s own `run()` helpers correctly do for inline edits, see `LeadTable.tsx:126` and `LeadDetail.tsx:55`).
+
+Concretely:
+- `EditLeadModal` lets the admin change `name`, `email`, `phone`, `company`, `status`, `notes` on `/admin/leads/[id]`. After a successful save, the page header (`lead.name`, `lead.company`) and Profile card (`lead.status`, `lead.email`, etc.) keep showing the pre-edit values until the admin manually navigates or reloads.
+- `SendQuoteModal`'s "existing quote" tab calls `assignQuoteToLead`, which updates the lead's `status` to `"proposal_sent"` server-side — the Profile card's status badge will not reflect this until a manual refresh.
+- `LogActivityModal` updates `last_contact_date` via `createActivity` — the "Ultimo contatto" field and the Activity Log list will not show the new entry until a manual refresh.
+
+**Fix:**
+```tsx
+// LeadForm.tsx EditLeadModal (and CreateLeadModal), SendQuoteModal.tsx, LogActivityModal.tsx
+import { useRouter } from "next/navigation";
+
+// inside the component
+const router = useRouter();
+
+async function onSubmit(data: ...) {
+  setLoading(true);
+  try {
+    const result = await updateLead(lead.id, data); // or assignQuoteToLead / logActivity
+    if (result.success) {
+      setOpen(false);
+      router.refresh();
+    } else {
+      console.error("Error updating lead:", result.error);
+    }
+  } finally {
+    setLoading(false);
+  }
+}
+```
+
+### WR-02: renameLeadTag can throw an unhandled unique-constraint violation surfaced raw to the UI
+
+**File:** `src/app/admin/leads/actions.ts:248-260`
+
+**Issue:** `renameLeadTag(oldValue, newValue)` runs:
+```ts
+await db
+  .update(tags)
+  .set({ name: next })
+  .where(and(eq(tags.entity_type, LEADS_TAG_ENTITY), eq(tags.name, oldValue)));
+```
+This updates **every** `tags` row across **all leads** that currently have `name === oldValue` to `name = next`. The `tags` table has a unique index on `(entity_type, entity_id, name)` (`src/db/schema.ts:133-137`). If any lead that has tag `oldValue` *also already has* a tag named `next`, that row's update violates the unique constraint and Drizzle/Postgres throws.
+
+Unlike `createLead`/`updateLead`/`deleteLead`/`logActivity`/`assignQuoteToLead`, this function (and `addLeadTag`/`removeLeadTag`) has **no try/catch** — the thrown error propagates up through the `"use server"` boundary to the client's `run()` wrapper in `LeadTable.tsx`/`LeadDetail.tsx`, which does `setError(e instanceof Error ? e.message : ...)` and renders that message directly in the table row. This surfaces a raw Postgres error message (e.g. `duplicate key value violates unique constraint "tags_entity_name_unique"`) to the admin UI instead of a friendly message.
+
+**Fix:**
+```ts
+export async function renameLeadTag(oldValue: string, newValue: string) {
+  await requireAdmin();
+  const next = newValue.trim();
+  if (next.length === 0) throw new Error("Nuovo nome richiesto");
+  if (next === oldValue) return;
+
+  try {
+    await db
+      .update(tags)
+      .set({ name: next })
+      .where(and(eq(tags.entity_type, LEADS_TAG_ENTITY), eq(tags.name, oldValue)));
+  } catch (error) {
+    console.error("renameLeadTag error:", error);
+    throw new Error(`Esiste già un tag "${next}" su uno o più lead`);
+  }
+
+  revalidatePath("/admin/leads");
+}
+```
+
+### WR-03: updateLeadField("email", ...) bypasses email format validation
+
+**File:** `src/app/admin/leads/actions.ts:200-207`
+
+**Issue:** `createLeadSchema`/`updateLeadSchema` (`src/lib/lead-validators.ts:18`) validate `email` with `z.string().email(...)`. But the inline-edit path `updateLeadField(leadId, "email", value)` falls into the generic `else` branch:
+```ts
+} else {
+  // email | phone | company | next_action — nullable text fields, empty clears
+  const s = value.trim();
+  await db
+    .update(leads)
+    .set({ [fieldName]: s || null, updated_at: new Date() })
+    .where(eq(leads.id, leadId));
+}
+```
+No format check is applied, so an admin can type `"not an email"` into the inline `email` cell (`LeadTable.tsx:144-151`, `EditableCell` with `type="text"`) and it will be persisted as-is. This is inconsistent with the create/edit-modal path which rejects invalid emails via Zod.
+
+**Fix:**
+```ts
+} else if (fieldName === "email") {
+  const s = value.trim();
+  if (s && !z.string().email().safeParse(s).success) {
+    throw new Error("Email non valida");
+  }
+  await db.update(leads).set({ email: s || null, updated_at: new Date() }).where(eq(leads.id, leadId));
+} else {
+  // phone | company | next_action — nullable text fields, empty clears
+  const s = value.trim();
+  await db
+    .update(leads)
+    .set({ [fieldName]: s || null, updated_at: new Date() })
+    .where(eq(leads.id, leadId));
+}
+```
+
+### WR-04: Inconsistent authorization — requireAdmin() only guards the new Phase 14 actions
+
+**File:** `src/app/admin/leads/actions.ts:18-168` vs `170-260`
+
+**Issue:** `requireAdmin()` (lines 170-173) is called by `updateLeadField`, `addLeadTag`, `removeLeadTag`, and `renameLeadTag` (the Phase 14 additions), but **not** by the pre-existing `createLead`, `updateLead`, `deleteLead`, `logActivity`, or `assignQuoteToLead`. All of these are exported `"use server"` actions reachable by anyone who can call them directly (e.g. via a crafted request to the server action endpoint), regardless of whether they can see the `/admin/leads` UI — and `src/app/admin/layout.tsx:10-18` does **not** redirect unauthenticated users away from `/admin/*`, it only conditionally renders the sidebar. This means the new code introduces a visible double-standard: half the mutations in this file require a session, half don't, even though they operate on the same `leads` table and are reachable from the same unauthenticated page.
+
+**Fix:** Apply `await requireAdmin();` consistently at the top of every exported action in this file (or factor the check into a shared wrapper), e.g.:
+```ts
+export async function createLead(data: z.infer<typeof createLeadSchema>) {
+  await requireAdmin();
+  const parsed = createLeadSchema.safeParse(data);
+  ...
+}
+```
+Note: fixing this fully also requires the admin layout/middleware gap (no redirect for unauthenticated `/admin/*` requests) to be addressed, but that is pre-existing and out of this phase's file set — flagging here because the new code makes the inconsistency visible within a single file.
+
+### WR-05: Dead `generate_new` branch in assignQuoteToLead is now unreachable
+
+**File:** `src/app/admin/leads/actions.ts:121-132`
+
+**Issue:** The 14-03 commit message states "remove dead onSubmit branch in SendQuoteModal (CRM-12)" — and indeed `SendQuoteModal.tsx` now only calls `assignQuoteToLead({ lead_id: leadId, quote_token: data.quote_token, generate_new: false })` (hardcoded `false`, line 54 of `SendQuoteModal.tsx`), and the "Crea Nuovo" tab navigates via `window.location.href` without calling the action at all. As a result, the server-side branch:
+```ts
+if (parsed.data.generate_new) {
+  // Redirect handled on client; this is a no-op
+  return { success: true };
+}
+```
+in `assignQuoteToLead` (lines 129-132) is now dead code — `generate_new` is always `false` from the only caller. The `assignQuoteSchema` field `generate_new: z.boolean()` (line 118) and its branch should be removed for consistency with the stated cleanup.
+
+**Fix:**
+```ts
+const assignQuoteSchema = z.object({
+  lead_id: z.string().min(1),
+  quote_token: z.string().optional(),
+});
+
+export async function assignQuoteToLead(data: z.infer<typeof assignQuoteSchema>) {
+  const parsed = assignQuoteSchema.safeParse(data);
+  if (!parsed.success) {
+    return { success: false, error: parsed.error.issues[0].message };
+  }
+  try {
+    const token = parsed.data.quote_token;
+    const leadId = parsed.data.lead_id;
+    if (!token) {
+      return { success: false, error: "Token preventivo richiesto" };
+    }
+    // ... rest unchanged, drop the generate_new check entirely
+  }
+}
+```
+And update `SendQuoteModal.tsx`'s call site / local schema to match (see WR-06).
+
+### WR-06: SendQuoteModal duplicates the assignQuoteSchema with `useForm<any>`, diverging from the 14-03 typing fix
+
+**File:** `src/components/admin/leads/SendQuoteModal.tsx:28-32, 39, 48`
+
+**Issue:** The 14-03 commit `ee509cd fix(14-03): type LeadForm useForm with CreateLeadInput (CRM-11)` typed `LeadForm.tsx`'s `useForm` hooks with `CreateLeadInput` instead of `any`. `SendQuoteModal.tsx` was not updated to match: it still uses `useForm<any>(...)` (line 39) and `onSubmit(data: any)` (line 48), and additionally defines its **own copy** of `assignQuoteSchema` (lines 28-32) that is structurally similar to but independent from the one in `actions.ts` (lines 115-119) — including a `generate_new: z.boolean().default(false)` field that, per WR-05, should be removed server-side. If the two schemas drift (e.g., someone adds a field to one but not the other), `zodResolver` validation on the client and `safeParse` on the server will disagree silently.
+
+**Fix:**
+- Replace `useForm<any>` with a proper type, e.g. infer from a schema that only models what this form actually needs:
+```ts
+const sendQuoteFormSchema = z.object({
+  quote_token: z.string().min(1, "Token richiesto"),
+});
+type SendQuoteFormInput = z.infer<typeof sendQuoteFormSchema>;
+
+const form = useForm<SendQuoteFormInput>({
+  resolver: zodResolver(sendQuoteFormSchema),
+  defaultValues: { quote_token: "" },
+});
+
+async function onSubmit(data: SendQuoteFormInput) {
+  ...
+  const result = await assignQuoteToLead({ lead_id: leadId, quote_token: data.quote_token });
+  ...
+}
+```
+- Remove the local `assignQuoteSchema` duplicate and the unused `lead_id`/`generate_new` fields from the client-side schema — `lead_id` is already known from props and should not be a form field.
+
+## Info
+
+### IN-01: Unused `Button` import in LeadDetail.tsx
+
+**File:** `src/components/admin/leads/LeadDetail.tsx:8`
+
+**Issue:** `import { Button } from "@/components/ui/button";` is imported but never referenced anywhere in the file — all action buttons are rendered inside `LogActivityModal`, `SendQuoteModal`, and `EditLeadModal`, which manage their own `<Button>` triggers.
+
+**Fix:** Remove the unused import:
+```tsx
+// remove this line
+import { Button } from "@/components/ui/button";
+```
+
+### IN-02: StatusCell dispatches an update even when selecting the already-active status
+
+**File:** `src/components/admin/leads/LeadTable.tsx:82-102`
+
+**Issue:** Unlike `EditableCell.commit()` (which has an explicit "skip redundant server action when nothing changed" guard, see `editable-cell.tsx:49-54`), `StatusCell`'s dropdown `onClick` handler calls `run(() => updateLeadField(lead.id, "status", stage))` unconditionally — including when `stage === lead.status`. This triggers an unnecessary `UPDATE`, `revalidatePath`, and `router.refresh()` for a true no-op.
+
+**Fix:**
+```tsx
+onClick={() => {
+  setIsOpen(false);
+  if (stage === lead.status) return;
+  run(() => updateLeadField(lead.id, "status", stage));
+}}
+```
+
+### IN-03: `LeadDetail` prop typed as `Lead` but actually receives `LeadWithTags`
+
+**File:** `src/components/admin/leads/LeadDetail.tsx:40` vs `src/app/admin/leads/[id]/page.tsx:24-30`
+
+**Issue:** `page.tsx` passes `lead={lead}` where `lead` is a `LeadWithTags` (i.e., `Lead & { tags: string[] }`, from `getLeadsWithTags()`), but `LeadDetail`'s prop type declares `lead: Lead`. This happens to type-check because `LeadWithTags` is a structural superset of `Lead`, but it means the component's declared type doesn't reflect what it actually receives (it separately receives `tags: string[]` as its own prop, duplicating data already present on `lead.tags`).
+
+**Fix:** Either type the prop as `LeadWithTags` and drop the separate `tags` prop (reading `lead.tags` directly), or keep `Lead` and have `page.tsx` strip `tags` before passing — for clarity, prefer:
+```ts
+import type { LeadWithTags } from "@/lib/admin-queries";
+
+export function LeadDetail({
+  lead,
+  activities,
+  reminders,
+  tagOptions,
+}: {
+  lead: LeadWithTags;
+  activities: Activity[];
+  reminders: Reminder[];
+  tagOptions: string[];
+}) {
+  // use lead.tags instead of a separate `tags` prop
+}
+```
+
+---
+
+_Reviewed: 2026-06-14T11:35:00Z_
+_Reviewer: Claude (gsd-code-reviewer)_
+_Depth: standard_
diff --git a/.planning/phases/14-crm-attio-style-fix/14-VERIFICATION.md b/.planning/phases/14-crm-attio-style-fix/14-VERIFICATION.md
new file mode 100644
index 0000000..d98f7a4
--- /dev/null
+++ b/.planning/phases/14-crm-attio-style-fix/14-VERIFICATION.md
@@ -0,0 +1,174 @@
+---
+phase: 14-crm-attio-style-fix
+verified: 2026-06-14T13:50:00Z
+re_verified: 2026-06-14T13:20:00Z
+status: passed
+score: 5/5 must-haves verified
+overrides_applied: 0
+gaps: []
+resolved_gaps:
+  - truth: "Il flusso SendQuoteModal (preventivo esistente vs nuovo) non contiene rami di codice irraggiungibili"
+    resolution: "Removed `generate_new: z.boolean()` from assignQuoteSchema and the dead `if (parsed.data.generate_new) { return { success: true } }` branch in src/app/admin/leads/actions.ts (assignQuoteToLead). Removed the matching local schema field, defaultValues entry, and call-site argument from src/components/admin/leads/SendQuoteModal.tsx. `npx tsc --noEmit` clean post-fix. Committed as fix(14): remove dead generate_new branch from assignQuoteToLead (CRM-12)."
+deferred: []
+human_verification:
+  - test: "Open /admin/leads in a browser as an authenticated admin. Click each editable cell (Nome, Email, Telefono, Azienda, Prossima Azione) on a lead row, type a new value, press Enter, and confirm the value persists after the page reflows (router.refresh)."
+    expected: "Each field updates in place without opening a modal; invalid/empty Nome shows a validation error in the row's error <tr>."
+    why_human: "Requires live browser interaction with a running dev server and an authenticated admin session — cannot be exercised via static code inspection."
+  - test: "Click the Stato badge on a lead row — confirm only the 6 closed LEAD_STAGES values are selectable (no free-text/'Crea' option), and selecting a new value updates the badge color per STAGE_COLOR semantics (won=green, lost=red, etc.)."
+    expected: "Closed dropdown with exactly 6 entries, semantic colors applied, persists via updateLeadField."
+    why_human: "Visual/interactive behavior of StatusCell's dropdown."
+  - test: "Click the Tag cell on a lead row, type a brand-new tag name not in the existing pool, and confirm a 'Crea «...»' option appears and creates the tag on Enter/click; then remove it and rename an existing tag from another row to confirm propagation across leads sharing that tag name."
+    expected: "New tags can be created on the fly (CRM-09); removing/renaming works and renameLeadTag propagates to all leads sharing the old tag name."
+    why_human: "Requires live interaction with OptionMultiSelect + server actions + DB state across multiple leads."
+  - test: "Type a query into the /admin/leads search box that matches a lead by name, email, company, status, or tag, and confirm the table filters instantly with no network request (check Network tab)."
+    expected: "Instant client-side filtering; 'Nessun lead trovato' shown when no match."
+    why_human: "Requires browser DevTools network inspection to confirm zero-roundtrip filtering."
+  - test: "Open the FollowUpWidget on the admin dashboard with at least one lead overdue for follow-up, and visually confirm all visible text is Italian ('Richiedi Follow-up', 'X lead da contattare', 'Contatta', 'Vedi Tutto (X)', or 'Tutti i lead sono aggiornati!' if none)."
+    expected: "No English text visible in any state of the widget."
+    why_human: "Visual confirmation of rendered output across both populated and empty states."
+---
+
+# Phase 14: CRM Attio-style & Fix Verification Report
+
+**Phase Goal:** La tabella lead (`/admin/leads`) è ridisegnata in stile Attio/Pipedrive — inline editing dei campi principali e tag multi-select — e i bug residui del modulo CRM (FollowUpWidget non in italiano, LeadForm con type-relaxation, SendQuoteModal con rami irraggiungibili) sono risolti
+
+**Verified:** 2026-06-14T13:50:00Z
+**Re-verified:** 2026-06-14T13:20:00Z
+**Status:** passed
+**Re-verification:** Yes — SC5/CRM-12 gap closed (see Resolution Summary)
+
+## Goal Achievement
+
+### Observable Truths
+
+| #   | Truth   | Status     | Evidence       |
+| --- | ------- | ---------- | -------------- |
+| 1   | La tabella lead supporta inline editing dei campi principali (status, next_action, ecc.) senza apertura di modale | VERIFIED | `src/components/admin/leads/LeadTable.tsx` rewritten as raw `<table>` (no shadcn `Table`/`TableRow`/`TableCell` imports). `LeadRow` uses `EditableCell` for name/email/phone/company/next_action (lines 136-178), each wired to `updateLeadField(lead.id, <field>, v)` via the `run()` transition helper (router.refresh on success). `StatusCell` (lines 41-108) provides a closed click-to-open dropdown over the 6 fixed `LEAD_STAGES` values with semantic `STAGE_COLOR` badges, wired to `updateLeadField(lead.id, "status", stage)`. No modal opens for any of these edits. |
+| 2   | L'utente assegna tag multi-select ai lead, creando nuovi tag al volo | VERIFIED | `LeadTable.tsx` Tag cell (lines 179-187) renders `OptionMultiSelect` with `values={lead.tags}`, `options={options.tags}`, wired to `addLeadTag`/`removeLeadTag`/`renameLeadTag`. `OptionMultiSelect` (`src/components/ui/option-multi-select.tsx` lines 200-209) renders a "Crea «query»" button when the typed query has no exact match, calling `createFromQuery()` → `onAdd(trimmed)` → `addLeadTag`. Server side: `addLeadTag`/`removeLeadTag`/`renameLeadTag` in `src/app/admin/leads/actions.ts` (lines 217-260) insert/delete/update rows in the polymorphic `tags` table scoped to `entity_type="leads"` via `LEADS_TAG_ENTITY` constant, each guarded by `requireAdmin()`. Also surfaced in `LeadDetail.tsx`'s "Profilo" card (lines 90-100) with the same wiring. |
+| 3   | Il `FollowUpWidget` è interamente in italiano, coerente col resto dell'app | VERIFIED | `src/components/admin/dashboard/FollowUpWidget.tsx` (47 lines, fully read): "Richiedi Follow-up" (CardTitle), "{count} lead da contattare" (no pluralization ternary), "Contatta" (button), "Vedi Tutto ({count})" (link), "Tutti i lead sono aggiornati!" (empty state). No English strings remain ("Require Follow-up", "to contact", "Contact", "View All", "up to date" all absent). |
+| 4   | Il form lead (`LeadForm`) valida i campi senza workaround di type-relaxation su react-hook-form | VERIFIED | `src/components/admin/leads/LeadForm.tsx` (full file read): `CreateLeadModal` (line 38) and `EditLeadModal` (line 202) both use `useForm<CreateLeadInput>(...)`, with `CreateLeadInput` imported from `@/lib/lead-validators` (line 6) — no local `type CreateLeadInput = z.infer<...>` redeclaration. The only cast is the narrowing `status: lead.status as CreateLeadInput["status"]` (line 209) — no `as any` or `useForm<any>` anywhere in the file. `npx tsc --noEmit` exits clean (required `src/components/ui/form.tsx` FormField generic-signature fix, made in the same plan, also confirmed present and type-checking). |
+| 5   | Il flusso `SendQuoteModal` (preventivo esistente vs nuovo) non contiene rami di codice irraggiungibili | VERIFIED | `SendQuoteModal.tsx`'s `onSubmit` no longer contains the dead `if (data.tab === "new") {...}` branch (`onSubmit` begins directly with `setLoading(true)`). Post-fix, `assignQuoteToLead` in `src/app/admin/leads/actions.ts` no longer has the `generate_new` field or the dead `if (parsed.data.generate_new) {...}` branch — `assignQuoteSchema` now only has `lead_id`/`quote_token`, and the function body goes straight to `// Link quote to lead and update lead status`. `SendQuoteModal.tsx`'s local schema/defaultValues/call site no longer reference `generate_new`. `npx tsc --noEmit`: "No errors found". |
+
+**Score:** 5/5 truths verified
+
+### Required Artifacts
+
+| Artifact | Expected    | Status | Details |
+| -------- | ----------- | ------ | ------- |
+| `src/lib/admin-queries.ts` | `LeadWithTags`, `LeadFieldOptions`, `getLeadsWithTags()`, `getLeadFieldOptions()` | VERIFIED | All present (lines 884-943). `getLeadsWithTags()` left-joins `leads`+`tags` scoped by `eq(tags.entity_type, LEADS_TAG_ENTITY)` with `LEADS_TAG_ENTITY = "leads"` (line 889), Map-reduce pattern matches `getAllServices` analog. `getLeadFieldOptions()` returns `status: [...LEAD_STAGES]` + distinct sorted lead tag names. |
+| `src/app/admin/leads/actions.ts` | `updateLeadField`, `addLeadTag`, `removeLeadTag`, `renameLeadTag` server actions with `requireAdmin()` guard | VERIFIED | All four present (lines 180-260), each calls `await requireAdmin()` first (line 170-173 helper). `updateLeadField`'s status branch validates against `LEAD_STAGES.includes(...)`, throwing "Stato non valido" before any DB write. Tag CRUD scoped via `LEADS_TAG_ENTITY = "leads"` (line 215). |
+| `src/components/admin/leads/LeadTable.tsx` | Raw-table LeadRow + LeadTable, inline-edit + status/tags dropdowns, `EditableCell` | VERIFIED | Full rewrite confirmed: 8-column raw `<table>`, `StatusCell` local component, `OptionMultiSelect` for tags, "Nessun lead trovato" empty state, per-row error `<tr>`. |
+| `src/app/admin/leads/LeadsSearch.tsx` | Client-side instant search wrapper for LeadTable, `useMemo` | VERIFIED | New file, `useMemo`-based filter over name/email/company/status/tags, renders `<LeadTable leads={filtered} options={options} />`. |
+| `src/app/admin/leads/page.tsx` | Server component fetching `getLeadsWithTags`+`getLeadFieldOptions`, rendering `LeadsSearch` | VERIFIED | Confirmed: `Promise.all([getLeadsWithTags(), getLeadFieldOptions()])`, renders `<LeadsSearch leads={leads} options={options} />` + `CreateLeadModal`, `export const revalidate = 0`. |
+| `src/components/admin/dashboard/FollowUpWidget.tsx` | Italian-only follow-up widget copy, contains "Richiedi Follow-up" | VERIFIED | Confirmed — see Truth 3. |
+| `src/components/admin/leads/LeadForm.tsx` | Typed react-hook-form for lead create/edit, `useForm<CreateLeadInput>` | VERIFIED | Confirmed — see Truth 4. `grep -c "useForm<CreateLeadInput>"` = 2, `grep -c "useForm<any>\|as any"` = 0. |
+| `src/components/admin/leads/SendQuoteModal.tsx` | `onSubmit` without dead 'new' tab branch, contains `onSubmit` | VERIFIED | `onSubmit` is fixed (dead branch removed). The linked server action `assignQuoteToLead` no longer has the `generate_new` dead branch either — see Resolution Summary. |
+
+### Key Link Verification
+
+| From | To  | Via | Status | Details |
+| ---- | --- | --- | ------ | ------- |
+| `src/app/admin/leads/actions.ts` | `src/db/schema.ts` tags table | `db.insert(tags)/db.delete(tags)/db.update(tags)` scoped by `entity_type='leads'` | WIRED | `addLeadTag` inserts (line 222-225), `removeLeadTag` deletes (line 234-242), `renameLeadTag` updates (line 254-257) — all with `eq(tags.entity_type, LEADS_TAG_ENTITY)`. |
+| `src/lib/admin-queries.ts getLeadsWithTags` | `src/db/schema.ts` tags table | `leftJoin` scoped by `entity_type='leads'` | WIRED | `eq(tags.entity_type, LEADS_TAG_ENTITY)` present in the leftJoin condition (line 915). |
+| `src/app/admin/leads/page.tsx` | `src/lib/admin-queries.ts` | `getLeadsWithTags()` + `getLeadFieldOptions()` | WIRED | Both imported and called via `Promise.all`. |
+| `src/components/admin/leads/LeadTable.tsx` | `src/app/admin/leads/actions.ts` | `updateLeadField`/`addLeadTag`/`removeLeadTag`/`renameLeadTag` | WIRED | All four imported (lines 11-16) and called with `lead.id` as first arg in `LeadRow`/`StatusCell`. |
+| `src/app/admin/leads/LeadsSearch.tsx` | `src/components/admin/leads/LeadTable.tsx` | renders `<LeadTable leads={filtered} options={options} />` | WIRED | Confirmed line 43. |
+| `src/components/admin/leads/LeadForm.tsx` | `src/lib/lead-validators.ts` | `import type { CreateLeadInput }` | WIRED | Line 6: `import { createLeadSchema, LEAD_STAGES, type CreateLeadInput } from "@/lib/lead-validators";`. |
+
+### Data-Flow Trace (Level 4)
+
+| Artifact | Data Variable | Source | Produces Real Data | Status |
+| -------- | ------------- | ------ | ------------------ | ------ |
+| `LeadsSearch` → `LeadTable` | `leads: LeadWithTags[]` | `getLeadsWithTags()` (DB left-join, real query against `leads`+`tags` tables) | Yes | FLOWING |
+| `LeadTable` → `OptionMultiSelect` (tags) | `options.tags: string[]` | `getLeadFieldOptions()` → `selectDistinct(tags.name)` where `entity_type='leads'` | Yes | FLOWING |
+| `LeadTable` → `StatusCell` (status options) | `options.status: string[]` | `getLeadFieldOptions()` → `[...LEAD_STAGES]` (fixed constant, not DB-derived but intentionally so per spec) | Yes (static-by-design) | FLOWING |
+| `LeadDetail` → `OptionMultiSelect` (Profilo tags) | `tags: string[]`, `tagOptions: string[]` | `[id]/page.tsx`: `getLeadsWithTags().find(l => l.id === id)` for `tags`, `getLeadFieldOptions().tags` for `tagOptions` | Yes | FLOWING |
+
+No hollow/disconnected props found — all dynamic data on `/admin/leads` and `/admin/leads/[id]` traces back to real DB queries.
+
+### Behavioral Spot-Checks
+
+| Behavior | Command | Result | Status |
+| -------- | ------- | ------ | ------ |
+| Project type-checks cleanly after Phase 14 changes | `npx tsc --noEmit` | "No errors found" | PASS |
+| LeadTable has no shadcn Table wrapper | grep for `from "@/components/ui/table"` in `LeadTable.tsx` | 0 matches (confirmed via full-file read — no such import) | PASS |
+| FollowUpWidget contains zero English strings | Full-file read of `FollowUpWidget.tsx` | "Richiedi Follow-up" / "lead da contattare" / "Contatta" / "Vedi Tutto" / "Tutti i lead sono aggiornati!" present; "Require Follow-up"/"to contact"/"View All"/"up to date" absent | PASS |
+| LeadForm has zero `useForm<any>`/`as any` | Full-file read of `LeadForm.tsx` | 2x `useForm<CreateLeadInput>`, 1x `as CreateLeadInput["status"]`, 0x `as any`/`useForm<any>` | PASS |
+| SendQuoteModal onSubmit has zero `data.tab === "new"` checks | Full-file read of `SendQuoteModal.tsx` | `onSubmit` (line 48) begins with `setLoading(true)`, no `tab` check inside it | PASS |
+| `npm run build` (per task instructions, claimed clean post-merge) | Not re-run (tsc --noEmit alone is sufficient given `next build` invokes the same type-check plus lint; tsc result is clean and matches SUMMARY claim) | N/A | SKIP (tsc sufficient; full build adds >60s with no new signal for this phase's scope) |
+
+### Requirements Coverage
+
+| Requirement | Source Plan | Description | Status | Evidence |
+| ----------- | ---------- | ----------- | ------ | -------- |
+| CRM-08 | 14-01, 14-02 | La tabella lead (`/admin/leads`) supporta inline editing dei campi principali (status, next_action, ecc.) senza apertura modale | SATISFIED | LeadTable.tsx raw-table rewrite + updateLeadField server action, verified above (Truth 1). |
+| CRM-09 | 14-01, 14-02 | L'utente assegna tag multi-select ai lead, creando nuovi tag al volo | SATISFIED | OptionMultiSelect + addLeadTag/removeLeadTag/renameLeadTag, verified above (Truth 2), surfaced both in LeadTable and LeadDetail. |
+| CRM-10 | 14-03 | Il `FollowUpWidget` è in italiano, coerente col resto dell'app | SATISFIED | FollowUpWidget.tsx fully translated, verified above (Truth 3). |
+| CRM-11 | 14-03 | Il form lead (`LeadForm`) valida i campi senza workaround di type-relaxation su react-hook-form | SATISFIED | LeadForm.tsx uses `useForm<CreateLeadInput>()` in both modals, no `as any`/`useForm<any>`, verified above (Truth 4). |
+| CRM-12 | 14-03 | Il flusso `SendQuoteModal` (preventivo esistente vs nuovo) non contiene rami di codice irraggiungibili | SATISFIED | SendQuoteModal.tsx's onSubmit dead branch removed (plan 14-03 Task 3), and the remaining `generate_new` dead branch in `assignQuoteToLead` was removed in the gap-closure fix — see Resolution Summary. |
+
+No orphaned requirements found — all 5 requirement IDs from PLAN frontmatter (CRM-08 through CRM-12) match REQUIREMENTS.md's "CRM Custom Attio-style (v1)" section exactly, and all 5 are claimed across the three plans' `requirements-completed` fields.
+
+### Anti-Patterns Found
+
+| File | Line | Pattern | Severity | Impact |
+| ---- | ---- | ------- | -------- | ------ |
+| `src/app/admin/leads/actions.ts` | 118, 129-132 | Dead `generate_new` branch in `assignQuoteToLead` (unreachable from only caller) | RESOLVED | Removed in gap-closure fix — see Resolution Summary. |
+| `src/components/admin/leads/SendQuoteModal.tsx` | 28-32, 39, 48 | Duplicate local `assignQuoteSchema`, `useForm<any>`, `onSubmit(data: any)` (WR-06) | INFO | Does not block SC4 (SC4 is scoped to "LeadForm" specifically, which is fully fixed) or SC5 (this is a typing/duplication concern, not an unreachable-branch concern). Already logged in `deferred-items.md` with documented technical justification (Resolver/zodResolver generic incompatibility). |
+| `src/app/admin/leads/actions.ts` | 170-260 vs 18-168 | Inconsistent `requireAdmin()` coverage — only new Phase 14 actions guarded (WR-04) | INFO | Pre-existing gap (createLead/updateLead/deleteLead/logActivity/assignQuoteToLead unguarded), explicitly out-of-scope per plan 14-01's interfaces section ("out of scope per RESEARCH.md A5 / Open Question 4"). Does not map to any of the 5 success criteria. |
+| `src/app/admin/leads/actions.ts` | 248-260 | `renameLeadTag` has no try/catch around unique-constraint-violating update (WR-02) | INFO | Real correctness issue for future hardening but not mapped to SC1-5; does not block CRM-09 ("assegna tag multi-select... creando nuovi tag al volo" — core add/remove/create flow works; rename-collision edge case is an error-message-quality issue). |
+| `src/app/admin/leads/actions.ts` | 200-207 | `updateLeadField("email",...)` skips zod email validation (WR-03) | INFO | Does not map to SC1 (inline editing works) or any other SC; a data-quality hardening item for future cleanup. |
+| Multiple (LeadForm EditLeadModal, SendQuoteModal, LogActivityModal) | various | Missing `router.refresh()` after non-inline-edit modal saves (WR-01) | INFO | Affects UX freshness of `/admin/leads/[id]` after modal-based edits, but does not block SC1 (LeadTable inline-edit IS wired with router.refresh, verified) or SC2 (LeadDetail's tag OptionMultiSelect also has its own router.refresh via `run()`, verified). Out of scope for the 5 literal success criteria. |
+
+### Human Verification Required
+
+### 1. Inline-edit persistence on /admin/leads
+
+**Test:** Open `/admin/leads` as authenticated admin. Click Nome/Email/Telefono/Azienda/Prossima Azione cells on a lead row, edit, press Enter.
+**Expected:** Value saves without a modal opening; table reflects new value after `router.refresh()`.
+**Why human:** Requires live browser + authenticated session; cannot exercise server actions statically.
+
+### 2. Status dropdown closed-enum behavior
+
+**Test:** Click the Stato badge on a lead row.
+**Expected:** Only the 6 fixed LEAD_STAGES values appear (no free-text/"Crea" option); selecting one updates the badge with the correct semantic color (won=green, lost=red, etc.) and persists.
+**Why human:** Visual/interactive verification of `StatusCell` dropdown rendering and color mapping.
+
+### 3. Tag create-on-the-fly and rename propagation
+
+**Test:** On the Tag cell, type a brand-new tag not in the option pool and create it; then rename an existing tag shared by multiple leads.
+**Expected:** New tag created and assigned (CRM-09); rename propagates to all leads sharing the old tag name.
+**Why human:** Requires multi-row DB state and live interaction with OptionMultiSelect.
+
+### 4. Instant client-side search
+
+**Test:** Type a query in the `/admin/leads` search box matching by name/email/company/status/tag.
+**Expected:** Table filters instantly with zero network requests (check DevTools Network tab); "Nessun lead trovato" when no match.
+**Why human:** Requires browser DevTools to confirm zero-roundtrip behavior.
+
+### 5. FollowUpWidget visual Italian-only check
+
+**Test:** View the FollowUpWidget on the admin dashboard in both populated and empty states.
+**Expected:** All visible text is Italian in both states.
+**Why human:** Visual confirmation across conditional render branches.
+
+## Resolution Summary
+
+**5 of 5 success criteria are now fully verified with concrete code evidence**: CRM-08 (inline editing, no modal), CRM-09 (lead tag multi-select with create-on-the-fly, wired in both LeadTable and LeadDetail), CRM-10 (FollowUpWidget fully translated to Italian, no English strings remain), CRM-11 (LeadForm.tsx fully typed with `useForm<CreateLeadInput>()`, zero `as any`/`useForm<any>` in the file), and CRM-12 (SendQuoteModal flow, modal + server action, free of unreachable branches).
+
+**SC5 (CRM-12) gap closed.** The initial verification found `onSubmit`'s dead `if (data.tab === "new") {...}` branch correctly removed by plan 14-03, but flagged one residual unreachable branch: `assignQuoteToLead` in `src/app/admin/leads/actions.ts` still contained `if (parsed.data.generate_new) { return { success: true } }`, dead because the only caller (`SendQuoteModal.tsx`) always passed `generate_new: false`. Per user direction ("Fix it now"), this was closed with a small mechanical edit:
+
+- `src/app/admin/leads/actions.ts`: removed `generate_new: z.boolean()` from `assignQuoteSchema` and the entire dead `if (parsed.data.generate_new) {...}` block from `assignQuoteToLead`.
+- `src/components/admin/leads/SendQuoteModal.tsx`: removed `generate_new` from its local `assignQuoteSchema` duplicate, from `defaultValues`, and from the `assignQuoteToLead(...)` call site.
+- `npx tsc --noEmit` → "No errors found" post-fix.
+- Committed as `fix(14): remove dead generate_new branch from assignQuoteToLead (CRM-12)`.
+
+Note: `SendQuoteModal.tsx`'s own `useForm<any>` / duplicate-schema pattern (WR-06, INFO-level) was intentionally left as-is — it's a typing/duplication concern unrelated to the "unreachable branch" criterion and is tracked separately in the code review.
+
+**5 items require human/browser verification** (interactive UI behavior of inline editing, status dropdown, tag multi-select, instant search, and FollowUpWidget visual rendering) — these cover SC1-3, which are code-verified but benefit from a live interaction pass before considering the phase fully closed in practice.
+
+---
+
+_Verified: 2026-06-14T13:50:00Z_
+_Re-verified: 2026-06-14T13:20:00Z_
+_Verifier: Claude (gsd-verifier / gsd-executor gap-closure)_