v2: add old->real tool mapping audit

REMAP_AUDIT.md

@@ -0,0 +1,48 @@
+# Old mock surface -> real Swiggy MCP surface
+
+Generated 2026-07-26 by `remap/remap.py` from `evals/surface/` (35 tools) and the pristine dataset snapshot in `evals/_hf_snapshot/`.
+
+## Mapped
+
+| Dataset | Old tool | Real server | Real tool | Rows |
+|---|---|---|---|---|
+| `food-delivery-evals` | `search_restaurants` | food | `search_restaurants` | 26 |
+| `food-delivery-evals` | `view_menu` | food | `get_restaurant_menu` | 19 |
+| `food-delivery-evals` | `place_order` | food | `place_food_order` | 20 |
+| `food-delivery-evals` | `track_delivery` | food | `track_food_order` | 13 |
+| `food-delivery-evals` | `apply_promo` | food | `apply_food_coupon` | 13 |
+| `instamart-evals` | `search_grocery` | instamart | `search_products` | 29 |
+| `instamart-evals` | `view_product` | instamart | `search_products` | 17 |
+| `instamart-evals` | `add_to_cart` | instamart | `update_cart` | 12 |
+| `instamart-evals` | `checkout_cart` | instamart | `checkout` | 10 |
+| `instamart-evals` | `track_grocery_order` | instamart | `track_order` | 14 |
+| `dineout-evals` | `search_venues` | dineout | `search_restaurants_dineout` | 37 |
+| `dineout-evals` | `view_venue_details` | dineout | `get_restaurant_details` | 15 |
+| `dineout-evals` | `check_availability` | dineout | `get_available_slots` | 14 |
+| `dineout-evals` | `book_table` | dineout | `book_table` | 15 |
+
+## Dropped -- no real tool can carry these
+
+| Dataset | Old tool | Rows | Nearest tool considered | Why not |
+|---|---|---|---|---|
+| `food-delivery-evals` | `rate_restaurant` | 10 | `get_food_order_details (read-only; cannot record a rating)` | No rating or review write API exists on any of the three servers. The real Food surface is discovery, cart, order, track and support only; nothing accepts a star rating or review text. |
+| `food-delivery-evals` | `contact_driver` | 10 | `track_food_order (returns status, exposes no contact channel)` | No driver-contact channel exists on any server. track_food_order returns delivery progress, but the published schema exposes no phone number, message endpoint or delivery-partner identifier to contact. |
+| `instamart-evals` | `apply_grocery_promo` | 18 | `food.apply_food_coupon (wrong server; Food carts only)` | Instamart's 13-tool surface has no coupon or promo tool at all. Coupons exist only on the Food server (apply_food_coupon / fetch_food_coupons). Re-pointing grocery promo tasks at the Food coupon tool would both cross servers and assert Instamart coupon support that Swiggy does not publish. |
+| `dineout-evals` | `cancel_booking` | 19 | `get_booking_status (read-only; cannot cancel)` | No cancellation, refund or replacement write API exists on any server. Swiggy does publish an explicit do-not-call-a-tool instruction for cancellation -- but only for Food and Instamart ORDERS (place_food_order and checkout agent_guidance). It publishes nothing about cancelling a Dineout BOOKING, so re-targeting these 19 rows as BLOCKED_NO_TOOL would extend that instruction beyond its stated scope. The documented no-tool cancellation behaviour is tested instead in the model-selection suite, on the two servers where the text actually exists. |
+
+## Totals
+
+| Dataset | Original | Kept | Dropped |
+|---|---|---|---|
+| `food-delivery-evals` | 111 | 91 | 20 |
+| `instamart-evals` | 100 | 82 | 18 |
+| `dineout-evals` | 100 | 81 | 19 |
+| **total** | **311** | **254** | **57** |
+
+## Name collisions on the real surface
+
+SmolTrace scores `expected_tool` by exact tool-NAME membership, so these
+cannot be graded by name alone unless the agent mounts them server-prefixed:
+
+- `get_addresses` -- published on food, instamart
+- `report_error` -- published on food, instamart, dineout