From 042a0a90b36089a7a64bc9d1cb5efdbfeb637e2c Mon Sep 17 00:00:00 2001 From: Eric Viana Date: Tue, 4 Aug 2026 15:45:26 -0300 Subject: [PATCH] fix(api-sync): drop stale spec-map ignore.schemas entries The v5.3.0 spec refresh (#72) removed CreateInstanceRfiBody, CreateRfiBody, and LedgerOperation from the API spec, but .api-sync/spec-map.json's ignore.schemas still listed all three, failing map.test.ts's "every ignore.schemas name exists in the spec's components.schemas" check on main. Verified every remaining ignore.schemas entry (including the other Rfi-family ones: InstanceRfi, Rfi, RfiField, RfiSection) still resolves against the committed spec-snapshot.json; only these three were stale. Claude-Session: https://claude.ai/code/session_01F1stiNzuNtJXoXtiW9ZCbs --- .api-sync/spec-map.json | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/.api-sync/spec-map.json b/.api-sync/spec-map.json index 95e0aac..7625ae8 100644 --- a/.api-sync/spec-map.json +++ b/.api-sync/spec-map.json @@ -1758,14 +1758,6 @@ "name": "BlockchainWalletWebhookOut", "reason": "Webhook payload body for blockchainWallet.new; same reasoning as BankAccountWebhookOut." }, - { - "name": "CreateInstanceRfiBody", - "reason": "Orphan schema, same situation as CreateRfiBody." - }, - { - "name": "CreateRfiBody", - "reason": "Orphan schema (zero $ref anywhere; the actual POST /rfi request body is inline `{type: object, additionalProperties: {}}`, not $ref'd to this schema). Grouped with the Rfi family since it is a request-body remnant for the unmodeled RFI resource." - }, { "name": "CustomerDeleteWebhookOut", "reason": "Webhook payload body for customer.delete; same reasoning as BankAccountWebhookOut." @@ -1782,10 +1774,6 @@ "name": "InstanceRfi", "reason": "Instance-level RFI variant; not modeled, same as Rfi." }, - { - "name": "LedgerOperation", - "reason": "unreferenced by any public operation" - }, { "name": "LimitIncreaseNewWebhookOut", "reason": "Webhook payload body for limitIncrease.new; same reasoning as BankAccountWebhookOut."