2 Commits

Include renames

Author	SHA1	Message	Date
naps62-yoloandClaude Opus 4.7	50f24a2cf9	fix(maestro): pin pnpm via packageManager so corepack doesn't grab v11 ... The Dockerfile's `web-builder` stage (NAP-218) uses Node 20 + corepack. Without a `packageManager` field, corepack defaulted to pnpm@latest, which is now 11.3.0 — that release requires Node ≥22.13 and imports `node:sqlite`, so it dies on Node 20 with `ERR_UNKNOWN_BUILTIN_MODULE: node:sqlite`. Dokploy builds were failing in the `pnpm install` step. Pin pnpm@9.15.4 (latest 9.x, fully Node-20 compatible). No code change to the web bundle itself. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-25 10:44:34 +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