[mikepitre]

Why

Four recent fixes (#1027, #1055, #1059, #1064) were for FAPI responses the SDK serializers could not decode. Each fix added its own unit test. This adds one place to keep such response shapes, so the next one is a JSON file and not a new test.

What changed

• RecordedResponseDecodingTest decodes every file under source/api/src/test/resources/fapi/<type>/ with ClerkApi.json and the serializer registered for that directory. It lists every file that fails. A directory with no registered serializer also fails.
• Four fixtures, one per past bug: an RFC 3339 created_at, an enterprise connection without a logo, an unknown invitation status, and null role descriptions.

Scope

• The fixtures were copied from the fix PRs' tests, not recorded from live FAPI. The expired invitation status is invented.
• The test only checks that a response decodes, not what it decodes into. It would not have caught the swapped Verification.Status names (fix(api): correct swapped Verification.Status serial names #986) or the sessions converter bug (fix(api): decode active sessions from the plain JSON array #1002).

Verification

• :source:api:testDebugUnitTest --tests RecordedResponseDecodingTest on this branch: 1 test, 0 failures.
• The same test on 49d297c4^, before all four fixes: it fails and names each fixture with the decode error its fix addressed.

🤖 Generated with Claude Code

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}

[mikepitre]

Closing. Hand-written fixtures only guard the four shapes that already broke; they would stay green when FAPI drifts.