# MiniMax npm 12 real-app reproduction

Environment: Linux x64, Chromium 151, light theme, 1440×900; npm 12.2.2,
MiniMax Code 0.2.7 from the live ACP Registry. No MiniMax account or API key.

Base: 9efd960925f0899c0a6d045d128557c5d82818e8
Head: 2bea70f6a370654328994fc29506ae702956887a

1. Install dependencies in both checkouts with `vp i`.
2. Install npm 12.2.2 into an isolated scratch prefix. Expose its npm-cli.js
   through the base checkout's ignored node_modules/.bin/npm symlink.
3. Run the base with `T3CODE_DEV_SEED=0 vp run dev`. Confirm from the actual
   server process's environment that `npm --version` is 12.2.2 and that no
   npm script-policy variables are present.
4. Pair the browser, open Settings > Providers > Add provider > Show more.
   Search MiniMax, choose Add MiniMax Code, then Continue to sign-in.
   Observe failed sign-in discovery. Skip for now and select MiniMax Code.
5. Refresh provider status. Record the failure. The paired recordings cover
   this identical refresh action on each revision.
6. Create an empty synthetic git project, add it with the real `t3 project add`
   CLI, and run `t3 thread start --provider acpRegistry_minimax_code --model
   default <project> Hello`. Base exits before ACP initialization with the
   missing better-sqlite3 binding shown in base-runtime.txt.
7. Stop the base server. Preserve its entire isolated T3 home, managed package,
   and receipt. Start the head dev runner from the head checkout with
   `--home-dir <same-isolated-home>`. Inherit the previous server's environment,
   including its unchanged PATH, so the npm executable path stays identical.
8. Head automatically installs into npm-scripts beside the old npm directory.
   Open the head web client and repeat step 5. The Sign in button is available.
   Repeating step 6 now gets the ACP protocol error 'Authentication required:
   Run mcode login and try again', rather than the missing native binding.

Only environment identity is hidden in captures using CSS. The head's Account
paragraph contains the environment name, so that paragraph is also hidden;
the Sign in button and all provider status text remain visible. Runtime
transcripts redact checkout paths. Paired stills were checked against a second
identical screenshot taken at least 500 ms later. Videos were inspected as
contact sheets before upload.

The replay scenario runner was not used: its documentation excludes
provider-specific behavior, and this reproduction needs the actual MiniMax npm
package and native SQLite dependency. No tests stand in for runtime evidence.
