@researai/deepscientist 1.5.16 → 1.6.0

package/docs/en/33_WORKSPACE_EXPLORER_QA.md

@@ -0,0 +1,121 @@
+# Workspace Explorer Q&A
+
+This page explains a common surprise: a file or folder is visible in the terminal, but it does not appear in the Web Explorer or Search panel.
+
+## 1. Is Explorer the same as the local quest root?
+
+Not always.
+
+The desktop `FILES` view shows the backend's active workspace root, not always `<home>/quests/<id>`. The active root resolves in this order:
+
+1. `current_workspace_root` in `.ds/research_state.json`
+2. `research_head_worktree_root` in `.ds/research_state.json`
+3. the quest root
+
+During an analysis or paper branch, the active root may be:
+
+```text
+<quest_root>/.ds/worktrees/<branch-worktree-name>
+```
+
+If you manually create a folder in the quest root while Explorer is pointed at a worktree, the folder may not appear in Explorer.
+
+## 2. Which paths are hidden?
+
+The desktop `FILES` view recursively lists the active workspace root, but skips:
+
+- `.git`
+- `.ds/worktrees` when the active root is the quest root
+- `__pycache__`
+- `.pytest_cache`
+
+If the active workspace root itself is a `.ds/worktrees/<name>` directory, Explorer treats that worktree as the root and shows its contents.
+
+Mobile uses a smaller profile and may hide or truncate `.ds`, `artifacts`, `tmp`, `userfiles`, and deep directories.
+
+## 3. What is the difference between `FILES`, `SCOPE`, and `SNAPSHOT`?
+
+- `FILES`: live tree for the current active workspace root.
+- `SCOPE`: files related to the selected graph node, stage, diff, or reveal target.
+- `SNAPSHOT`: a read-only git revision or commit view.
+
+To check whether a terminal-created file is visible, switch to `FILES` and refresh.
+
+## 4. Will a terminal-created folder appear automatically?
+
+No. DeepScientist does not currently watch the local filesystem.
+
+After creating files manually:
+
+1. Make sure they are under the current active workspace root.
+2. Switch Explorer to `FILES`.
+3. Click refresh or reload the page.
+
+Empty folders can appear in Explorer, but Search usually cannot find empty folders because it mainly scans file paths and readable text content.
+
+## 5. Why can Search miss something?
+
+Search scans files under the active workspace root. It does not search every worktree at once.
+
+It also skips large files, binary files, and Explorer-filtered paths. Use plain text queries such as:
+
+```text
+run_probe
+experiments/analysis
+```
+
+Do not use shell glob syntax for normal searches. Older frontend code wrapped queries as `*term*`; newer code tolerates that legacy shape, but plain keywords are preferred.
+
+## 6. How do I check what Explorer is looking at?
+
+Use the Explorer API:
+
+```bash
+curl -s "http://127.0.0.1:<port>/api/quests/<quest_id>/explorer" | jq -r '.quest_root'
+```
+
+Or inspect the research state:
+
+```bash
+cat <quest_root>/.ds/research_state.json
+```
+
+Check:
+
+- `current_workspace_root`
+- `research_head_worktree_root`
+- `paper_parent_worktree_root`
+- `analysis_parent_worktree_root`
+
+If your terminal `pwd` differs from the Explorer API's `quest_root`, it is normal for Web Explorer not to show that file.
+
+## 7. How should I hand files to the agent?
+
+The most reliable option is to ask the agent to write them in the current active worktree:
+
+```text
+Create experiments/analysis/... under the current active worktree,
+write the scripts, results, and report there, then record the artifact and update PLAN/CHECKLIST.
+```
+
+Files created through Web upload, new file, or editor save also go through backend APIs and are written to the active workspace root.
+
+## 8. Does writing a file mean it is in Git?
+
+No.
+
+A file created inside a git worktree appears in that worktree's `git status`, often as untracked. It enters Git history only after:
+
+- `git add` / `git commit`
+- or a DeepScientist artifact / checkpoint flow records it
+
+Also note that a `.ds/worktrees/<name>` worktree has its own git status; it may not appear in the quest root's `git status`.
+
+## 9. Recommended checklist
+
+1. Switch Web Explorer to `FILES`.
+2. Refresh Explorer.
+3. Check `.quest_root` from the Explorer API.
+4. Compare that path with terminal `pwd`.
+5. If the file is in another worktree, ask the agent to merge or copy it into the current active worktree.
+6. If it should persist, ask the agent to record an artifact or checkpoint.

