[GaspardPeduzzi]

What

• Adds extensions.reported (boolean) to token.schema.json. Without it, additionalProperties: false rejects the key. The description says to set it on the token's own entry, never inside a wrapper's extensions.vault.
• Sets "reported": true on mevUSDC (Silo, Avalanche 0x4dc1…c0e8). Users reported it as illiquid at the Silo level.
• Adds a README row for the key.

Why

spectra-app#2293 asks for an orange "This market has been reported by users. Proceed with caution." warning:

• above the CTA of every market built on a reported IBT;
• behind an (i) next to the IBT name.

spectra-app#2294 adds it. The flag belongs with the token rather than in the app, so the team can raise and lift it without an app release. It is set on the token's own entry, not per pool. The Spectra API forwards it to every market built on the token:

• directly: PT-mevUSDC;
• through its Spectra wrapper: PT-sw-mevUSDC. The API resolves the wrapper through its extensions.vault, so nothing needs to be set on sw-mevUSDC.

Deleting the key lifts the warning everywhere. Flags are report-based, non-exhaustive and not an audit.

Verification

• Schema validation mirroring token-validation.yml (ajv 6, allErrors): tokens 390/390, wrappers 114/114, protocols 1/1 valid.
• bun run src/build.ts && tsup: spectraTokens mevUSDC carries reported: true, and no other token or wrapper does.
• /all, /tokens and /wrappers pass extensions through untouched, so tokens.spectra.finance will serve the key after the usual publish + deploy hook.

Merge order: this one can go first.

• Market pages warn once the API forwards the flag (perspectivefi/spectra-sdk#268, then an API release).
• The app's pool-creation flow reads /all directly (spectra-app#2294), so it warns as soon as this is live and #2294 is deployed.
• Please merge it on its own: back-to-back merges collide in the version-bump job.

🤖 Generated with Claude Code