feat(demo): one-command docker demo of vouch + the console

[plind-junior]

adds a self-contained demo/ that runs vouch serve + the vouch-ui console in
one image — docker run or docker compose up, and the browser opens onto a
review-gated starter kb seeded on first run. published at
ghcr.io/plind-junior/vouch-demo so people can try vouch without a clone.

three pieces:

• demo/ — dockerfile, entrypoint, compose, env example, readme, and a
  stdlib-only anthropic shim (vouch-llm.py).
• proxy deploy mode — proxyMiddleware gains an optional pinned upstream +
  bearer token, read from VOUCH_TARGET / VOUCH_HTTP_TOKEN by the preview
  server, so the browser never picks the endpoint or sees the token. the dev
  behavior (per-request X-Vouch-Target, no injected token) is unchanged.
• .dockerignore — keep the host's webapp/node_modules and build output out
  of the demo build context (npm ci reinstalls in-image for cross-arch).

the llm-backed actions (compile, summarize session) are bring-your-own-key: the
entrypoint wires compile.llm_cmd to the shim only when ANTHROPIC_API_KEY is
set, and everything else works without one. verified end-to-end in the built
image — seeded kb, healthy console, and a live kb.compile round-trip (clean
401 on a bad key, clean "not configured" with none).

base is test to match #446 — the vendored console lives there, not yet on main.

[coderabbitai]

Warning

Review limit reached

@plind-junior, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 57 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 6608e85d-b7eb-48ea-b2fc-ce6e47049d77

📥 Commits

Reviewing files that changed from the base of the PR and between ef4b6c9 and 4c46316.

📒 Files selected for processing (9)

• .dockerignore
• demo/.env.example
• demo/Dockerfile
• demo/README.md
• demo/docker-compose.yml
• demo/entrypoint.sh
• demo/vouch-llm.py
• webapp/plugins/vouch-proxy.test.ts
• webapp/plugins/vouch-proxy.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/demo-docker

---

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.}

[plind-junior]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.