feat: add EventBlock type and refactor SyncConnectionRequest fields

[jfrench9]

Summary

This PR introduces the EventBlock type to the GraphQL schema and SDK, and refactors fields on SyncConnectionRequest to support the new event-driven ingestion architecture. These are primarily auto-generated type and query updates reflecting backend schema changes.

Changes

GraphQL Schema & Generated Types (clients/graphql/generated/graphql.ts)

• Added new EventBlock type definition to the generated GraphQL types
• Updated related queries to incorporate EventBlock in the schema
• Net addition of ~48 lines of new type definitions and query adjustments

SDK Types (sdk/types.gen.ts)

• Updated SyncConnectionRequest type fields to align with the new event-driven ingestion model
• Adjusted type definitions (+14/-3 lines), suggesting field additions/renames rather than removals

SDK Client (sdk/sdk.gen.ts)

• Minor update (1 line change) to keep the SDK client in sync with the updated type definitions

Key Improvements

• Lays the groundwork for event-driven ingestion by introducing EventBlock as a first-class type
• Refactored SyncConnectionRequest fields likely improve clarity and alignment with the new ingestion pipeline

Breaking Changes

• ⚠️ Potentially breaking: The refactored SyncConnectionRequest fields may require updates in any code that constructs or consumes this type. Consumers of the SDK should verify their usage of SyncConnectionRequest still compiles and behaves correctly.
• The EventBlock type is additive and should not break existing functionality.

Testing Notes for Reviewers

• Verify that all existing sync connection flows still work end-to-end with the updated SyncConnectionRequest fields
• Confirm that the new EventBlock type is correctly generated and matches the backend schema
• Check that no existing GraphQL queries or mutations are broken by the schema additions
• Since these are generated files, confirm the codegen source (schema/OpenAPI spec) has been updated and committed separately or is referenced appropriately
• Run the full type-check (tsc --noEmit) to ensure no downstream compilation errors

Browser Compatibility

• No browser compatibility concerns — these changes are limited to TypeScript type definitions and auto-generated client code with no runtime or UI impact.

---

🤖 Generated with Claude Code

Branch Info:

• Source: feature/event-driven-ingest
• Target: main
• Type: feature

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