test: verify migrate-success warnings handling (v2026-02-01)

[jeffredodd]

Summary

⚠️ Sub-PR off #2233 (the v2026-02-01 base bump).

v2026-02-01 adds a warnings[] array to migrate-success responses. The migrate flow is partner-driven; no SDK component in src/ currently consumes the migrate-success response shape, so this is verify-only at the SDK layer.

Changes

• e2e/tests/company/04-migrate-warnings-handling.spec.ts (new): asserts the SDK doesn't choke when migrate-success carries a warnings[] array.

Currently test.skip — un-skip once we have a Demo scenario that provisions a fresh pre-migration company (tracked alongside SDK-999).

Open follow-up

If we later decide to surface warnings to partners (e.g. a hook return value or a toast), that's a separate feature PR — not part of this bump.

References

• Notion deep-dive: https://app.notion.com/p/387ad673c6c2811cb9f1c4a9aac7be46
• Jira: SDK-1000

Test plan

• CI green after the base PR's dep bump
• Stage a fresh pre-migration scenario and un-skip the spec
• Decide on partner-facing warnings surfacing (separate PR)

🤖 Generated with Claude Code

[jeffredodd]

Superseded by the base PR #2233 — the E2E scaffold for this breaking change was moved onto the base branch so the upgrade-base CI shows the verification trail directly (per Jeff's review-flow ask). This sub-PR's diff is now empty and can be closed; no further SDK code change was needed for this breaking change.