[Bug][desktop]: Installing official "MiniMax Bot" plugin always fails with 500 — materialized Plugin package identity does not match full-state #494

Summary

Installing the official MiniMax Bot plugin from the Plugin Marketplace always fails with HTTP 500. The failure is deterministic — four attempts produced the exact same error. Retrying and clearing the local cache have no effect.

Steps to reproduce

1. MiniMax Code → Plugins → Marketplace → search "MiniMax Bot"
2. Click Install
3. Observed: install failed ("安裝失敗")

Actual

ERROR: unhandled error: Error: materialized Plugin package identity does not match full-state
http POST /minimax-desktop/api/v1/plugins/minimax-bot/install status=500

Four attempts on 2026-10-16 (UTC+8) at 04:20:13, 04:20:22, 04:31:02, 04:34:32 — all identical.

Expected

Install succeeds; the plugin appears under installed plugins and the /bot surface opens.

Where it fails

In preparePackage() (app.asar). The pipeline completes every earlier step and fails only on the final identity check:

1. authorizeDownload(...) — passes
2. assertSamePackage(packageVersion, authorization.package) — passes
3. download + materializeOfficialPluginArchive({ expectedArchiveSha256, expectedContentDigest }) — passes, so the archive is authentic and uncorrupted
4. isUsableCachedPackage(materialized.packageRoot, packageVersion) — fails

That check reads .minimax-plugin/plugin.json and compares only:

plugin.name === expected.name && plugin.version === expected.version

The authentic archive declares minimax-bot@0.6.2 in both .minimax-plugin/plugin.json and package.json — the two are self-consistent. So expected (the marketplace full-state PluginPackageVersion) appears to advertise a different name or version than the archive actually contains.

Ruled out

• Network / CDN / truncated download — authorization and both digest verifications passed.
• Corrupted local cache — the client already wipes the digest path before materializing on every attempt, so each run re-downloads. Manually clearing the cache changes nothing.
• Manifest schema problem — .minimax-plugin/plugin.json is present and valid; the 30 other official cache entries have no package.json at all, since official packages are keyed on the manifest only.
• Missing local dependency — there is no install action available to the agent (miniapp exposes list/init/open/inspect/publish/restart/stop only), so this cannot be worked around from an agent session.

Suggestion

Include the expected and materialized identities in that error message so the mismatch is visible without reading app.asar, e.g.:

materialized Plugin package identity does not match full-state:
expected minimax-bot@<x> (contentDigest <y>), got minimax-bot@0.6.2

Environment

• MiniMax Code 3.1.1 (build 3.1.1.178)
• macOS (Darwin 25.6.0), arm64
• Plugin: minimax-bot v0.6.2 (OFFICIAL)
• Logs: ~/.minimax/v2/observability/logs/runtime-2026101604.log