docs: add safe local testing guide
From the PR description
Summary
- add a safe local testing guide for lawyers and firms evaluating Mike
- link the guide from the README setup flow
- remove the Supabase service-role key from the frontend env example
Why
Mike is likely to attract legal users who want to test it with sensitive workflows. The first-run docs should steer people toward disposable infrastructure, synthetic documents, capped provider keys, and keeping service-role/model-provider secrets server-side.
This also removes a footgun from the frontend example env file: the browser-facing app should not ask new self-hosters to place a Supabase service-role key in frontend/.env.local.
Test
- Documentation-only change
Our analysis
Add a safe local testing guide and pull the service-role key from the frontend env example — read the full analysis →
Think the analysis missed something the PR description covers?
Commits in this PR (2)
| SHA | Subject | Author | Date | |
|---|---|---|---|---|
fce2f2d9 | docs: add safe local testing guide | Eli Fayerman | 2026-05-04 | ↗ GitHub |
1f191fea | Merge branch 'main' into codex/safe-local-testing-guide | cosimoastrada | 2026-05-08 | ↗ GitHub |
Capture this PR into my fork
Download a Markdown prompt that tells Claude how to port every
commit in this PR into your working tree. Run it via
claude -p < capture-pull-31.md from
inside the repo you want the changes in.