5 Commits

Include renames

Author	SHA1	Message	Date
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-yoloandClaude Opus 4.8	1cafa2c2af	fix(maestro): install maestro without the registry feature ... The installer's cargo install of the umbrella maestro crate built the default feature set (cli+daemon+registry+tui), forcing every host to compile the registry — which a host neither needs nor runs (the registry is a separate, centrally-deployed service). Install with --no-default-features --features cli,daemon,tui instead. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-05-29 06:42:43 +00:00
naps62-yolo	ade0d49096	chore(maestro): retarget installer, e2e harness, and docs at unified maestro binary (NAP-245) ... - Installer: one `cargo install maestro` instead of two; ExecStart becomes `~/.cargo/bin/maestro daemon`; user unit renamed `maestrod.service` → `maestro.service`; configure step is `maestro daemon configure`. - E2E harness: both `Daemon` and `Registry` subprocess wrappers shell out to the unified `maestro` binary with the appropriate subcommand. - State dir: `~/.local/state/maestrod` → `~/.local/state/maestro`. - Docs: CLAUDE.md repo layout, design spec repo layout + "Daemon (`maestro daemon`)" heading, INSTALL.md (full rewrite of CLI references + new thin-builds section).	2026-05-27 10:43:51 +00:00
naps62-yolo	476a414c6f	feat(maestro): make installer re-run safe (auto-detect = update) ... The wizard now treats existing state as "we're updating, not installing": - If `~/.config/maestrod/config.toml` exists, skip the configure prompt with a clear notice. Sets `configured = true` so the systemd start logic still makes sense. - If the systemd user unit already exists, refresh the file in place, skip the enable prompt (it's either already enabled or the user said no last time), and ask to `restart` instead of `start` — so the new binary actually takes effect. Adds `SystemctlAction::Restart` and a test for it. Same `./install.sh` works for both first install and subsequent updates; no `--update` flag. Refs NAP-225.	2026-05-25 15:07:09 +00:00
naps62-yolo	2da41cc720	feat(maestro): add maestro-install wizard (cargo install + systemd) ... New `maestro-installer` crate exposing the `maestro-install` binary. Bootstrap flow: `cargo install --git ... maestro-installer && maestro-install` runs `cargo install` for `maestro-daemon` and `maestro-cli`, optionally drives `maestrod configure`, and on systemd hosts writes a user unit at `~/.config/systemd/user/maestrod.service` plus reload/enable/start. Pure builders (cargo install args, systemctl args, unit body) live in the lib and are unit-tested; main.rs is the prompt glue. Refs NAP-225.	2026-05-25 14:30:03 +00:00