@v-office/website-sdk 2.11.0 → 2.13.0

package/dist/index.mjs

@@ -1,4 +1,4 @@
-import { $ as ServiceBeonDataSchema, A as ErgoBookRequestSchema, At as quoteEffect, B as OnOfficeUnitSchema, C as DocumentResourceSchema, Ct as clearAdditionalServicesEffect, D as DocumentTypeSchema, Dt as getRentalsEffect, E as DocumentSummarySchema, Et as getInitialAvailabilityEffect, F as ErgoPolicyNumberRequestSchema, Ft as selectInsurancePaymentEffect, G as QuotePricesResponseSchema, H as PaymentScheduleSchema, I as ErgoReadPreContractRequestSchema, It as submitContactEffect, J as RawObjectResponseSchema, K as QuoteSchema, L as ErgoTripAndCustomerRequestSchema, Lt as submitPaymentOption, M as ErgoCreatePreContractRequestSchema, Mt as searchEffect, N as ErgoPersonSchema, Nt as selectCancellationPolicyEffect, O as ErgoAddressSchema, Ot as getStartDateSelectedAvailabilityEffect, P as ErgoPlanSearchRequestSchema, Pt as selectInsuranceEffect, Q as SearchPropertiesResponseSchema, R as FacilityListResponseSchema, Rt as submitPaymentOptionEffect, S as DocumentResourceResponseSchema, St as bookInsuranceEffect, T as DocumentStatusUpdateRequestSchema, Tt as getFiltersEffect, U as QuoteLineSchema, V as PaymentScheduleItemSchema, W as QuotePricesPayloadSchema, X as RegionListResponseSchema, Y as RawVofficeObjectSchema, Z as RoomImageSchema, _ as CalendarDaySchema, _t as V1_OPERATIONS, at as TileCollectionResponseSchema, b as CustomerUnitSummarySchema, bt as addAdditionalServiceEffect, c as V0OpenApiClient, ct as TravelInsuranceBookingSchema, d as makeV0OpenApiClientLive, dt as UnitListItemSchema, et as ServiceImageSchema, f as V1OpenApiClient, ft as UnitListResponseSchema, g as ApiEnvelopeBaseSchema, gt as V1_BASE_URL, h as makeV1OpenApiClientLive, ht as UnitServicePriceSchema, it as SetupResponseSchema, j as ErgoCommonFieldsSchema, jt as removeAdditionalServiceEffect, k as ErgoBankSchema, kt as getTermsAndPrivacyPolicyEffect, l as V0OpenApiClientError, lt as TravelInsuranceBookingStoreRequestSchema, m as makeV1OpenApiClientFetchLive, mt as UnitResponseSchema, nt as ServiceListResponseSchema, ot as TileSchema, p as V1OpenApiClientError, pt as UnitOfferSchema, q as QuoteServiceSchema, rt as SetupDataSchema, st as TileTagSchema, t as createWebsiteSDK, tt as ServiceLimitSchema, u as makeV0OpenApiClientFetchLive, ut as UnitIdsResponseSchema, v as CalendarResponseSchema, vt as VideoResponseSchema, w as DocumentStatusSchema, wt as createInsurancePreContractEffect, x as DocumentCollectionResponseSchema, xt as bookEffect, y as CurrentMemberResponseSchema, yt as decodeV1OperationResponse, z as OnOfficeUnitCollectionResponseSchema, zt as defineWebsiteSDKOptions } from "./client-DYAHnU5F.mjs";
+import { $ as ServiceBeonDataSchema, A as ErgoBookRequestSchema, At as quoteEffect, B as OnOfficeUnitSchema, C as DocumentResourceSchema, Ct as clearAdditionalServicesEffect, D as DocumentTypeSchema, Dt as getRentalsEffect, E as DocumentSummarySchema, Et as getInitialAvailabilityEffect, F as ErgoPolicyNumberRequestSchema, Ft as selectInsurancePaymentEffect, G as QuotePricesResponseSchema, H as PaymentScheduleSchema, I as ErgoReadPreContractRequestSchema, It as submitContactEffect, J as RawObjectResponseSchema, K as QuoteSchema, L as ErgoTripAndCustomerRequestSchema, Lt as submitPaymentOption, M as ErgoCreatePreContractRequestSchema, Mt as searchEffect, N as ErgoPersonSchema, Nt as selectCancellationPolicyEffect, O as ErgoAddressSchema, Ot as getStartDateSelectedAvailabilityEffect, P as ErgoPlanSearchRequestSchema, Pt as selectInsuranceEffect, Q as SearchPropertiesResponseSchema, R as FacilityListResponseSchema, Rt as submitPaymentOptionEffect, S as DocumentResourceResponseSchema, St as bookInsuranceEffect, T as DocumentStatusUpdateRequestSchema, Tt as getFiltersEffect, U as QuoteLineSchema, V as PaymentScheduleItemSchema, W as QuotePricesPayloadSchema, X as RegionListResponseSchema, Y as RawVofficeObjectSchema, Z as RoomImageSchema, _ as CalendarDaySchema, _t as V1_OPERATIONS, at as TileCollectionResponseSchema, b as CustomerUnitSummarySchema, bt as addAdditionalServiceEffect, c as V0OpenApiClient, ct as TravelInsuranceBookingSchema, d as makeV0OpenApiClientLive, dt as UnitListItemSchema, et as ServiceImageSchema, f as V1OpenApiClient, ft as UnitListResponseSchema, g as ApiEnvelopeBaseSchema, gt as V1_BASE_URL, h as makeV1OpenApiClientLive, ht as UnitServicePriceSchema, it as SetupResponseSchema, j as ErgoCommonFieldsSchema, jt as removeAdditionalServiceEffect, k as ErgoBankSchema, kt as getTermsAndPrivacyPolicyEffect, l as V0OpenApiClientError, lt as TravelInsuranceBookingStoreRequestSchema, m as makeV1OpenApiClientFetchLive, mt as UnitResponseSchema, nt as ServiceListResponseSchema, ot as TileSchema, p as V1OpenApiClientError, pt as UnitOfferSchema, q as QuoteServiceSchema, rt as SetupDataSchema, st as TileTagSchema, t as createWebsiteSDK, tt as ServiceLimitSchema, u as makeV0OpenApiClientFetchLive, ut as UnitIdsResponseSchema, v as CalendarResponseSchema, vt as VideoResponseSchema, w as DocumentStatusSchema, wt as createInsurancePreContractEffect, x as DocumentCollectionResponseSchema, xt as bookEffect, y as CurrentMemberResponseSchema, yt as decodeV1OperationResponse, z as OnOfficeUnitCollectionResponseSchema, zt as defineWebsiteSDKOptions } from "./client-Ma0daa2H.mjs";
 import { AdditionalServiceLimitExceeded, CoreSDKError, CoreSDKError as CMSError, CustomAttributeCatalogSchema, GuestQuoteSchema, InvalidAdditionalServiceQuantity, LocaleSchema, SearchSearchFieldOrderBySchema, SearchSearchFieldSortSchema, SearchSearchInputSchema, SearchSearchOutputSchema, SearchSearchPriceSortSchema, SearchSearchRandomSortSchema, SearchSearchRatingSortSchema, SearchSearchSortSchema, SearchSortDirectionSchema, UnknownAdditionalService, defineCustomAttributes, defineCustomAttributesFromUnknown, fetchCustomAttributeCatalog, parseCustomAttributeCatalog, validateContactSubmitInput } from "@v-office/sdk-core";
 //#region codegen/v9/heuristic-generation/public-api.ts
 const customDataAttribute = (name) => name;

