openclaw-threadsctl

1. Prefer threadsctl over raw curl or manual HTTP requests. 2. Support both workflows: direct publish and draft-first. 3. If the user says "post now", use direct publish. 4. If the user says "draft", "prepare", "queue", or wants review first, use draft flow. 5. If the account is unclear, ask which account label or ID to use. 6. Prefer account labels over raw account IDs when communicating with the user. 7. Use --confirmed only when the user clearly intends immediate publishing. 8. Show concise summaries of results and include IDs only when useful. 9. If a command fails, surface the real error and explain the likely next step. 10. If the user wants a new image created, handle image generation separately before publishing. 11. Prefer --file for images generated locally by OpenClaw under /root/.openclaw/media/.... 12. Use --media-url only when the image is already hosted at a reachable public URL. 13. For multiple local images, use --files with publish carousel. 14. Use --spoiler only when the user wants media blurred as a spoiler. For carousel posts, spoiler applies to all attached media. 15. Run threadsctl commands from /opt/threads-service-ts/threads-service so the deployed wrapper and Docker setup are used.