v0.14.0 — rename PSLauncher.exe → PS_Launcher.exe (with backward compat)

Aligns the executable name with the repo / product naming. Backward-
compatible: existing installs that have PSLauncher.exe on disk continue
to work — the self-updater overwrites the file at the running .exe path
without renaming, so the historical filename persists on those machines.

Changes
- AssemblyName : PSLauncher → PS_Launcher (both App and Updater csproj)
- Inno Setup : MyAppExeName, MyUpdaterExeName, OutputBaseFilename all
  now use PS_Launcher prefix
- LauncherSelfUpdater : looks for PS_Launcher.Updater.exe first, falls
  back to legacy PSLauncher.Updater.exe so old installs keep updating
- Build scripts (build-launcher / build-updater / build-installer /
  build-all) : taskkill both legacy AND new names; output paths printed
  with new names
- .gitignore : added PS_Launcher.exe / PS_Launcher.Updater.exe /
  PS_Launcher-*.exe patterns alongside the legacy ones; also ignored
  the WebView2 user-data folder and Office ~$ lock files
- Server admin/launcher.php : URL pattern now generates
  PS_Launcher-{ver}.exe ; SignManifest's existing tolerant glob
  *{ver}*.exe still matches both names
- Versions bumped to 0.14.0 (App + Updater + installer .iss)

Migration story for clients
- Brand-new install via PS_Launcher-Setup-0.14.0.exe → PS_Launcher.exe
  on disk
- Existing install (PSLauncher.exe) auto-updates to v0.14 → file stays
  named PSLauncher.exe but contains v0.14 code; self-updater fallback
  ensures future updates keep working

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

server/admin/launcher.php

@@ -53,14 +53,14 @@ if ($_SERVER['REQUEST_METHOD'] === 'POST') {
                 'version'         => $lver,
                 'minRequired'     => $lmin !== '' ? $lmin : '0.5.0',
                 'download'        => [
-                    'url'       => "{$base}/builds/launcher/PSLauncher-{$lver}.exe",
+                    'url'       => "{$base}/builds/launcher/PS_Launcher-{$lver}.exe",
                     'sizeBytes' => 0,
                     'sha256'    => 'REPLACE_AFTER_BUILD',
                 ],
                 'releaseNotesUrl' => null,
             ];
             saveManifest($manifestPath, $manifest);
-            $message = "Section launcher mise à jour (v{$lver}). Upload PSLauncher-{$lver}.exe dans builds/launcher/ puis clique « Hasher le launcher + signer ».";
+            $message = "Section launcher mise à jour (v{$lver}). Upload PS_Launcher-{$lver}.exe dans builds/launcher/ puis clique « Hasher le launcher + signer ».";
         }
         elseif ($action === 'remove_launcher') {
             unset($manifest['launcher']);
@@ -130,7 +130,7 @@ Layout::header('Launcher', 'launcher');
     <ol class="muted">
         <li>Remplis le formulaire <strong>Définir / mettre à jour</strong> ci-dessous (ex : <code>0.6.0</code>).</li>
         <li>Sur ton poste : <code>dotnet publish src\PSLauncher.App -c Release</code> et <code>dotnet publish src\PSLauncher.Updater -c Release</code> (les exes sont copiés à la racine du repo).</li>
-        <li>Renomme la copie : <code>PSLauncher.exe → PSLauncher-X.Y.Z.exe</code>.</li>
+        <li>Renomme la copie : <code>PS_Launcher.exe → PS_Launcher-X.Y.Z.exe</code> (v0.14+ ; ancien nom <code>PSLauncher.exe</code> reste accepté côté serveur via le glob <code>*{ver}*.exe</code>).</li>
         <li>Upload via SFTP dans <code>www/PS_Launcher/builds/launcher/</code>.</li>
         <li>Clique <strong>🔁 Hasher le launcher + signer</strong>.</li>
         <li>Les launchers déjà déployés détecteront la nouvelle version au prochain « Vérifier les MAJ ».</li>