T3 CLI concurrent install — BEFORE Linux x86_64 | released CLI 0.1.10 | isolated fresh T3 home Installer commit a99faf5a629023a5aca16fc8422553a5a4a9067f Same home + version; publication barrier forces the reported interleaving. [1] Finding your release... [2] Finding your release... [2] Installing T3 Code 0.1.10 [1] Installing T3 Code 0.1.10 [2] [1] [2] Downloading... [1] Downloading... [1] Verifying the download... [1] Extracting T3 Code... [1] [scheduler] installer 1 reached publication after destination removal [2] Verifying the download... [2] Extracting T3 Code... [2] [scheduler] installer 2 reached publication after destination removal [1] [scheduler] installer 1 executing real /usr/bin/mv [1] Setting up the t3 command... [2] [scheduler] installer 2 executing real /usr/bin/mv [2] Setting up the t3 command... [1] Installed T3 Code 0.1.10 [1] Installed launcher is available at $RUN/bin/t3. [1] [2] Installed T3 Code 0.1.10 [2] Installed launcher is available at $RUN/bin/t3. [2] Installer exit codes: [0, 0] Inspection with hidden files visible (relative to runtime/versions): 0.1.10/.install-complete 0.1.10/.staging-azN9QK/ .staging-azN9QK/.install-complete .staging-azN9QK/client/ .staging-azN9QK/lib/ .staging-azN9QK/node_modules/ .staging-azN9QK/resource-monitor/ .staging-azN9QK/t3 0.1.10/client/ 0.1.10/lib/ 0.1.10/node_modules/ 0.1.10/resource-monitor/ 0.1.10/t3 Published executable --version: t3 v0.1.10 Nested executable --version: t3 v0.1.10 Nested .install-complete: 0.1.10 Nested staging runtime count: 1 RESULT: BUG — complete duplicate retained despite both installers succeeding