fix(eve): unblock main typecheck after chat-sdk drift (#1504)

[iroiro147]

fix(eve): unblock main typecheck after chat-sdk drift (#1504)

Summary

CI typecheck and every downstream E2E job on main is failing because the vendored chat-sdk roll added two type requirements that callers don't yet satisfy:

1. Author gained required fullName: string.
2. MessageData gained required formatted: FormattedContent, metadata: MessageMetadata, attachments: Attachment[].
3. ActionEvent's thread field uses the interface's lone generic (TRawMessage) where it lands on Thread<TRawMessage, unknown> — so with the default TRawMessage = unknown, event.thread is Thread<unknown, unknown>, not assignable to the Thread<Record<string, unknown>, unknown> that bridgeSend accepts.

Reproduced on a clean checkout of origin/main (6ad578ae) with npx tsc --noEmit -p packages/eve: 5 errors across chatSdkChannel.ts:273, photon/inboundContent.test.ts, and photon/photonIMessageChannel.test.ts.

Fix

• src/public/channels/chat-sdk/chatSdkChannel.ts: narrow event.thread at the bridgeSend boundary with as unknown as Thread. Runtime is unaffected — serializeThread only calls thread.toJSON(). Two-line comment explains the variance mismatch. The file remains at exactly the 700-line production-source cap enforced by analytics.test.ts — tests still fail when accessed via the messages view wrapper (5 sites).
• src/public/channels/photon/photonIMessageChannel.test.ts: same rich stub, factored through a buildMessage(text, threadId) helper so the four call sites stay consistent.

Verification

• pnpm run typecheck — clean (was 5 TS errors).
• pnpm run test:unit → 5829 passed / 1 skipped / 4 pre-existing failures in test/bin-bootstrap.test.ts (Node ≥24 environment check; the runner is on v22.22.3). Reproduced identically on a clean checkout of origin/main with the patch stashed, so this is environmental and unrelated.
• Targeted: pnpm exec vitest run src/public/channels/photon src/public/channels/chat-sdk → 26/26 pass.

Compatibility / risk

• No production-code shape change; test stubs are additive only (extra required fields, plus the previously required ones). Existing successful test expectations are untouched.
• The cast at chatSdkChannel.ts:273 is a no-op at runtime; documents the variance mismatch at the seam where the SDK's drifted type meets our bridge.
• Longer-term fix is to update the chat-sdk ActionEvent interface so thread uses Thread<Record<string, unknown>, TRawMessage> (or similar); out of scope here since .generated/compiled/chat/* is vendored.

Fixes #1504

[vercel]

@iroiro147 is attempting to deploy a commit to the Vercel Team on Vercel.

A member of the Team first needs to authorize it.