Dashboard API Integration Audit

Endpoints

Adapter mapper to add to apps/dashboard/src/lib/apiAdapter.ts

// Add imports:
// import scannersApi from "@/features/scanners/services/scannersApi";
// import type { BeScanner } from "@/features/scanners/services/scannersApi";

function mapBeScannerToAdapterRow(s: BeScanner): Record<string, unknown> {
  return {
    id: String(s.id),
    serial_number: s.code,
    model: s.type ?? "",
    name: s.name,
    status: s.status ?? "active",
    status_id: s.status_id,
    condition: s.condition ?? "",
    condition_id: s.condition_id,
    type: s.type ?? "",
    type_id: s.type_id,
    auditor: s.auditor ?? null,
    assigned_date: s.assigned_date ?? null,
    created_at: s.assigned_date ?? "",
  };
}

MAPPERS["scanners"] = {
  fetch: async (filters) => {
    try {
      const result = await store
        .dispatch(
          scannersApi.endpoints.getScanners.initiate({
            page: 1,
            number_per_page: 100,
            sort: "desc",
            sort_by: "assigned_date",
          }),
        )
        .unwrap();
      const rows = (result.data ?? []).map(mapBeScannerToAdapterRow);
      return { data: applyFilters(rows, filters) as unknown[], error: null };
    } catch (error) {
      console.error("MAPPERS[scanners] fetch failed:", error);
      return { data: null, error: error as Error };
    }
  },
};

// scanner_facility_assignments: GAP noop stub stays until BE ships the endpoint.

Caveats

1. useScanners.ts already bypasses the adapter (calls useGetScannersQuery directly). Mapper covers only residual supabase.from("scanners") call sites (e.g. confidence.ts).
2. scanner_facility_assignments is a confirmed GAP. Scanners page degrades gracefully: facility column shows "Pending assignment". Confidence score underweights scanner count until BE ships.
3. "last used by" column uses a mock hash function — no BE audit-log source. Intentional.
4. No DELETE /company/scanner endpoint exists. Delete button already disabled.
5. transferScanner takes user_id (numeric), NOT facility_id. "Assign to Facility" dialog intentionally disabled (BE-blocked).
6. Dashboard scannersApi already uses baseApi.injectEndpoints with 'Scanner' tag. No tagTypes change needed.

BE spec for scanner_facility_assignments (GAP — hand to backend)

Endpoints

Adapter mapper (already live — reproduced with fix)

function mapSatAuditToRow(a: SatAuditItem): Record<string, unknown> {
  // Fix: read both purchase_order and po_number (field name varies by BE version)
  const poNumber = (a.reference as any)?.purchase_order
    ?? (a.reference as any)?.po_number
    ?? null;
  return {
    id: String(a.id),
    session_id: a.id,          // no real session join; audit id as stand-in
    ft_id: a.fibretrace_id ?? null,
    blockchain_guid: null,     // no BE source on sat-audits
    result: a.status ?? null,  // "PROCESSED"/"PENDING" - see caveat 4
    notes: poNumber ? `PO: ${poNumber}` : (a.reference as any)?.notes ?? null,
    created_at: a.created_at,
    deleted_at: null,
  };
}

Caveats

1. Reference field name: dashboard uses po_number, canonical SAT uses purchase_order. The fix above reads both. Verify actual BE response before deploying.
2. session_id uses audit's own id. Sessions column shows "—" — correct behavior.
3. blockchain_guid always null. AuditsTable does not render this column.
4. result maps "PROCESSED"/"PENDING" to Lovable's "pass"/"fail"/"warning" column. Badge color falls through to "warning" style — semantic mismatch until BE exposes pass/fail/warning.
5. All AdminVerifications mutations already stub-blocked with toast.info(). No call-site RTK migration needed.
6. Dashboard auditsApi.ts does not yet register 'Audits' tag in baseApi.tagTypes. keepUnusedDataFor: 0 is used instead — works but prevents cross-endpoint cache invalidation.

Endpoints

Adapter mapper (already live at apiAdapter.ts:349-371 — DO NOT re-apply)

function mapPublicCompanyToRow(c: PublicCompanyBeRow): Record<string, unknown> {
  return {
    id: String(c.uid ?? c.id ?? ""),
    name: c.name ?? "",
    confidence_score: null,    // no BE source; Lovable-only field
    confidence_rating: null,   // no BE source; Lovable-only field
    confidence_summary: null,  // no BE source; Lovable-only field
  };
}

Caveats

1. confidence_score / confidence_rating hard-coded null — BE returns only uid + name. Confidence UI remains empty until BE adds those fields.
2. No mutations target the companies table. usePartners.ts mutations all target company_partners — separate scope.
3. Slice (companiesPublicApi.ts) and MAPPERS["companies"] are both already live. No new files or edits required.

Endpoints

Field mapping (BE → Lovable)

Caveats

