Skip to content

docs: write the help cluster — getting-started / faq / troubleshooting (Cycle 21)#25

Merged
kbennett2000 merged 1 commit into
mainfrom
cycle-21-help-cluster
Jun 22, 2026
Merged

docs: write the help cluster — getting-started / faq / troubleshooting (Cycle 21)#25
kbennett2000 merged 1 commit into
mainfrom
cycle-21-help-cluster

Conversation

@kbennett2000

Copy link
Copy Markdown
Owner

Fills the last three empty stubs so the README/landing "Help" links stop dead-ending. Zero-assumptions audience — warm, plain, encouraging, more hand-holding when in doubt.

Cycle spec: docs/cycles/cycle-21-help-cluster.md.

Pages

  • getting-started.md — the gentle on-ramp: the simplest path in four plain beats (Docker → get the project → docker compose up mash → open localhost:8090 → upload a .acs + Speak), then hands off to the per-OS install guides; signposts to voice / what-is-this / characters / developers.
  • faq.md — the common questions answered short, each routing to the canonical page: is this legal, do I need to be a programmer, why no sound / why extra files, which characters work, what platforms, is my data sent anywhere, why the first line is a touch slow, can I embed it.
  • troubleshooting.md — grouped by symptom, de-scared: no sound, character won't load, Docker/port conflicts (8090/8080), the loud speech.h/runtime FATAL build messages, first-build-slow, Linux sudo.

No duplication (route, don't re-paste)

Per-platform steps → install pages; sourcing + IP → legal-and-assets.md; authentic-voice concepts → voice/*; what-Microsoft-Agent-was → what-is-this.md. The help pages link to all of these.

Accuracy

Every troubleshooting error string + path was verified against the repo — MASH status messages (apps/mash/src/app.ts), the loud build FATALs (services/voice-server/Dockerfile, incl. the exact speech.h drop path), ports + the up vs up mash distinction + the port-remap (docker-compose.yml).

Marker cleanup

Cleared the now-stale (coming soon) markers pointing at these three pages: README (×3) + the three install-page "Trouble?" footers (faq/troubleshooting, ×6) — same links, no path churn. No install content/steps altered.

Verification

  • pnpm -r typecheck && pnpm -r test && pnpm lint && pnpm format — green (docs only).
  • Every relative link resolves; the three pages cross-link each other + the docs landing.
  • code-reviewer verified all six obligations clean: no duplication, troubleshooting matches real behaviors, faq/getting-started facts correct, markers cleared, links resolve, scope docs-only.

Out of scope: expanding characters.md / architecture.md (optional later polish). Base main, not merged.

🤖 Generated with Claude Code

…g (Cycle 21)

Fill the last three empty stubs so the README/landing "Help" links stop
dead-ending. Zero-assumptions audience: warm, plain, encouraging, more
hand-holding when in doubt (spec voice/tone).

- getting-started.md — the gentle on-ramp: the simplest path in four plain
  beats (Docker → get project → `docker compose up mash` → localhost:8090 →
  upload + Speak), then hands off to the per-OS install guides; signposts to
  voice / what-is-this / characters / developers.
- faq.md — the common questions answered short, each routing to the canonical
  page: is this legal, do I need to be a programmer, why no sound / why extra
  files, which characters work, what platforms, is my data sent anywhere, why
  the first line is a touch slow, can I embed it.
- troubleshooting.md — grouped by symptom, de-scared: no sound, character won't
  load, Docker/port conflicts (8090/8080), the loud speech.h/runtime FATAL
  build messages, first-build-slow, Linux sudo. Every error string + path
  verified against apps/mash/src/app.ts, services/voice-server/Dockerfile, and
  docker-compose.yml.

No duplication: routes to install (steps) / legal-and-assets (sourcing) /
voice/* (concepts), never re-pastes them.

Cleared now-stale "(coming soon)" markers pointing at these three pages: README
(getting-started/faq/troubleshooting) + the three install-page "Trouble?"
footers (faq/troubleshooting) — same links, no path churn.

Docs only; CI green; verified by code-reviewer (no duplication, real behaviors,
links resolve, markers cleared).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@kbennett2000 kbennett2000 merged commit e63eefa into main Jun 22, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant