CI: make “Lint (non-blocking)” run client lint as report-only

[Copilot]

The non-blocking lint job was failing during ESLint config resolution instead of reporting lint results, due to running root lint with dependencies installed via root --ignore-scripts. This updates the job to execute lint in the client context and keep failures explicitly non-blocking.

• Workflow scope correction

  • Install dependencies for the frontend lint target directly:
    • npm install --prefix client --ignore-scripts
  • Run lint from the same target:
    • npm run lint --prefix client

• Non-blocking behavior at lint step

  • Keep lint diagnostics visible while preventing the step from failing the job:
    • continue-on-error: true on the lint step

- run: npm install --prefix client --ignore-scripts
- name: Client lint (report-only)
  continue-on-error: true
  run: npm run lint --prefix client

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
healthmint	Ready	Preview, Comment	Jun 13, 2026 3:58am

[Copilot]

Pull request overview

Updates the non-blocking CI lint job to lint the frontend (client) in its own dependency context, so ESLint can resolve the correct config/plugins and report results without blocking the workflow.

Changes:

• Install dependencies for the client workspace in the lint job (npm install --prefix client ...).
• Run client lint explicitly (npm run lint --prefix client).
• Make the lint step explicitly report-only via continue-on-error: true.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.