docs: sync stale unit test count in PROGRESS.md (BEN-152)

[benSepanski]

Context

BEN-152 asked for a doc review for correctness. PROGRESS.md's gate-status
line stated 329 unit tests, but pnpm test now runs 336 across 28 files.

TL;DR

Bump PROGRESS.md's cached unit-test count from 329 to 336 (the actual pnpm test result).

Summary

• Updated the single stale count in PROGRESS.md — the "Gate status" bullet.
• Verified the rest of the docs I sampled (AGENTS.md, ARCHITECTURE.md, docs/DESIGN.md, docs/FRONTEND.md, docs/product-specs/live-dashboard.md, docs/product-specs/orchestrator.md, docs/QUALITY_SCORE.md, docs/design-docs/index.md) — no further concrete drift surfaced this pass.
• No source-code changes. Eval scenarios (5), HTTP surface, CLI commands, event types, provider interfaces, and web helper file list all still match reality.

Demo

n/a — docs-only, no user-visible surface.

Alternatives

• Bulk-bump every "Last reviewed:" date across docs/. Rejected — updating those dates without an actual regrade of each doc's contents would be dishonest and would defeat the doc-gardening spec's whole point of surfacing stale docs.
• File the count-drift as a Backlog ticket instead of fixing inline. Rejected — the fix is a one-line, verifiable change; opening a ticket for it costs more than shipping it.

Test Plan

• pnpm all — typecheck + fmt:check + lint + test + eval (green locally: 336 unit + 5 eval)
• Manually verified the new count matches pnpm test output.

---

Generated by Claude Code