Replace schedule operations with information block operations in ledger client

[jfrench9]

Summary

Refactors the ledger client to replace the schedule-based domain model with a new Information Block abstraction. This is a significant domain shift that renames and restructures CRUD operations, request/response models, and GraphQL queries throughout the client library. Additionally, a new Evaluate Rules operation is introduced.

Key Accomplishments

Domain Model Replacement

• Renamed all schedule operations (op_create_schedule, op_delete_schedule, op_update_schedule) to their information block equivalents (op_create_information_block, op_delete_information_block, op_update_information_block)
• Removed schedule-specific models: CreateScheduleRequest, UpdateScheduleRequest, DeleteScheduleRequest, ScheduleMetadataRequest, EntryTemplateRequest, and EntryTemplateRequestEntryType
• Added new information block models: CreateInformationBlockRequest, CreateInformationBlockRequestPayload, UpdateInformationBlockRequest, UpdateInformationBlockRequestPayload, DeleteInformationBlockRequest, DeleteInformationBlockRequestPayload

New Evaluate Rules Operation

• Implemented op_evaluate_rules — a new operation (301 lines) for evaluating rules against the ledger
• Added corresponding EvaluateRulesRequest model

Client & Query Layer Updates

• Updated ledger_client.py to expose information block operations and the new evaluate rules operation
• Updated GraphQL query definitions in the ledger module to align with the new information block schema
• Updated model re-exports in models/__init__.py

Breaking Changes

⚠️ This is a breaking change. All consumers of the ledger client that reference schedule operations or schedule-related models will need to migrate:

• create_schedule → create_information_block
• update_schedule → update_information_block
• delete_schedule → delete_information_block
• All *ScheduleRequest / *ScheduleMetadataRequest / EntryTemplateRequest* models are removed and replaced with *InformationBlock* equivalents
• The request payload structure has been simplified (e.g., removal of EntryTemplateRequest and ScheduleMetadataRequest in favor of a flatter payload model)

Testing Notes

• test_ledger_client.py has been substantially updated (124 lines changed) to cover the new information block operations and evaluate rules functionality
• Tests reflect the new model structures and client method signatures
• Verify that all downstream services and integrations are updated to use the new API surface before merging

Infrastructure Considerations

• GraphQL schema changes are required on the server side to support information block mutations and the evaluate rules query/mutation
• Ensure the backend ledger service has been updated or is being deployed in coordination with this client change
• Any CI/CD pipelines that depend on the old schedule-based models or operations will need to be updated

---

🤖 Generated with Claude Code

Branch Info:

• Source: feature/information-block
• Target: main
• Type: feature

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