4 Commits

Include renames

Author	SHA1	Message	Date
Miguel Palhas	0061378193	feat(maestro): scaffold React + Tailwind + Zustand ... Adds react, react-dom, zustand, tailwindcss, @tailwindcss/vite as a new skeleton alongside the existing vanilla SPA. New src/index.tsx entry point (unused until wired into index.html in a later issue); main.ts stays the active entry.	2026-09-09 00:01:33 +01:00
Miguel Palhas	c856333e4a	docs(maestro): describe the single-host architecture ... Rewrites CLAUDE.md as the current-architecture reference, drops the registry from INSTALL/PRODUCT/DESIGN and the web README, deletes the registry Dockerfile, and marks the dated design specs superseded where they describe the registry, JWT auth, or cross-host attach. The installer loses its configure step — every config field now has a default, so a daemon starts with no config file at all.	2026-08-22 10:26:49 +01:00
naps62-yolo	f0b01ae295	feat(maestro): let vite dev proxy honor \$MAESTRO_REGISTRY ... `web/vite.config.ts` was hard-coded to proxy `/api` at `http://127.0.0.1:8080`, so pointing the dev UI at a remote registry meant hand-editing the file. Read `MAESTRO_REGISTRY` from the environment via `loadEnv` instead, with the local default preserved. Accept either the HTTP base URL (`https://…`) or the daemon-facing URL (`wss://…/daemon`) — the latter is rewritten to `https://…` and the `/daemon` suffix stripped, since the proxy needs the HTTP origin. Flips `changeOrigin: true` for HTTPS upstreams so the proxied Host matches the cert. Documented under `web/README.md` § Dev.	2026-05-25 15:35:57 +00:00
naps62-yoloandClaude Opus 4.7	e68c9b6d73	feat(maestro): web client (Vite + TS + xterm.js) ... NAP-218. Browser UI for the prototype: catalog tree derived from `metadata.label`, live updates over `WS /api/events`, search across session name+label, spawn modal (with optional git worktree), and an attach view that opens the daemon's per-session WS for xterm.js. Framework choice: vanilla TypeScript. The interactivity surface is small enough that pulling in a framework wouldn't pay back; xterm.js does the heavy lifting. Easy to swap later without protocol impact. Hash-based routing (`#/`, `#/attach/<id>`) keeps the registry's static surface dumb — no SPA fallback needed; concurrent attaches work by opening the same hash URL in another tab. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-25 09:57:11 +00:00