docs: clarify safe local env setup
From the PR description
Summary
- surface the existing safe local testing guidance earlier in the README
- recommend disposable Supabase/R2/model-provider resources and synthetic documents for first runs
- split frontend env examples into browser-safe public vars and server-side Next runtime vars
- clarify that SUPABASE_SECRET_KEY must never be exposed as a NEXT_PUBLIC_* value
Validation
- git diff --check
Documentation-only change.
Our analysis
Surface safe local testing guidance and split frontend env vars — read the full analysis →
Think the analysis missed something the PR description covers?
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-133.md from
inside the repo you want the changes in.