​

Documentation Source Snapshot

​

Source commits

​

Update workflow for the next iteration

1. Pull latest master in all three source repositories.
2. Diff each repository from the matching anchor above.
3. Read only the files changed by those diffs, plus directly referenced helpers when needed.
4. Update the relevant docs pages and screenshot capture instructions.
5. Replace the commit anchors in this file after validation passes.

​

Weekly automation helper

python3 scripts/prepare_weekly_docs_update.py --output-dir .docs-update-reports/latest --force

​

Useful diff commands

cd /Users/kamat/Documents/projects/dashboard-be
git fetch origin master
git diff 5c391dc73bb5ef79c0dbc96a5bf94c05ad99734f..origin/master --name-only

cd /Users/kamat/Documents/projects/dashboard-fe
git fetch origin master
git diff 29f713c82682503b318bcbe5246d7ee514a4e26f..origin/master --name-only

cd /Users/kamat/Documents/projects/speech-ai
git fetch origin master
git diff e8788bcfbdf9c81e847bc3896a486338b24ca536..origin/master --name-only

​

Scope notes

• The current Voice AI docs reflect public dashboard behavior for Deepgram, Soniox, Speech to Speech agents, fallback STT validation and billing, Boosted Keywords, Prompt Caching, empty model response recovery, language-aware filler, OpenAI, Google, Groq, ElevenLabs, Cartesia, phone routing, SIP trunking, Telephony Config, destination validation, call evidence, web call warmup and teardown, TTS ordering and continuity, and Audio Cache.
• The current dashboard docs reflect public behavior for MCP OAuth consent, workspace assistant questions and approved actions, assistant edit, retry, feedback, and session history controls, Knowledge Base attachments, agent timezone awareness, DateTime post-call analysis fields, batch CSV column mapping, batch upload phone-number review, batch progress rollups, workflow Application nodes, workflow Time nodes, and dynamic custom-function authentication headers.
• Provider or model names intentionally excluded from public docs should stay excluded unless the product owner asks otherwise.
• The generated integration catalog is separate from the dashboard integration docs. Link to catalog pages only where they help the reader understand a provider or business-system example.
• Individual MCP tool pages mirror dashboard-be/src/modules/mcp/tools/*.tools.ts through npm run mcp:export and scripts/build-mcp-tools-from-export.py. The builder also regenerates resource overviews, safety labels, request examples, navigation, redirects, and the tracked manifest. Treat any dashboard-be diff touching src/modules/mcp/** as requiring a full re-sync and python3 scripts/validate_mcp_tool_docs.py.