Failed attempt to not open IPA.exe window

README.md

@@ -106,9 +106,10 @@ py -m plugin_helper
 py -m plugin_helper --config plugin-helper.windows.toml --profile windows installed --instance 1.44.1
 ```
 
-On native Windows, `bootstrap` runs `IPA.exe -n` directly instead of through
-Proton. `bootstrap-check` accepts a recorded native bootstrap without requiring
-`Logs/_latest.log` when `IPA.exe -n` completed successfully.
+On native Windows, `bootstrap` runs `IPA.exe "Beat Saber.exe" -n` directly
+instead of through Proton. `bootstrap-check` accepts a recorded native bootstrap
+without requiring `Logs/_latest.log` when `IPA.exe "Beat Saber.exe" -n`
+completed successfully.
 
 When no config file is present on Windows, defaults are
 `~/BSManager/BSInstances` and `%LOCALAPPDATA%/plugin-helper`.
@@ -212,10 +213,10 @@ custom content or non-obvious user choices rather than pure cache data.
   arguments such as `--no-yeet fpfc` can make the game fail command-line
   parsing after BSIPA and plugins have already loaded.
 - BSIPA is managed as a first-class bootstrap phase. The `bootstrap` command
-  applies the locked `bsipa` root archive, runs `IPA.exe -n` (natively on
-  Windows or through Proton on Linux), and records every bootstrap-relevant
-  file under root `IPA.exe*`, `winhttp.dll`, `Libs/`, and `IPA/`, including
-  backups created during patching.
+  applies the locked `bsipa` root archive, runs `IPA.exe "Beat Saber.exe" -n`
+  (natively on Windows or through Proton on Linux), and records every
+  bootstrap-relevant file under root `IPA.exe*`, `winhttp.dll`, `Libs/`, and
+  `IPA/`, including backups created during patching.
 - If an instance version lock includes `bsipa`, ordinary plugin plans require a
   recorded bootstrap state plus a `Logs/_latest.log` that shows BSIPA startup.
   Use `bootstrap-check` before planning a batch when you want a quick gate.