A Node.js project uses setup-node dependency caching. CI fails before npm ci because the configured cache-dependency-path points at a lockfile that does not exist in the checked-out revision. What is the appropriate first correction?

1. Correct cache-dependency-path to match the committed lockfile at the tested revision, then retry the dependency setup.
2. Download the lockfile from an unrelated workflow run without checking its revision.
3. Replace the cache key with the repository secret containing the registry password.
4. Change the cache save policy but leave the nonexistent lockfile path unchanged.