package/dist/instructions/CHANGELOG.md

@@ -4,6 +4,8 @@ This file is the versioned changelog index for the website SDK instructions.
 
 ## Versions
 
+- `versions/2.13.0/CHANGELOG.md`: `@v-office/website-sdk` 2.13.0 release notes.
+- `versions/2.12.0/CHANGELOG.md`: `@v-office/website-sdk` 2.12.0 release notes.
 - `versions/2.11.0/CHANGELOG.md`: `@v-office/website-sdk` 2.11.0 release notes.
 - `versions/2.10.0/CHANGELOG.md`: `@v-office/website-sdk` 2.10.0 release notes.
 - `versions/2.9.0/CHANGELOG.md`: `@v-office/website-sdk` 2.9.0 release notes.

package/dist/instructions/MIGRATION.md

@@ -4,6 +4,8 @@ This file is the versioned migration index for the website SDK instructions.
 
 ## Available Guides
 
+- `versions/2.13.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.12.0 to 2.13.0.
+- `versions/2.12.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.11.0 to 2.12.0.
 - `versions/2.11.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.10.0 to 2.11.0.
 - `versions/2.10.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.9.0 to 2.10.0.
 - `versions/2.9.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.8.0 to 2.9.0.

package/dist/instructions/README.md

@@ -1,7 +1,7 @@
 # Website SDK Instructions
 
 These instructions describe the current source targeted for
-`@v-office/website-sdk` 2.11.0. Package versions remain unchanged until the release
+`@v-office/website-sdk` 2.13.0. Package versions remain unchanged until the release
 workflow performs the coordinated core and website bumps.
 
 Use this directory as the consumer-facing reference for the package:
@@ -12,12 +12,18 @@ Use this directory as the consumer-facing reference for the package:
 - `custom-attributes.md`: custom attribute catalog, configuration, per-backend behaviour, and the v9-to-v10 move.
 - `search.md`: `sdk.live.search.search`.
 - `availability.md`: date-picker availability flows.
-- `quote.md`: quote, additional services, cancellation policy, and insurance flows.
+- `quote.md`: quote booking-card modifiers, additional services, cancellation policy, and insurance flows.
 - `booking.md`: booking and payment option submission.
 - `contact.md`: contact submission.
 - `document-structured-json.md`: `sdk.static.documents.getTermsAndPrivacyPolicy` and structured document JSON rendering rules.
 - `CHANGELOG.md`: versioned changelog index.
 - `MIGRATION.md`: versioned migration index.
+- `versions/2.13.0/`: 2.13.0 static search capability discovery, shared v9/v10
+  booking-payment output, corrected remaining-payment deadlines, opaque booking
+  credentials, and the 2.12.0-to-2.13.0 migration guide.
+- `versions/2.12.0/`: 2.12.0 legacy-v9 search discounts, empty-query browsing,
+  and flexible-period rejection; quote booking-card cleanup; and v10 modifier
+  guidance, plus the 2.11.0-to-2.12.0 migration guide.
 - `versions/2.11.0/`: 2.11.0 search-discount release notes and
   2.10.0-to-2.11.0 migration guide.
 - `versions/2.10.0/`: 2.10.0 option-booking release notes and 2.9.0-to-2.10.0 migration guide.
@@ -39,7 +45,9 @@ Use this directory as the consumer-facing reference for the package:
 pnpm add @v-office/website-sdk
 ```
 
