Fix CI workflow: sync package-lock.json with package.json

[Copilot]

Description

CI failing on npm ci due to package-lock.json drift. Missing commander@13.1.0 and magicast@0.3.5 from lock file. Regenerated lock file to restore sync.

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📝 Documentation update
• 🎨 Style/UI update (non-functional change)
• ♻️ Code refactoring (no functional changes)
• ⚡ Performance improvement
• ✅ Test update

Related Issue

CI workflow failure on all jobs due to dependency installation error.

Changes Made

• Regenerated package-lock.json via npm install to sync with package.json

Testing

• Unit tests pass (npm run test:unit)
• E2E tests pass (npm run test:e2e)
• Linting passes (npm run lint)
• Type checking passes (npm run typecheck)
• Manual testing completed

Test Coverage

• Added tests for new functionality
• Updated existing tests
• Coverage threshold maintained (80%+)

Screenshots (if applicable)

N/A

Checklist

Code Quality

• Code follows the style guidelines (AGENTS.md)
• Self-review completed
• Comments added for complex code
• No console.log or debugging code
• No TODO comments (or linked to issues)

Documentation

• README updated (if needed)
• API documentation updated (if needed)
• Component documentation added (if needed)

Database & Breaking Changes

• Database migrations created (if needed)
• Breaking changes documented
• Backward compatibility maintained (or documented)

Dependencies

• No unnecessary dependencies added
• package.json updated correctly
• No security vulnerabilities introduced

Deployment Notes

• Requires environment variable updates
• Requires database migration
• Requires data seeding
• No special deployment steps needed

Additional Context

Verified npm ci succeeds locally. All CI jobs should now pass dependency installation step.

---

Reviewer Checklist

• Code follows project conventions
• Tests are adequate and passing
• Documentation is clear and complete
• No security concerns
• Performance impact is acceptable
• Ready to merge

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• checkpoint.prisma.io
  • Triggering command: /usr/local/bin/node /usr/local/bin/node /home/REDACTED/work/only-paws/only-paws/node_modules/prisma/build/child {"product":"prisma","version":"7.3.0","cli_install_type":"local","information":"","local_timestamp":"2026-01-25T18:20:35Z","project_hash":"6428904f","cli_path":"/home/REDACTED/work/only-paws/only-paws/node_modules/.bin/prisma","cli_path_hash":"37fe40cc","en (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Fix the ci workflow</issue_title>
<issue_description>The ci workflow is failing with the following error:

npm error npm cican only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file withnpm install before continuing.

Fix this.</issue_description>

<agent_instructions>Check the output of the latest build to see error details</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes [bugfix] Fix the ci workflow #1

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.