fix: resolve CI failures introduced by PR #2 quality gates

[bdevierno1]

Summary

PR #2 (add-data-quality-checks) introduced CI quality gates that immediately fail on their own codebase. This draft PR fixes the root causes so the gates go green.

Root causes & fixes

1. Backend — ruff check . (5 errors)

Four unused-import (F401) errors auto-fixed via ruff check --fix, one E402 suppressed with # noqa:

File	Error	Fix
backend/app/main.py:9	fastapi.Request imported but unused	Removed from import list
backend/app/main.py:14	sqlalchemy.ext.asyncio.async_sessionmaker imported but unused	Removed import line
backend/tests/test_errors.py:5	math imported but unused	Removed import line
backend/tests/test_http_client.py:5	unittest.mock.MagicMock imported but unused	Removed from import list
backend/agent/vecna_litellm.py:80	E402 module-level import not at top of file	Added # noqa: E402 — the import litellm must follow litellm_main patching; the position is intentional

Verified locally: ruff check . now reports "All checks passed!"

2. Frontend — npm ci failure (lock file out of sync)

package-lock.json was missing entries for @emnapi/core@1.11.1 and @emnapi/runtime@1.11.1, and had a version mismatch for @emnapi/wasi-threads. Fixed by running npm install in frontend/ to regenerate a consistent lock file.

Verified locally:

• npm ci ✅
• npm run build ✅ (tsc + vite build, 271 KB bundle)

3. CI gate (required check)

The required gate only failed as a downstream consequence of the above two. No separate change needed — it should go green once this PR is merged into add-data-quality-checks.

Test plan

• CI on this PR runs green (backend ruff + tests, frontend lint/type-check/build, required gate)
• Merge into add-data-quality-checks and verify PR reliability: add CI quality gates (tests, lint, type-check, PR-size) #2's CI goes green
• Operator reviews diff — changes are strictly import-list cleanup + lock file regeneration

Out of scope

• npm audit vulnerabilities (5 flagged: 1 low, 3 moderate, 1 high) — not introduced by this PR, separate concern
• Any functional/logic changes to the application

🤖 Generated with Claude Code