| vsix_native_not_from_npm | First native VSIX design: GitHub Actions compiled napi on `analytical/v*`, published platform packages, and Azure fetched `--latest` from npm.
Azure did not compile Rust.
That design treated npm as a hand-off between the two pipelines.
After a changeset release, platform packages stayed on the previous patch (received `1.11.0`) while analytical and the extension moved (expected `1.11.1`).
["../../packages/analytical/test/native-packaging.test.ts"] failed on that mismatch.
The lag is structural: `changeset version`, a glob in the Changesets `fixed` group, and a registry wait are not one atomic git snapshot.
Decision: keep npm for CLI and MCP; compile the matrix in Azure from git for VSIX. | done | | Azure must not use the npm deploy path as an input when it packs VSIXes.
Git at the `ext/v*` tag is canonical. Azure compiles the [native_targets] matrix from that commit ( [vsix_export], [extension_distribution] ).
npm stays the install path for CLI and MCP only ( [npm_distribution], [rust_binary_distribution] ). | 0.241 |