-The package is ESM-only and exports the root SDK facade from `@v-office/website-sdk`.
+The package is ESM-only. It exports the SDK facade from `@v-office/website-sdk`
+and instance-independent search capability helpers from
+`@v-office/website-sdk/capabilities/search`.
 
 ## Quick Start
 
@@ -79,5 +87,5 @@ website-sdk --backend v10 search --locale de-DE --query "adults=2" --sort '{"by"
 ```
 
 Config file examples in these docs use the flat `WebsiteSDKConfig` shape introduced
-in 2.0.0 and kept in 2.11.0. v10 config additionally requires `searchEndpoint` as
+in 2.0.0 and kept in 2.13.0. v10 config additionally requires `searchEndpoint` as
 of 2.5.0.

package/dist/instructions/booking.md

@@ -78,47 +78,63 @@ Sample:
 ```json
 {
   "bookingNumber": "B-2026-0001",
-  "guestToken": "guest-token",
-  "paymentSchedules": [
-    {
-      "label": "Deposit",
-      "dueOn": "2026-06-15",
-      "lines": [
-        {
-          "label": "Deposit",
-          "amount": "300.00 EUR"
-        }
-      ],
-      "total": "300.00 EUR",
-      "paymentOptions": [
-        {
-          "kind": "bank_transfer",
-          "label": "Bank transfer",
-          "holder": "Example GmbH",
-          "iban": "DE02120300000000202051",
-          "swiftOrBic": "BYLADEM1001",
-          "remittanceText": "B-2026-0001"
-        },
-        {
-          "kind": "redirect",
-          "provider": "adyen",
-          "label": "Credit card",
-          "url": "https://checkout.example.com"
-        },
-        {
-          "kind": "stripe_checkout",
-          "provider": "stripe",
-          "label": "Credit card",
-          "sessionId": "cs_live_a1Upmvi1v62AdILeDZl4l",
-          "accountId": "acct_1MpAB7AFrTg9gw7b"
-        }
-      ]
-    }
-  ],
-  "insurancePaymentOptions": []
+  "payment": {
+    "schedule": [
+      {
+        "kind": "prepayment",
+        "label": "Down payment",
+        "amount": "€76.00",
+        "dueOn": "Payable until August 19, 2026",
+        "paymentOptions": [
+          {
+            "kind": "bank_transfer",
+            "label": "Bank transfer",
+            "holder": "Example GmbH",
+            "iban": "DE02120300000000202051",
+            "swiftOrBic": "BYLADEM1001",
+            "remittanceText": "Booking number: B-2026-0001"
+          }
+        ]
+      },
+      {
+        "kind": "remaining_payment",
+        "label": "Remaining payment",
+        "amount": "€304.00",
+        "dueOn": "Payable until February 6, 2027"
+      }
+    ],
+    "alternatives": [
+      {
+        "kind": "full_amount",
+        "label": "Total payment",
+        "amount": "€380.00",
+        "paymentOptions": [
+          {
+            "kind": "bank_transfer",
+            "label": "Bank transfer",
+            "holder": "Example GmbH",
+            "iban": "DE02120300000000202051",
+            "swiftOrBic": "BYLADEM1001",
+            "remittanceText": "Booking number: B-2026-0001"
+          }
+        ]
+      }
+    ]
+  }
 }
 ```
 
+`payment.schedule` contains the remaining contractual payment steps known to the backend. Its `kind` is one of `prepayment`, `remaining_payment`, `installment`, or `deposit`. `v9` emits named prepayment and remaining-payment steps; `v10` emits its backend-provided installment and deposit steps.
+
+`payment.alternatives` contains ways to settle the complete outstanding balance. A `full_amount` alternative has no inferred deadline. `dueOn`, `paymentAt`, labels, amounts, and line amounts are already translated and formatted for the booking locale.
+
+`paymentOptions` is present only when the SDK can currently perform that payment. Future or on-site steps remain visible without payment options.
+
+An optional `insurancePaymentOptions` array is returned only when post-booking insurance payment is available.
+
+Sites upgrading from 2.12.0 must replace the former `paymentSchedules` output. See
+`versions/2.13.0/MIGRATION.md`.
+
 Payment option variants:
 
 - `bank_transfer`: display-only payment details.
@@ -153,13 +169,13 @@ try {
 
 Online payment providers return the guest to a URL derived from `relativeRedirectUrl`. Stripe returns to that path with `payment=stripe&success=true` after payment and `payment=stripe&cancel=true` after cancellation, so the path must exist in your site and should read those query parameters.
 
-`relativeRedirectUrl` is supplied before the reservation exists, so the return URL cannot carry the booking number or guest token. Persist whatever the return page needs, for example in `sessionStorage`, before submitting a payment option.
+`relativeRedirectUrl` is supplied before the reservation exists, so the return URL cannot carry the booking number. Persist whatever the return page needs, for example in `sessionStorage`, before submitting a payment option.
 
 A successful return means the provider sent the browser back, not that the payment has settled. Confirmation reaches vOffice through the provider's webhook.
 
 ## Configuration
 
-Booking requests are rate-limited to one backend request per second with a queue size of five. `v9` books through the v0 `book` action and initializes one Stripe Checkout Session per payment schedule option when the property has Stripe enabled. `v10` books through GraphQL and initializes Adyen redirect payment options.
+Booking requests are rate-limited to one backend request per second with a queue size of five. `v9` books through the v0 `book` action and initializes Stripe only for currently payable choices when the property has Stripe enabled. `v10` books through GraphQL, preserves all remaining payment steps for display, and initializes Adyen for the next payable online step and the full-outstanding alternative.
 
 ## CLI Usage
 

package/dist/instructions/quote.md

@@ -62,13 +62,13 @@ Sample:
 ```
 
 Dates are local dates formatted as `YYYY-MM-DD`. For `v9`, `rentalId` must be a numeric vOffice unit id.
