From 70a669d3c61ad61b1deac61f5ea6c8bf7074a55e Mon Sep 17 00:00:00 2001
From: ospab <gvoprgrg@gmail.com>
Date: Sat, 18 Jul 2026 15:10:57 +0300
Subject: [PATCH] fix(install): setup wizard is a subcommand now, not a --setup
 flag

Both installers still invoked `ostp --setup` / `ostp.exe --setup` to launch
the first-run wizard on a fresh install. The CLI's subcommand refactor
(2026-07-08, "Refactor CLI to subcommands") turned `setup` into
`Commands::Setup { .. }` with no top-level `--setup` flag left in Args at
all, so every fresh install has hit "error: unexpected argument '--setup'
found" and dropped the user out of the installer instead of the wizard.
Verified `ostp setup --help` parses correctly with the fix.
---
 scripts/install.ps1 | 2 +-
 scripts/install.sh  | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/install.ps1 b/scripts/install.ps1
index 0b09224..bc8527d 100644
--- a/scripts/install.ps1
+++ b/scripts/install.ps1
@@ -138,5 +138,5 @@ Write-Host "No configuration found. Launching setup wizard..."
 Write-Host ""
 
 Push-Location $InstallDir
-& .\ostp.exe --setup
+& .\ostp.exe setup
 Pop-Location
diff --git a/scripts/install.sh b/scripts/install.sh
index 0ee5276..5b09f36 100644
--- a/scripts/install.sh
+++ b/scripts/install.sh
@@ -238,4 +238,4 @@ echo "No configuration found. Launching setup wizard..."
 echo ""
 
 cd "$INSTALL_DIR"
-exec ./ostp --setup --config "$CONFIG_FILE"
+exec ./ostp setup --config "$CONFIG_FILE"