1. Already implemented — no new files or edits needed for the fetch path.
2. companies(name) join: list endpoint does not join company info. Column always shows "—".
3. pdf_url and notes are Lovable-only — mapped to empty strings.
4. Admin invoice CRUD mutations already throw not_implemented. No canvas write equivalent.
5. Verify BE actually returns paginated shape { data: Invoice[]; meta: { total: number } }.

Endpoints (both already in userApi.ts)

notification_templates — BE spec (GAP)

Caveats

1. SettingsNotifications.tsx is FULLY WIRED. The apiAdapter no-op stub is a crash-guard only.
2. notification_templates is a genuine GAP. AdminNotifications.tsx already has TODO comments and toast stubs for all mutations — UI does not crash.
3. PUT /api/v2/user: VITE_API_URL must be the bare API origin (not ending in /api/v1). Verify .env before shipping.
4. Canvas gates 3 admin-only OPT_IN keys behind is_company_admin. Dashboard shows all 10 unconditionally. Wire user.is_company_admin if product requires gating.

Endpoints

Adapter changes (apply these)

// MAPPERS["collections"] is ALREADY wired (apiAdapter.ts:388-408) — DO NOT replace.

// MAPPERS["verifications"] — wire to GET /orders/:code/processes.
// Only works for filtered calls (.eq("collection_id", orderCode)).
MAPPERS["verifications"] = {
  fetch: async (filters) => {
    try {
      const orderCode = filters.eq?.["collection_id"] as string | undefined;
      if (!orderCode) {
        return { data: [], error: null };
      }
      const result = await store
        .dispatch(
          collectionsApi.endpoints.getOrderProcesses.initiate(orderCode),
        )
        .unwrap();
      const rows = (result.data ?? []).map((p: OrderProcess) =>
        mapProcessToVerification(p, orderCode),
      );
      return { data: applyFilters(rows, filters) as unknown[], error: null };
    } catch (error) {
      console.error("MAPPERS[verifications] fetch error:", error);
      return { data: null, error: error as Error };
    }
  },
};

function mapProcessToVerification(
  p: OrderProcess,
  orderCode: string,
): Record<string, unknown> {
  return {
    id: String(p.id),
    collection_id: orderCode,
    name: (p as any).name ?? `Process ${p.id}`,
    status: (p as any).status != null ? String((p as any).status) : "active",
  };
}

// MAPPERS["sessions"] — GAP stub (must NOT wire to processes; field-set mismatch).
MAPPERS["sessions"] = {
  fetch: async (_filters) => ({ data: [], error: null }),
};

// MAPPERS["session_shares"] — GAP stub.
MAPPERS["session_shares"] = {
  fetch: async () => ({ data: [], error: null }),
};

Slice extension — add getOneProcess to collectionsApi.ts

getOneProcess: builder.query<{ data: OrderProcess }, { orderCode: string; processId: string | number }>({
  query: ({ orderCode, processId }) => ({
    url: `orders/${orderCode}/processes/${processId}`,
    method: 'GET',
  }),
  providesTags: (_result, _error, { orderCode, processId }) => [
    { type: 'Verifications', id: `${orderCode}-process-${processId}` },
  ],
}),

// Add to exports:
export const {
  useGetOrdersQuery,
  useLazyGetOrdersQuery,
  useGetOrderByCodeQuery,
  useLazyGetOrderByCodeQuery,
  useGetOrderProcessesQuery,
  useLazyGetOrderProcessesQuery,
  useGetOneProcessQuery,       // NEW
  useLazyGetOneProcessQuery,   // NEW
} = collectionsApi;

Call-site mutations — replace with BE-pending toast

• CreateCollectionFlow.tsx:151-160 — supabase.from('collections').insert(...) — adapter throws. Replace with BE-pending toast until BE confirms POST /orders field mapping (order_name vs name).
• CreateCollectionFlow.tsx:174-177 — supabase.from('verifications').update({ collection_id }) — GAP mutation. BE-pending toast.
• AddVerificationsModal.tsx:137-140 — same GAP mutation. BE-pending toast.

BE spec for gaps

id                   uuid  PK
session_code         text  — human-readable code
conducted_at         timestamptz
fibre_detected       text  — fibre type label
scan_count           int
facility_id          uuid  FK -> facilities.id
verification_id      uuid  FK -> verifications.id
production_record_id uuid  nullable FK
auditor_name         text
pigment_id           uuid  nullable FK -> pigment_ids.id
deleted_at           timestamptz nullable

Caveats

1. COLLECTIONS mapper is ALREADY wired and correct. The useCollections hook computes verificationCount/sessionCount/scanCount via sub-queries — these will be 0 until verifications and sessions are wired.
2. VERIFICATIONS mapper only works for filtered calls. Unfiltered calls (by facility_id) return [].
3. SESSIONS mapper: ProcessProcesList is missing 6 required fields. A new BE endpoint or response extension is required. SessionDetail.tsx and VerificationPreview.tsx will return empty/null data.
4. programme_id in CollectionRow mapped to null — fibre_programmes is a Lovable-only table. Consumers resolving fibre_type via programme_id always get empty string.
5. session_shares: is_shared / shared_with_company_name fields always false/null.