dramaclawlisted

# DramaClaw Follow the product manual and the repository's official skill. Treat the current source tree and live API responses as the authority for implementation details; treat the manual as the authority for production order and review boundaries. ## Start Every DramaClaw Task 1. Locate the active repository and project. On this machine the usual repository is `F:\DramaClaw`, but verify when paths or sessions differ. 2. Inspect the current source, CLI help, API routes, configuration, and project status before choosing commands. Do not infer endpoints or state from chat history. 3. Read [product-manual.md](references/product-manual.md) for production workflow, confirmation gates, 虾画 write-back, 3GS, 虾格, and quality checks. 4. Read [official-skill.md](references/official-skill.md) and the matching official reference only when API, async, update, resume, or delivery details are needed. 5. Read [local-patches-and-pitfalls.md](references/local-patches-and-pitfalls.md) whenever this machine's local fixes could be involved: model selection (Agnes/DeepSeek/embedding), sketch/render generation, audio/TTS, video backend, canvas projections, service startup, or after an upstream `git pull`. This file records every local code fix plus re-apply instructions so upstream updates do not silently overwrite them. 6. If copied documentation conflicts with the checked-out source, follow the current source and report the mismatch. Never invent a compatibility workaround. ## Local Machine C