naps62-yolo
2aa2d3e20d
ci / rust (push) Successful in 2m9s
After the daemon-unit step, the wizard now offers a second user unit (`maestro-web.service`) that runs `maestro-registry` on 127.0.0.1:8888 so the web UI is reachable in a browser locally. Decisions: - The unit runs `maestro-registry` directly — the web bundle is already embedded in that binary, so a separate `maestro-web` binary would be pure cost. `Description=` and the unit filename make the user-facing framing clear. - `Wants=maestrod.service` + `After=` (not `Requires=`): the registry process doesn't actually need the daemon to start; the web UI just has nothing to show without one. Soft dependency expresses that. - Default loopback bind is `127.0.0.1:8888` to make it obvious which port is the local UI vs a separately deployed registry on `:8080`. Wizard surface: - New prompt (default *no*) after the daemon-systemd step. - New flags: `--no-web`, `--web-bind <addr>`, `--web-exec-start <path>`. - Skipped automatically when systemd is absent or `--no-systemd` is set. - The re-run/update path mirrors the daemon flow: refresh the unit, daemon-reload, restart instead of start. - `maestro-registry` is only `cargo install`ed when the user opts in, keeping the no-web install footprint unchanged. docs/INSTALL.md gets the new flags + a full sample unit body.