Add native accounting operations and enhance API error handling

[jfrench9]

Summary

This PR introduces a comprehensive set of native accounting (RoboLedger) CRUD operations and significantly enhances error handling and response parsing across all RoboInvestor and GraphQL API operations in the robosystems_client.

Key Accomplishments

New RoboLedger Operations (16 new endpoint modules)

• Elements: Create, update, and delete accounting elements with full support for balance types, classifications, element types, period types, and source enums
• Journal Entries: Create, update, delete, and reverse journal entries with line item support
• Associations: Bulk create, update, and delete associations (including bulk association items with typed association types)
• Schedules: Delete, update, and manage schedules (including truncation)
• Structures: Delete and update organizational structures
• Taxonomies: Delete and update taxonomy definitions

New Models (30+ new model files)

• Request models for all new operations (CreateElementRequest, CreateJournalEntryRequest, BulkCreateAssociationsRequest, etc.)
• Supporting enum models for typed fields (CreateElementRequestBalanceType, CreateJournalEntryRequestType, UpdateElementRequestClassificationType0, etc.)
• JournalEntryLineItemInput for structured journal entry line items
• OperationError and OperationErrorDetailType1 for standardized error representation
• OperationEnvelope updates to support the new error structure

Enhanced Error Handling & Response Parsing

• All existing RoboInvestor operations (9 modules: create/update/delete for portfolio, position, security) updated with improved error handling and richer response parsing
• All existing RoboLedger operations (20+ modules) updated with consistent error handling patterns
• GraphQL operations (GET and POST handlers) enhanced with better response parsing
• Ledger client (ledger_client.py) updated to integrate with new operations

Breaking Changes

• OperationEnvelope model has been updated — consumers relying on the previous error field structure should update to use the new OperationError model
• New operations may introduce additional required dependencies or import paths in the models/__init__.py module

Testing Notes

• Verify all new CRUD operations for elements, journal entries, associations, schedules, structures, and taxonomies against the API
• Test error scenarios to validate the enhanced error handling produces correctly structured OperationError responses across all modules
• Confirm backward compatibility of existing RoboInvestor and GraphQL operations after the error handling refactor
• Validate enum models serialize/deserialize correctly for all typed request fields (balance types, classifications, period types, etc.)
• Test the reverse journal entry flow end-to-end as it represents a new business operation

Infrastructure Considerations

• The significant number of new model and operation files (85 files changed) suggests this was likely generated or scaffolded from an updated API specification — ensure the code generation tooling and API spec are version-tracked accordingly
• The models/__init__.py module has been updated to export all new models; downstream consumers pulling from this package will pick up the new types automatically
• No new external dependencies appear to be introduced; changes are additive within the existing client architecture

---

🤖 Generated with Claude Code

Branch Info:

• Source: feature/native-accounting-ops
• Target: main
• Type: feature

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