@v-office/website-sdk 2.11.0 → 2.12.0

package/dist/{search-QlZrI7ue.mjs → search-BlL8vSPY.mjs}

@@ -1,5 +1,5 @@
-import { a as parseQueryParameters, i as collectQueryParameters, n as makeV9CustomAttributeFilterCapabilities, o as toQueryString, r as toBasicQueryInputs, s as applyVofficeFilterDerivedBasicQueryInputs } from "./client-DYAHnU5F.mjs";
-import { a as searchQuery, c as VofficeUnitDataFieldSchemas, m as parseVofficeUnitData, n as toImages, r as toAddress, t as toRentalHighlights } from "./to-rental-highlights-B6a_fi0j.mjs";
+import { a as parseQueryParameters, i as collectQueryParameters, n as makeV9CustomAttributeFilterCapabilities, o as toQueryString, r as toBasicQueryInputs, s as applyVofficeFilterDerivedBasicQueryInputs } from "./client-Bmxh2SAu.mjs";
+import { a as searchQuery, c as VofficeUnitDataFieldSchemas, m as parseVofficeUnitData, n as toImages, r as toAddress, t as toRentalHighlights } from "./to-rental-highlights-BVikT4Iz.mjs";
 import { CoreSDKError, STABLE_SEARCH_INPUTS, daysBetweenLocalDates, expandCustomAttributeFilterCompositions, parseChildrenAges, parseOccupancyCount, resolveExpandedCompositions, toFormattedSearchPrice, toIsoDateFromPeriodQueryDate, toStableSearchInputBackendQueryKeys, toStableSearchInputParameterValues, toStableSearchInputQueryKeys, toUnusedFilterKeys } from "@v-office/sdk-core";
 import { Effect } from "effect";
 //#region src/legacy-v9/parser/search/input/search-input-error.ts
@@ -79,9 +79,11 @@ const PERIOD_QUERY_KEYS = toStableSearchInputBackendQueryKeys({
 	backend: "v9",
 	group: STABLE_SEARCH_INPUTS.period
 });
+const UNSUPPORTED_FLEXIBLE_PERIOD_QUERY_KEYS = new Set(STABLE_SEARCH_INPUTS.period.keys.filter((key) => !PERIOD_QUERY_KEYS.has(key)));
 //#endregion
 //#region src/legacy-v9/parser/search/input/period/collect-period-query-parameters.ts
 const hasPeriodInput = (query) => parseQueryParameters(query).some(([key]) => PERIOD_QUERY_KEYS.has(key));
