/sop-ack memory-consulted Cold-runner kill issue confirmed in CI logs: job killed before vitest could run. This fix resolves it.
/sop-n/a no-backwards-compat N/A: CI config change, no runtime backwards-compat concern.
/sop-ack five-axis-review Correctness: npm ci is the standard for CI environments, matches Dockerfile. Readability: simpler one-liner. Architecture: no change. Security: no impact. Performance:…
/sop-ack root-cause Root cause: rm -f package-lock.json forces npm install to re-resolve deps on cold cache (~5 min). Fix: use npm ci which uses the lockfile (seconds). This is the actual root cause.
/sop-n/a local-postgres-e2e N/A: CI step change. No database interactions.
/sop-n/a staging-smoke N/A: CI step change. Verified in CI run on this PR.
/sop-n/a comprehensive-testing N/A: CI workflow step change. No application code.
/sop-ack memory-consulted No prior memory/incidents needed — hygiene fix.
/sop-ack root-cause No bug fix — hygiene. Pinning aligns with existing standard across all other Gitea workflows.
/sop-n/a no-backwards-compat N/A: workflow CI config change — no runtime backwards-compat concern.
/sop-ack five-axis-review Correctness: SHA matches existing ci.yml/e2e-staging-canvas.yml standard. Readability: no change to workflow logic. Architecture: no architecture impact. Security:…
/sop-n/a local-postgres-e2e N/A: YAML-only workflow change. No database interactions.
/sop-n/a staging-smoke N/A: YAML-only workflow change. No staging deploy required.
/sop-n/a comprehensive-testing N/A: YAML-only workflow pinning change. No application code.