cradle-clilisted

# Cradle CLI Use `cradle` to manage Cradle or query its state from the terminal. You can use it for quick queries, scripted interactions, or as a reference for how the HTTP API maps to user-friendly commands. ## Core Rules - Prefer `cradle` for Cradle-owned product semantics. Use ordinary shell tools for local file/process work, but do not replace Cradle session awaits, issue state, delegation, Chronicle, automation, workspace, usage, or observability workflows with ad hoc scripts. - For waiting on external or future events, register a Cradle session await and end your turn. Do not use `sleep`, long polling loops, `gh run watch`, or repeated manual checks when Cradle has an await source for the condition. - Use `gh` only for GitHub actions that Cradle does not expose. If the goal is to pause this session until CI or PR review changes, use `cradle session await ...`. - `cradle man` prints the full generated command manual. Use `cradle man <module>` or `cradle man <command...>` to narrow it. - This skill is not the full route list. It gives operating patterns and an auto-generated module index; exact commands come from `cradle man`. - Default output is human-readable. Use `--json <fields>` for Agent workflows and `--format json` for compact pipeline output. - Most relationships use IDs, but issue statuses are Agent-facing names/slugs. Use status names like `triage`, `to_do`, or `in_progress` instead of status IDs when creating or moving issues. - Use `--server <url>` only wh