docs: update technical FAQ, support FAQ, and AI server run instructions #3847
+17
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Stacked on #3801. Documents recent architectural changes from the past week that weren't covered by the parent PR:
faq/3.technical.mdx: Added two new Q&A entries explaining (1) cloud LLM routing via OpenRouter (aftercrates/openaiwas replaced bycrates/openrouter) and (2) the MCP-based support chat architecture (after feat: addread_github_dataMCP tool for Supabase Postgres #3771, feat: integrate MCP tools for support chat #3785, Add MCP Prompt support to SupportMcpServer with askama templates #3789).faq/5.support.mdx: Expanded the support chat description to mention it can search existing GitHub issues/discussions via theread_github_dataMCP tool.developers/5.run.mdx: Added run instructions for the AI server (apps/ai), which was missing from the developer docs despite being a key service.Review & Testing Checklist for Human
cargo run -p aiis the correct command to start the AI server (the Cargo package name may differ from the directory nameapps/ai/)OPENROUTER_API_KEYis sufficient for cloud LLM access3.technical.mdxmatch actual capabilities (submit bug reports, create discussions, query GitHub data)Notes