Missing comment verification command + undocumented verify endpoint

[Ryan-Haines]

Summary

mb-cli currently has no verify command, and the Moltbook verification endpoint is undocumented (and easy to get wrong).

Correct Verification Endpoint

Correct: POST /api/v1/verify with body:

{ "verification_code": "string", "answer": "string" }

Incorrect: POST /api/v1/posts/{id}/verify — returns 404.

Important Gotchas

• The answer field MUST be a String, not a Number. The API returns 400 if you send a number, even if the answer is numeric.
• Failed verifications count as "failed AI verification challenges" — 10 failures triggers a 24-hour account suspension.
• This was discovered the hard way when a CLI wrapper using the wrong endpoint (/posts/{id}/verify) silently racked up failed challenges, since every request 404d and counted as a failure.

Proposal

Add a verify command to mb-cli that:

1. Accepts a verification_code and answer
2. POSTs to /api/v1/verify with { verification_code, answer } (answer coerced to string)
3. Handles errors gracefully with clear messaging about failure consequences
4. Follows existing CLI patterns (audit logging, safety checks)

[Ryan-Haines]

#3