-Both backends accept `voucher` on quote and booking flows. `v10` can expose voucher discounts as booking-card modifiers when the backend returns voucher modifiers; `v9` reflects voucher effects in the quoted totals but does not expose a separate voucher modifier line.
+Both backends accept `voucher` on quote and booking flows. On `v10`, applied voucher and non-voucher modifiers can be exposed through the booking-card fields described below. `v9` reflects voucher effects in quoted totals but does not expose booking-card modifier details.
 
 ## Output
 
 Returns `Promise<GuestQuoteResult>`.
 
-Available sample:
+Available sample without modifiers:
 
 ```json
 {
@@ -139,6 +139,94 @@ Unavailable sample:
 
 Selection methods return `{ ok: true, quote }` or `{ ok: false, error }`. Possible selection errors include unknown additional service, additional service limit exceeded, unknown cancellation policy, unavailable cancellation policy quote, and unavailable quote combination.
 
+## Booking-Card Breakdown
+
+Booking-card sections are returned in display order. On both v9 and v10, the SDK
+omits numeric zero-value lines without subitems from the included, tax, and other
+breakdown sections. If no lines remain in a section, the section is omitted.
+Non-zero lines are unchanged, including when they share an `other` section with a
+filtered zero-value line.
+
+A zero-total line with subitems can remain because those subitems carry
+descriptive content. Do not use the absence or presence of a zero-value price row
+as service-selection state; use the quote's explicit service or selection data.
+
+### Modifiers and Pre-Modifier Totals
+
+On `v10`, a booking-card item at
+`bookingCardInformation.sections[].lines[].item` can include these optional
+fields:
+
+```ts
+{
+  modifiers?: readonly {
+    label: string;
+    amount: string;
+  }[];
+  totalBeforeModifiers?: string;
+}
+```
+
+`modifiers` contains localized, formatted adjustments applied to that item. A
+negative amount represents a deduction and a positive amount represents a
+surcharge. The SDK groups backend modifiers with the same label and formats their
+summed amount as one entry. The field is omitted when the item has no modifiers.
+
+`item.totalBeforeModifiers` is the formatted item amount before its modifiers. It
+is present when the item has a non-zero net modifier effect and the amount can be
+derived; otherwise it is omitted. `item.appliedCharge` remains the final amount
+after modifiers.
+
+The booking card itself can also include
+`bookingCardInformation.totalBeforeModifiers`. It is the formatted whole-card
+total before all backend modifiers and is present when those modifiers have a
+non-zero net effect. It is omitted when there are no modifiers or their amounts
+net to zero. The SDK derives quote pre-modifier totals from the final amounts and
+modifier values.
+
+Items in the included, tax, and other sections carry their adjustments in
+`item.modifiers`; do not expect those adjustments to be separate section lines.
+Negative modifiers on backend lines that cannot be mapped to those sections may
+instead appear as dedicated booking-card lines. `v9` quote cards omit
+`modifiers` and both `totalBeforeModifiers` fields.
+
+Discounted `v10` example for locale `de-DE`:
+
+```json
+{
+  "bookingCardInformation": {
+    "sections": [
+      {
+        "lines": [
+          {
+            "item": {
+              "position": "Inklusivpreis",
+              "appliedCharge": "1.554,00 €",
+              "modifiers": [
+                {
+                  "label": "Frühbucher/Last-Minute",
+                  "amount": "-140,00 €"
+                }
+              ],
+              "totalBeforeModifiers": "1.694,00 €"
+            }
+          }
+        ]
+      }
+    ],
+    "total": "1.596,70 €",
+    "totalBeforeModifiers": "1.736,70 €"
+  }
+}
+```
+
+For a price breakdown that keeps its arithmetic visible, render
+`totalBeforeModifiers` as the pre-modifier amount, show each modifier as an
+adjustment row, and use `appliedCharge` or `total` as the resulting final amount.
+The SDK supplies formatted values but does not decide whether a reference price
+should be displayed or struck through; that presentation and its legal
+requirements remain the consuming site's responsibility.
+
 ## Vouchers
 
 When `voucher` is provided in the quote input, an available quote may include `quote.voucher`:
@@ -153,7 +241,11 @@ When `voucher` is provided in the quote input, an available quote may include `q
 
 `status` is `"applied"`, `"not_applied"`, or `"unknown"`. `v10` reports `"applied"` when the backend returns a non-zero voucher modifier and `"not_applied"` when no voucher modifier is returned for the requested voucher. `v9` returns `"unknown"` for available voucher quotes because the legacy response does not provide a reliable voucher modifier signal.
 
