docs: clarify demo safety boundaries

[jeffgreendesign]

Summary

• add a top-level demo safety boundary for sample data/test accounts
• soften audit wording and clarify synthetic stress/fatigue demo signals
• remove stale screenshot placeholder and replace illustrative email in design wireframes

Verification

• git diff --check
• npm run lint (passes with 2 pre-existing warnings in lib/hooks/use-gemini-live.ts)
• npm run typecheck

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
commerce-changeset	Ready	Preview, Comment	Jun 8, 2026 12:03pm

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: dfb9eb88-96f8-4f56-9935-3f136ef18c9b

📥 Commits

Reviewing files that changed from the base of the PR and between 660b295 and 3e3e807.

📒 Files selected for processing (2)

• README.md
• docs/living-workspace-design-spec.md

---

Walkthrough

This PR updates documentation across two files to improve clarity about the demo environment and ensure consistent demo account identity. README.md additions include a demo safety boundary note explaining that live API calls are limited to sample Google Sheet and test accounts, clarification that CIBA Guardian push approval gates writes, expanded "real vs. simulated" table entries with non-inference disclaimers and updated dataset links, and removal of screenshot placeholder comments in favor of exposed image links. The design spec wireframes are updated to use a consistent demo email address (demo@commerce-changeset.local) across three separate example layouts, replacing the previous jeff@stride.co references.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'docs: clarify demo safety boundaries' directly aligns with the main objective of adding demo safety boundary clarifications to the documentation.
Description check	✅ Passed	The description is directly related to the changeset, covering all three key documentation updates: demo safety boundaries, synthetic signal clarification, and email/screenshot replacements in design wireframes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/public-safety-boundaries

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}