Add schedule & closing entry APIs, remove legacy extensions

[jfrench9]

Summary

This PR introduces comprehensive schedule management and period closing capabilities to the ledger API while removing deprecated client extensions (Subgraph Workspace and View Builder). It also refactors the mapping association response model for consistency.

Key Accomplishments

New Ledger API Endpoints

• Create Schedule (create_schedule.py) — Create new schedules with metadata and entry templates
• List Schedules (list_schedules.py) — Retrieve available schedules
• Get Schedule Facts (get_schedule_facts.py) — Fetch fact data associated with schedules
• Create Closing Entry (create_closing_entry.py) — Support for period-end closing entries
• Get Period Close Status (get_period_close_status.py) — Query the status of period close processes

New Models (16 added)

• Schedule domain: CreateScheduleRequest, ScheduleCreatedResponse, ScheduleSummaryResponse, ScheduleListResponse, ScheduleFactResponse, ScheduleFactsResponse, ScheduleMetadataRequest, ScheduleSummaryResponseEntryTemplateType0, ScheduleSummaryResponseScheduleMetadataType0
• Closing entry domain: CreateClosingEntryRequest, ClosingEntryResponse
• Period close domain: PeriodCloseStatusResponse, PeriodCloseItemResponse, PeriodSpec
• Supporting: EntryTemplateRequest

Refactoring

• Renamed ElementAssociationResponse → AssociationResponse for broader applicability (R097 — 97% similarity)
• Updated MappingDetailResponse and create_mapping_association API to reference the renamed model
• Extended CreateReportRequest, RegenerateReportRequest, ReportResponse, FactRowResponse, and StatementResponse with additional fields and updated type handling
• Added new enum values to CreateStructureRequestStructureType and CreateTaxonomyRequestTaxonomyType

Removed Legacy Extensions

• Deleted SubgraphWorkspaceClient (746 lines) — deprecated subgraph workspace functionality
• Deleted ViewBuilderClient (601 lines) — deprecated view builder functionality
• Updated extensions __init__.py to remove all exports (module retained but emptied)

Breaking Changes

⚠️ High impact — these are breaking changes:

1. ElementAssociationResponse renamed to AssociationResponse — Any code importing or referencing ElementAssociationResponse must be updated.
2. SubgraphWorkspaceClient removed — Consumers relying on this extension must migrate to alternative approaches.
3. ViewBuilderClient removed — Consumers relying on this extension must migrate to alternative approaches.
4. Extensions module emptied — from robosystems_client.extensions import * will no longer provide any classes.
5. Modified response/request models — StatementResponse, FactRowResponse, CreateReportRequest, and RegenerateReportRequest have structural changes that may affect deserialization in downstream consumers.

Testing Notes

• Verify all new API endpoints return expected response models with valid payloads
• Confirm schedule CRUD lifecycle works end-to-end (create → list → get facts)
• Validate closing entry creation and period close status retrieval
• Ensure the renamed AssociationResponse model correctly deserializes in mapping association flows
• Regression test any existing functionality that previously used ElementAssociationResponse, StatementResponse, or FactRowResponse given field changes
• Confirm no remaining references to removed extensions in dependent services

Infrastructure Considerations

• This is a client library update — downstream services consuming robosystems_client will need to update their dependencies and adapt to breaking changes
• The removal of extensions reduces the overall package footprint by ~1,350 lines, simplifying maintenance
• New API endpoints imply corresponding backend services must be deployed and available before client adoption

---

🤖 Generated with Claude Code

Branch Info:

• Source: feature/schedules
• Target: main
• Type: feature

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