chore(sdk): regenerate from API 1.10.x

[jfrench9]

Summary

Regenerates the SDK against the API's 1.10 line (1.10.0–1.10.4 plus the OAuth connected-apps endpoints landing in robosystems #1275). The client was last generated from 1.9.x. Net effect on the public surface: the REST MCP tool pair leaves api/mcp, the connected-apps and reconciling-item operations arrive, two close operations gain a flag, and the GraphQL schema snapshot picks up two fields. Curated release notes for the minor are included.

Changes

• Regenerated robosystems_client/api and models — removed: api/mcp/ (list_mcp_tools, call_mcp_tool) and the models MCPToolCall, MCPToolCallArguments, MCPToolsResponse, MCPToolsResponseToolsItem (the API dropped GET …/mcp/tools and POST …/mcp/call-tool in 1.10.2). Added: api/user/list_user_o_auth_grants, revoke_user_o_auth_grant (+ OAuthGrantInfo, OAuthGrantsResponse); api/extensions_robo_ledger/preview_reconciling_item, resolve_reconciling_item (+ the reconciling-item plan/delta/catch-up/request/response models and their operation envelopes). Widened: FiscalCalendarResponse gains reconciling_item_count / reconciling_item_sample; ClosePeriodOperation and BackfillPlanHistoryOperation gain allow_reconciling_items; DeleteSubgraphOp.backup_first and create_event_block carry richer descriptions. models/__init__.py follows.
• Refreshed graphql/schema.graphql (+10 lines: reconcilingItemCount, reconcilingItemSample on the fiscal calendar) and regenerated the ariadne models from it, so the CI drift gate stays clean.
• .github/release-notes/v1.12.0.md — the contract document for the minor: names the generated-tier removal and its replacement (the Streamable HTTP transport), and describes the additions.

No hand-written code changed. Facades and root exports are untouched.

Compatibility

Under the two-tier rule (CLAUDE.local.md § Versioning): ADDITIVE on the stable tier — with one generated-tier removal (api.mcp.*), which rides a minor and is named in the release notes. Checked by hand against the integration template's emit path: AuthenticatedClient, types.UNSET, all six emit operations (create_file_upload, ingest_file, materialize, create_event_block, assert_metrics, create_taxonomy_block) and their request models resolve in the regenerated tree; no facade referenced the removed operations. The removal meets the dead-surface test: the endpoints no longer exist upstream, and nothing in the stable tier or the template imported them. Intended version: 1.12.0 (the notes file is named for it; the bump itself stays with the release dispatch).

Testing

just generate-sdk (REST + schema refresh) and just generate-graphql against the local stack running robosystems main + #1275 (verified the two grants operations and no mcp paths in its openapi.json before generating).

just test-all — passes: 526 tests (17 skipped), ruff check and format clean, basedpyright 0 errors. The pre-commit hook re-ran the same gate on commit.

[jfrench9]

@claude please review this PR

[claude]

Claude encountered an error after 2s —— View job

---

I'll analyze this and get back to you.

[jfrench9]

@claude please review this PR — post-merge backfill: the review run failed on the previous token.

[claude]

Claude finished @jfrench9's task in 1m 44s —— View job

---

Review complete

• Gather context (PR body, diff, CLAUDE.md)
• Review generated API/model changes
• Review release notes file
• Check compatibility claims against versioning rules
• Post final review

Note: this is a post-merge backfill review — the PR was already merged, so I reviewed the merged state directly against the description rather than a live diff (network/gh/git fetch tools were unavailable in this sandboxed run).

The generated surface itself looks clean and internally consistent:

• api/mcp/* and the four MCP models are fully removed with no stray references anywhere in the tree except the release notes describing the removal.
• The new api.user.list_user_o_auth_grants / revoke_user_o_auth_grant and api.extensions_robo_ledger.preview_reconciling_item / resolve_reconciling_item operations follow the standard openapi-python-client shape (sync/async/detailed variants, status-code branches, docstrings) and match their models.
• models/__init__.py exports line up with the added/removed files — no dangling imports.
• ClosePeriodOperation, BackfillPlanHistoryOperation, and FiscalCalendarResponse gained the documented allow_reconciling_items / reconciling_item_count / reconciling_item_sample fields with correctly generated to_dict/from_dict handling.

One real gap I found:

GraphQL: the new schema fields aren't actually wired into the generated client. robosystems_client/graphql/schema.graphql:1222-1227 adds reconcilingItemCount / reconcilingItemSample to the FiscalCalendar type, but the query document at robosystems_client/graphql/operations/ledger/GetLedgerFiscalCalendar.graphql:2-13 was never updated to select them, so the corresponding generated Pydantic model in robosystems_client/graphql/generated/get_ledger_fiscal_calendar.py:14-36 doesn't expose either field. The REST FiscalCalendarResponse model gets both new fields, but the GraphQL path for the same data (GetLedgerFiscalCalendar) doesn't — despite the PR description implying the schema refresh closes the gap ("the GraphQL schema snapshot picks up two fields"). This is likely just an incomplete regen step (the operation .graphql files aren't auto-updated by just generate-graphql when the schema changes — someone has to add the field to the query by hand), rather than a hand-written bug, but it means a caller using the GraphQL client still can't see reconciling-item blockers on the fiscal calendar the way a REST caller can.

Fix this →

Everything else — the compatibility framing (generated-tier removal riding a minor, additive stable tier), the release notes content, and the two widened close operations — matches what's in the repo. No other issues found.