@v-office/website-sdk 2.9.0 → 2.11.0

package/README.md

@@ -2,9 +2,8 @@
 
 Website-facing SDK facade for vOffice backends.
 
-The 2.8.0 line adds the catalog-backed custom-attribute registry, backend-aware
-atomic filter compositions, and consistent custom-attribute display and highlight
-behavior.
+The current SDK includes catalog-backed custom attributes, backend-aware search,
+and localized v10 REST search discount details.
 See `instructions/CHANGELOG.md` for the complete release history.
 
 ## Install

package/dist/cli.mjs

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import { t as createWebsiteSDK, zt as defineWebsiteSDKOptions } from "./client-CYK_5Vk7.mjs";
+import { t as createWebsiteSDK, zt as defineWebsiteSDKOptions } from "./client-DYAHnU5F.mjs";
 import { SearchSearchSortSchema, defineCustomAttributesFromUnknown } from "@v-office/sdk-core";
 import { Console, Effect, FileSystem, Layer, Option, Path, Schema, Stdio, Terminal } from "effect";
 import { Command, Flag } from "effect/unstable/cli";
@@ -16,7 +16,7 @@ var CLICheckFailed = class extends Error {
 const toCLIError = (message, cause) => cause instanceof Error ? new CLICheckFailed(`${message}: ${cause.message}`, { cause }) : new CLICheckFailed(message, { cause });
 //#endregion
 //#region package.json
-var version = "2.9.0";
+var version = "2.11.0";
 //#endregion
 //#region src/cli/output.ts
 const toJson = (value) => Effect.try({

package/dist/{client-CYK_5Vk7.mjs → client-DYAHnU5F.mjs}

@@ -3770,7 +3770,7 @@ const toBookingInput = ({ input }) => Effect.gen(function* () {
 		message: "Expected a v9 quote for v9 booking."
 	}));
 	return {
-		action: "booking",
+		action: input.kind === "OPTION" ? "option" : "booking",
 		reservation: { customer: {
 			...input.contact.title === void 0 ? {} : { title: input.contact.title },
 			forename: input.contact.forename,
@@ -4952,7 +4952,7 @@ const parseV9SearchCursor = (cursor) => Effect.gen(function* () {
 	return page;
 });
 const loadV9SearchRuntime = Effect.tryPromise({
-	try: () => import("./search-CO9ID9op.mjs"),
+	try: () => import("./search-QlZrI7ue.mjs"),
 	catch: (cause) => new CoreSDKError({
 		source: "v10",
 		operation: "v9.search.runtime",

package/dist/index.d.mts

@@ -350,6 +350,14 @@ declare const searchEffect: (input: SearchSearchInput$1) => Effect.Effect<{
       readonly province?: string;
       readonly country?: string;
     };
+    readonly formattedTotal?: string;
+    readonly discount?: {
+      readonly formattedOriginalTotal: string;
+      readonly applied: readonly {
+        readonly label: string;
+        readonly formattedAmount: string;
+      }[];
+    };
     readonly highlights?: readonly string[];
     readonly property?: {
       readonly id: string;
@@ -379,7 +387,6 @@ declare const searchEffect: (input: SearchSearchInput$1) => Effect.Effect<{
         readonly country?: string;
       };
     };
-    readonly formattedTotal?: string;
   }[];
   readonly alternatives?: readonly {
     readonly item: {
@@ -411,6 +418,14 @@ declare const searchEffect: (input: SearchSearchInput$1) => Effect.Effect<{
         readonly province?: string;
         readonly country?: string;
       };
+      readonly formattedTotal?: string;
+      readonly discount?: {
+        readonly formattedOriginalTotal: string;
+        readonly applied: readonly {
+          readonly label: string;
+          readonly formattedAmount: string;
+        }[];
+      };
       readonly highlights?: readonly string[];
       readonly property?: {
         readonly id: string;
@@ -440,12 +455,18 @@ declare const searchEffect: (input: SearchSearchInput$1) => Effect.Effect<{
           readonly country?: string;
         };
       };
-      readonly formattedTotal?: string;
     };
     readonly alternativePeriods: readonly {
+      readonly formattedTotal?: string;
+      readonly discount?: {
+        readonly formattedOriginalTotal: string;
+        readonly applied: readonly {
+          readonly label: string;
+          readonly formattedAmount: string;
+        }[];
+      };
       readonly start: string;
       readonly end: string;
-      readonly formattedTotal?: string;
     }[];
   }[];
   readonly appliedFilters: readonly {

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-CYK_5Vk7.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-DYAHnU5F.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.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.
 - `versions/2.8.0/CHANGELOG.md`: `@v-office/website-sdk` 2.8.0 release notes.
 - `versions/2.7.0/CHANGELOG.md`: `@v-office/website-sdk` 2.7.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.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.
 - `versions/2.8.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.7.0 to 2.8.0.
 - `versions/2.7.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.5.x to 2.7.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.9.0. Package versions remain unchanged until the release
+`@v-office/website-sdk` 2.11.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:
@@ -18,6 +18,9 @@ Use this directory as the consumer-facing reference for the package:
 - `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.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.
 - `versions/2.9.0/`: 2.9.0 highlight-selection release notes and 2.8.0-to-2.9.0 migration guide.
 - `versions/2.8.0/`: 2.8.0 custom-attribute release notes and 2.7.0-to-2.8.0 migration guide.
 - `versions/2.7.0/`: 2.7.0 release notes and 2.5.x-to-2.7.0 migration guide.
@@ -75,4 +78,6 @@ website-sdk --backend v10 search --locale de-DE --query "adults=2"
 website-sdk --backend v10 search --locale de-DE --query "adults=2" --sort '{"by":"field","orderBy":{"label":"ASC"}}'
 ```
 
-Config file examples in these docs use the flat `WebsiteSDKConfig` shape introduced in 2.0.0 and kept in 2.9.0. v10 config additionally requires `searchEndpoint` as of 2.5.0.
+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
+of 2.5.0.

package/dist/instructions/booking.md

@@ -2,7 +2,8 @@
 
 ## Service
 
-Use the live booking API to turn an available `GuestQuote` into a booking:
+Use the live booking API to turn an available `GuestQuote` into a confirmed or
+option booking:
 
 ```ts
 const booking = await sdk.live.booking.book(input);
@@ -31,6 +32,7 @@ type BookingInput = {
     note?: string;
   };
   relativeRedirectUrl: string;
+  kind?: "CONFIRMED" | "OPTION";
 };
 ```
 
@@ -63,6 +65,8 @@ const booking = await sdk.live.booking.book({
 });
 ```
 
+`kind: "OPTION"` creates an option booking on v10 and legacy v9. Omitting `kind`,
+or passing `"CONFIRMED"`, retains the existing confirmed-booking behavior.
 `relativeRedirectUrl` is used for online payment redirects after booking creation.
 
 ## Output

package/dist/instructions/search.md

@@ -227,6 +227,18 @@ The supported fields are `label`, `name`, all six `roomSummary` counters, `attri
 
 Returns `Promise<RentalSearchOutput>`.
 
+Priced items and alternative periods share this optional discount shape:
+
+```ts
+type SearchDiscount = {
+  readonly formattedOriginalTotal: string;
+  readonly applied: readonly {
+    readonly label: string;
+    readonly formattedAmount: string;
+  }[];
+};
+```
+
 Sample:
 
 ```json
@@ -250,7 +262,16 @@ Sample:
         }
       ],
       "highlights": ["2 bedrooms", "WiFi", "Parking"],
-      "formattedTotal": "1.234,00 €"
+      "formattedTotal": "1.111,00 €",
+      "discount": {
+        "formattedOriginalTotal": "1.234,00 €",
+        "applied": [
+          {
+            "label": "Frühbucher-Rabatt",
+            "formattedAmount": "-123,00 €"
+          }
+        ]
+      }
     }
   ],
   "alternatives": [
@@ -264,7 +285,16 @@ Sample:
         {
           "start": "2026-07-10",
           "end": "2026-07-17",
-          "formattedTotal": "1.456,00 €"
+          "formattedTotal": "1.310,00 €",
+          "discount": {
+            "formattedOriginalTotal": "1.456,00 €",
+            "applied": [
+              {
+                "label": "Frühbucher-Rabatt",
+                "formattedAmount": "-146,00 €"
+              }
+            ]
+          }
         }
       ]
     }
@@ -288,7 +318,15 @@ Sample:
 }
 ```
 
-Search items share the rental base fields and may include `scope`, `address`, `property`, `highlights`, and `formattedTotal`. Exact-period results are returned in `items`; alternative-period suggestions are returned in root-level `alternatives`.
+Search items share the rental base fields and may include `scope`, `address`,
+`property`, `highlights`, and `formattedTotal`. A priced item or alternative period
+may also include `discount`. When it does, `formattedTotal` is the final price and
+`discount.formattedOriginalTotal` is the price before the applied discounts.
+Discount totals, labels, and amounts are already localized and formatted for the
+requested locale; backend numeric amounts and modifier type keys are not exposed.
+`applied` may be empty when the backend supplies an original total without
+individual modifier lines. Exact-period results are returned in `items`;
+alternative-period suggestions are returned in root-level `alternatives`.
 
 `appliedFilters` reports what the backend actually applied, and is what a "remove
 this filter" chip should be built from. `label` is localized presentation and can
@@ -319,6 +357,8 @@ v10 search runs against the dedicated REST search backend (`POST` to the configu
 - `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.
 
 ## Configuration

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

@@ -0,0 +1,26 @@
+# Changelog: 2.10.0
+
+This release adds option bookings to the shared booking input and supports them
+consistently through the v10 and legacy v9 backends.
+
+## Added
+
+- `BookingInput.kind` accepts `"CONFIRMED"` or `"OPTION"`.
+- Passing `kind: "OPTION"` creates an option booking through
+  `sdk.live.booking.book(...)`.
+
+## Changed
+
+- v10 maps `"OPTION"` to the GraphQL booking status `OPTION`.
+- Legacy v9 maps `"OPTION"` to the v0 booking action `option`.
+- Omitting `kind`, or passing `"CONFIRMED"`, retains the existing confirmed-booking
+  behavior on both backends.
+
+## Migration Impact
+
+- Existing booking calls require no changes because `kind` is optional.
+- The booking service name, remaining input fields, and `BookingOutput` are
+  unchanged.
+- `relativeRedirectUrl` remains required for both booking kinds.
+- Sites that want to create option bookings can opt in by passing
+  `kind: "OPTION"`. See `versions/2.10.0/MIGRATION.md`.

package/dist/instructions/versions/2.10.0/MIGRATION.md

@@ -0,0 +1,63 @@
+# Migration: 2.9.0 to 2.10.0
+
+2.10.0 adds an optional booking kind. Existing calls continue to create confirmed
+bookings and require no migration.
+
+## 1. Choose the Booking Kind
+
+`BookingInput` now includes:
+
+```ts
+kind?: "CONFIRMED" | "OPTION";
+```
+
+The values behave as follows:
+
+- Omit `kind`, or pass `"CONFIRMED"`, to create a confirmed booking.
+- Pass `"OPTION"` to create an option booking.
+
+The SDK maps these values to the native backend representation:
+
+- v10 uses booking status `CONFIRMED` or `OPTION`.
+- Legacy v9 uses booking action `booking` or `option`.
+
+## 2. Create an Option Booking
+
+Use the existing booking service and set `kind` to `"OPTION"`:
+
+```ts
+const optionBooking = await sdk.live.booking.book({
+  quote,
+  contact,
+  relativeRedirectUrl: "/booking/payment-return",
+  kind: "OPTION",
+});
+```
+
+No separate option-booking method is required. The returned value remains a
+`BookingOutput`.
+
+## 3. Keep Existing Confirmed Bookings Unchanged
+
+Existing calls remain valid:
+
+```ts
+const booking = await sdk.live.booking.book({
+  quote,
+  contact,
+  relativeRedirectUrl: "/booking/payment-return",
+});
+```
+
+Passing `kind: "CONFIRMED"` is equivalent to omitting the field. Other input
+requirements, including `relativeRedirectUrl`, are unchanged.
+
+## Recommended Verification
+
+1. Create a booking without `kind` and confirm it remains confirmed.
+2. Create a booking with `kind: "OPTION"` and confirm the backend records it as an
+   option.
+3. Repeat both checks against v10 and legacy v9 when the site supports both
+   backends.
+4. Verify existing booking-result and payment handling still accepts the unchanged
+   `BookingOutput`.

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

@@ -0,0 +1,28 @@
+# Changelog: 2.11.0
+
+This release exposes localized v10 REST search discount details on priced search
+results.
+
+## Added
+
+- Priced v10 search items may include an optional `discount` with the localized
+  pre-discount total in `formattedOriginalTotal`.
+- `discount.applied` lists each applied discount as a localized `label` and
+  `formattedAmount`.
+- Alternative-period suggestions expose the same optional discount shape on each
+  priced period.
+
+## Changed
+
+- When `discount` is present, `formattedTotal` remains the final price after the
+  listed discounts.
+- Backend modifier types and numeric amounts remain internal; the public search
+  output contains presentation-ready localized strings.
+
+## Migration Impact
+
+- Existing search calls require no changes because `discount` is optional.
+- Search configuration and input are unchanged.
+- Legacy v9 search does not populate `discount`.
+- Sites can opt in to strike-through pricing and discount labels by reading the
+  new field. See `versions/2.11.0/MIGRATION.md` and `../../search.md`.

package/dist/instructions/versions/2.11.0/MIGRATION.md

@@ -0,0 +1,72 @@
+# Migration: 2.10.0 to 2.11.0
+
+2.11.0 adds optional localized discount information to priced v10 search results.
+Existing search calls and rendering remain valid without changes.
+
+## 1. Read the Optional Discount
+
+Exact-period items and individual alternative periods may now include:
+
+```ts
+type SearchDiscount = {
+  readonly formattedOriginalTotal: string;
+  readonly applied: readonly {
+    readonly label: string;
+    readonly formattedAmount: string;
+  }[];
+};
+```
+
+The field is omitted when the REST search backend returns no discount. Keep
+rendering `formattedTotal` as before and add discount presentation only when
+`discount` is present.
+
+## 2. Distinguish Final and Original Totals
+
+When a discount is present:
+
+- `formattedTotal` is the final price after the applied discounts.
+- `discount.formattedOriginalTotal` is the total before those discounts.
+- `discount.applied` contains presentation-ready localized labels and formatted
+  amounts.
+
+All monetary values already include locale-aware currency formatting. Backend
+numeric amounts and modifier type keys are intentionally not exposed.
+
+## 3. Handle Exact and Alternative Periods
+
+For a fixed-period match, read the field from the item:
+
+```ts
+result.items[0]?.discount;
+```
+
+For a nearby-period suggestion, read it from the individual period:
+
+```ts
+result.alternatives?.[0]?.alternativePeriods[0]?.discount;
+```
+
+Each alternative period has independent pricing and may have a different discount
+or no discount.
+
+## 4. Keep Search Inputs Unchanged
+
+No configuration or input migration is required. The SDK continues to request the
+existing default v10 search pricing and does not opt search into alternative
+cancellation-policy pricing.
+
+Legacy v9 search does not populate `discount`; consumers supporting both backends
+must treat it as optional.
+
+## Recommended Verification
+
+1. Run a priced v10 exact-period search that has a configured discount and verify
+   the final and original totals.
+2. Verify each applied entry has a localized label and formatted amount in every
+   supported locale.
+3. Run a priced search without a discount and confirm existing rendering is
+   unchanged.
+4. Check nearby alternative periods independently because discounts can differ by
+   period.
+5. If the site supports v9, confirm its existing search output remains unchanged.

package/dist/instructions/versions/2.5.0/MIGRATION.md

@@ -121,6 +121,9 @@ The public output type is unchanged, but v10 search cards now reflect the REST p
 - `property` is the minimal `{ id, nameOrLabel }` shape. Hydrate `property.location`, `property.images`, or `property.address` from `sdk.static.rentals.getRentals(...)` when a search card needs them.
 - Exact-period matches are returned in `items` with `formattedTotal`; nearby suggestions are returned in root-level `alternatives`, unchanged.
 
+Starting with 2.11.0, priced v10 items and alternative periods may also include
+optional localized `discount` details. See `../../search.md`.
+
 ## Backend Behavior
 
 - Fixed-period and flexible searches are priced by the REST backend; occupancy is required for priced searches.

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

@@ -1,4 +1,4 @@
-import { a as parseQueryParameters, i as collectQueryParameters, n as makeV9CustomAttributeFilterCapabilities, o as toQueryString, r as toBasicQueryInputs, s as applyVofficeFilterDerivedBasicQueryInputs } from "./client-CYK_5Vk7.mjs";
+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 { CoreSDKError, STABLE_SEARCH_INPUTS, daysBetweenLocalDates, expandCustomAttributeFilterCompositions, parseChildrenAges, parseOccupancyCount, resolveExpandedCompositions, toFormattedSearchPrice, toIsoDateFromPeriodQueryDate, toStableSearchInputBackendQueryKeys, toStableSearchInputParameterValues, toStableSearchInputQueryKeys, toUnusedFilterKeys } from "@v-office/sdk-core";
 import { Effect } from "effect";

package/instructions/CHANGELOG.md

@@ -4,6 +4,8 @@ This file is the versioned changelog index for the website SDK instructions.
 
 ## Versions
 
+- `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.
 - `versions/2.8.0/CHANGELOG.md`: `@v-office/website-sdk` 2.8.0 release notes.
 - `versions/2.7.0/CHANGELOG.md`: `@v-office/website-sdk` 2.7.0 release notes.

package/instructions/MIGRATION.md

@@ -4,6 +4,8 @@ This file is the versioned migration index for the website SDK instructions.
 
 ## Available Guides
 
+- `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.
 - `versions/2.8.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.7.0 to 2.8.0.
 - `versions/2.7.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.5.x to 2.7.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.9.0. Package versions remain unchanged until the release
+`@v-office/website-sdk` 2.11.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:
@@ -18,6 +18,9 @@ Use this directory as the consumer-facing reference for the package:
 - `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.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.
 - `versions/2.9.0/`: 2.9.0 highlight-selection release notes and 2.8.0-to-2.9.0 migration guide.
 - `versions/2.8.0/`: 2.8.0 custom-attribute release notes and 2.7.0-to-2.8.0 migration guide.
 - `versions/2.7.0/`: 2.7.0 release notes and 2.5.x-to-2.7.0 migration guide.
@@ -75,4 +78,6 @@ website-sdk --backend v10 search --locale de-DE --query "adults=2"
 website-sdk --backend v10 search --locale de-DE --query "adults=2" --sort '{"by":"field","orderBy":{"label":"ASC"}}'
 ```
 
-Config file examples in these docs use the flat `WebsiteSDKConfig` shape introduced in 2.0.0 and kept in 2.9.0. v10 config additionally requires `searchEndpoint` as of 2.5.0.
+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
+of 2.5.0.

package/instructions/booking.md

@@ -2,7 +2,8 @@
 
 ## Service
 
-Use the live booking API to turn an available `GuestQuote` into a booking:
+Use the live booking API to turn an available `GuestQuote` into a confirmed or
+option booking:
 
 ```ts
 const booking = await sdk.live.booking.book(input);
@@ -31,6 +32,7 @@ type BookingInput = {
     note?: string;
   };
   relativeRedirectUrl: string;
+  kind?: "CONFIRMED" | "OPTION";
 };
 ```
 
@@ -63,6 +65,8 @@ const booking = await sdk.live.booking.book({
 });
 ```
 
+`kind: "OPTION"` creates an option booking on v10 and legacy v9. Omitting `kind`,
+or passing `"CONFIRMED"`, retains the existing confirmed-booking behavior.
 `relativeRedirectUrl` is used for online payment redirects after booking creation.
 
 ## Output

package/instructions/search.md

@@ -227,6 +227,18 @@ The supported fields are `label`, `name`, all six `roomSummary` counters, `attri
 
 Returns `Promise<RentalSearchOutput>`.
 
+Priced items and alternative periods share this optional discount shape:
+
+```ts
+type SearchDiscount = {
+  readonly formattedOriginalTotal: string;
+  readonly applied: readonly {
+    readonly label: string;
+    readonly formattedAmount: string;
+  }[];
+};
+```
+
 Sample:
 
 ```json
@@ -250,7 +262,16 @@ Sample:
         }
       ],
       "highlights": ["2 bedrooms", "WiFi", "Parking"],
-      "formattedTotal": "1.234,00 €"
+      "formattedTotal": "1.111,00 €",
+      "discount": {
+        "formattedOriginalTotal": "1.234,00 €",
+        "applied": [
+          {
+            "label": "Frühbucher-Rabatt",
+            "formattedAmount": "-123,00 €"
+          }
+        ]
+      }
     }
   ],
   "alternatives": [
@@ -264,7 +285,16 @@ Sample:
         {
           "start": "2026-07-10",
           "end": "2026-07-17",
-          "formattedTotal": "1.456,00 €"
+          "formattedTotal": "1.310,00 €",
+          "discount": {
+            "formattedOriginalTotal": "1.456,00 €",
+            "applied": [
+              {
+                "label": "Frühbucher-Rabatt",
+                "formattedAmount": "-146,00 €"
+              }
+            ]
+          }
         }
       ]
     }
@@ -288,7 +318,15 @@ Sample:
 }
 ```
 
-Search items share the rental base fields and may include `scope`, `address`, `property`, `highlights`, and `formattedTotal`. Exact-period results are returned in `items`; alternative-period suggestions are returned in root-level `alternatives`.
+Search items share the rental base fields and may include `scope`, `address`,
+`property`, `highlights`, and `formattedTotal`. A priced item or alternative period
+may also include `discount`. When it does, `formattedTotal` is the final price and
+`discount.formattedOriginalTotal` is the price before the applied discounts.
+Discount totals, labels, and amounts are already localized and formatted for the
+requested locale; backend numeric amounts and modifier type keys are not exposed.
+`applied` may be empty when the backend supplies an original total without
+individual modifier lines. Exact-period results are returned in `items`;
+alternative-period suggestions are returned in root-level `alternatives`.
 
 `appliedFilters` reports what the backend actually applied, and is what a "remove
 this filter" chip should be built from. `label` is localized presentation and can
@@ -319,6 +357,8 @@ v10 search runs against the dedicated REST search backend (`POST` to the configu
 - `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.
 
 ## Configuration

package/instructions/versions/2.10.0/CHANGELOG.md

@@ -0,0 +1,26 @@
+# Changelog: 2.10.0
+
+This release adds option bookings to the shared booking input and supports them
+consistently through the v10 and legacy v9 backends.
+
+## Added
+
+- `BookingInput.kind` accepts `"CONFIRMED"` or `"OPTION"`.
+- Passing `kind: "OPTION"` creates an option booking through
+  `sdk.live.booking.book(...)`.
+
+## Changed
+
+- v10 maps `"OPTION"` to the GraphQL booking status `OPTION`.
+- Legacy v9 maps `"OPTION"` to the v0 booking action `option`.
+- Omitting `kind`, or passing `"CONFIRMED"`, retains the existing confirmed-booking
+  behavior on both backends.
+
+## Migration Impact
+
+- Existing booking calls require no changes because `kind` is optional.
+- The booking service name, remaining input fields, and `BookingOutput` are
+  unchanged.
+- `relativeRedirectUrl` remains required for both booking kinds.
+- Sites that want to create option bookings can opt in by passing
+  `kind: "OPTION"`. See `versions/2.10.0/MIGRATION.md`.

package/instructions/versions/2.10.0/MIGRATION.md

@@ -0,0 +1,63 @@
+# Migration: 2.9.0 to 2.10.0
+
+2.10.0 adds an optional booking kind. Existing calls continue to create confirmed
+bookings and require no migration.
+
+## 1. Choose the Booking Kind
+
+`BookingInput` now includes:
+
+```ts
+kind?: "CONFIRMED" | "OPTION";
+```
+
+The values behave as follows:
+
+- Omit `kind`, or pass `"CONFIRMED"`, to create a confirmed booking.
+- Pass `"OPTION"` to create an option booking.
+
+The SDK maps these values to the native backend representation:
+
+- v10 uses booking status `CONFIRMED` or `OPTION`.
+- Legacy v9 uses booking action `booking` or `option`.
+
+## 2. Create an Option Booking
+
+Use the existing booking service and set `kind` to `"OPTION"`:
+
+```ts
+const optionBooking = await sdk.live.booking.book({
+  quote,
+  contact,
+  relativeRedirectUrl: "/booking/payment-return",
+  kind: "OPTION",
+});
+```
+
+No separate option-booking method is required. The returned value remains a
+`BookingOutput`.
+
+## 3. Keep Existing Confirmed Bookings Unchanged
+
+Existing calls remain valid:
+
+```ts
+const booking = await sdk.live.booking.book({
+  quote,
+  contact,
+  relativeRedirectUrl: "/booking/payment-return",
+});
+```
+
+Passing `kind: "CONFIRMED"` is equivalent to omitting the field. Other input
+requirements, including `relativeRedirectUrl`, are unchanged.
+
+## Recommended Verification
+
+1. Create a booking without `kind` and confirm it remains confirmed.
+2. Create a booking with `kind: "OPTION"` and confirm the backend records it as an
+   option.
+3. Repeat both checks against v10 and legacy v9 when the site supports both
+   backends.
+4. Verify existing booking-result and payment handling still accepts the unchanged
+   `BookingOutput`.

package/instructions/versions/2.11.0/CHANGELOG.md

@@ -0,0 +1,28 @@
+# Changelog: 2.11.0
+
+This release exposes localized v10 REST search discount details on priced search
+results.
+
+## Added
+
+- Priced v10 search items may include an optional `discount` with the localized
+  pre-discount total in `formattedOriginalTotal`.
+- `discount.applied` lists each applied discount as a localized `label` and
+  `formattedAmount`.
+- Alternative-period suggestions expose the same optional discount shape on each
+  priced period.
+
+## Changed
+
+- When `discount` is present, `formattedTotal` remains the final price after the
+  listed discounts.
+- Backend modifier types and numeric amounts remain internal; the public search
+  output contains presentation-ready localized strings.
+
+## Migration Impact
+
+- Existing search calls require no changes because `discount` is optional.
+- Search configuration and input are unchanged.
+- Legacy v9 search does not populate `discount`.
+- Sites can opt in to strike-through pricing and discount labels by reading the
+  new field. See `versions/2.11.0/MIGRATION.md` and `../../search.md`.

package/instructions/versions/2.11.0/MIGRATION.md

@@ -0,0 +1,72 @@
+# Migration: 2.10.0 to 2.11.0
+
+2.11.0 adds optional localized discount information to priced v10 search results.
+Existing search calls and rendering remain valid without changes.
+
+## 1. Read the Optional Discount
+
+Exact-period items and individual alternative periods may now include:
+
+```ts
+type SearchDiscount = {
+  readonly formattedOriginalTotal: string;
+  readonly applied: readonly {
+    readonly label: string;
+    readonly formattedAmount: string;
+  }[];
+};
+```
+
+The field is omitted when the REST search backend returns no discount. Keep
+rendering `formattedTotal` as before and add discount presentation only when
+`discount` is present.
+
+## 2. Distinguish Final and Original Totals
+
+When a discount is present:
+
+- `formattedTotal` is the final price after the applied discounts.
+- `discount.formattedOriginalTotal` is the total before those discounts.
+- `discount.applied` contains presentation-ready localized labels and formatted
+  amounts.
+
+All monetary values already include locale-aware currency formatting. Backend
+numeric amounts and modifier type keys are intentionally not exposed.
+
+## 3. Handle Exact and Alternative Periods
+
+For a fixed-period match, read the field from the item:
+
+```ts
+result.items[0]?.discount;
+```
+
+For a nearby-period suggestion, read it from the individual period:
+
+```ts
+result.alternatives?.[0]?.alternativePeriods[0]?.discount;
+```
+
+Each alternative period has independent pricing and may have a different discount
+or no discount.
+
+## 4. Keep Search Inputs Unchanged
+
+No configuration or input migration is required. The SDK continues to request the
+existing default v10 search pricing and does not opt search into alternative
+cancellation-policy pricing.
+
+Legacy v9 search does not populate `discount`; consumers supporting both backends
+must treat it as optional.
+
+## Recommended Verification
+
+1. Run a priced v10 exact-period search that has a configured discount and verify
+   the final and original totals.
+2. Verify each applied entry has a localized label and formatted amount in every
+   supported locale.
+3. Run a priced search without a discount and confirm existing rendering is
+   unchanged.
+4. Check nearby alternative periods independently because discounts can differ by
+   period.
+5. If the site supports v9, confirm its existing search output remains unchanged.

package/instructions/versions/2.5.0/MIGRATION.md

@@ -121,6 +121,9 @@ The public output type is unchanged, but v10 search cards now reflect the REST p
 - `property` is the minimal `{ id, nameOrLabel }` shape. Hydrate `property.location`, `property.images`, or `property.address` from `sdk.static.rentals.getRentals(...)` when a search card needs them.
 - Exact-period matches are returned in `items` with `formattedTotal`; nearby suggestions are returned in root-level `alternatives`, unchanged.
 
+Starting with 2.11.0, priced v10 items and alternative periods may also include
+optional localized `discount` details. See `../../search.md`.
+
 ## Backend Behavior
 
 - Fixed-period and flexible searches are priced by the REST backend; occupancy is required for priced searches.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@v-office/website-sdk",
-  "version": "2.9.0",
+  "version": "2.11.0",
   "description": "Website-facing SDK facade backed by @v-office/sdk-core",
   "bin": {
     "website-sdk": "./dist/cli.mjs"
@@ -41,7 +41,7 @@
   },
   "dependencies": {
     "@graphql-typed-document-node/core": "3.2.0",
-    "@v-office/sdk-core": "^1.9.0",
+    "@v-office/sdk-core": "^1.11.0",
     "effect": "4.0.0-beta.85",
     "graphql": "16.14.2",
     "yaml": "^2.9.0"