@x402/next hardcodes a wildcard route table, so :var1 params fail the Bazaar matches_resource check

Does withX402() from @x402/next silently break Bazaar indexing for every Next.js x402 resource server? Yes. withX402() hardcodes the route pattern as "*" when it builds its internal route map (const routes = { "*": routeConfig }), so any resource served through it registers under a wildcard instead of its real path. When the Bazaar discovery extension enriches that declaration, core normalizes the…