+const hasUnsupportedFlexiblePeriodInput = (query) => parseQueryParameters(query).some(([key]) => UNSUPPORTED_FLEXIBLE_PERIOD_QUERY_KEYS.has(key));
 const collectPeriodQueryParameters = ({ query }) => {
 	const { matchingParameters, remainingParameters } = collectQueryParameters({
 		query,
@@ -178,6 +180,7 @@ const toVofficeSorting = (sort) => {
 //#endregion
 //#region src/legacy-v9/parser/search/input/to-query-input.ts
 const toQueryInput = ({ query, sort, customAttributeFilterDefinitions, locale, translations }) => Effect.gen(function* () {
+	if (hasUnsupportedFlexiblePeriodInput(query)) return yield* failInvalidV9SearchInput("Legacy v9 search does not support flexible period query parameters \"month\", \"dates\", \"nights\", or \"weekend\". Use \"start\" and \"end\" for a fixed period.");
 	const compositionResult = expandCustomAttributeFilterCompositions({
 		capabilities: makeV9CustomAttributeFilterCapabilities(customAttributeFilterDefinitions),
 		customAttributeFilterDefinitions,
@@ -221,21 +224,41 @@ const toQueryInput = ({ query, sort, customAttributeFilterDefinitions, locale, t
 				alternatives: true,
 				sorting: toVofficeSorting(sort)
 			},
-			basicQueryInputs
+			basicQueryInputs: basicQueryInputs.length > 0 ? basicQueryInputs : null
 		},
 		unusedFilterKeys: compositionFilters.unusedFilterKeys
 	};
 });
 //#endregion
-//#region src/legacy-v9/parser/search/output/to-formatted-price.ts
-const DEFAULT_V9_SEARCH_CURRENCY$1 = "EUR";
-const toFormattedPrice = ({ locale, calc }) => {
-	if (calc?.total == null) return Effect.succeed(null);
-	return Effect.succeed(toFormattedSearchPrice({
+//#region src/legacy-v9/parser/search/output/to-search-price-fields.ts
+const DEFAULT_V9_SEARCH_CURRENCY = "EUR";
+const toSearchPriceFields = ({ locale, calc }) => {
+	if (calc?.total == null) return {};
+	const formattedTotal = toFormattedSearchPrice({
 		amount: calc.total,
-		currency: DEFAULT_V9_SEARCH_CURRENCY$1,
+		currency: DEFAULT_V9_SEARCH_CURRENCY,
 		locale
-	}));
+	});
+	if (calc.oTotal == null || calc.oTotal <= calc.total) return { formattedTotal };
+	const label = calc.discountName?.trim();
+	return {
+		formattedTotal,
+		discount: {
+			formattedOriginalTotal: toFormattedSearchPrice({
+				amount: calc.oTotal,
+				currency: DEFAULT_V9_SEARCH_CURRENCY,
+				locale
+			}),
+			applied: label == null || label.length === 0 ? [] : [{
+				label,
+				formattedAmount: toFormattedSearchPrice({
+					amount: calc.total - calc.oTotal,
+					currency: DEFAULT_V9_SEARCH_CURRENCY,
+					locale
+				})
+			}]
+		}
+	};
 };
 //#endregion
 //#region src/legacy-v9/parser/search/to-search-output-item.ts
@@ -258,26 +281,23 @@ const toSearchOutputItem = ({ locale, imageProxyBaseUrl, rentalHighlightPrioriti
 		attributes: data
 	});
 	if (highlights != null) item.highlights = highlights;
-	const formattedPrice = yield* toFormattedPrice({
+	if (includeFormattedTotal) Object.assign(item, toSearchPriceFields({
 		locale,
 		calc: rental.additional_voffice_data?.calc
-	});
-	if (includeFormattedTotal && formattedPrice != null) item.formattedTotal = formattedPrice;
+	}));
 	return item;
 });
 //#endregion
 //#region src/legacy-v9/parser/search/output/to-alternative-periods.ts
-const DEFAULT_V9_SEARCH_CURRENCY = "EUR";
 const toAlternativePeriods = ({ locale, alternatives }) => Effect.succeed((alternatives ?? []).flatMap((alternative) => {
 	if (alternative.fromdate == null || alternative.tilldate == null) return [];
 	return [{
 		start: alternative.fromdate,
 		end: alternative.tilldate,
-		...alternative.calc?.total == null ? {} : { formattedTotal: toFormattedSearchPrice({
-			amount: alternative.calc.total,
-			currency: DEFAULT_V9_SEARCH_CURRENCY,
-			locale
-		}) }
+		...toSearchPriceFields({
+			locale,
+			calc: alternative.calc
+		})
 	}];
 }));
 //#endregion

package/dist/{to-rental-highlights-B6a_fi0j.mjs → to-rental-highlights-BVikT4Iz.mjs}

@@ -5900,10 +5900,11 @@ const toRentalHighlights = ({ locale, translations, highlightPrioritization, cus
 			const attribute = customAttributes.byKey[highlightKey];
 			if (attribute === void 0) continue;
 			const binding = attribute.v9;
+			const value = binding === void 0 ? void 0 : knownAttributes[binding] ?? attributes.unknown[binding];
 			const highlight = renderResolvedCustomAttribute({
 				attribute,
 				locale,
-				value: binding === void 0 ? void 0 : knownAttributes[binding] ?? attributes.unknown[binding]
+				value
 			});
 			if (highlight != null) {
 				highlights.push(highlight);
@@ -5914,9 +5915,10 @@ const toRentalHighlights = ({ locale, translations, highlightPrioritization, cus
 		if (seenKeys.has(v9Key)) continue;
 		seenKeys.add(v9Key);
 		const metadata = VofficeUnitDataPropertyMetadata[v9Key];
+		const label = yield* translate(metadata.labelKey, v9Key);
 		const highlight = renderLabeledAttributeValue({
 			key: v9Key,
-			label: yield* translate(metadata.labelKey, v9Key),
+			label,
 			locale,
 			value: knownAttributes[v9Key]
 		});

package/instructions/CHANGELOG.md

@@ -4,6 +4,7 @@ This file is the versioned changelog index for the website SDK instructions.
 
 ## Versions
 
+- `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/instructions/MIGRATION.md

@@ -4,6 +4,7 @@ This file is the versioned migration index for the website SDK instructions.
 
 ## Available Guides
 
+- `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/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.12.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,15 @@ 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.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.
@@ -79,5 +82,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.12.0. v10 config additionally requires `searchEndpoint` as
 of 2.5.0.

package/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
 

package/instructions/search.md

@@ -87,17 +87,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 +127,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 +155,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 +179,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 +373,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/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`.