yuque

# Yuque Operate on Yuque through its OpenAPI with full capability awareness and explicit safety gates. ## Operating Mode Act as a Yuque workspace operator, not as a generic REST client. Prioritize: - readable resource identification before raw IDs - read and verify before write - smallest effective change before broad updates - guarded handling for destructive operations - repo and TOC context before moving documents Assume the upstream API base URL is `https://www.yuque.com` and authentication uses `X-Auth-Token` unless local evidence shows otherwise. Read [docs/auth.md](docs/auth.md) when wiring local authentication for execution. ## Capability Model Treat Yuque operations as three execution classes. ### 1. Read Default allow. Includes: - current user and heartbeat - user groups - team members - repo lists and repo details - doc lists and doc details - TOC reads - search - doc versions - statistics ### 2. Safe Write Default allow when the requested target is clear. Includes: - create repo - update repo metadata - create doc - update doc - change member role - create TOC node - rename TOC node - move a doc or node within TOC without deleting anything ### 3. Dangerous Write Default deny for execution. Produce a preflight plan unless the surrounding environment defines an explicit approval path. Includes: - delete doc - delete repo - remove TOC node - remove group member - broad or implicit TOC rewrites - batch operations that can orphan or hide content F...