-Voucher modifiers can appear in `bookingCardInformation.sections`. Sections are returned in display order.
+Do not assume an applied voucher appears as its own section line. On `v10`, a
+voucher adjustment on an included, tax, or other line appears in that line's
+`item.modifiers`; an unmapped negative modifier can appear as a dedicated line.
+Use `quote.voucher.status` for voucher application status and the booking-card
+fields for price presentation.
 
 ## Additional Services
 
@@ -301,16 +393,18 @@ quote = await sdk.live.quote.selectInsurancePayment({
 });
 ```
 
-After the rental booking is created, complete insurance booking with the booking number and guest token:
+After the rental booking is created, complete insurance booking with the opaque booking result. Keep the live result object; its private backend credentials are intentionally not serialized:
 
 ```ts
 const insuranceBooking = await sdk.live.quote.bookInsurance({
   quote,
-  bookingNumber: booking.bookingNumber,
-  guestToken: booking.guestToken,
+  booking,
 });
 ```
 
+This is a breaking change in 2.13.0. The former public `guestToken` input is no
+longer used; see `versions/2.13.0/MIGRATION.md`.
+
 `v9` supports real insurance option refresh, pre-contract, payment selection, and booking. `v10` currently returns a no-insurance placeholder and insurance actions resolve as not required.
 
 ## Configuration

package/dist/instructions/search.md

@@ -77,6 +77,28 @@ Common stable query keys:
 - Occupancy: `adults`, `children`, `childrenAges`, `babies`, `pets`, `petsCount`.
 - Filters: use `searchParameterQueryKey` values from `sdk.static.filter.getFilters(...)`.
 
+### Static Backend Capabilities
+
+Search capabilities that only depend on a backend name are available without
+constructing an SDK:
+
+```ts
+import {
+  getSupportedPeriodQueryKeys,
+  supportsFlexiblePeriodSearch,
+} from "@v-office/website-sdk/capabilities/search";
+
+supportsFlexiblePeriodSearch("v9"); // false
+supportsFlexiblePeriodSearch("v10"); // true
+
+getSupportedPeriodQueryKeys("v9").has("month"); // false
+getSupportedPeriodQueryKeys("v10").has("month"); // true
+```
+
+The returned read-only set contains the stable period query keys accepted by the
+selected backend, including aliases such as `from` and `till`. Key support does
+not replace validation of complete query combinations.
+
 ## Query Structure
 
 The `query` field is a URL query-string style value without a leading `?`.
@@ -87,17 +109,38 @@ Use `&` to combine period, occupancy, and filter parameters:
 "start=20-06-2026&end=27-06-2026&adults=2&wifi";
 ```
 
