feat(docs): release the Claude Code editor section and chat-thread FAQ
Releases three landing page commits from staging to main, so the production docs site gets them:
- 940cd98ce feat(docs): show the editor section as a real Claude Code session
- ffce110f4 fix(docs): use Databuddy domains in the landing activity feed
- 02ba406c5 feat(docs): turn the landing FAQ into a chat-thread conversation (#1119)
Cherry-picked with -x onto origin/main, with no conflicts. The landing files are byte-identical to origin/staging, which has served them on the staging docs deploy.
Verification: bunx biome check passes on the changed files, apps/docs check-types passes, and next build generates all 206 pages.
Summary by cubic
Releases the landing page updates from staging to main so the production docs site gets them.
The editor section is now a realistic Claude Code terminal session that types a question, runs Databuddy MCP tool calls, and shows JSON results — replacing the generic MCP demo. The transcript matches the real Databuddy MCP tool schemas, including how error_segments labels browser rows, and the question starts typing only once the section is on screen. The landing FAQ switches from an accordion to a chat-thread conversation where selecting a question opens the answer as a reply, and the activity feed now uses Databuddy domains (dby.sh, api.databuddy.cc) instead of acme placeholders.
The change removes the now-unused Radix accordion component and its @radix-ui/react-accordion dependency from the docs app.
Review fixes, also on staging through #1122: