feat(adminsite): test harness, typed client and the not-connected state

The repo's first frontend test setup: Vitest, React Testing Library, jsdom.
Scoped to the flows that lose money or leak data when broken, per spec 4.

lib/api.ts collapses every failure into three the UI can act on:
NotConnected (unreachable, or no URL baked in), ApiError 401 (redirect), and
ApiError with the backend's own message, which is customer-facing and shown
verbatim rather than replaced with something vaguer.

The not-connected panel names the variable, the value baked in, and both
reasons it fails -- unreachable from the browser, or missing from admin's
ADMIN_ORIGIN. Proven by test before it existed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

This commit is contained in:

mrhid6

2026-07-25 20:57:51 +01:00

co-authored by

Claude Opus 5

parent 6953f5e972

commit 3e447fd024

7 changed files with 346 additions and 0 deletions

									
										adminsite/test/setup.ts
									
		+8
		
												View File
												
				@@ -0,0 +1,8 @@

				import "@testing-library/jest-dom/vitest";

				import { cleanup } from "@testing-library/react";

				import { afterEach, vi } from "vitest";

				afterEach(() => {

				    cleanup();

				    vi.restoreAllMocks();

				});