SDK regeneration

[fern-api]

Automated SDK generation by Fern

[mikekono]

🤖 I tested the Reporting API changes against https://connect.squareupstaging.com and pushed a fix commit (819006a0).

What was wrong:

• LoadResponse was generated as { results: LoadResult[] }, but staging and the public Reporting docs return a top-level row payload: { data: [...] } with sibling fields like annotation, dataSource, lastRefreshTime, query, external, and dbType. The old model made successful /reporting/v1/load calls look like they had no results.
• TimeDimension.dateRange was generated as an object only, but the API accepts documented string ranges like "last 30 days" and array ranges like ["2026-05-01", "2026-05-31"]. The SDK serializer rejected the string form before sending the request.
• Reporting filter union branches had optional discriminator fields, so { or: [...] } / { and: [...] } could be serialized through the condition branch and stripped to {}. I made member/operator, or, and and required in their respective variants.
• Query.responseFormat was exposed by the generated model, but staging rejects responseFormat: "compact" and responseFormat: "columnar" with HTTP 400. I removed it from the request model for now.
• The live integration test and README were still asserting/logging response.results; they now use response.data.

Validation performed:

• yarn test:unit --testPathPattern reporting ✅ 7 tests
• yarn test:wire --testPathPattern reporting ✅ 3 tests
• yarn build ✅
• yarn test ✅ 126 suites / 869 tests
• live staging integration: TEST_SQUARE_BASE_URL=https://connect.squareupstaging.com yarn test:integration --testPathPattern reporting ✅ 3 tests
• additional staging matrix ✅ 12/12 checks: metadata schema, direct load, loadAndWait, string/array date ranges, tuple ordering, pagination, simple filters, compound or/and filters, segments, and cache mode.

Notes for Fern/API definition follow-up:

• Please update the source API definition/generator inputs so LoadResponse, TimeDimension.dateRange, Reporting filters, and absence of responseFormat regenerate this shape. These files are generated, so the SDK-side patch is a band-aid unless Fern emits the corrected models.
• Direct HTTP to staging also rejects object-form order even though docs show it; tuple-array order works. That looks like either docs drift or API-definition drift worth reconciling separately.