@curless/hotel-storefront 0.27.4 → 0.27.6

package/README.md

@@ -5,7 +5,7 @@ vocabulary and where the rooms come from live in a `HotelConfig`, so the second
 hotel group is a JSON file rather than a fork.
 
 ```bash
-npx curless-hotel-storefront ./config.json   # a brand's own repo, e.g. curless-group1/shangrila-mcp
+npx @curless/hotel-storefront ./config.json   # a brand's own repo, e.g. curless-group1/shangrila-mcp
 ```
 
 It answers on `POST /mcp` (streamable HTTP), serves its own card as a `ui://`
@@ -21,16 +21,26 @@ weekend" books someone the wrong nights, and they find out at the front desk.
 
 ## The tools
 
+Nineteen, named from the brand's prefix. A backend that cannot do something
+says so in its `capabilities`, and those tools are not listed at all - Huazhu's
+deployment has twelve (no loyalty, add-ons, in-place changes or policy text).
+
 | | |
 |---|---|
-| `list_<brand>_hotels` | Hotels by city or free text. A city usually holds several, and all of them come back |
-| `get_<brand>_hotel` | One hotel; with `checkIn`/`checkOut`, its rooms priced for those nights |
-| `list_<brand>_extras` | Transfers, dining, experiences, spa, family |
+| `list_<brand>_hotels` | The group's destinations, or hotels by city or free text - with filters, a sort and a nightly ceiling, and with `checkIn`/`checkOut` each priced for those nights. A city usually holds several, and all of them come back |
+| `look_up_<brand>_hotels` | Up to six hotels read as text and drawn nowhere: what a comparison or a plan is made from |
+| `get_<brand>_hotel` | One hotel; with dates, its rooms priced for those nights and the arrival days either side |
+| `compare_<brand>_hotels` | Two to four side by side - the model's judgement, the server's figures (it takes no prices) |
+| `show_<brand>_itinerary` | Day by day, each item marked as in the trip or only planned |
+| `list_<brand>_extras` | Transfers, dining, experiences, spa, family - for a stay, or for a booking already made |
 | `add_to_<brand>_trip` · `view_` · `clear_` | The trip: room nights plus add-ons, priced as one |
-| `request_<brand>_booking` | Holds the rooms (demo) or books them, paid at the hotel (a group's own API); a confirmation code per stay |
-| `list_my_<brand>_bookings` | |
+| `request_<brand>_booking` | A demonstration hold (demo) or a booking paid at the hotel (a group's own API); a confirmation code per stay |
+| `list_my_<brand>_bookings` | This conversation's bookings, or one found by its code and the email it was made with |
 | `preview_<brand>_cancellation` · `cancel_<brand>_booking` | The fee and its rule, before anything is cancelled |
+| `preview_<brand>_booking_change` · `change_<brand>_booking` | New nights, rooms or add-ons: the difference first, then the change |
 | `get_<brand>_hotel_policies` | What the property itself publishes |
+| `sign_in_<brand>_member` · `sign_out_` | A membership number and the surname on it - a member rate, never a way into anybody's booking |
+| `forget_<brand>_preferences` | Removes the room preferences a member asked to have remembered |
 
 Tool descriptions say what a tool does and nothing else; how to behave lives in
 the server's `instructions`, which is what both assistant directories' listing
@@ -62,7 +72,7 @@ Everything goes through one `HotelBackend` interface, and there are two:
   the config.
 - **`data.api.sandbox: true`** is the same connector against a SIMULATED
   Huazhu, for testing before there is an account: `node dist/huazhu/sandbox.js`
-  serves the distributor API as its documentation describes it, with eight
+  serves the distributor API as its documentation describes it, with nine
   invented hotels named 【模拟】/[Sandbox] and no photographs, and keeps its
   bookings in `SANDBOX_STATE_FILE`. The flag makes every answer say `demo`, the
   instructions and the legal pages say it is a test environment, and nothing
@@ -76,7 +86,7 @@ something that always says no.
 ```bash
 # The first call against a real environment, read-only - it never books:
 HUAZHU_CLIENT_ID=… HUAZHU_CLIENT_SECRET=… HUAZHU_DISTRIBUTOR_ID=… \
-  npx curless-hotel-storefront --check ./config.json
+  npx @curless/hotel-storefront --check ./config.json
 ```
 
 ## Payment

package/dist/card.generated.d.ts

@@ -1,4 +1,4 @@
 export declare const HOTEL_CARD_HTML: string;
 /** sha256 of widget/src + widget/index.html at build time - the drift guard reads this. */
-export declare const HOTEL_CARD_SOURCE_SHA = "a328c0c854922e1418ca0d3e2e7a3b5957e6750d43649be6380fbcf8b2c7dfcf";
+export declare const HOTEL_CARD_SOURCE_SHA = "f3eef32efeac05656919cfe87bcefa621e47cb16849b8f12add95b741f9bc904";
 //# sourceMappingURL=card.generated.d.ts.map