fix(spec): expose event.data on Attempt when include=event.data

[alexluong]

Stacked on #916.

The bug

listAttempts({ include: ['event.data', 'response_data'] }) was returning attempt.event without the data payload, even though the server returns it on the wire.

Speakeasy's TS generator emits zod unions in declaration order, and z.union matches the first member that validates — it does not pick the best fit. The OpenAPI spec listed EventSummary before EventFull, and EventSummary is a plain (non-strict) z.object that silently accepts and strips any unknown keys — including data. So the union matched EventSummary first and dropped data before EventFull ever got a turn.

sdks/outpost-typescript/src/models/components/attempt.ts (before):

export const EventUnion$inboundSchema = z.union([
  z.lazy(() => EventSummary$inboundSchema),  // ← matches first, drops `data`
  z.lazy(() => EventFull$inboundSchema),
]);

export const EventSummary$inboundSchema = z.object({
  id: z.string().optional(),
  // …
  // no `data` field, no `.strict()` — extras silently dropped
});

This is a Speakeasy TS-generator pattern (not an OpenAPI spec problem, not a server problem). Other SDKs are unaffected:

• Python — Pydantic v2 smart-union picks EventFull when data is present ✅
• Go — tries EventSummary with disallowUnknownFields=true, falls through to EventFull ✅
• TS — Zod has no equivalent in z.union, so spec order matters ❌

Fix

Swap the oneOf order so EventFull is declared first:

 event:
   nullable: true
   oneOf:
-    - $ref: "#/components/schemas/EventSummary"
     - $ref: "#/components/schemas/EventFull"
+    - $ref: "#/components/schemas/EventSummary"

After regen, EventUnion$inboundSchema lists EventFull first and matches when data is present.

Test

TDD: failing test added that asserts attempt.event.data round-trips through listAttempts({ include: ['event.data', …] }).

Verified locally

• Regenerated TS SDK (./spec-sdk-tests/scripts/regenerate-sdk.sh TS) — EventUnion$inboundSchema now lists EventFull first
• New test passes
• Full spec-sdk-tests suite: 152 passing, 1 unrelated pre-existing SQS failure

SDK regen will follow via the standard Speakeasy bot flow once this merges. Considering an upstream Speakeasy request later so order-independence isn't required.