chore: Update dependencies and fix create-pr workflow permissions

[jfrench9]

Summary of Changes

This PR performs routine maintenance across the project by updating dependencies and fixing CI workflow permissions.

🔧 CI/CD Changes

• .github/workflows/create-pr.yml: Added explicit permissions block for pull request operations. This ensures the workflow has the necessary pull-requests permission to create/update PRs, addressing potential authorization failures in GitHub Actions.

📦 Dependency Updates

• package.json / package-lock.json: Streamlined and updated project dependencies. The net reduction in lines (-22 lines removed vs +13 lines added) suggests consolidation — likely removing redundant or duplicate dependency entries and aligning version specifications.

Key UI/UX Improvements

• No user-facing UI/UX changes. This is a housekeeping PR focused on infrastructure and dependency hygiene.

Breaking Changes

• None expected. Dependency updates appear to be minor/patch-level based on the minimal diff footprint. However, reviewers should verify that no transitive dependency has introduced a breaking API change.

Testing Notes for Reviewers

1. CI Workflow Verification:

   • Confirm that the create-pr workflow runs successfully with the new permissions block by triggering the workflow (or verifying it on a subsequent PR).
   • Ensure no other workflow steps are inadvertently affected by the permissions scope.

2. Dependency Validation:

   • Run npm install (or npm ci) from a clean node_modules to verify the lock file resolves correctly with no peer dependency warnings or conflicts.
   • Run the full test suite (npm test) to confirm no regressions from updated packages.
   • Run npm run build to verify the Next.js production build completes without errors.
   • Spot-check the dev server (npm run dev) for any runtime issues.

3. Lock File Integrity:

   • Verify that package-lock.json is consistent with package.json (no drift) — running npm install should produce zero changes to the lock file.

Browser Compatibility Considerations

• No browser compatibility impact. Changes are limited to build tooling, CI configuration, and dependency metadata. No application code, polyfills, or transpilation settings were modified.

---

🤖 Generated with Claude Code

Branch Info:

• Source: chore/package-update-alignment
• Target: main
• Type: feature

Co-Authored-By: Claude noreply@anthropic.com