♻️ Split server baseline routes

[Robdel12]

Why

The local server routes for baselines, projects, screenshots, and TDD handling are core contracts between the CLI runtime, SDK clients, and the local dashboard. They should have explicit behavior and tests because small response-shape changes can break multiple entrypoints at once.

This PR isolates the baseline-facing server route cleanup from the event/router cleanup. That gives reviewers a bounded contract to inspect: request handling, project/baseline behavior, screenshot ingestion, and the TDD handler path.

What Changed

• Tightened baseline, project, and screenshot route behavior.
• Updated the TDD handler where it interacts with those local server routes.
• Removed the old screenshot server service wrapper as part of moving toward the current route/server boundary.
• Added route and handler tests around the observable server responses.

Verification

• npm run build
• node --test tests/server/handlers/api-handler.test.js tests/server/handlers/tdd-handler.test.js tests/server/routers/baseline.test.js tests/server/routers/projects.test.js tests/server/routers/screenshot.test.js

Stack

5/10 in the CLI audit stack.

Base: rd/cli-audit-api-review
Head: rd/cli-audit-server-baselines

[vizzly-testing]

Vizzly - Visual Test Results

CLI Reporter - 2 changes need review

Status	Count
Passed	17
Changed	2
Auto-approved	17

Changes needing review (2)

dashboard-mixed-state · Firefox · 1920×1080 · 2.7% diff

fullscreen-viewer · Firefox · 375×667 · 78.3% diff

Review changes

CLI TUI - Approved

5 comparisons, no changes detected.

View build

---

_{rd/cli-audit-server-baselines · b6478de5}