package/docs/en/91_DEVELOPMENT.md

@@ -67,6 +67,33 @@ npm --prefix src/tui install
 npm --prefix src/tui run build
 ```
 
+Run the TUI with route/render diagnostics:
+
+```bash
+ds --tui --debug --debug-log /tmp/deepscientist_tui_debug.jsonl
+```
+
+Use this when validating command routing, config editor behavior, or Web/TUI parity. Debug JSONL must stay redacted for config editor buffers and secret-like fields; if a TUI change adds a new input surface, add or update an E2E assertion for that redaction boundary.
+
+Run Web Settings with the browser debug inspector:
+
+```text
+/settings/connector/qq?debug=1
+```
+
+or:
+
+```js
+localStorage.setItem('deepscientist.debug', '1')
+localStorage.setItem('deepscientist.debug.log', '1')
+```
+
+The Web inspector must stay hidden unless debug is enabled. It must not include raw config document content or secret-like structured config fields in the snapshot. Focused regression check:
+
+```bash
+cd src/ui && E2E_BASE_URL=http://127.0.0.1:21888/ui npx playwright test e2e/web-debug.spec.ts --project=chromium
+```
+
 ## Test Commands
 
 Quick Python test run:
@@ -92,6 +119,8 @@ Before publishing or cutting a release, verify:
 3. `npm pack --dry-run --ignore-scripts` succeeds.
 4. README and linked docs match the current runtime behavior.
 5. Any new config, route, or quest-state fields have matching tests.
+6. Any TUI command or surface change updates the debug snapshot mapping and keeps `--debug-log` free of raw secrets.
+7. Confirm any new bundled third-party material has an explicit provenance note and license-compatible release path.
 
 ## Managed Runtime Tools
 
@@ -179,6 +208,243 @@ match = service.resolve_binary("example-binary", preferred_tools=("example",))
 - keep clear source reporting such as `tinytex` versus `path`
 - add tests for registration, status, and binary resolution
 
+## Extending Core Runtime
+
+This section is the maintainer checklist for adding one new built-in MCP tool, one new skill, or one new connector.
+
+Keep the extension shape close to the repository's existing registries and contracts. Do not invent a parallel path when the current registry or prompt system already covers the need.
+
+### Add a built-in MCP tool
+
+Public MCP surface must stay limited to:
+
+- `memory`
+- `artifact`
+- `bash_exec`
+
+Do not add a new public namespace such as `git`, `connector`, or `runtime_tool`.
+
+If you need new Git behavior, add it under `artifact`.
+If you need new durable shell behavior, add it under `bash_exec`.
+
+#### Files to change
+
+- `src/deepscientist/mcp/server.py`
+  - add the new `@server.tool(...)` handler under `build_memory_server(...)`, `build_artifact_server(...)`, or `build_bash_exec_server(...)`
+- `src/deepscientist/mcp/context.py`
+  - only if the new tool needs extra quest/runtime context wiring
+- `src/deepscientist/runners/codex.py`
+  - if the tool should appear in built-in MCP approval policy defaults, add it under `_BUILTIN_MCP_TOOL_APPROVALS`
+- `docs/en/07_MEMORY_AND_MCP.md`
+  - update user-visible semantics if the tool changes how the namespace should be used
+- `docs/en/14_PROMPT_SKILLS_AND_MCP_GUIDE.md`
+  - update the built-in MCP description if the tool meaning materially changes
+
+#### Implementation rules
+
+1. Keep the handler thin. Put durable state changes in the underlying service layer such as `ArtifactService`, `MemoryService`, or `BashExecService`.
+2. Use `McpContext` for quest-local paths instead of reconstructing runtime state ad hoc.
+3. Use read-only annotations for non-mutating tools.
+4. If the tool changes durable quest state but does not itself send a user-visible message, follow the existing artifact watchdog pattern in `mcp/server.py`.
+5. Do not bypass the current namespace meaning. Example: do not hide shell execution inside `artifact`.
+
+#### Minimum test checklist
+
+- `tests/test_mcp_servers.py`
+  - namespace wiring and tool call behavior
+- `tests/test_memory_and_artifact.py`
+  - if the tool changes artifact or memory semantics
+- `tests/test_daemon_api.py`
+  - if API payloads or quest projections depend on the new tool's outputs
+
+### Add a skill
+
+Skills are discovered from disk. The canonical location is:
+
+- `src/skills/<skill_id>/SKILL.md`
+
+The runtime discovers skills through:
+
+- `src/deepscientist/skills/registry.py`
+
+The prompt builder projects them through:
+
+- `src/deepscientist/prompts/builder.py`
+- `src/deepscientist/skills/installer.py`
+
+#### Minimal skill shape
+
+Create a directory:
+
+```text
+src/skills/<skill_id>/
+```
+
+and add:
+
+```md
+---
+name: my-skill
+description: One-line purpose statement.
+skill_role: stage
+skill_order: 60
+---
+
+# My Skill
+...
+```
+
+Supported `skill_role` values are:
+
+- `stage`
+- `companion`
+- `custom`
+
+Optional projected agent files:
+
+- `src/skills/<skill_id>/agents/openai.yaml`
+- `src/skills/<skill_id>/agents/claude.md`
+
+#### Files to change
+
+- `src/skills/<skill_id>/SKILL.md`
+  - required
+- `src/deepscientist/skills/registry.py`
+  - update `_DEFAULT_STAGE_SKILLS` or `_DEFAULT_COMPANION_SKILLS` if this is a canonical built-in stage or companion skill rather than an ad hoc custom one
+- `src/deepscientist/prompts/builder.py`
+  - update `STAGE_MEMORY_PLAN` if the skill is a real stage that needs a first-class memory retrieval plan
+- `docs/en/14_PROMPT_SKILLS_AND_MCP_GUIDE.md`
+  - update the skill guide if the public workflow shape changed
+
+#### Skill rules
+
+1. Put execution discipline inside `SKILL.md`, not inside a central Python stage scheduler.
+2. Reuse the existing prompt contract language:
+   - interaction discipline
+   - tool discipline
+   - stage purpose
+   - completion or handoff rules
+3. If the skill is a canonical stage, give it a stable place in the stage order and memory plan.
+4. If the skill is only auxiliary, prefer `skill_role: companion` or `custom` rather than bloating the canonical stage chain.
+5. Remember that `SkillInstaller` mirrors skills into the active Codex/Claude projection trees. Keep paths and file names stable.
+
+#### Minimum test checklist
+
+- `tests/test_stage_skills.py`
+  - stage ordering and canonical skill availability
+- `tests/test_skill_contracts.py`
+  - frontmatter and skill contract expectations
+- `tests/test_prompt_builder.py`
+  - prompt builder output and visible skill path blocks
+
+### Add a connector
+
+Connectors have three distinct layers:
+
+1. config and validation
+2. inbound / outbound transport adaptation
+3. optional background runtime lifecycle
+
+For a simple connector, changing only one layer is usually not enough.
+
+#### Core files to inspect first
+
+- config defaults:
+  - `src/deepscientist/config/models.py`
+- config validation and live test behavior:
+  - `src/deepscientist/config/service.py`
+- connector profile support:
+  - `src/deepscientist/connector/connector_profiles.py`
+- inbound/outbound adaptation:
+  - `src/deepscientist/bridges/base.py`
+  - `src/deepscientist/bridges/connectors.py`
+  - `src/deepscientist/bridges/builtins.py`
+- channel delivery:
+  - `src/deepscientist/channels/base.py`
+  - `src/deepscientist/channels/builtins.py`
+- daemon lifecycle:
+  - `src/deepscientist/daemon/app.py`
+- API endpoints:
+  - `src/deepscientist/daemon/api/router.py`
+  - `src/deepscientist/daemon/api/handlers.py`
+- optional prompt fragment:
+  - `src/prompts/connectors/<connector>.md`
+
+#### Step-by-step connector checklist
+
+1. Add default config in `src/deepscientist/config/models.py`.
+   - If it is a system connector, add it to `SYSTEM_CONNECTOR_NAMES`.
+   - Add its default payload under `default_connectors()`.
+2. Add validation and config test behavior in `src/deepscientist/config/service.py`.
+   - validate required tokens, ids, transport, and live probe behavior
+3. Decide whether it is profileable.
+   - If yes, add a spec in `src/deepscientist/connector/connector_profiles.py`
+4. Add or extend a bridge in `src/deepscientist/bridges/connectors.py`.
+   - subclass `BaseConnectorBridge`
+   - implement inbound parsing and outbound formatting / delivery as needed
+5. Register the bridge in `src/deepscientist/bridges/builtins.py`.
+6. Register a channel in `src/deepscientist/channels/builtins.py`.
+   - use `GenericRelayChannel` when the standard relay flow is enough
+   - add a dedicated channel class only when the connector needs special outbound behavior
+7. If the connector needs a long-running runtime such as polling, gateway, QR session, or long connection:
+   - add the service class under `src/deepscientist/channels/`
+   - add daemon state fields in `DaemonApp.__init__`
+   - wire startup in `DaemonApp._start_background_connectors()`
+   - wire shutdown in `DaemonApp._stop_background_connectors()`
+8. If the connector needs custom web/API flows beyond the generic inbound route:
+   - update `src/deepscientist/daemon/api/router.py`
+   - update `src/deepscientist/daemon/api/handlers.py`
+9. If the connector needs connector-specific prompt behavior:
+   - add `src/prompts/connectors/<connector>.md`
+   - the prompt builder will load it automatically when the connector is active or bound
+10. Add user docs if it is a public connector.
+
+#### Connector rules
+
+1. Prefer the generic bridge/channel model. Do not special-case a connector inside unrelated quest logic.
+2. Keep transport adaptation in bridges and delivery/runtime behavior in channels.
+3. Do not add a connector-specific public MCP namespace.
+4. If the connector is public, keep route and status behavior consistent with the existing `/api/connectors/...` surface.
+5. If it is only a relay connector, try `GenericRelayChannel` first before writing a bespoke channel class.
+
+#### Minimum test checklist
+
+- `tests/test_connector_config_validation.py`
+  - config shape and required fields
+- `tests/test_connector_bridges.py`
+  - inbound parse and outbound formatting
+- connector-specific tests such as:
+  - `tests/test_telegram_connector.py`
+  - `tests/test_weixin_connector.py`
+  - `tests/test_qq_connector.py`
+  - `tests/test_whatsapp_local_session.py`
+  - or a new connector-specific test file
+- `tests/test_daemon_api.py`
+  - if new routes, status payloads, or connector availability behavior changed
+
+### Quick extension map
+
+Use this when you only need the shortest file-level reminder:
+
+- new MCP tool:
+  - `src/deepscientist/mcp/server.py`
+  - maybe `src/deepscientist/runners/codex.py`
+  - tests: `test_mcp_servers.py`
+- new skill:
+  - `src/skills/<skill_id>/SKILL.md`
+  - maybe `src/deepscientist/skills/registry.py`
+  - maybe `src/deepscientist/prompts/builder.py`
+  - tests: `test_stage_skills.py`, `test_skill_contracts.py`, `test_prompt_builder.py`
+- new connector:
+  - `src/deepscientist/config/models.py`
+  - `src/deepscientist/config/service.py`
+  - maybe `src/deepscientist/connector/connector_profiles.py`
+  - `src/deepscientist/bridges/*`
+  - `src/deepscientist/channels/*`
+  - maybe `src/deepscientist/daemon/app.py`
+  - maybe `src/prompts/connectors/<connector>.md`
+  - tests: connector validation + bridge + daemon/API coverage
+
 ## Documentation Rules
 
 When behavior changes:

package/docs/en/99_ACKNOWLEDGEMENTS.md

@@ -6,29 +6,34 @@ DeepScientist was shaped by many prior systems, open-source efforts, and researc
 
 We especially thank the following projects for their ideas, research direction, and systems inspiration:
 
-- The AI Scientist
-- The AI Scientist v2
-- AlphaEvolve
-- OpenEvolve
-- EvoScientist
-- Orchestra-Research
-- Orchestra-Research/AI-Research-SKILLs
-- Overleaf / overleaf/overleaf
-- Monaco Editor / microsoft/monaco-editor
-- Novel / steven-tey/novel
-
-These projects have been important references for thinking about automated research, open-ended exploration, evolutionary search, experiment organization, long-horizon research agents, collaborative LaTeX editing workflows, browser-based code editing experiences, and rich notebook-style writing interactions.
+- [The AI Scientist](https://github.com/SakanaAI/AI-Scientist)
+- [The AI Scientist v2](https://github.com/SakanaAI/AI-Scientist-v2)
+- [AlphaEvolve](https://deepmind.google/blog/alphaevolve-a-gemini-powered-coding-agent-for-designing-advanced-algorithms/)
+- [OpenEvolve](https://github.com/algorithmicsuperintelligence/openevolve)
+- [EvoScientist](https://github.com/EvoScientist/EvoScientist)
+- [AutoSOTA](https://github.com/tsinghua-fib-lab/AutoSOTA)
+- [Orchestra-Research](https://www.orchestra-research.com/)
+- [Orchestra-Research/AI-Research-SKILLs](https://github.com/Orchestra-Research/AI-Research-SKILLs)
+- [Overleaf / overleaf/overleaf](https://github.com/overleaf/overleaf)
+- [Monaco Editor / microsoft/monaco-editor](https://github.com/microsoft/monaco-editor)
+- [Novel / steven-tey/novel](https://github.com/steven-tey/novel)
+- [paper-plot-skills / Trae1ounG/paper-plot-skills](https://github.com/Trae1ounG/paper-plot-skills)
+- [nature-skills / Yuan1z0825/nature-skills](https://github.com/Yuan1z0825/nature-skills)
+- [FermiLink / TaoELi/FermiLink](https://github.com/TaoELi/FermiLink)
+
+These projects have been important references for thinking about automated research, open-ended exploration, evolutionary search, experiment organization, long-horizon research agents, collaborative LaTeX editing workflows, browser-based code editing experiences, rich notebook-style writing interactions, paper-figure generation and polish workflows, Nature-style scientific writing, data, figure, and presentation skills, and autonomous scientific simulation / package-knowledge workflows.
 
 ## Personal acknowledgements
 
 We also sincerely thank the following researchers, collaborators, and supporters:
 
-- Shichen Li
-- Guangsheng Bao
-- Fuchen Shen
-- Wenyang Gao
-- Luodan Zhang
-- Junshu Pan
-- Panzhong Lu
+- [Shichen Li](https://www.google.com/search?q=%22Shichen+Li%22)
+- [Siqi Wen](https://www.google.com/search?q=%22Siqi+Wen%22)
+- [Guangsheng Bao](https://www.google.com/search?q=%22Guangsheng+Bao%22)
+- [Fuchen Shen](https://www.google.com/search?q=%22Fuchen+Shen%22)
+- [Wenyang Gao](https://www.google.com/search?q=%22Wenyang+Gao%22)
+- [Luodan Zhang](https://www.google.com/search?q=%22Luodan+Zhang%22)
+- [Junshu Pan](https://www.google.com/search?q=%22Junshu+Pan%22)
+- [Panzhong Lu](https://www.google.com/search?q=%22Panzhong+Lu%22)
 
 We are grateful to all of the above projects and individuals.

package/docs/en/README.md

@@ -28,18 +28,37 @@ AI Scientist and AutoFigure projects worth exploring alongside DeepScientist:
 
 This page is the shortest path to the right document.
 
+Built-in runners today:
+
+- `codex`
+- `claude`
+- `kimi`
+- `opencode`
+
 ## If you are new
 
 - [00 Quick Start](./00_QUICK_START.md)
-  Start here if you want to install DeepScientist, launch it locally, and create your first project.
+  Start here if you want to install DeepScientist, choose between Codex / Claude Code / Kimi Code / OpenCode, launch it locally, and create your first project.
 - [20 Workspace Modes Guide](./20_WORKSPACE_MODES_GUIDE.md)
   Read this if you want to choose correctly between Copilot and Autonomous before creating a project.
-- [19 Local Browser Auth](./19_LOCAL_BROWSER_AUTH.md)
+- [31 Local Browser Auth](./31_LOCAL_BROWSER_AUTH.md)
   Read this if you want to understand the local password prompt, where to find the password, and how to disable it.
+- [32 Windows + WSL2 Deployment Guide](./32_WINDOWS_WSL2_DEPLOYMENT_GUIDE.md)
+  Read this if you are on Windows and want the recommended WSL2-based deployment path instead of guessing the environment setup.
 - [05 TUI Guide](./05_TUI_GUIDE.md)
-  Read this if your main surface is the terminal and you want one end-to-end path through `ds --tui`, quests, connectors, and cross-surface work.
+  Read this if your main surface is the terminal and you want one end-to-end path through `ds --tui`, quests, connectors, cross-surface work, and TUI debug snapshots.
 - [15 Codex Provider Setup](./15_CODEX_PROVIDER_SETUP.md)
-  Read this when you want to run DeepScientist through MiniMax, GLM, Volcengine Ark, Alibaba Bailian, or another Codex profile.
+  Read this when you want to run DeepScientist through OpenAI, Ollama, MiniMax, GLM, Volcengine Ark, Alibaba Bailian Coding Plan, or another Codex profile. Gemini through Codex is an advanced experiment; OpenCode is usually the better Gemini route.
+- [24 Claude Code Setup](./24_CLAUDE_CODE_PROVIDER_SETUP.md)
+  Read this when Claude Code already works on your machine and you want DeepScientist to reuse it directly, or when you want to use Ollama through its Anthropic-compatible API.
+- [27 Kimi Code Setup](./27_KIMI_CODE_PROVIDER_SETUP.md)
+  Read this when the official Kimi Code CLI already works on your machine and you want DeepScientist to use it as a separate builtin runner.
+- [25 OpenCode Setup](./25_OPENCODE_PROVIDER_SETUP.md)
+  Read this when OpenCode already works on your machine and you want DeepScientist to reuse its provider/model configuration, especially for Gemini or Ollama.
+- [21 Local Model Backends Guide](./21_LOCAL_MODEL_BACKENDS_GUIDE.md)
+  Read this if you want to run DeepScientist through local model backends such as vLLM, Ollama, or SGLang and need to choose between Codex, Claude Code, and OpenCode.
+- [26 Citation And Attribution](./26_CITATION_AND_ATTRIBUTION.md)
+  Read this if DeepScientist materially helped a paper or report and you want the preferred citation, acknowledgment wording, and attribution boundary.
 - [12 Guided Workflow Tour](./12_GUIDED_WORKFLOW_TOUR.md)
   Follow the real product flow from landing page to workspace, step by step.
 - [02 Start Research Guide](./02_START_RESEARCH_GUIDE.md)
@@ -52,14 +71,22 @@ This page is the shortest path to the right document.
 - [20 Workspace Modes Guide](./20_WORKSPACE_MODES_GUIDE.md)
   Use this when the main question is not “how do I fill the form?” but “should this project start as Copilot or Autonomous?”.
 - [01 Settings Reference](./01_SETTINGS_REFERENCE.md)
-  Use this when you need to configure runners, connectors, runtime defaults, or home paths.
+  Use this when DeepScientist is already running and you want to configure runtime defaults, models, connectors, baselines, DeepXiv, extensions, or MCP from the visual Settings page before touching raw YAML.
+- [30 Settings Control Center Guide](./30_SETTINGS_CONTROL_CENTER_GUIDE.md)
+  Use this when the question is not configuration but runtime supervision: summary, hardware, diagnostics, errors, logs, quests, repairs, controllers, stats, or search.
 - [11 License And Risk Notice](./11_LICENSE_AND_RISK.md)
   Read this first if you care about the license boundary, server safety, fabricated outputs, connector leakage, and public exposure risk.
+- [26 Citation And Attribution](./26_CITATION_AND_ATTRIBUTION.md)
+  Use this when the question is not runtime risk but how to cite or acknowledge DeepScientist fairly in research outputs.
 
 ## If you want to collaborate through external surfaces
 
 - [16 Telegram Connector Guide](./16_TELEGRAM_CONNECTOR_GUIDE.md)
   Bind Telegram through the built-in polling runtime and continue quests from bot chats.
+- [28 Discord Connector Guide](./28_DISCORD_CONNECTOR_GUIDE.md)
+  Configure the built-in Discord gateway connector from the Settings page and keep the workflow visual-first.
+- [29 Slack Connector Guide](./29_SLACK_CONNECTOR_GUIDE.md)
+  Configure the built-in Slack Socket Mode connector from the Settings page after launch.
 - [17 WhatsApp Connector Guide](./17_WHATSAPP_CONNECTOR_GUIDE.md)
   Bind WhatsApp through the local-session runtime and continue quests from local chat sessions.
 - [18 Feishu Connector Guide](./18_FEISHU_CONNECTOR_GUIDE.md)
@@ -88,22 +115,36 @@ This page is the shortest path to the right document.
 
 - [09 Doctor](./09_DOCTOR.md)
   Start here for diagnostics and common runtime problems.
+- [33 Workspace Explorer Q&A](./33_WORKSPACE_EXPLORER_QA.md)
+  Check this when files or folders exist in the terminal but do not appear in Web Explorer or Search; it explains active worktrees, `FILES` / `SCOPE`, refresh behavior, and Git status boundaries.
+- [30 Settings Control Center Guide](./30_SETTINGS_CONTROL_CENTER_GUIDE.md)
+  Use this when you want the operator view of summary, hardware, diagnostics, errors, logs, quests, repairs, controllers, stats, and search.
 - [15 Codex Provider Setup](./15_CODEX_PROVIDER_SETUP.md)
   Check this if the problem is likely in your Codex profile, provider endpoint, API key, or model configuration.
+- [24 Claude Code Setup](./24_CLAUDE_CODE_PROVIDER_SETUP.md)
+  Check this if the problem is likely in your Claude Code login, config directory, permission mode, or Anthropic-compatible gateway setup.
+- [27 Kimi Code Setup](./27_KIMI_CODE_PROVIDER_SETUP.md)
+  Check this if the problem is likely in your Kimi Code login, `~/.kimi` home, agent selection, or `--yolo` / thinking configuration.
+- [25 OpenCode Setup](./25_OPENCODE_PROVIDER_SETUP.md)
+  Check this if the problem is likely in your OpenCode provider login, config file, model selection, agent, or variant setup.
+- [21 Local Model Backends Guide](./21_LOCAL_MODEL_BACKENDS_GUIDE.md)
+  Check this if the problem is specifically about local OpenAI-compatible backends and whether they support `/v1/responses`.
 - [01 Settings Reference](./01_SETTINGS_REFERENCE.md)
   Check this if the problem is likely caused by config, credentials, or connector setup.
 
 ## If you are developing DeepScientist
+- [23 BenchStore GitHub Releases Spec](./23_BENCHSTORE_GITHUB_RELEASES_SPEC.md)
+  Read this when you want to publish BenchStore benchmark source packages on GitHub Releases and make the frontend Download flow work for users.
 
 - [90 Architecture](./90_ARCHITECTURE.md)
   High-level system contracts and repository structure.
 - [91 Development](./91_DEVELOPMENT.md)
-  Maintainer-facing workflow and implementation notes.
+  Maintainer-facing workflow, implementation notes, and the concrete checklists for adding MCP tools, skills, and connectors.
 
 ## Community
 
 Welcome to join the WeChat group for discussion.
 
 <p align="center">
-  <img src="../../assets/readme/wechat.jpg" alt="DeepScientist WeChat group" width="360" />
+  <img src="../../assets/readme/wechat6.jpg" alt="DeepScientist WeChat group" width="360" />
 </p>