+### Empty Queries
+
+On v9, an empty query returns the first page of searchable inventory under the
+configured rental scope:
+
+```ts
+await sdk.live.search.search({
+  locale: "de-DE",
+  query: "",
+});
+```
+
+The v9 facade serializes an empty backend-filter set as GraphQL `data: null`.
+Pagination and the configured `limit` still apply; an undated query does not
+assert availability for a particular stay.
+
 ### Period Queries
 
 Use one supported period structure per query.
 
-Exact period search:
+Fixed-period search is supported by both v9 and v10:
 
 ```ts
 "start=20-06-2026&end=27-06-2026";
 ```
 
-Flexible search by month:
+Flexible-period search is supported by v10 only. Legacy v9 rejects the `month`,
+`dates`, `nights`, and `weekend` keys before transport instead of silently
+returning an unpriced item list. Keep the flexible selector unavailable on v9
+sites and use `start` plus `end` for a fixed-period search.
+
+Flexible v10 search by month:
 
 ```ts
 "month=06-2026&nights=7";
@@ -106,7 +149,7 @@ Flexible search by month:
 "month=06-2026&month=07-2026&weekend";
 ```
 
-Flexible search by exact date tuples:
+Flexible v10 search by exact date tuples:
 
 ```ts
 "dates=20-06-2026,22-06-2026&nights=2";
@@ -134,6 +177,9 @@ Boolean filters can be provided as presence-only flags when supported:
 
 ### Invalid Combinations
 
+The following flexible-query validation rules apply to v10. Legacy v9 rejects
+every flexible-period key as described above.
+
 Do not mix exact period search with flexible period options:
 
 ```ts
