agent: add adapter for Zomato

[alectimison-maker]

Summary

• add a narrowly scoped Zomato adapter for consumer restaurant-delivery pages
• mirror the guidance across Chrome and Firefox
• distinguish Delivery from Dining Out and Nightlife
• make location, exact branch, live orderability, menu choices, and delivery-specific ratings explicit
• treat promoted ranking, variable fees, and approximate ETA without overclaiming
• separate app-only/closed restaurants, cart, payment, and confirmed order states
• reject business/blog subdomains, embedded-domain URLs, and suffix look-alikes
• add positive, negative, content, bullet-count, and browser-parity coverage

Research

The guidance is dated 2026-08 and reflects current Zomato delivery/result/order pages plus the February 2026 Terms of Service covering address accuracy, fees, approximate timing, cancellation, refunds, and evidence requirements.

Test plan

• node test/run.js — new Zomato coverage passes; 1412 passed / 1 inherited failure because package.json is 26.0.4 while the newest CHANGELOG.md entry is 26.0.0
• npm run test:fixtures — 125/125 passed
• npm run test:security — 60/60 passed
• npm run test:ci — passed
• npm run test:webmcp — passed with Chrome 150.0.7871.187

Anonymous LLM scenarios were not run because they require an externally configured provider/API key and interactive headed setup; they are not part of the adapter-specific test seam.

[vercel]

@alectimison-maker is attempting to deploy a commit to the esokullu's projects Team on Vercel.

A member of the Team first needs to authorize it.