CLI: `documents move` returns HTTP 405 Method Not Allowed

[jacksweeney5]

Summary

omni documents move always returns 405 Method Not Allowed, regardless of body format. The command exists and has help text, but the underlying HTTP method appears to be incorrect (likely sending POST instead of PUT to the API).

Steps to Reproduce

# Attempt to move a dashboard into a folder
omni documents move f307e2eb --body '{"folderId": "91496caa-9e16-48d6-9a37-8fcca6e55341"}'

# Also tried with folderPath
omni documents move f307e2eb --body '{"folderPath": "testing-claude-dashboards"}'

Error Output

{
  "detail": "Method not allowed",
  "status": 405
}
Error: API returned HTTP 405

Workaround

Calling the API directly with PUT works:

curl -X PUT "https://<instance>.omniapp.co/api/v1/documents/f307e2eb/move" \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{"folderPath": "testing-claude-dashboards"}'

Expected Behavior

omni documents move <identifier> --body '{"folderPath": "..."}' should successfully move the document.

---

Updated by Claude

[ernestoongaro]

Verified against current main (available in v1.1.0+):

• omni documents move --schema reports PUT /api/v1/documents/{identifier}/move
• the embedded OpenAPI spec defines the move operation as put
• go test ./... passes

The corrected spec landed with #62. Closing as fixed.