x402 Bazaar discovery not re-indexing re-settled resources (seller 402.com.tr)

We operate the seller at **402.com.tr** (100+ x402 services on Base, settling via the CDP facilitator). We have a consistent Bazaar discovery-indexing problem, with clean on-chain proof.

**Symptom:** 29 of our resources settle successfully but never appear in the Bazaar discovery index — while every *newly added* resource from the same seller indexes within ~1 day. On 2026-07-18 we re-settled all 29 cleanly (payer `0xFe21a68f21d556A3C4274a44c2Fb5410c50cDa1C` → payTo `0x973a31858f4d2125f48c880542da11a2796f12d6`), and 36+ hours later none have indexed.

**Likely cause:** these 29 share one history — their *first* settlements (months ago) carried a malformed extension payload. It looks like discovery deduped them on first-seen and won't re-evaluate them on later clean settlements. Newly-created resources (e.g. `wallet-delegation`, `commerce-escrow`, `commerce-operator-audit`, all indexed this week) confirm the normal path works — only these first-seen-broken ones are stuck.

**Ask:** could you re-trigger indexing / clear the dedupe state for these 29 resources? Each row is `service → endpoint → a recent clean settlement tx` (all on Base mainnet, 2026-07-18 06:37–06:51 UTC):

| service | endpoint | clean settlement tx (Base) |
|---|---|---|
| watchlist-diff | https://402.com.tr/api/x402/watchlist-diff | `0xfd5a4d344f849212ffe06547332366a472137dbf9e10feb335032df0b6d2e1b7` |
| address-intel | https://402.com.tr/api/x402/address-intel | `0x0a7660d579e85cfdce44583dec7152657bdbd55c8af3be5351d062fd7773b9a4` |
| gas-oracle | https://402.com.tr/api/x402/gas-oracle | `0x03e1bc19ef2e3acec38571b741b10a24eacf9722445b0c388819e94150ebc3dd` |
| token-price | https://402.com.tr/api/x402/token-price | `0xdc63fc976e3d40734a48d8451d51122f167178034a2698b8f7f13a100f725d90` |
| tx-decode | https://402.com.tr/api/x402/tx-decode | `0xce09ce4670f1cbc3cdc04030938bbc5e6e92ee9e585f7d4c01b1fc86240e799e` |
| exit-liquidity | https://402.com.tr/api/x402/exit-liquidity | `0xcb4336e8092614f78d759247cdd330d8ae45696998c3a79120fb258681019292` |
| holder-forensics | https://402.com.tr/api/x402/holder-forensics | `0xf86eb3c24b006897169987fe1f59a6bf6d93e4ae7c116f5f97d581f75166b8cf` |
| proxy-check | https://402.com.tr/api/x402/proxy-check | `0x792bf51c5cf2ffb79eb6d3ea2c407a2ccb3b3983609e84111d36f5d17ddc31a7` |
| lp-lock | https://402.com.tr/api/x402/lp-lock | `0x101bbbd1e8f79e34127189d3737792d8ed2ecfb0a338907ebd3d25896cd554d8` |
| deployer-rep | https://402.com.tr/api/x402/deployer-rep | `0xf91df66644a8948fdd6cad02cb7a19146754e737e87ef18498f128aa442a3b4d` |
| token-unlock | https://402.com.tr/api/x402/token-unlock | `0xfbb0babbae0ae9beefa22942972f1f0ca6705c0be94460d8998a1bc28b2ff329` |
| volume-check | https://402.com.tr/api/x402/volume-check | `0x7670f901105b61a2d035e631359385fbb74f5ae4a2416b13b3af5fb8562e8daf` |
| position-health | https://402.com.tr/api/x402/position-health | `0x06fec717cecfaab5b4d18600c4f6d9152888a4dc6f8d1c434e2eb99c9a134eff` |
| token-compare | https://402.com.tr/api/x402/token-compare | `0x7ec95f1c941b9d624938c5e729558754b2309fdd8f8bde69631d6f1b9015e452` |
| price-alert | https://402.com.tr/api/x402/price-alert | `0xc28455f8ef5ffb12e82b8028a4934967d131c774fef36ba1b1042a3a81a59f87` |
| basename | https://402.com.tr/api/x402/basename | `0x2a4da17300e4d14fa9877cdb1b905f3c948d498e7b5d81b56b7b74e0e3b84bb4` |
| revoke-builder | https://402.com.tr/api/x402/revoke-builder | `0xb7bba0323278fde176f992ed75770de5630c7984cb92552950f68f1f6430d19a` |
| wallet-tokens | https://402.com.tr/api/x402/wallet-tokens | `0xa29cc285fbec16e6cf20b006861eb9e416661418157399437ddd50fb9e51c699` |
| trending-tokens | https://402.com.tr/api/x402/trending-tokens | `0x846abd9a6984e50ce1d905ef54d1a50de1a3b103bab8c962c653c94b0c3d411f` |
| token-pools | https://402.com.tr/api/x402/token-pools | `0x5f768b0f17dde1ea4160eb580cccd6b2af0a6e66656736bd0145632c5591d764` |
| sanctions | https://402.com.tr/api/x402/sanctions | `0xa9c82cec20ccedc5a2eb73e50d916f0f421d0b7044c5c6cc3c8d6ea4c9928423` |
| holders | https://402.com.tr/api/x402/holders | `0xbdc77c958239625aebaf1c5c379ecdc4ea95d1550d846ff2301ea68806e40fdc` |
| multi-price | https://402.com.tr/api/x402/multi-price | `0x759ff2e92be3407d5a4ccd054be233c4c72b2bc3f613203c6573831a18f2da57` |
| compliance-check | https://402.com.tr/api/x402/compliance-check | `0xfe32d43a21f63866ec597a40c1df02da7722d7c28e731c9415cac45cc6ae3d8e` |
| sanctions-batch | https://402.com.tr/api/x402/sanctions-batch | `0x2aba9926e3750aa62aa013bf1f329796dc08be9f8123e830d63cb880acee1fb6` |
| rug-score | https://402.com.tr/api/x402/rug-score | `0x26bed06128795082a6a338446fd5321e4e60a97ab76549ff2d846e74b9f85410` |
| batch-risk | https://402.com.tr/api/x402/batch-risk | `0xcc98f53fba7ac351c50b6ba21c55d2a884e64288e452a2f9a618a351ea085c8f` |
| token-momentum | https://402.com.tr/api/x402/token-momentum | `0xd6abb506db1fe43ad7da3a484c283659fb0e88ae6454563123211be548f85b4b` |
| token-info | https://402.com.tr/api/x402/token-info | `0xd0cff5fc34a7b6cc5a3f52ec753f40c2a464a8c39b7df84b5e05cd1ee68a17cf` |

The discovery endpoint we check: `GET https://api.cdp.coinbase.com/platform/v2/x402/discovery/resources`. All txs are verifiable on BaseScan. Happy to provide anything else — thanks!

Start by querying GET https://api.cdp.coinbase.com/platform/v2/x402/discovery/resources and comparing the listed resources with the 29 services and their Base settlement transactions. Trace how the discovery endpoint handles first-seen resources and later settlements, if that implementation is available in this repository. Done means the affected resources appear in the discovery index after clean settlements without manual intervention.

Written by the indexing model from the issue text.