v3.2.1

What's Changed

Bug Fixes

• OpenCode engine now resolves under npx-launched MCP: The MCP server runs via npx -y amicus@latest mcp, which installs the opencode engine packages hoisted beside amicus rather than nested under it. The resolver was only checking the nested location, causing engineMissing failures on every fanout. Both the PATH builder and binary resolver now probe the hoisted root layout as well (#69).
• AVX2 build searched before baseline fallback: The default AVX2 opencode build was being skipped on capable machines due to reversed PATH search order. PATH is now built as one ordered group so AVX2 installs are found first, preventing silent degradation to slower pre-AVX2 builds.

Features

• Cross-install engine verification in amicus doctor: A new "OpenCode engine (MCP launch path)" check enumerates every amicus install that could serve the MCP (running, global, and each npx-cache copy) and verifies the engine in each. This prevents the green-while-broken state where doctor reports success but the npx copy the MCP launches is actually broken. Single npx copies report errors; ambiguous multi-copy cases warn with exact paths.
• Runtime engine errors now show searched paths: When the opencode engine is missing at runtime, the error message now prints which roots were searched, making npx-cache versus global install divergence visible at the point of failure rather than requiring a separate doctor run.

Full Changelog: v3.2.0...v3.2.1