[jfrench9]

Summary

A regeneration from the current API. It picks up three efforts:

• the graph-limits response now publishes only the limits the platform enforces;
• consolidation's opening entries and the worksheet's omitted columns;
• the consolidated-report wording on create-report (feat(roboledger): a consolidated report is the consolidation entity's robosystems#1878).

No hand-written facade needed a change: every affected facade returns the generated models as they are, and none reads a removed field.

Changes

All generated (api/, models/), no hand-written changes:

• Graph limits:
  • GraphLimitsResponse.storage, .copy_operations and .backups are now optional, because they are user graphs only.
  • Removed fields: BackupLimits.max_backup_size_gb, GraphTierBackup.max_backup_size_gb, QueryLimits.concurrent_queries, and CopyOperationLimits / GraphTierCopyOperations .timeout_seconds, .concurrent_operations, .max_files_per_operation, .daily_copy_operations.
  • Added BackupLimits.max_downloads_per_month.
  • Descriptions reworded across the limit models.
• Consolidation: ConsolidationProposal.opening and ConsolidationWorksheetResponse.omitted_periods, both optional; reworded posting_date, joined_on / left_on and omitted_periods descriptions.
• Reports: create_report and CreateReportRequest.entity_id describe the consolidation entity's report.

Compatibility

Generated tier, so a client minor; the removals must be named in its release notes.

• Additive: the two consolidation fields and max_downloads_per_month.
• Removed and loosened (generated tier):
  • The fields listed above are gone. Nothing in the stable tier or the integration template's emit path uses them.
  • The three limit sections are now None for a shared repository.
• Consumers checked: robosystems-app, roboledger-app and roboinvestor-app read none of the removed fields. The usage page's max_timeout_seconds stays.

Testing

just test-all passes: 699 passed, 17 skipped; ruff, format, basedpyright clean.

🤖 Generated with Claude Code