Refactor API methods with operation envelope wrappers for consistency

[jfrench9]

Summary

Large-scale refactoring of the robosystems_client API layer to improve consistency and readability across all API method modules. This PR touches 141 files spanning the entire client SDK surface — covering API endpoint handlers across all domains (agent, auth, backup, billing, connections, credits, documents, files, graphs, operations, org, schema, search, subgraphs, usage, user, etc.) as well as numerous model classes.

Key Changes

API Method Consistency (70+ endpoint files)

• Added consistent operation envelope patterns across all API endpoint modules (each receiving a +1 line change), standardizing how responses are wrapped and returned
• This uniform change across agent, auth, backup, billing, connections, credits, documents, extensions, files, graph health/info/limits, graphs, MCP, operations, org, org members, org usage, schema, search, service offerings, status, subgraphs, subscriptions, tables, usage, and user APIs suggests the introduction of a shared decorator, import, or envelope pattern

Enhanced API Methods

• sync_connection.py: Significantly reworked (+75 lines changed) — likely restructured to support additional operation envelope handling or improved async/polling behavior for connection sync operations
• create_graph.py: Notable expansion (+41 lines changed) — enhanced graph creation flow, potentially adding support for additional configuration options or operation tracking

Model Layer Updates (40+ model files)

• Broad updates to response and request model classes to align with the new envelope/wrapper patterns
• Affected models span agents, auth, backups, billing, connections, credits, documents, graphs, operations, schemas, transactions, and more
• Changes ensure model serialization/deserialization is consistent with the updated API response structures

Breaking Changes

⚠️ Potential breaking changes — consumers of this client library should be aware:

• API method return types may now be wrapped in operation envelopes, which could change how callers access response data
• Model structure changes may affect code that directly accesses model attributes or performs custom serialization
• The sync_connection and create_graph methods have undergone more substantial changes that may alter their signatures or behavior

Testing Notes

• Verify all API domains return correctly structured envelope responses
• Pay special attention to sync_connection and create_graph which received the most substantial changes
• Validate that model deserialization works correctly with the updated envelope format
• Integration tests should confirm backward compatibility or document migration steps for downstream consumers
• Check that async/sync client variants both handle the new patterns correctly

Infrastructure Considerations

• This is a client SDK change — no server-side infrastructure changes required
• Downstream services and applications consuming this client library will need to be validated against the updated response structures
• Consider a version bump strategy (semver) given the breadth of changes and potential breaking nature of envelope wrapping

---

🤖 Generated with Claude Code

Branch Info:

• Source: refactor/additional-ops-envelopes
• Target: main
• Type: feature

Co-Authored-By: Claude noreply@anthropic.com