Bryan Helmkamp a8599a924f feat(install): pivot happy path to fabro server start web wizard ... The primary install flow is now to start the server, complete setup in a browser-based wizard, and restart. fabro install is retained as the headless CLI-only alternative. - Auto-open the install URL in the user's browser when fabro server start enters install mode; print a manual-open fallback when open::that fails - Rewrite install.md so agents drive the full start → wait → restart loop - Retarget install.sh Y/n prompt from fabro install to fabro server start - Update README, quick-start, deploy-server, cli reference, and marketing captions to point at fabro server start as the next step after download - Add troubleshooting entries for "wizard didn't open" and "server exited after wizard" Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-21 16:02:49 -04:00
..
src	feat(install): pivot happy path to fabro server start web wizard	2026-04-21 16:02:49 -04:00
tests/it	refactor(oauth): brand CLI callback pages to match the Fabro auth theme	2026-04-21 16:02:49 -04:00
build.rs	feat(cli): surface debug build profile in version output	2026-04-18 09:44:54 -04:00
Cargo.toml	refactor(client): extract fabro-client crate	2026-04-20 20:42:20 -04:00