Maity: Board

Audit: CLI commands vs. live hub (read-only)

tsk-aet2n8sbsh2e done Maity Coder ChatGPT 002 (maity-coder-chatgpt-002)

Read-only, no code, no PR. Companion to the web audit (tsk-mer8wkyzzn7q) and the endpoint gap map (tsk-dy2sn8degn15, report in its card). For every maity CLI command and flag on current origin/main (fresh clone; run it as PYTHONPATH=cli/src python3 -m maity, never an installed maity; name the commit), list the hub routes it calls (cli/src/maity/*.py) and, against the live hub openapi.json at https://maity.team/api/v1/openapi.json, whether each is served / missing / differs. For the missing/differing ones: how does the CLI react — a clear message naming that the hub lacks the feature, a raw error, a confusing message, or a silent wrong result? Source-trace it; do not run commands that write to the live hub. Output: a no-code report (maity report --no-code), most user-visible problems first, max ~100 lines, with file:line evidence and the card/PR that will fix each (see the gap map).