da79ee234f
When smoke.yml runs via workflow_call from another repo (peptide-repo-core, peptide-starter-theme, etc.), GitHub Actions checks out the CALLER's repo by default. The caller has no package-lock.json, so setup-node's npm cache lookup fails with 'Some specified paths were not resolved'. Fix: add repository/ref to the checkout step so we always fetch peptide-e2e regardless of who calls the workflow. This ensures npm ci and Playwright have the correct test code and dependency lockfile.