setup-node's cache: 'pnpm' requires the cache-dependency-path to
resolve, but several legacy .component-builds/* Workers only ship
package-lock.json (historical mixed state — see rule
05-deploy-convention.md). With pnpm-lock.yaml missing, setup-node
fails fast with "Some specified paths were not resolved" before
the install step's fallback logic even gets a chance to run.
Since each Worker deploy takes ~30s on its own runner, skipping
the per-job cache costs nothing in practice.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Leo
2bfe16ba61