[Issue]: Windows v2.1.0 updater build step fails when pnpm is not globally available

[SpicyMarinara]

Summary

Updating to v2.1.0 on Windows can fail during the build stage if pnpm is not globally available, even though Corepack uses pnpm 10.33.2 for dependency installation. The launcher appears to call pnpm build directly through cmd.exe, which fails when corepack enable or a global pnpm install has not been configured.

Expected behavior

The launcher should reliably run the build step by checking for global pnpm, invoking pnpm through Corepack such as corepack pnpm build, or documenting corepack enable as a prerequisite.

Actual behavior

Dependency installation succeeds using Corepack-managed pnpm 10.33.2, but the build step fails because Windows does not recognize the pnpm command. A launcher script typo is also visible: "ALLBACK"=="1" is not recognized...

Steps to reproduce

1. Use a Windows machine with Node.js installed.
2. Do not run corepack enable globally and do not install pnpm globally.
3. Run the Marinara Engine updater/launcher to update to v2.1.0.
4. Observe dependency installation succeeding, followed by the build step failing when pnpm build is executed.

Environment

• Marinara Engine version: v2.1.0
• Install type: Not provided
• OS + version: Windows, version not provided
• Browser or app shell: Marinara Engine launcher, details not provided

Logs, screenshots, or video

Reported visible error: "ALLBACK"=="1" is not recognized.... User also reported that Windows fails to recognize pnpm during pnpm build. Full log output was not provided in the Discord context.

Additional context

Suggested workaround from support: exit Marinara Engine, open Command Prompt, cd to the Marinara Engine location, run pnpm install, then pnpm build, then run Marinara Engine and press Ctrl+Shift+R when the window opens. Maintainer noted this may explain multiple pnpm-related issues.

Discord thread: Updating to v2.1.0
Discord thread link: https://discord.com/channels/1417099416812392641/1523937252927864873
Requested by: Marinara (marinara_spaghetti, Discord ID 169561011928432653)

Discord thread transcript (3 messages)

[2026-07-07T06:22:34.483Z] Expick: Updating to v2.1.0 caused an error, which I resolved with AI help. I also asked the AI ​​to file a bug report. I'm just not very knowledgeable about this stuff myself.

### Description
During the latest update to v2.1.0, the launcher fails at the building stage. While Corepack aligns and uses `pnpm 10.33.2` internally to install dependencies, the subsequent execution of `pnpm build` is passed directly to the Windows command line (`cmd.exe`). If `corepack enable` or a global `pnpm` installation hasn't been run beforehand on the system, Windows fails to recognize the command, halting the update.

There is also a syntax typo visible in the launcher script: `"ALLBACK"=="1" is not recognized...`

### Steps to Reproduce
1. Have a Windows machine with Node.js installed, but without `corepack enable` run globally.
2. Run the Marinara Engine updater/launcher.
3. Observe the dependency installation succeeding, but the build step failing.

### Expected Behavior
The launcher should either check if `pnpm` is available globally in the system environment before running native shell commands, use Corepack explicitly to call the build script (`corepack pnpm build`), or document the need for `corepack enable` in the prerequisites.

### Actual Log Output
[Discord message: https://discord.com/channels/1417099416812392641/1523937252927864873/1523937252927864873]

[2026-07-07T07:52:04.620Z] kolache: exit out of Marinara Engine, open command prompt, cd to your Marinara Engine location, run “pnpm install” then “pnpm build”, when they are done run Marinara Engine and ctrl+shift+R when the window opens
[Discord message: https://discord.com/channels/1417099416812392641/1523937252927864873/1523959776915226656]

[2026-07-07T07:52:34.019Z] kolache: ty for the report will look into it that is probably why there’s so many pnpm-related issues
[Discord message: https://discord.com/channels/1417099416812392641/1523937252927864873/1523959900223443004]

Template check

Please uncheck (untick) the box below before submitting so we know you read the template. It is intentionally pre-checked:

• I DID NOT read this template and provide the requested details.

[SpicyMarinara]

Codex is picking this up for the v2.1.1 issue sweep in draft PR #3331.

[SpicyMarinara]

Fixed in PR #3331 and merged to staging for v2.1.1. Thank you for the report.