Files
autocraft/web/README.md
aiongg b7b2aaaab6 Serve the React frontend over the JSON API; operator, maintainer and viewer roles
- web/: an HTTP client for the Api interface (CSRF from the X-CSRF-Token
  response header, errors carry the server's text, 401 goes to sign-in);
  the mock API and its view-as menu only in VITE_MOCK=1 builds; the clock
  is real time outside the mock; nav links to the server-rendered pages.
- Server: serves web/dist (CRAFT_AUTO_WEB_DIST) behind sign-in, hashed
  assets cached a year, index.html uncached for every client route, a 503
  page when the build is missing; a strict CSP for the app with the hash
  of the Radix scroll-lock style.
- The v1 Decisions, Item and Progress pages are gone; Contributors,
  Classifiers, Run and cost, Repos and Access stay at their paths.
- Access roles operator, maintainer and viewer; rows with role admin
  become operator on connect.
- v1 form POSTs and sign-out refuse a foreign Origin or Sec-Fetch-Site.
2026-11-02 18:11:09 +00:00

736 B

Triage dashboard frontend

React + TypeScript + Vite + Tailwind. Design: docs/ui-design.md.

pnpm install
pnpm dev      # http://127.0.0.1:5173, mock API with fixture data
pnpm build    # tsc, then dist/ (no inline scripts or styles; fonts bundled)
VITE_MOCK=1 pnpm build   # the mockup: dist/ on fixture data, no server needed

A normal build talks to the dashboard server's JSON API (src/api/http.ts), and the server serves dist/ behind sign-in. The dev server and the mockup build run against createMockApi() (src/api/mock/); pick the signed-in role with ?as=operator|maintainer|viewer or the user menu.

A feature is a module in src/modules/<name>/ listed in src/registry/index.ts.