Doc location
Repo-wide: README.md, docs/**, docs/releases/**, CONTRIBUTING cross-links
What kind of change?
Outdated or wrong information
What’s wrong or missing?
Post-v0.2.0 shipping left some drift risk: install order is correct in README, but deep pages may still under-emphasize the .exe, over-emphasize dev:desktop, or lack links to releases index. Screenshots are PNG-heavy (see GIF issue). Architecture Mermaid was fixed; other pages need a single editorial pass for tone (visitor-facing, no maintainer ops language).
Suggested fix (optional)
- Every “how do I run this?” path matches: exe →
npm run desktop → npm run dev.
- Grep for:
planned, draft, desktop-setup, upload, gitignored, internal ops wording — remove or rephrase.
- Ensure Voice/Electron-only warnings are consistent.
- Link docs/releases/README.md from docs index (already partly done).
- Cross-link CONTRIBUTING ripple table where useful.
- Coordinate with motion GIF issue for embeds; do not block this pass on GIFs.
Checklist
Doc location
Repo-wide:
README.md,docs/**,docs/releases/**, CONTRIBUTING cross-linksWhat kind of change?
Outdated or wrong information
What’s wrong or missing?
Post-v0.2.0 shipping left some drift risk: install order is correct in README, but deep pages may still under-emphasize the
.exe, over-emphasizedev:desktop, or lack links to releases index. Screenshots are PNG-heavy (see GIF issue). Architecture Mermaid was fixed; other pages need a single editorial pass for tone (visitor-facing, no maintainer ops language).Suggested fix (optional)
npm run desktop→npm run dev.planned,draft,desktop-setup,upload,gitignored, internal ops wording — remove or rephrase.Checklist