What

Adds five FAQ answers collected from community support (Sep 21 – Oct 4). Each one is based on a maintainer reply or a merged fix.

faq/troubleshooting.md

1. A bot published to the agent marketplace shows "model does not exist" for other accounts. Explains the cause (the referenced model was resolved as the caller instead of the publisher) and points to the fix in fix(console): resolve models for published bots  #1681, which was merged after v1.1.2. The answer gives the exact pull + up -d commands for console-hub and console-frontend. In the reported case, the user first only recreated the containers and kept seeing the error, so the answer warns about that and links to the existing latest-image entry in setup.md.

faq/features.md

2. Workflow publish still fails after the basic info is filled in. Extends the existing "发布不成功" entry with the workflow_version deleted-state bug that fix(console): resolve models for published bots  #1681 also fixes.
3. Does the open-source edition have team spaces? Yes. Shows the entry point next to "个人空间" (with a screenshot) and links to the existing review-rules entry.
4. How to enable the E2B sandbox for Agent Skills. Lists the steps under Resource Management → Script Sandbox. It points out the enable switch at the top of the dialog, which users missed, and what happens when E2B is off. Includes a screenshot.
5. Can Skill scripts read the deployment .env? No, because they run inside the E2B sandbox.

Notes

• Two screenshots are added under faq/assets/.
• New features.md entries are appended at the end, and the troubleshooting entry is inserted before the MinIO 403 entry. This keeps them away from the lines docs(faq): add workflow code-node, trace and log entries from community support #1685 touches, so the two PRs can merge in either order.
• Files keep their CRLF line endings; docs only.