@@ -155,7 +201,7 @@ Flexible queries require either `nights` or `weekend`, but not both:
 "month=06-2026&nights=7&weekend";
 ```
 
-Dates should use `DD-MM-YYYY`; months should use `MM-YYYY`.
+Flexible date tuples accept `DD-MM-YYYY` and `YYYY-MM-DD`; months use `MM-YYYY`.
 
 Use `rentalIdsIn` to restrict results to specific rental IDs. This option is currently supported by `v10` only.
 Use `voucher` to price v10 search results with a voucher code. This option is currently supported by `v10` only.
@@ -349,17 +395,58 @@ the expanded leaf entries. A UI may collapse those leaves under the composition
 display, but should keep the returned keys and canonical values when removing direct
 filters.
 
-## v10 Backend
+## Backend Behavior
+
+### v10
 
-v10 search runs against the dedicated REST search backend (`POST` to the configured `searchEndpoint`). Existing calls and the output type remain compatible, while the input additionally supports optional sorting. v10 results reflect the REST projection:
+v10 search runs against the dedicated REST search backend (`POST` to the configured
+`searchEndpoint`). Existing calls and the output type remain compatible, while the
+input additionally supports optional sorting. v10 results reflect the REST
+projection:
 
 - At most five images per item, and no image `category`.
-- `property` is the minimal `{ id, nameOrLabel }` shape. Hydrate `property.location`, `property.images`, or `property.address` from `sdk.static.rentals.getRentals(...)` when a card needs them.
-- Custom-attribute search filters and highlights require the `customAttributes` registry. A definition with no catalog ID cannot be executed, so its query key is left in `unusedFilterKeys`. v9 never executes a custom-attribute filter at all. See `custom-attributes.md`.
-- Fixed-period and flexible searches are priced by the REST backend and require occupancy.
-- Priced items and alternative periods may include localized `discount` details when the REST backend returns them. Legacy v9 search does not populate this field.
-- Search inputs are unchanged. The SDK keeps alternative-cancellation-policy pricing out of search; cancellation-policy selection remains part of the quote and booking flow.
-- Pagination uses the backend `from`/`size` window behind the same opaque `cursor`, capped at 1,000 results.
+- `property` is the minimal `{ id, nameOrLabel }` shape. Hydrate
+  `property.location`, `property.images`, or `property.address` from
+  `sdk.static.rentals.getRentals(...)` when a card needs them.
+- Custom-attribute search filters and highlights require the `customAttributes`
+  registry. A definition with no catalog ID cannot be executed, so its query key
+  is left in `unusedFilterKeys`. See `custom-attributes.md`.
+- Fixed-period and flexible searches are priced by the REST backend and require
+  occupancy.
+- Priced items and alternative periods may include localized `discount` details
+  with multiple applied modifiers when the REST backend returns them.
+- The v10 public search input shape is unchanged. The SDK keeps
+  alternative-cancellation-policy
+  pricing out of search; cancellation-policy selection remains part of the quote
+  and booking flow.
+- Pagination uses the backend `from`/`size` window behind the same opaque `cursor`,
+  capped at 1,000 results.
+
+### Legacy v9
+
+Legacy v9 maps its aggregated search calculation into the shared price and discount
+shape:
+
+- Flexible-period keys (`month`, `dates`, `nights`, and `weekend`) are rejected
+  before transport. v9 sites must use a fixed `start`/`end` period.
+- Empty basic-filter sets are sent as GraphQL `data: null`, allowing an empty
+  query to browse the scoped searchable inventory without a dummy occupancy
+  value.
+- `calc.total` becomes `formattedTotal`.
+- `discount` is included only when `calc.oTotal` is greater than `calc.total`.
+- `calc.oTotal` becomes `discount.formattedOriginalTotal`.
+- A non-empty `calc.discountName` becomes the label of the single `applied` entry.
+- The applied amount is the formatted negative difference
+  `calc.total - calc.oTotal`.
+- Missing discount names produce an empty `applied` array without discarding the
+  formatted original total.
+- The same mapping applies to exact-period items and individual alternative
+  periods.
+- v9 never executes a custom-attribute search filter.
+
+The field is omitted when v9 returns no final total or when its original total is
+not greater than the final total. v9 exposes at most one aggregated applied entry,
+whereas v10 can expose multiple detailed modifiers.
 
 ## Configuration
 

package/dist/instructions/versions/2.12.0/CHANGELOG.md

@@ -0,0 +1,56 @@
+# Changelog: 2.12.0
+
+This release extends the optional search discount output introduced in 2.11.0 to
+legacy v9 search results, keeps zero-value lines out of quote booking-card
+breakdowns, and completes v10 card-level pre-modifier totals across all modifier
+presentation paths. It also rejects unsupported v9 flexible-period searches before
+transport and restores empty-query inventory browsing on v9.
+
+## Added
+
+- Priced legacy v9 exact-period items may include the shared optional `discount`
+  output.
+- Individual legacy v9 alternative periods expose the same optional discount
+  shape.
+- v9 maps its aggregated original total and discount name into
+  `formattedOriginalTotal` and at most one localized `applied` entry.
+
+## Changed
+
+- Legacy v9 search now rejects the unsupported flexible-period query keys
+  `month`, `dates`, `nights`, and `weekend` before transport instead of silently
+  returning an unpriced item list. Fixed `start`/`end` searches are unchanged.
+- Legacy v9 search serializes an empty backend-filter set as GraphQL `data: null`
+  instead of `data: []`. Empty queries can therefore browse searchable inventory
+  without seeding a dummy occupancy value.
+- When a v9 discount is present, `formattedTotal` remains the final price and the
+  applied amount is the formatted difference from the original total.
+- v10 search discount behavior is unchanged from 2.11.0 and can continue to expose
+  multiple applied modifiers.
+- Quote booking cards now omit zero-value lines without subitems from the `other`
+  section on both v10 and legacy v9, matching the existing empty-line behavior of
+  the included and tax sections.
+- If an `other` section contains both zero-value and non-zero lines, only the
+  non-zero lines remain. The section is omitted when no lines remain.
+- v10 derives card-level `totalBeforeModifiers` from all backend modifiers,
+  including negative modifiers rendered as dedicated booking-card lines.
+- Booking-card items omit the optional `modifiers` field when no modifier entries
+  are present instead of producing `modifiers: []`.
+
+## Migration Impact
+
+- Existing supported search calls require no changes because `discount` remains
+  optional. v9 sites must keep flexible search unavailable and use `start`/`end`
+  period queries.
+- v9 sites that inject `adults=1` only to make an empty query return results
+  should remove that workaround. Real occupancy filters remain supported.
+- Search configuration, the public input type, and the discount schema are
+  unchanged. Runtime validation is stricter for unsupported v9 flexible-period
+  keys.
+- Cross-backend sites can use one discount renderer for v9 and v10, while allowing
+  v9 to return at most one applied entry.
+- Quote inputs and booking-card types are unchanged. Consumers may receive fewer
+  booking-card lines and may now receive the existing optional card-level
+  `totalBeforeModifiers` in additional v10 modifier cases. Do not rely on
+  zero-value rows to represent declined services.
+- See `versions/2.12.0/MIGRATION.md`, `../../search.md`, and `../../quote.md`.