Make tests explicit in CI

[vetrovk]

Fixes #158.

This change makes CI output easier to diagnose by separating unit and integration test stages explicitly while continuing to use the existing npm scripts.

Changes:

• replace npm test with explicit npm run test:unit
• add separate npm run test:integration CI step

Validation:

• npm ci --cache .npm-cache --no-audit --no-fund
• npm run test:integration
• npm run format:check
• git diff --check

Notes:

• npm run test:unit currently has existing unrelated local failures in StaticFileHandler specs (403 responses instead of expected static file responses).
• No application/runtime code was changed, only .github/workflows/ci.yml.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 33bb20dd-5f63-4194-a2ce-240802f9ae6c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[VikramAditya33]

LGTM, Thank you