@v-office/website-sdk 2.14.0 → 2.16.0

package/dist/cli.mjs

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import { t as createWebsiteSDK, zt as defineWebsiteSDKOptions } from "./client-BvQRpzYY.mjs";
+import { t as createWebsiteSDK, zt as defineWebsiteSDKOptions } from "./client-CaZZGJAW.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.14.0";
+var version = "2.16.0";
 //#endregion
 //#region src/cli/output.ts
 const toJson = (value) => Effect.try({

package/dist/{client-BvQRpzYY.mjs → client-CaZZGJAW.mjs}

@@ -5202,7 +5202,7 @@ const bookV9Insurance = ({ quote, bookingNumber, guestToken, v1Client }) => Effe
 //#region src/legacy-v9/live/quote.ts
 const loadQuoteRuntime = Effect.tryPromise({
 	try: async () => {
-		return { toGuestQuote: (await import("./quote-Qy_affum.mjs")).toGuestQuote };
+		return { toGuestQuote: (await import("./quote-C-Bs3XTE.mjs")).toGuestQuote };
 	},
 	catch: (cause) => new CoreSDKError({
 		source: "v10",
@@ -5477,7 +5477,7 @@ const parseV9SearchCursor = (cursor) => Effect.gen(function* () {
 	return page;
 });
 const loadV9SearchRuntime = Effect.tryPromise({
-	try: () => import("./search-uXcReJdL.mjs"),
+	try: () => import("./search-Dqiou4mc.mjs"),
 	catch: (cause) => new CoreSDKError({
 		source: "v10",
 		operation: "v9.search.runtime",
@@ -5820,7 +5820,11 @@ const makeV9FilterApi = ({ options }) => {
 };
 //#endregion
 //#region src/legacy-v9/static/rentals.ts
-const DEFAULT_RENTAL_FACILITY_DATA_ATTRIBUTES = ["name", "description"];
+const DEFAULT_RENTAL_FACILITY_DATA_ATTRIBUTES = [
+	"name",
+	"description",
+	"images"
+];
 const DEFAULT_RENTAL_RATING_DATA_ATTRIBUTES = [];
 const DEFAULT_RENTAL_FEEDBACK_DATA_ATTRIBUTES = [
 	"id",
@@ -5840,7 +5844,7 @@ const DEFAULT_RENTAL_FEEDBACK_DATA_ATTRIBUTES = [
 	"avgRating"
 ];
 const loadV9RentalsRuntime = Effect.tryPromise({
-	try: () => import("./rentals-CN01jEkv.mjs"),
+	try: () => import("./rentals--cnnFS4I.mjs"),
 	catch: (cause) => new CoreSDKError({
 		source: "v10",
 		operation: "v9.rentals.runtime",

package/dist/index.d.mts

@@ -7334,6 +7334,17 @@ type KnownVofficeImageDataAttribute = KnownDataAttribute<KnownVofficeImageData>;
 declare const VofficeFacilityDataFieldSchemas: {
   readonly name: Schema.Union<readonly [Schema.String, Schema.$Record<Schema.String, Schema.String>]>;
   readonly description: Schema.Union<readonly [Schema.String, Schema.$Record<Schema.String, Schema.String>]>;
+  readonly images: Schema.mutable<Schema.$Array<Schema.Struct<{
+    readonly id: Schema.optionalKey<Schema.Number>;
+    readonly width: Schema.optionalKey<Schema.Number>;
+    readonly height: Schema.optionalKey<Schema.Number>;
+    readonly name: Schema.optionalKey<Schema.String>;
+    readonly ask: Schema.optionalKey<Schema.NullOr<Schema.Union<readonly [Schema.String, Schema.Number]>>>;
+    readonly tag: Schema.optionalKey<Schema.String>;
+    readonly otaId: Schema.optionalKey<Schema.Number>;
+    readonly titles: Schema.optionalKey<Schema.Unknown>;
+    readonly season: Schema.optionalKey<Schema.String>;
+  }>>>;
 };
 type KnownVofficeFacilityData = KnownJsonData<typeof VofficeFacilityDataFieldSchemas>;
 type ParsedVofficeFacilityData = ParsedJsonData<KnownVofficeFacilityData>;

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-BvQRpzYY.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-CaZZGJAW.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.16.0/CHANGELOG.md`: `@v-office/website-sdk` 2.16.0 release notes.
+- `versions/2.15.0/CHANGELOG.md`: `@v-office/website-sdk` 2.15.0 release notes.
 - `versions/2.14.0/CHANGELOG.md`: `@v-office/website-sdk` 2.14.0 release notes.
 - `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.

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.16.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.15.0 to 2.16.0.
+- `versions/2.15.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.14.0 to 2.15.0.
 - `versions/2.14.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.13.0 to 2.14.0.
 - `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.

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.14.0. Package versions remain unchanged until the release
+`@v-office/website-sdk` 2.16.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,12 @@ 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.16.0/`: 2.16.0 machine-readable unavailable quote codes,
+  multi-rate configuration diagnostics, and the 2.15.0-to-2.16.0 migration
+  guide.
+- `versions/2.15.0/`: 2.15.0 v9 facility images in normalized
+  `property.images`, responsive vOffice image URLs, and the 2.14.0-to-2.15.0
+  migration guide.
 - `versions/2.14.0/`: 2.14.0 catalog-backed v9 property types and options,
   corrected option/count rendering and translations, and the 2.13.0-to-2.14.0
   migration guide.
@@ -90,5 +96,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.14.0. v10 config additionally requires `searchEndpoint` as
+in 2.0.0 and kept in 2.16.0. v10 config additionally requires `searchEndpoint` as
 of 2.5.0.

package/dist/instructions/quote.md

@@ -133,10 +133,40 @@ Unavailable sample:
 ```json
 {
   "status": "unavailable",
+  "code": "NotBookable",
   "reason": "Rental is not available for the selected period."
 }
 ```
 
+From 2.16.0, every unavailable quote includes a machine-readable `code`:
+
+- `NotBookable`: the backend did not return a bookable price, including normal
+  availability failures. Legacy v9 unavailable quotes always use this code.
+- `AmbiguousMultiRate`: v10 priced the stay, but more than one multi-rate
+  matched the default cancellation policy.
+- `UnresolvableMultiRate`: v10 priced the stay, but no multi-rate could be
+  resolved for the default cancellation policy.
+
+Use `code` for application behavior and logging. `reason` remains localized
+display text and can be identical for inventory and multi-rate failures. The SDK
+keeps ambiguous and unresolvable v10 quotes unavailable because booking requires
+one exact multi-rate.
+
+```ts
+const result = await sdk.live.quote.quote(input);
+
+if (result.status === "unavailable") {
+  if (result.code === "AmbiguousMultiRate" || result.code === "UnresolvableMultiRate") {
+    reportQuoteConfigurationProblem(result.code);
+  }
+
+  showUnavailableMessage(result.reason);
+}
+```
+
+See `versions/2.16.0/CHANGELOG.md` and
+`versions/2.16.0/MIGRATION.md` for release and upgrade details.
+
 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

package/dist/instructions/rentals.md

@@ -87,6 +87,42 @@ Sample item:
 
 Optional fields include `scope`, `address`, `property`, `rooms`, `roomSummary`, `vicinity`, and `reviews`.
 
+### Legacy v9 Facility Images
+
+From 2.15.0, v9 static rentals request facility image metadata and return it in
+`property.images`:
+
+```json
+{
+  "property": {
+    "id": "1512",
+    "nameOrLabel": "Haus Köbesine",
+    "images": [
+      {
+        "idOrPath": "28458352",
+        "src": "https://dyn.v-office.com/image/xl/28458352.jpg",
+        "srcset": "https://dyn.v-office.com/image/tn/28458352.jpg 141w, https://dyn.v-office.com/image/tnx/28458352.jpg 225w, https://dyn.v-office.com/image/s/28458352.jpg 450w, https://dyn.v-office.com/image/m/28458352.jpg 600w, https://dyn.v-office.com/image/xl/28458352.jpg 1440w, https://dyn.v-office.com/image/xxl/28458352.jpg 2400w",
+        "alt": "Hauptansicht",
+        "title": "Hauptansicht",
+        "category": "buildingMain"
+      }
+    ]
+  }
+}
+```
+
+Facility image `src` and `srcset` URLs use `dyn.v-office.com`. Top-level v9
+rental `images` continue to use the configured `imageProxyBaseUrl`. Consumers
+must allow both origins when they render both collections.
+
+The SDK supplies width-descriptor `srcset`; the UI remains responsible for an
+HTML `sizes` attribute that matches its layout. `property.images` is omitted
+when the facility has no usable image IDs. Because the service returns one item
+per rental, rentals in the same facility contain the same nested property image
+list.
+
+See `versions/2.15.0/CHANGELOG.md` and `versions/2.15.0/MIGRATION.md`.
+
 ### Legacy v9 Built-In Attributes
 
 From 2.14.0, built-in v9 property types and ordered option values come from the

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

@@ -0,0 +1,66 @@
+# Changelog: 2.15.0
+
+This release adds facility images to normalized v9 static rental output. v9
+consumers can now read responsive property images from the same
+`property.images` field already used by the shared rental contract.
+
+## Added
+
+- v9 static rentals request the facility `images` data attribute through the
+  existing GraphQL `all` query.
+- Parsed facility images are exposed under:
+
+  ```ts
+  rental.property?.images;
+  ```
+
+- Every mapped facility image includes:
+  - `idOrPath` from the vOffice image ID
+  - an `xl` fallback `src`
+  - a responsive width-descriptor `srcset`
+  - localized `alt` and `title` when a title is available
+  - `category` when vOffice supplies an image tag
+  - the original v9 image metadata under `metadata.dataImage`
+- The generated v9 facility-data schema recognizes facility image records and
+  validates them with the existing `ImageDataSchema`.
+- Facility `srcset` candidates use the unique vOffice dynamic-image presets:
+  `141w`, `225w`, `450w`, `600w`, `1440w`, and `2400w`. Candidates are capped
+  at the known original image width and duplicate widths are omitted.
+
+## Changed
+
+- v9 facility image bytes are served by the documented vOffice dynamic-image
+  origin:
+
+  ```text
+  https://dyn.v-office.com/image/<size>/<image-id>.jpg
+  ```
+
+- Facility images no longer need to be inferred from a rental image storage
+  path. That inference was invalid because facility image IDs are not present
+  in the v9 rental image rows.
+- A v9 property shared by several rentals carries the same facility image list
+  on each normalized rental's nested `property` object.
+
+## Unchanged
+
+- `sdk.static.rentals.getRentals({ locale })` and its input are unchanged.
+- The public `RentalPropertySchema` and image shape are unchanged because
+  `property.images` was already part of the shared contract.
+- Top-level v9 rental `images` continue to use the configured
+  `imageProxyBaseUrl`.
+- v10 rental and property image behavior is unchanged.
+- No new SDK configuration or environment variable is required.
+
+## Compatibility
+
+- This is an additive output change. v9 consumers that ignore
+  `property.images` do not need code changes.
+- Content Security Policy or image-host allowlists must permit
+  `https://dyn.v-office.com` before rendering the new v9 property images.
+- Snapshots that include complete v9 property objects must account for the new
+  optional `images` field.
+- Facility image entries without a numeric vOffice image ID are omitted because
+  no deterministic dynamic-image URL can be constructed.
+
+See `versions/2.15.0/MIGRATION.md` and `../../rentals.md`.

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

@@ -0,0 +1,148 @@
+# Migration: 2.14.0 to 2.15.0
+
+2.15.0 adds facility images to v9 static rental properties. The SDK call,
+configuration, and public TypeScript shape are unchanged, but complete v9
+property objects can now contain `images`.
+
+Consumers that use only v10 are not affected.
+
+## 1. Allow the vOffice Image Origin
+
+v9 facility image URLs use:
+
+```text
+https://dyn.v-office.com
+```
+
+Add that origin to image-host allowlists and Content Security Policy before
+rendering `property.images`. For example:
+
+```text
+Content-Security-Policy: img-src 'self' https://dyn.v-office.com
+```
+
+Top-level v9 rental images still use the configured `imageProxyBaseUrl`. A page
+that renders both image kinds must allow both origins.
+
+## 2. Read Facility Images from `property.images`
+
+No new service call is required:
+
+```ts
+const rentals = await sdk.static.rentals.getRentals({ locale: "de-DE" });
+
+for (const rental of rentals) {
+  for (const image of rental.property?.images ?? []) {
+    renderPropertyImage(image);
+  }
+}
+```
+
+The field remains optional. It is omitted when a rental has no facility, when
+the facility has no images, or when no facility image has a usable numeric ID.
+
+Example image:
+
+```json
+{
+  "idOrPath": "28458352",
+  "src": "https://dyn.v-office.com/image/xl/28458352.jpg",
+  "srcset": "https://dyn.v-office.com/image/tn/28458352.jpg 141w, https://dyn.v-office.com/image/tnx/28458352.jpg 225w, https://dyn.v-office.com/image/s/28458352.jpg 450w, https://dyn.v-office.com/image/m/28458352.jpg 600w, https://dyn.v-office.com/image/xl/28458352.jpg 1440w, https://dyn.v-office.com/image/xxl/28458352.jpg 2400w",
+  "alt": "Hauptansicht",
+  "title": "Hauptansicht",
+  "category": "buildingMain"
+}
+```
+
+## 3. Provide the Layout-Specific `sizes` Attribute
+
+The SDK provides `src` and `srcset`. The consuming UI must provide `sizes`
+because only the application knows the rendered layout:
+
+```tsx
+<img
+  src={image.src}
+  srcSet={image.srcset}
+  sizes="(max-width: 768px) 100vw, 50vw"
+  alt={image.alt ?? ""}
+/>
+```
+
+Do not copy that example `sizes` value blindly. Match it to the actual image
+width in the application's responsive layout.
+
+The fallback `src` uses the `xl` vOffice preset. Browsers that support `srcset`
+select an appropriate candidate using `srcset`, `sizes`, viewport width, and
+device pixel ratio.
+
+## 4. Keep Rental and Property Images Distinct
+
+The two image collections represent different entities:
+
+```ts
+rental.images; // images belonging to the rental/unit
+rental.property?.images; // images belonging to the facility/property
+```
+
+They also use different origins in v9:
+
+- `rental.images`: configured `imageProxyBaseUrl`
+- `rental.property.images`: `https://dyn.v-office.com`
+
+Do not merge the arrays unless the UI deliberately presents a combined gallery.
+Keeping them separate prevents facility images from being mistaken for
+unit-specific rooms or amenities.
+
+## 5. Account for Repeated Property Data
+
+The normalized rentals API returns one item per rental. When several rentals
+belong to the same facility, each rental contains the same nested property image
+list.
+
+Applications that build a property-level view can deduplicate by `property.id`:
+
+```ts
+const properties = new Map(
+  rentals.flatMap((rental) =>
+    rental.property == null ? [] : [[rental.property.id, rental.property] as const],
+  ),
+);
+```
+
+No separate property endpoint or persistence layer was added in 2.15.0.
+
+## 6. Update Snapshots and Complete-Object Assertions
+
+Tests that compare only selected property fields are unaffected. Tests that
+snapshot or deeply compare complete v9 rental output can now observe:
+
+```ts
+rental.property.images;
+```
+
+Update those expectations without making `property.images` mandatory. Backend
+facilities are allowed to have no usable images.
+
+## Required Consumer Work
+
+For applications that render v9 property images:
+
+1. Allow `https://dyn.v-office.com` in CSP and image-host configuration.
+2. Render `rental.property.images` separately from top-level rental images.
+3. Supply an HTML `sizes` value appropriate for the layout.
+4. Keep empty and missing image arrays valid.
+5. Update complete-output snapshots.
+
+Applications that do not render v9 property images require no migration work.
+
+## Recommended Verification
+
+1. Fetch v9 static rentals in both `de-DE` and `en-US`.
+2. Confirm facilities with images expose `property.images`.
+3. Confirm localized image titles populate `alt` and `title`.
+4. Confirm the browser selects responsive candidates after adding `sizes`.
+5. Confirm `dyn.v-office.com` is accepted by production CSP.
+6. Confirm top-level rental images still use the configured image proxy.
+7. Confirm a shared facility does not create duplicate property cards when the
+   application deduplicates by `property.id`.
+8. Confirm v10 rental and property image rendering remains unchanged.

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

@@ -0,0 +1,44 @@
+# Changelog: 2.16.0
+
+This release makes unavailable quote results machine-readable. Applications can
+now distinguish normal booking unavailability from v10 multi-rate
+configuration failures without parsing localized text.
+
+## Added
+
+- Every unavailable `GuestQuoteResult` contains a `code`:
+  - `NotBookable`
+  - `AmbiguousMultiRate`
+  - `UnresolvableMultiRate`
+- The public quote output schema validates the new code.
+- v10 reports `AmbiguousMultiRate` when a priced default cancellation policy
+  matches more than one multi-rate.
+- v10 reports `UnresolvableMultiRate` when a priced default cancellation policy
+  cannot be mapped to a multi-rate.
+
+## Changed
+
+- Legacy v9 unavailable quotes now include `code: "NotBookable"`.
+- Normal v10 quote failures also use `code: "NotBookable"`.
+- v10 retains the exact default-policy multi-rate resolution result instead of
+  reducing it to a boolean before creating the public unavailable result.
+
+## Unchanged
+
+- `sdk.live.quote.quote(input)` and its input are unchanged.
+- Available quote results remain `{ status: "available", quote }`.
+- Unavailable results retain the localized `reason` field.
+- Ambiguous or unresolvable v10 multi-rates remain unavailable. The SDK does not
+  select an arbitrary fallback because booking requires one exact multi-rate.
+- Search and calendar availability behavior are unchanged.
+
+## Compatibility
+
+- Consumers that only inspect `status` and display `reason` continue to work.
+- TypeScript mocks, complete-object assertions, snapshots, and schema fixtures
+  for unavailable quotes must include `code`.
+- Application behavior should branch on `code`, not localized `reason`.
+- `AmbiguousMultiRate` and `UnresolvableMultiRate` indicate configuration or
+  mapping problems and should normally be reported to site operations.
+
+See `versions/2.16.0/MIGRATION.md` and `../../quote.md`.

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

@@ -0,0 +1,109 @@
+# Migration: 2.15.0 to 2.16.0
+
+2.16.0 adds a required machine-readable `code` to unavailable quote results.
+The service call, quote input, available result, and localized unavailable
+`reason` are unchanged.
+
+## 1. Handle the Unavailable Code
+
+An unavailable result now has this shape:
+
+```ts
+type UnavailableGuestQuoteResult = {
+  readonly status: "unavailable";
+  readonly code: "NotBookable" | "AmbiguousMultiRate" | "UnresolvableMultiRate";
+  readonly reason: string;
+};
+```
+
+Branch on `code` after narrowing by `status`:
+
+```ts
+const result = await sdk.live.quote.quote(input);
+
+if (result.status === "unavailable") {
+  switch (result.code) {
+    case "AmbiguousMultiRate":
+    case "UnresolvableMultiRate":
+      reportQuoteConfigurationProblem(result.code);
+      break;
+    case "NotBookable":
+      break;
+  }
+
+  showUnavailableMessage(result.reason);
+}
+```
+
+Keep displaying `reason` when appropriate, but do not parse or compare it to
+select application behavior. It is localized and can still contain the same
+text for different codes.
+
+## 2. Treat Multi-Rate Codes as Operational Failures
+
+The v10-specific codes mean:
+
+- `AmbiguousMultiRate`: the stay was priced, but more than one multi-rate
+  matched the default cancellation policy.
+- `UnresolvableMultiRate`: the stay was priced, but no multi-rate could be
+  resolved for the default cancellation policy.
+
+These are not proof that another guest booked the period. Keep the public quote
+unavailable, show suitable fallback copy, and send the code to monitoring or
+site operations so the rental configuration can be corrected.
+
+Do not retry booking with an arbitrary multi-rate. The price alone does not
+identify the exact multi-rate required by the booking request.
+
+## 3. Keep Normal Unavailability Handling
+
+`NotBookable` represents ordinary unavailable quote results, including backend
+responses without a bookable price:
+
+```ts
+if (result.status === "unavailable" && result.code === "NotBookable") {
+  showUnavailableMessage(result.reason);
+}
+```
+
+Legacy v9 unavailable quotes always use `NotBookable`. No v9 configuration or
+request change is required.
+
+## 4. Update Mocks, Fixtures, and Snapshots
+
+Add `code` anywhere an unavailable result is constructed or compared:
+
+```ts
+const unavailableQuote = {
+  status: "unavailable",
+  code: "NotBookable",
+  reason: "Not available",
+} as const;
+```
+
+Update:
+
+1. TypeScript mocks typed as `GuestQuoteResult` or `QuoteQuoteOutput`.
+2. JSON fixtures decoded with `QuoteQuoteOutputSchema`.
+3. Complete-object assertions and snapshots.
+4. API adapters that persist or forward quote results.
+
+Available-result fixtures require no changes.
+
+## Required Consumer Work
+
+1. Add `code` to unavailable quote mocks and fixtures.
+2. Replace reason-string comparisons with code checks.
+3. Route `AmbiguousMultiRate` and `UnresolvableMultiRate` to operational
+   diagnostics.
+4. Keep all three codes unavailable in booking UI.
+
+## Recommended Verification
+
+1. Confirm a normal blocked period returns `NotBookable`.
+2. Confirm unavailable copy still uses the localized `reason`.
+3. Confirm monitoring distinguishes both multi-rate codes from
+   `NotBookable`.
+4. Confirm the UI never enables booking for either multi-rate code.
+5. Confirm available quote, option selection, and booking flows are unchanged.
+6. Confirm legacy v9 unavailable quote snapshots include `NotBookable`.

package/dist/{quote-Qy_affum.mjs → quote-C-Bs3XTE.mjs}

@@ -286,6 +286,7 @@ const toGuestQuote = (input, guestQuoteResult, locale, translations, options) =>
 	const errorReason = toErrorReason(guestQuoteResult);
 	if (errorReason !== void 0) return {
 		status: "unavailable",
+		code: "NotBookable",
 		reason: errorReason
 	};
 	const sections = yield* toSections({

package/dist/{rentals-CN01jEkv.mjs → rentals--cnnFS4I.mjs}

@@ -1,4 +1,4 @@
-import { a as toLocalizedString, c as rentalsAllWithoutFeedbacksQuery, d as VofficeUnitDataPropertyCategoryValues, f as VofficeUnitDataPropertyMetadata, h as parseVofficeUnitData, i as toAddress, l as VofficeUnitDataFieldSchemas, m as parseVofficeFeedbackData, n as renderVofficePropertyAttribute, p as parseVofficeFacilityData, r as toImages, s as rentalsAllFeedbacksQuery, t as toRentalHighlights, u as VofficeUnitDataPropertyCategoryLabelKeys } from "./to-rental-highlights-D_VRHaaC.mjs";
+import { a as toAddress, c as rentalsAllFeedbacksQuery, d as VofficeUnitDataPropertyCategoryLabelKeys, f as VofficeUnitDataPropertyCategoryValues, g as parseVofficeUnitData, h as parseVofficeFeedbackData, i as toImages, l as rentalsAllWithoutFeedbacksQuery, m as parseVofficeFacilityData, n as renderVofficePropertyAttribute, o as toLocalizedString, p as VofficeUnitDataPropertyMetadata, r as toFacilityImages, t as toRentalHighlights, u as VofficeUnitDataFieldSchemas } from "./to-rental-highlights-BAsEuxoy.mjs";
 import { makeTranslate, renderResolvedCustomAttribute, toCustomAttributeList, toResolvedCustomAttributeCategoryTranslationKey } from "@v-office/sdk-core";
 import { Effect } from "effect";
 //#region src/legacy-v9/parser/rentals/to-description.ts
@@ -38,11 +38,13 @@ const toProperty = (facility, locale) => {
 	const data = parseVofficeFacilityData(facility.data);
 	const name = toLocalizedString(data.known.name, locale);
 	const description = toLocalizedString(data.known.description, locale);
+	const images = toFacilityImages(data.known.images ?? [], locale);
 	const property = {
 		id: facility.id,
 		nameOrLabel: name ?? facility.name
 	};
 	if (description != null) property.description = { description };
+	if (images.length > 0) property.images = images;
 	return property;
 };
 //#endregion

package/dist/{search-uXcReJdL.mjs → search-Dqiou4mc.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-BvQRpzYY.mjs";
-import { h as parseVofficeUnitData, i as toAddress, l as VofficeUnitDataFieldSchemas, o as searchQuery, r as toImages, t as toRentalHighlights } from "./to-rental-highlights-D_VRHaaC.mjs";
+import { a as parseQueryParameters, i as collectQueryParameters, n as makeV9CustomAttributeFilterCapabilities, o as toQueryString, r as toBasicQueryInputs, s as applyVofficeFilterDerivedBasicQueryInputs } from "./client-CaZZGJAW.mjs";
+import { a as toAddress, g as parseVofficeUnitData, i as toImages, s as searchQuery, t as toRentalHighlights, u as VofficeUnitDataFieldSchemas } from "./to-rental-highlights-BAsEuxoy.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

package/dist/{to-rental-highlights-D_VRHaaC.mjs → to-rental-highlights-BAsEuxoy.mjs}

@@ -4861,7 +4861,8 @@ Schema.String, Schema.String;
 /** Known structure of VofficeFacility.data attributes. */
 const VofficeFacilityDataFieldSchemas = {
 	name: localizedString,
-	description: localizedString
+	description: localizedString,
+	images: Schema.mutable(Schema.Array(ImageDataSchema))
 };
 const parseVofficeFacilityData = (input) => parseJsonData(VofficeFacilityDataFieldSchemas, input);
 Schema.String, Schema.String, Schema.Number, Schema.String;
@@ -6754,12 +6755,33 @@ const IMAGE_SRCSET_WIDTHS = [
 	2560
 ];
 const IMAGE_DEFAULT_WIDTH = 960;
+const VOFFICE_DYNAMIC_IMAGE_BASE_URL = "https://dyn.v-office.com/image";
+const VOFFICE_DYNAMIC_IMAGE_SIZES = [
+	["tn", 141],
+	["tnx", 225],
+	["s", 450],
+	["m", 600],
+	["xl", 1440],
+	["xxl", 2400]
+];
+const VOFFICE_DYNAMIC_IMAGE_DEFAULT_SIZE = "xl";
 const buildImageUrl = (imageProxyBaseUrl, path, width) => {
 	const base = imageProxyBaseUrl.replace(/\/$/, "");
 	const normalizedPath = path.replace(/^\/+/, "");
 	return `${base}/_/rs:fill:${width}:${Math.round(width / IMAGE_ASPECT_RATIO)}:0/plain/${normalizedPath}`;
 };
 const buildSrcset = (imageProxyBaseUrl, path) => IMAGE_SRCSET_WIDTHS.map((width) => `${buildImageUrl(imageProxyBaseUrl, path, width)} ${width}w`).join(", ");
+const buildVofficeDynamicImageUrl = (imageId, size) => `${VOFFICE_DYNAMIC_IMAGE_BASE_URL}/${size}/${imageId}.jpg`;
+const buildVofficeDynamicImageSrcset = (imageId, originalImageWidth) => {
+	const originalWidth = originalImageWidth != null && originalImageWidth > 0 ? originalImageWidth : void 0;
+	const seenWidths = /* @__PURE__ */ new Set();
+	return VOFFICE_DYNAMIC_IMAGE_SIZES.flatMap(([size, maximumWidth]) => {
+		const width = originalWidth == null ? maximumWidth : Math.min(maximumWidth, originalWidth);
+		if (seenWidths.has(width)) return [];
+		seenWidths.add(width);
+		return [`${buildVofficeDynamicImageUrl(imageId, size)} ${width}w`];
+	}).join(", ");
+};
 const isNonEmptyString = (value) => typeof value === "string" && value.length > 0;
 const toDataImageId = (dataImage) => dataImage?.id?.toString();
 const getImagePath = (entry) => entry.image?.path ?? entry.normalizedPath;
@@ -6864,6 +6886,25 @@ const toImage = (imageProxyBaseUrl, entry, locale) => {
 const toImages = (imageProxyBaseUrl, rental, locale, data) => {
 	return mergeImageEntries(getImageEntries(rental, data)).map((entry) => toImage(imageProxyBaseUrl, entry, locale));
 };
+const toFacilityImages = (images, locale) => images.flatMap((image) => {
+	if (image.id == null) return [];
+	const title = toLocalizedString(image.titles, locale);
+	const item = {
+		idOrPath: image.id.toString(),
+		src: buildVofficeDynamicImageUrl(image.id, VOFFICE_DYNAMIC_IMAGE_DEFAULT_SIZE),
+		srcset: buildVofficeDynamicImageSrcset(image.id, image.width),
+		metadata: {
+			source: "voffice_facility_data_images",
+			dataImage: image
+		}
+	};
+	if (title != null) {
+		item.alt = title;
+		item.title = title;
+	}
+	if (image.tag != null) item.category = image.tag;
+	return [item];
+});
 //#endregion
 //#region src/legacy-v9/parser/rentals/render-property-attribute.ts
 const countLabelKey = (labelKey, value) => `${labelKey.slice(0, -6)}.count.${value === 1 ? "one" : "other"}`;
@@ -7278,4 +7319,4 @@ const toRentalHighlights = ({ locale, translations, highlightPrioritization, cus
 	return highlights;
 });
 //#endregion
-export { toLocalizedString as a, rentalsAllWithoutFeedbacksQuery as c, VofficeUnitDataPropertyCategoryValues as d, VofficeUnitDataPropertyMetadata as f, parseVofficeUnitData as h, toAddress as i, VofficeUnitDataFieldSchemas as l, parseVofficeFeedbackData as m, renderVofficePropertyAttribute as n, searchQuery as o, parseVofficeFacilityData as p, toImages as r, rentalsAllFeedbacksQuery as s, toRentalHighlights as t, VofficeUnitDataPropertyCategoryLabelKeys as u };
+export { toAddress as a, rentalsAllFeedbacksQuery as c, VofficeUnitDataPropertyCategoryLabelKeys as d, VofficeUnitDataPropertyCategoryValues as f, parseVofficeUnitData as g, parseVofficeFeedbackData as h, toImages as i, rentalsAllWithoutFeedbacksQuery as l, parseVofficeFacilityData as m, renderVofficePropertyAttribute as n, toLocalizedString as o, VofficeUnitDataPropertyMetadata as p, toFacilityImages as r, searchQuery as s, toRentalHighlights as t, VofficeUnitDataFieldSchemas as u };

package/instructions/CHANGELOG.md

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

package/instructions/MIGRATION.md

@@ -4,6 +4,8 @@ This file is the versioned migration index for the website SDK instructions.
 
 ## Available Guides
 
+- `versions/2.16.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.15.0 to 2.16.0.
+- `versions/2.15.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.14.0 to 2.15.0.
 - `versions/2.14.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.13.0 to 2.14.0.
 - `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.

package/instructions/README.md

@@ -1,7 +1,7 @@
 # Website SDK Instructions
 
 These instructions describe the current source targeted for
-`@v-office/website-sdk` 2.14.0. Package versions remain unchanged until the release
+`@v-office/website-sdk` 2.16.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,12 @@ 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.16.0/`: 2.16.0 machine-readable unavailable quote codes,
+  multi-rate configuration diagnostics, and the 2.15.0-to-2.16.0 migration
+  guide.
+- `versions/2.15.0/`: 2.15.0 v9 facility images in normalized
+  `property.images`, responsive vOffice image URLs, and the 2.14.0-to-2.15.0
+  migration guide.
 - `versions/2.14.0/`: 2.14.0 catalog-backed v9 property types and options,
   corrected option/count rendering and translations, and the 2.13.0-to-2.14.0
   migration guide.
@@ -90,5 +96,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.14.0. v10 config additionally requires `searchEndpoint` as
+in 2.0.0 and kept in 2.16.0. v10 config additionally requires `searchEndpoint` as
 of 2.5.0.

package/instructions/quote.md

@@ -133,10 +133,40 @@ Unavailable sample:
 ```json
 {
   "status": "unavailable",
+  "code": "NotBookable",
   "reason": "Rental is not available for the selected period."
 }
 ```
 
+From 2.16.0, every unavailable quote includes a machine-readable `code`:
+
+- `NotBookable`: the backend did not return a bookable price, including normal
+  availability failures. Legacy v9 unavailable quotes always use this code.
+- `AmbiguousMultiRate`: v10 priced the stay, but more than one multi-rate
+  matched the default cancellation policy.
+- `UnresolvableMultiRate`: v10 priced the stay, but no multi-rate could be
+  resolved for the default cancellation policy.
+
+Use `code` for application behavior and logging. `reason` remains localized
+display text and can be identical for inventory and multi-rate failures. The SDK
+keeps ambiguous and unresolvable v10 quotes unavailable because booking requires
+one exact multi-rate.
+
+```ts
+const result = await sdk.live.quote.quote(input);
+
+if (result.status === "unavailable") {
+  if (result.code === "AmbiguousMultiRate" || result.code === "UnresolvableMultiRate") {
+    reportQuoteConfigurationProblem(result.code);
+  }
+
+  showUnavailableMessage(result.reason);
+}
+```
+
+See `versions/2.16.0/CHANGELOG.md` and
+`versions/2.16.0/MIGRATION.md` for release and upgrade details.
+
 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

package/instructions/rentals.md

@@ -87,6 +87,42 @@ Sample item:
 
 Optional fields include `scope`, `address`, `property`, `rooms`, `roomSummary`, `vicinity`, and `reviews`.
 
+### Legacy v9 Facility Images
+
+From 2.15.0, v9 static rentals request facility image metadata and return it in
+`property.images`:
+
+```json
+{
+  "property": {
+    "id": "1512",
+    "nameOrLabel": "Haus Köbesine",
+    "images": [
+      {
+        "idOrPath": "28458352",
+        "src": "https://dyn.v-office.com/image/xl/28458352.jpg",
+        "srcset": "https://dyn.v-office.com/image/tn/28458352.jpg 141w, https://dyn.v-office.com/image/tnx/28458352.jpg 225w, https://dyn.v-office.com/image/s/28458352.jpg 450w, https://dyn.v-office.com/image/m/28458352.jpg 600w, https://dyn.v-office.com/image/xl/28458352.jpg 1440w, https://dyn.v-office.com/image/xxl/28458352.jpg 2400w",
+        "alt": "Hauptansicht",
+        "title": "Hauptansicht",
+        "category": "buildingMain"
+      }
+    ]
+  }
+}
+```
+
+Facility image `src` and `srcset` URLs use `dyn.v-office.com`. Top-level v9
+rental `images` continue to use the configured `imageProxyBaseUrl`. Consumers
+must allow both origins when they render both collections.
+
+The SDK supplies width-descriptor `srcset`; the UI remains responsible for an
+HTML `sizes` attribute that matches its layout. `property.images` is omitted
+when the facility has no usable image IDs. Because the service returns one item
+per rental, rentals in the same facility contain the same nested property image
+list.
+
+See `versions/2.15.0/CHANGELOG.md` and `versions/2.15.0/MIGRATION.md`.
+
 ### Legacy v9 Built-In Attributes
 
 From 2.14.0, built-in v9 property types and ordered option values come from the

package/instructions/versions/2.15.0/CHANGELOG.md

@@ -0,0 +1,66 @@
+# Changelog: 2.15.0
+
+This release adds facility images to normalized v9 static rental output. v9
+consumers can now read responsive property images from the same
+`property.images` field already used by the shared rental contract.
+
+## Added
+
+- v9 static rentals request the facility `images` data attribute through the
+  existing GraphQL `all` query.
+- Parsed facility images are exposed under:
+
+  ```ts
+  rental.property?.images;
+  ```
+
+- Every mapped facility image includes:
+  - `idOrPath` from the vOffice image ID
+  - an `xl` fallback `src`
+  - a responsive width-descriptor `srcset`
+  - localized `alt` and `title` when a title is available
+  - `category` when vOffice supplies an image tag
+  - the original v9 image metadata under `metadata.dataImage`
+- The generated v9 facility-data schema recognizes facility image records and
+  validates them with the existing `ImageDataSchema`.
+- Facility `srcset` candidates use the unique vOffice dynamic-image presets:
+  `141w`, `225w`, `450w`, `600w`, `1440w`, and `2400w`. Candidates are capped
+  at the known original image width and duplicate widths are omitted.
+
+## Changed
+
+- v9 facility image bytes are served by the documented vOffice dynamic-image
+  origin:
+
+  ```text
+  https://dyn.v-office.com/image/<size>/<image-id>.jpg
+  ```
+
+- Facility images no longer need to be inferred from a rental image storage
+  path. That inference was invalid because facility image IDs are not present
+  in the v9 rental image rows.
+- A v9 property shared by several rentals carries the same facility image list
+  on each normalized rental's nested `property` object.
+
+## Unchanged
+
+- `sdk.static.rentals.getRentals({ locale })` and its input are unchanged.
+- The public `RentalPropertySchema` and image shape are unchanged because
+  `property.images` was already part of the shared contract.
+- Top-level v9 rental `images` continue to use the configured
+  `imageProxyBaseUrl`.
+- v10 rental and property image behavior is unchanged.
+- No new SDK configuration or environment variable is required.
+
+## Compatibility
+
+- This is an additive output change. v9 consumers that ignore
+  `property.images` do not need code changes.
+- Content Security Policy or image-host allowlists must permit
+  `https://dyn.v-office.com` before rendering the new v9 property images.
+- Snapshots that include complete v9 property objects must account for the new
+  optional `images` field.
+- Facility image entries without a numeric vOffice image ID are omitted because
+  no deterministic dynamic-image URL can be constructed.
+
+See `versions/2.15.0/MIGRATION.md` and `../../rentals.md`.

package/instructions/versions/2.15.0/MIGRATION.md

@@ -0,0 +1,148 @@
+# Migration: 2.14.0 to 2.15.0
+
+2.15.0 adds facility images to v9 static rental properties. The SDK call,
+configuration, and public TypeScript shape are unchanged, but complete v9
+property objects can now contain `images`.
+
+Consumers that use only v10 are not affected.
+
+## 1. Allow the vOffice Image Origin
+
+v9 facility image URLs use:
+
+```text
+https://dyn.v-office.com
+```
+
+Add that origin to image-host allowlists and Content Security Policy before
+rendering `property.images`. For example:
+
+```text
+Content-Security-Policy: img-src 'self' https://dyn.v-office.com
+```
+
+Top-level v9 rental images still use the configured `imageProxyBaseUrl`. A page
+that renders both image kinds must allow both origins.
+
+## 2. Read Facility Images from `property.images`
+
+No new service call is required:
+
+```ts
+const rentals = await sdk.static.rentals.getRentals({ locale: "de-DE" });
+
+for (const rental of rentals) {
+  for (const image of rental.property?.images ?? []) {
+    renderPropertyImage(image);
+  }
+}
+```
+
+The field remains optional. It is omitted when a rental has no facility, when
+the facility has no images, or when no facility image has a usable numeric ID.
+
+Example image:
+
+```json
+{
+  "idOrPath": "28458352",
+  "src": "https://dyn.v-office.com/image/xl/28458352.jpg",
+  "srcset": "https://dyn.v-office.com/image/tn/28458352.jpg 141w, https://dyn.v-office.com/image/tnx/28458352.jpg 225w, https://dyn.v-office.com/image/s/28458352.jpg 450w, https://dyn.v-office.com/image/m/28458352.jpg 600w, https://dyn.v-office.com/image/xl/28458352.jpg 1440w, https://dyn.v-office.com/image/xxl/28458352.jpg 2400w",
+  "alt": "Hauptansicht",
+  "title": "Hauptansicht",
+  "category": "buildingMain"
+}
+```
+
+## 3. Provide the Layout-Specific `sizes` Attribute
+
+The SDK provides `src` and `srcset`. The consuming UI must provide `sizes`
+because only the application knows the rendered layout:
+
+```tsx
+<img
+  src={image.src}
+  srcSet={image.srcset}
+  sizes="(max-width: 768px) 100vw, 50vw"
+  alt={image.alt ?? ""}
+/>
+```
+
+Do not copy that example `sizes` value blindly. Match it to the actual image
+width in the application's responsive layout.
+
+The fallback `src` uses the `xl` vOffice preset. Browsers that support `srcset`
+select an appropriate candidate using `srcset`, `sizes`, viewport width, and
+device pixel ratio.
+
+## 4. Keep Rental and Property Images Distinct
+
+The two image collections represent different entities:
+
+```ts
+rental.images; // images belonging to the rental/unit
+rental.property?.images; // images belonging to the facility/property
+```
+
+They also use different origins in v9:
+
+- `rental.images`: configured `imageProxyBaseUrl`
+- `rental.property.images`: `https://dyn.v-office.com`
+
+Do not merge the arrays unless the UI deliberately presents a combined gallery.
+Keeping them separate prevents facility images from being mistaken for
+unit-specific rooms or amenities.
+
+## 5. Account for Repeated Property Data
+
+The normalized rentals API returns one item per rental. When several rentals
+belong to the same facility, each rental contains the same nested property image
+list.
+
+Applications that build a property-level view can deduplicate by `property.id`:
+
+```ts
+const properties = new Map(
+  rentals.flatMap((rental) =>
+    rental.property == null ? [] : [[rental.property.id, rental.property] as const],
+  ),
+);
+```
+
+No separate property endpoint or persistence layer was added in 2.15.0.
+
+## 6. Update Snapshots and Complete-Object Assertions
+
+Tests that compare only selected property fields are unaffected. Tests that
+snapshot or deeply compare complete v9 rental output can now observe:
+
+```ts
+rental.property.images;
+```
+
+Update those expectations without making `property.images` mandatory. Backend
+facilities are allowed to have no usable images.
+
+## Required Consumer Work
+
+For applications that render v9 property images:
+
+1. Allow `https://dyn.v-office.com` in CSP and image-host configuration.
+2. Render `rental.property.images` separately from top-level rental images.
+3. Supply an HTML `sizes` value appropriate for the layout.
+4. Keep empty and missing image arrays valid.
+5. Update complete-output snapshots.
+
+Applications that do not render v9 property images require no migration work.
+
+## Recommended Verification
+
+1. Fetch v9 static rentals in both `de-DE` and `en-US`.
+2. Confirm facilities with images expose `property.images`.
+3. Confirm localized image titles populate `alt` and `title`.
+4. Confirm the browser selects responsive candidates after adding `sizes`.
+5. Confirm `dyn.v-office.com` is accepted by production CSP.
+6. Confirm top-level rental images still use the configured image proxy.
+7. Confirm a shared facility does not create duplicate property cards when the
+   application deduplicates by `property.id`.
+8. Confirm v10 rental and property image rendering remains unchanged.

package/instructions/versions/2.16.0/CHANGELOG.md

@@ -0,0 +1,44 @@
+# Changelog: 2.16.0
+
+This release makes unavailable quote results machine-readable. Applications can
+now distinguish normal booking unavailability from v10 multi-rate
+configuration failures without parsing localized text.
+
+## Added
+
+- Every unavailable `GuestQuoteResult` contains a `code`:
+  - `NotBookable`
+  - `AmbiguousMultiRate`
+  - `UnresolvableMultiRate`
+- The public quote output schema validates the new code.
+- v10 reports `AmbiguousMultiRate` when a priced default cancellation policy
+  matches more than one multi-rate.
+- v10 reports `UnresolvableMultiRate` when a priced default cancellation policy
+  cannot be mapped to a multi-rate.
+
+## Changed
+
+- Legacy v9 unavailable quotes now include `code: "NotBookable"`.
+- Normal v10 quote failures also use `code: "NotBookable"`.
+- v10 retains the exact default-policy multi-rate resolution result instead of
+  reducing it to a boolean before creating the public unavailable result.
+
+## Unchanged
+
+- `sdk.live.quote.quote(input)` and its input are unchanged.
+- Available quote results remain `{ status: "available", quote }`.
+- Unavailable results retain the localized `reason` field.
+- Ambiguous or unresolvable v10 multi-rates remain unavailable. The SDK does not
+  select an arbitrary fallback because booking requires one exact multi-rate.
+- Search and calendar availability behavior are unchanged.
+
+## Compatibility
+
+- Consumers that only inspect `status` and display `reason` continue to work.
+- TypeScript mocks, complete-object assertions, snapshots, and schema fixtures
+  for unavailable quotes must include `code`.
+- Application behavior should branch on `code`, not localized `reason`.
+- `AmbiguousMultiRate` and `UnresolvableMultiRate` indicate configuration or
+  mapping problems and should normally be reported to site operations.
+
+See `versions/2.16.0/MIGRATION.md` and `../../quote.md`.

package/instructions/versions/2.16.0/MIGRATION.md

@@ -0,0 +1,109 @@
+# Migration: 2.15.0 to 2.16.0
+
+2.16.0 adds a required machine-readable `code` to unavailable quote results.
+The service call, quote input, available result, and localized unavailable
+`reason` are unchanged.
+
+## 1. Handle the Unavailable Code
+
+An unavailable result now has this shape:
+
+```ts
+type UnavailableGuestQuoteResult = {
+  readonly status: "unavailable";
+  readonly code: "NotBookable" | "AmbiguousMultiRate" | "UnresolvableMultiRate";
+  readonly reason: string;
+};
+```
+
+Branch on `code` after narrowing by `status`:
+
+```ts
+const result = await sdk.live.quote.quote(input);
+
+if (result.status === "unavailable") {
+  switch (result.code) {
+    case "AmbiguousMultiRate":
+    case "UnresolvableMultiRate":
+      reportQuoteConfigurationProblem(result.code);
+      break;
+    case "NotBookable":
+      break;
+  }
+
+  showUnavailableMessage(result.reason);
+}
+```
+
+Keep displaying `reason` when appropriate, but do not parse or compare it to
+select application behavior. It is localized and can still contain the same
+text for different codes.
+
+## 2. Treat Multi-Rate Codes as Operational Failures
+
+The v10-specific codes mean:
+
+- `AmbiguousMultiRate`: the stay was priced, but more than one multi-rate
+  matched the default cancellation policy.
+- `UnresolvableMultiRate`: the stay was priced, but no multi-rate could be
+  resolved for the default cancellation policy.
+
+These are not proof that another guest booked the period. Keep the public quote
+unavailable, show suitable fallback copy, and send the code to monitoring or
+site operations so the rental configuration can be corrected.
+
+Do not retry booking with an arbitrary multi-rate. The price alone does not
+identify the exact multi-rate required by the booking request.
+
+## 3. Keep Normal Unavailability Handling
+
+`NotBookable` represents ordinary unavailable quote results, including backend
+responses without a bookable price:
+
+```ts
+if (result.status === "unavailable" && result.code === "NotBookable") {
+  showUnavailableMessage(result.reason);
+}
+```
+
+Legacy v9 unavailable quotes always use `NotBookable`. No v9 configuration or
+request change is required.
+
+## 4. Update Mocks, Fixtures, and Snapshots
+
+Add `code` anywhere an unavailable result is constructed or compared:
+
+```ts
+const unavailableQuote = {
+  status: "unavailable",
+  code: "NotBookable",
+  reason: "Not available",
+} as const;
+```
+
+Update:
+
+1. TypeScript mocks typed as `GuestQuoteResult` or `QuoteQuoteOutput`.
+2. JSON fixtures decoded with `QuoteQuoteOutputSchema`.
+3. Complete-object assertions and snapshots.
+4. API adapters that persist or forward quote results.
+
+Available-result fixtures require no changes.
+
+## Required Consumer Work
+
+1. Add `code` to unavailable quote mocks and fixtures.
+2. Replace reason-string comparisons with code checks.
+3. Route `AmbiguousMultiRate` and `UnresolvableMultiRate` to operational
+   diagnostics.
+4. Keep all three codes unavailable in booking UI.
+
+## Recommended Verification
+
+1. Confirm a normal blocked period returns `NotBookable`.
+2. Confirm unavailable copy still uses the localized `reason`.
+3. Confirm monitoring distinguishes both multi-rate codes from
+   `NotBookable`.
+4. Confirm the UI never enables booking for either multi-rate code.
+5. Confirm available quote, option selection, and booking flows are unchanged.
+6. Confirm legacy v9 unavailable quote snapshots include `NotBookable`.

package/package.json

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