The publish workflow derives the npm version from this field, and on `main`
it uses it verbatim: `2.0.0` was already on the registry, so the release step
skipped and every change since then stayed unpublished. Staging and dev never
showed it because they append `-preview.N` and `-dev.N`, which are always new.
So the merged CLI work — the redirect refusal, the default endpoint, folder
path encoding, the request bound, the User-Agent, `run --follow`,
`runs wait` and `logs follow` — is on `main` but not on npm, and `sim@latest`
is still the build whose every write is dropped by the apex redirect.
Minor rather than patch: three commands are new and the default endpoint
changed.
Waleed
374c1064ea