✨ Split API review commands

[Robdel12]

Why

The API-facing commands are where users inspect builds, baselines, comparisons, projects, reviews, and uploads. These commands share the same risk: malformed inputs, inconsistent JSON/human output, and thin test coverage can make the CLI feel unreliable even when the backend is working correctly.

This PR keeps that review surface together. It focuses on the commands that translate user intent into API requests and render the response back to the terminal, with tests that verify outcomes instead of internal command wiring.

What Changed

• Hardened api, baselines, builds, comparisons, projects, review, and upload.
• Added shared HTTP/API test helpers for command-level tests.
• Expanded coverage for validation, API request construction, JSON output, human output, and failure handling.
• Kept this separate from setup/auth and server internals so command behavior can be reviewed on its own.

Verification

• npm run lint
• node --test tests/commands/api.test.js tests/commands/baselines.test.js tests/commands/builds.test.js tests/commands/comparisons.test.js tests/commands/projects.test.js tests/commands/review.test.js tests/commands/upload.test.js

Stack

4/10 in the CLI audit stack.

Base: rd/cli-audit-init-auth
Head: rd/cli-audit-api-review

[vizzly-testing]

Vizzly - Visual Test Results

CLI Reporter - 1 change needs review

Status	Count
Passed	18
Changed	1
Auto-approved	18

Changes needing review (1)

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

Review changes

CLI TUI - Approved

5 comparisons, no changes detected.

View build

---

_{rd/cli-audit-api-review · 03311ae5}