@v-office/website-sdk 2.16.2 → 2.17.0

package/dist/cli.mjs

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

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

@@ -1370,6 +1370,25 @@ const toFirstCalculationDate = ({ availability, now }) => {
 	return [Object.keys(availability.caldata_beon).toSorted()[0], today].filter((date) => date != null).toSorted().at(-1);
 };
 //#endregion
+//#region src/legacy-v9/parser/availability/to-initial-availability-calendar-days.ts
+const applyV9CalendarPrices = ({ availability, calendarDays, locale, currency }) => {
+	const result = { ...calendarDays };
+	for (const [date, day] of Object.entries(calendarDays)) {
+		const price = availability.caldata_beon[date]?.price;
+		if (day.canBeStartDate && typeof price === "number" && currency !== void 0) result[date] = {
+			...day,
+			formattedPrice: formatCurrency(price, locale, currency)
+		};
+	}
+	return result;
+};
+const toInitialAvailabilityCalendarDays$1 = ({ availability, currency, ...input }) => toInitialAvailabilityCalendarDays(input).pipe(Effect.map((calendarDays) => applyV9CalendarPrices({
+	availability,
+	calendarDays,
+	locale: input.input.locale,
+	...currency === void 0 ? {} : { currency }
+})));
+//#endregion
 //#region translations/v9/de-DE/core.json
 var core_default$1 = {
 	"Rental.rentalType.option.HOUSE": "Haus",
@@ -2885,6 +2904,7 @@ const makeV9AvailabilityApi = ({ config, options }) => {
 		apiKey: config.apiKey,
 		...config.v1ApiBaseUrl === void 0 ? {} : { baseUrl: config.v1ApiBaseUrl }
 	});
+	const bookingCurrencyByUnitId = /* @__PURE__ */ new Map();
 	const loadAvailability = (input) => Effect.gen(function* () {
 		const client = yield* V1OpenApiClient;
 		const unitId = yield* toVofficeUnitId$2(input);
@@ -2898,21 +2918,36 @@ const makeV9AvailabilityApi = ({ config, options }) => {
 			cause
 		})))).data;
 	}).pipe(Effect.provide(openApiClientLive));
+	const loadBookingCurrency = (input) => Effect.gen(function* () {
+		const client = yield* V1OpenApiClient;
+		const unitId = yield* toVofficeUnitId$2(input);
+		if (bookingCurrencyByUnitId.has(unitId)) return bookingCurrencyByUnitId.get(unitId);
+		const result = yield* client.execute("getUnit", { path: { voffice_unit: unitId } }).pipe(Effect.match({
+			onFailure: () => void 0,
+			onSuccess: (result) => result
+		}));
+		if (result === void 0) return void 0;
+		const currency = firstString(result.data.data.currency);
+		bookingCurrencyByUnitId.set(unitId, currency);
+		return currency;
+	}).pipe(Effect.provide(openApiClientLive));
 	return {
 		getInitialAvailability: (input) => Effect.runPromise(Effect.gen(function* () {
 			const now = yield* DateTime.now;
-			const availability = yield* loadAvailability(input);
+			const [availability, currency] = yield* Effect.all([loadAvailability(input), loadBookingCurrency(input)]);
 			const firstCalculationDate = toFirstCalculationDate({
 				availability,
 				now
 			});
 			const availabilityRestrictionsByDate = toAvailabilityRestrictionsByDate({ availability });
 			return {
-				calendarDays: yield* toInitialAvailabilityCalendarDays({
+				calendarDays: yield* toInitialAvailabilityCalendarDays$1({
+					availability,
 					input,
 					firstCalculationDate,
 					availabilityRestrictionsByDate,
-					translations
+					translations,
+					...currency === void 0 ? {} : { currency }
 				}),
 				minPersons: null,
 				maxPersons: null,
@@ -5477,7 +5512,7 @@ const parseV9SearchCursor = (cursor) => Effect.gen(function* () {
 	return page;
 });
 const loadV9SearchRuntime = Effect.tryPromise({
-	try: () => import("./search-Dqiou4mc.mjs"),
+	try: () => import("./search-zsnAfUtc.mjs"),
 	catch: (cause) => new CoreSDKError({
 		source: "v10",
 		operation: "v9.search.runtime",
@@ -5844,7 +5879,7 @@ const DEFAULT_RENTAL_FEEDBACK_DATA_ATTRIBUTES = [
 	"avgRating"
 ];
 const loadV9RentalsRuntime = Effect.tryPromise({
-	try: () => import("./rentals--cnnFS4I.mjs"),
+	try: () => import("./rentals-BokBV-ze.mjs"),
 	catch: (cause) => new CoreSDKError({
 		source: "v10",
 		operation: "v9.rentals.runtime",

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-CaZZGJAW.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-ScO68LGg.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.17.0/CHANGELOG.md`: `@v-office/website-sdk` 2.17.0 release notes.
+- `versions/2.16.3/CHANGELOG.md`: `@v-office/website-sdk` 2.16.3 release notes.
 - `versions/2.16.2/CHANGELOG.md`: `@v-office/website-sdk` 2.16.2 documentation release notes.
 - `versions/2.16.1/CHANGELOG.md`: `@v-office/website-sdk` 2.16.1 release notes.
 - `versions/2.16.0/CHANGELOG.md`: `@v-office/website-sdk` 2.16.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.17.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.16.3 to 2.17.0.
+- `versions/2.16.3/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.16.2 to 2.16.3.
 - `versions/2.16.2/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.16.1 to 2.16.2.
 - `versions/2.16.1/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.16.0 to 2.16.1.
 - `versions/2.16.0/MIGRATION.md`: migrate from `@v-office/website-sdk` 2.15.0 to 2.16.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.16.2. Package versions remain unchanged until the release
+`@v-office/website-sdk` 2.17.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,10 @@ 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.17.0/`: 2.17.0 legacy-v9 calendar-day prices and structured
+  rooms, shared bed-amount expansion, and the 2.16.3-to-2.17.0 migration guide.
+- `versions/2.16.3/`: 2.16.3 browser-origin resolution for relative payment
+  return URLs and the 2.16.2-to-2.16.3 migration guide.
 - `versions/2.16.2/`: 2.16.2 documentation release notes and migration guide.
 - `versions/2.16.1/`: 2.16.1 v10 multi-rate resolution restricted to rent rates,
   restored additional-service availability, and the 2.16.0-to-2.16.1 migration
@@ -100,5 +104,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.16.2. v10 config additionally requires `searchEndpoint` as
+in 2.0.0 and kept in 2.17.0. v10 config additionally requires `searchEndpoint` as
 of 2.5.0.

package/dist/instructions/availability.md

@@ -96,6 +96,31 @@ Start-date-selected availability returns `Promise<StartDateSelectedAvailabilityO
 
 Common statuses include `available`, `before_today`, `check_in_not_allowed`, `no_valid_check_out_from_start`, `after_last_bookable_date`, and `unavailable`. End-date results can also return `same_day`, `not_after_selected_start`, `minimum_stay_not_met`, `check_out_not_allowed`, and range-crossing statuses.
 
+### Legacy v9 Calendar-Day Prices
+
+From 2.17.0, v9 initial availability uses the numeric price supplied by the v1
+calendar to populate `formattedPrice` on valid start dates. The value is already
+localized and formatted in the rental unit's configured booking currency.
+Render it directly rather than parsing or reformatting it.
+
+`formattedPrice` remains `null` when the date cannot be used as a start date,
+the date is unavailable, the v1 calendar supplies no numeric price, or the
+unit's currency cannot be loaded. Start-date-selected availability does not
+include calendar prices.
+
+When no successful unit lookup is cached, a v9 initial-availability request loads
+the calendar and a unit record. Successful unit responses are cached by unit ID
+for the lifetime of the SDK instance, including responses without a currency.
+Failed unit requests are not cached and are retried on the next call. A missing
+currency or failed unit request does not fail availability; calendar prices
+remain `null`.
+
+No new configuration is required. The currency lookup uses the existing
+`v1ApiBaseUrl` and `apiKey`.
+
+See `versions/2.17.0/CHANGELOG.md` and
+`versions/2.17.0/MIGRATION.md`.
+
 ## Configuration
 
 Use flat `WebsiteSDKConfig` files.

package/dist/instructions/booking.md

@@ -68,6 +68,10 @@ 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.
+In a browser, the SDK resolves a relative value against `window.location.origin`
+before initializing a v10 Adyen payment. An absolute HTTP or HTTPS URL is passed
+through unchanged. Server-side callers must provide an absolute HTTP or HTTPS URL
+because no browser origin is available.
 
 ## Output
 
@@ -167,7 +171,13 @@ try {
 
 ## Payment Return
 
-Online payment providers return the guest to a URL derived from `relativeRedirectUrl`. Stripe returns to that path with `payment=stripe&success=true` after payment and `payment=stripe&cancel=true` after cancellation, so the path must exist in your site and should read those query parameters.
+Online payment providers return the guest to a URL derived from
+`relativeRedirectUrl`. A relative value such as `/booking/payment-return` uses
+the active browser origin, including `http://localhost:<port>` during local
+development and the deployed website origin in production. Stripe returns to
+that path with `payment=stripe&success=true` after payment and
+`payment=stripe&cancel=true` after cancellation, so the path must exist in your
+site and should read those query parameters.
 
 `relativeRedirectUrl` is supplied before the reservation exists, so the return URL cannot carry the booking number. Persist whatever the return page needs, for example in `sessionStorage`, before submitting a payment option.
 

package/dist/instructions/rentals.md

@@ -123,6 +123,47 @@ list.
 
 See `versions/2.15.0/CHANGELOG.md` and `versions/2.15.0/MIGRATION.md`.
 
+### Structured Bed Quantities
+
+From 2.17.0, both backends expand each source bed according to its `amount`.
+Because the public bed shape has no quantity field, a source amount greater than
+one is returned as that many identical entries in `rooms[].beds`. Each entry
+represents one bed and must not be deduplicated by its visible value.
+
+The v10 behavior is delivered by `@v-office/sdk-core`. Refresh the lockfile when
+upgrading so the website package resolves the coordinated core version shipped
+for 2.17.0.
+
+### Legacy v9 Structured Rooms
+
+From 2.17.0, when vOffice supplies `roomDetails`, v9 rentals return them as
+`rooms`. Room types, bed types, bed kinds, and supported room and bed attributes
+are localized.
+
+Supported per-room Boolean attributes are `hasPrivateBathroom`,
+`roomDarkeningOption`, and `wardrobe`. Supported per-bed Boolean attributes are
+`childrenOnly`, `extraLongBeds`, `openFootsection`, and `raisedBeds`.
+
+Translation overrides use:
+
+```text
+Room.type.option.<TYPE>
+RoomAttributes.<attribute>.label
+Bed.type.option.<TYPE>
+Bed.kind.option.<KIND>
+Bed.<attribute>.label
+```
+
+Incomplete room details are handled independently: rooms without a type and beds
+without a type or positive integer amount are omitted. The rental remains
+available, and `rooms` is omitted when no usable room remains.
+
+v9 rooms do not expose per-room descriptions, source `maxGuests`, a structured
+bed amount, room IDs or room-image associations, or `roomSummary`.
+
+See `versions/2.17.0/CHANGELOG.md` and
+`versions/2.17.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.16.3/CHANGELOG.md

@@ -0,0 +1,31 @@
+# Changelog: 2.16.3
+
+This release fixes v10 Adyen payment return URLs when booking is initiated with
+a relative `relativeRedirectUrl`.
+
+## Fixed
+
+- Relative payment return URLs are resolved against `window.location.origin`
+  before the SDK initializes an Adyen payment.
+- Adyen receives the website's complete return URL instead of an unresolved
+  path that could be interpreted relative to the payment provider's origin.
+- Local development can initialize test payments with return URLs such as
+  `http://localhost:4321/booking/payment-return`.
+
+## Unchanged
+
+- `sdk.live.booking.book`, its input, and its output keep the same public types.
+- Existing relative values such as `/booking/payment-return` require no code
+  changes.
+- Absolute HTTP and HTTPS return URLs continue to be passed through unchanged.
+- Legacy v9 booking and payment behavior is unchanged.
+
+## Compatibility
+
+- No consumer code change is required. Upgrade the website SDK and refresh the
+  lockfile.
+- Browser callers can keep supplying a site-relative return path. Server-side
+  callers must supply an absolute HTTP or HTTPS URL because no browser origin is
+  available.
+
+See `versions/2.16.3/MIGRATION.md` and `../../booking.md`.

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

@@ -0,0 +1,51 @@
+# Migration: 2.16.2 to 2.16.3
+
+2.16.3 fixes relative v10 Adyen payment return URLs through
+`@v-office/sdk-core` 1.16.2. No public type, service call, input, or result shape
+changes.
+
+## 1. Upgrade
+
+```sh
+pnpm add @v-office/website-sdk@2.16.3
+```
+
+Refresh the lockfile so the website SDK resolves `@v-office/sdk-core` 1.16.2.
+
+## 2. Keep the Existing Return Path
+
+No application code change is required. Existing relative return paths continue
+to work:
+
+```ts
+const booking = await sdk.live.booking.book({
+  quote,
+  contact,
+  relativeRedirectUrl: "/booking/payment-return",
+});
+```
+
+In a browser, the SDK now resolves that path against `window.location.origin`.
+For example:
+
+```text
+http://localhost:4321 + /booking/payment-return
+→ http://localhost:4321/booking/payment-return
+```
+
+Absolute HTTP and HTTPS return URLs remain unchanged. Server-side callers must
+provide an absolute URL because `window.location.origin` is unavailable.
+
+## Required Consumer Work
+
+None beyond upgrading the dependency and refreshing the lockfile.
+
+## Recommended Verification
+
+1. Start the website locally and create a deliberate v10 test booking.
+2. Confirm the Adyen initiation request contains the local website origin in its
+   `redirectUrl`.
+3. Complete or cancel the hosted test payment and confirm the browser returns to
+   the local payment-return page.
+4. Confirm a deployed website uses its own active origin for the same relative
+   return path.

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

@@ -0,0 +1,83 @@
+# Changelog: 2.17.0
+
+This release restores presentation-ready prices to legacy-v9 initial
+availability calendars and exposes structured v9 room and bed data through the
+shared rental contract. Bed quantities are represented consistently on v9 and
+v10 by returning one public bed entry for each source bed amount.
+
+## Added
+
+- Legacy-v9 static rentals expose source `roomDetails` through the existing
+  optional `rooms` field.
+- v9 room output includes localized room types, bed types, bed kinds, and the
+  supported room and bed attributes supplied by vOffice.
+- Supported v9 room attributes are `hasPrivateBathroom`,
+  `roomDarkeningOption`, and `wardrobe`. Supported bed attributes are
+  `childrenOnly`, `extraLongBeds`, `openFootsection`, and `raisedBeds`.
+
+## Fixed
+
+- Legacy-v9 initial availability calendar days once again expose a localized
+  `formattedPrice` when the date is a valid start date and the v1 calendar
+  supplies a numeric price.
+- Unavailable dates, dates that cannot be used as a start date, and dates without
+  a numeric source price continue to return `formattedPrice: null`.
+
+## Changed
+
+- v9 calendar prices use the rental unit's configured booking currency. The SDK
+  loads that currency through the existing v1 unit endpoint and caches successful
+  unit lookups for the lifetime of the SDK instance.
+- v9 calendar prices remain `null` when the unit currency is missing or cannot
+  be loaded. A currency lookup failure does not make the availability request
+  fail.
+- A source bed with `amount: 3` is represented as three identical entries in
+  `rooms[].beds`. This applies to v9 and v10, whose shared public bed shape does
+  not contain a separate amount field.
+- The first initial v9 availability request for a unit loads both its calendar
+  and unit record. Subsequent calls reuse a successfully loaded unit response,
+  including one that contains no currency. Failed unit requests are not cached
+  and are retried on the next call.
+- v9 room data that does not satisfy the stricter generated heuristic schema is
+  read leniently from the preserved unknown data instead of being discarded as a
+  complete array.
+- One incomplete v9 room or bed does not remove otherwise usable room data or
+  fail the rental.
+
+## Unchanged
+
+- `sdk.live.availability.getInitialAvailability(input)` and
+  `sdk.static.rentals.getRentals({ locale })` keep their existing signatures and
+  public TypeScript contracts.
+- No new v9 configuration value or endpoint is required. The existing
+  `v1ApiBaseUrl` and API key are used for the unit-currency lookup, and
+  `roomDetails` is already requested by the v9 rentals GraphQL operation.
+- v10 initial-availability pricing is unchanged.
+- Start-date-selected availability output does not gain calendar prices.
+- v9 `rooms` remains optional and is omitted when vOffice supplies no usable
+  room details.
+- v9 still does not expose per-room descriptions, source `maxGuests`, a
+  structured bed amount, room IDs or room-image associations, or `roomSummary`.
+- Existing localized `attributes` and `highlights` remain available and are not
+  removed when structured rooms are present.
+
+## Compatibility
+
+- Both features are additive for consumers that read selected fields.
+- Complete v9 availability snapshots can now contain non-null `formattedPrice`
+  values on valid start dates.
+- Complete v9 rental snapshots can now contain `rooms`.
+- v9 and v10 snapshots or UIs that assumed one public bed entry per source bed
+  record must account for repeated entries when the source amount is greater
+  than one.
+- Consumers must not deduplicate identical bed entries: repetition represents
+  the source quantity.
+- The v10 bed expansion is delivered through `@v-office/sdk-core`. Refresh the
+  lockfile when upgrading so the website package resolves the coordinated core
+  version shipped for 2.17.0.
+- A first initial-availability request for a v9 rental can perform one additional
+  v1 unit request for its currency. Applications with request-level mocks or
+  network assertions must account for it.
+
+See `versions/2.17.0/MIGRATION.md`, `../../availability.md`, and
+`../../rentals.md`.

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

@@ -0,0 +1,207 @@
+# Migration: 2.16.3 to 2.17.0
+
+2.17.0 adds presentation-ready prices to legacy-v9 initial availability days
+and structured rooms to legacy-v9 rental output. It also represents source bed
+amounts consistently on v9 and v10 by returning one public entry per bed.
+
+Service inputs, configuration, and public TypeScript shapes are unchanged.
+
+## 1. Render Initial Calendar Prices Directly
+
+For v9, `getInitialAvailability` can now return a non-null `formattedPrice` on
+valid start dates:
+
+```ts
+const availability = await sdk.live.availability.getInitialAvailability(input);
+
+for (const [date, day] of Object.entries(availability.calendarDays)) {
+  renderCalendarDay({
+    date,
+    status: day.status,
+    price: day.formattedPrice,
+  });
+}
+```
+
+`formattedPrice` is already localized for the input locale and formatted in the
+unit's configured booking currency. Render it directly. Do not parse it for
+arithmetic and do not replace its currency based on site assumptions.
+
+The field remains `null` when:
+
+- the day cannot be used as a start date
+- the calendar marks the day unavailable
+- the v1 calendar supplies no numeric price
+- the unit currency is missing or cannot be loaded
+
+## 2. Account for the Unit-Currency Request
+
+When no successful unit lookup is cached, a v9 initial-availability call loads
+two resources:
+
+1. the v1 unit calendar
+2. the v1 unit record used to read its booking currency
+
+Successful unit responses are cached by unit ID for the lifetime of the SDK
+instance, including responses without a currency. Failed unit requests are not
+cached and are retried by later initial-availability calls. A failed currency
+request does not fail availability; calendar prices remain `null` instead.
+
+Update HTTP mocks, request-count assertions, and service-worker fixtures that
+previously expected only the calendar request.
+
+No additional config is required. The lookup uses the existing `v1ApiBaseUrl`
+and `apiKey`.
+
+## 3. Read Structured v9 Rooms
+
+When vOffice supplies `roomDetails`, v9 rentals can now contain `rooms`:
+
+```ts
+const rentals = await sdk.static.rentals.getRentals({ locale: "de-DE" });
+
+for (const rental of rentals) {
+  for (const room of rental.rooms ?? []) {
+    renderRoomHeading(room.type);
+    renderRoomAttributes(room.attributes ?? []);
+
+    for (const bed of room.beds ?? []) {
+      renderBed({
+        type: bed.type,
+        kind: bed.kind,
+        attributes: bed.attributes ?? [],
+      });
+    }
+  }
+}
+```
+
+Room types, bed types, bed kinds, and attributes are already localized. Render
+them directly rather than comparing their visible text.
+
+The v9 source supports these per-room Boolean attributes:
+
+- `hasPrivateBathroom`
+- `roomDarkeningOption`
+- `wardrobe`
+
+It supports these per-bed Boolean attributes:
+
+- `childrenOnly`
+- `extraLongBeds`
+- `openFootsection`
+- `raisedBeds`
+
+Translation overrides use the same stable keys as v10:
+
+```text
+Room.type.option.<TYPE>
+RoomAttributes.<attribute>.label
+Bed.type.option.<TYPE>
+Bed.kind.option.<KIND>
+Bed.<attribute>.label
+```
+
+`rooms` remains optional. Keep an absent array valid when vOffice has no
+structured room details or no usable room remains after validation.
+
+## 4. Treat Repeated Beds as Quantity
+
+The public room-bed shape has no `amount` property. From 2.17.0, the SDK expands
+the source amount:
+
+```ts
+// Source
+{ type: "ORDINARY", kind: "SINGLE", amount: 2 }
+
+// Public rooms[].beds
+[
+  { type: "Standard bed", kind: "Single bed" },
+  { type: "Standard bed", kind: "Single bed" },
+]
+```
+
+Each public entry represents one bed. Do not deduplicate entries merely because
+their type, kind, and attributes are identical.
+
+This behavior applies to both backends:
+
+- v9 expands `roomDetails[].beds[].amount`
+- v10 expands `rooms[].beds[].amount`
+
+The v10 change is delivered by `@v-office/sdk-core`. Refresh the lockfile when
+upgrading the website SDK so it resolves the coordinated core version shipped
+for 2.17.0.
+
+Invalid, missing, zero, negative, and fractional v9 amounts do not produce bed
+entries. Other usable rooms and beds remain available.
+
+## 5. Keep Unsupported v9 Room Fields Optional
+
+The v9 source does not provide every v10 room capability. In particular, public
+v9 rooms do not currently expose:
+
+- per-room descriptions
+- source `maxGuests`
+- a structured bed amount; source quantities are represented by repeated entries
+- room IDs or room-image associations
+- `roomSummary`
+
+Do not derive these values from translated room labels or property-description
+prose. Existing top-level `attributes` and `highlights` remain the supported
+display sources for aggregate v9 facts such as bedrooms, bathrooms, rooms, and
+sleeping accommodations.
+
+## 6. Update Snapshots and Complete-Object Assertions
+
+Update expectations that previously assumed:
+
+```ts
+day.formattedPrice === null;
+rental.rooms === undefined;
+room.beds?.length === sourceRoom.beds.length;
+```
+
+New valid behavior includes:
+
+```ts
+day.formattedPrice; // localized string on a priced, valid v9 start date
+rental.rooms; // localized structured v9 rooms when roomDetails exists
+room.beds?.length; // total expanded bed amount, not source record count
+```
+
+Keep both `formattedPrice: null` and missing `rooms` valid because they still
+represent legitimate backend data.
+
+## Required Consumer Work
+
+Applications that use only selected fields and ignore the new output require no
+code changes.
+
+Applications that render or snapshot these areas should:
+
+1. Render `formattedPrice` directly when non-null.
+2. Account for the first v9 initial-availability currency request in mocks.
+3. Render `rental.rooms` as optional structured content.
+4. Treat every `rooms[].beds` entry as one bed and avoid value-based
+   deduplication.
+5. Refresh the lockfile so v10 resolves the coordinated core release.
+6. Update complete-output fixtures and snapshots.
+
+## Recommended Verification
+
+1. Load v9 initial availability for a non-EUR rental and confirm the configured
+   currency is used.
+2. Confirm a missing or failed currency lookup keeps calendar prices `null`
+   without failing availability.
+3. Confirm unavailable, non-start, and price-less dates retain
+   `formattedPrice: null`.
+4. Call initial availability twice for the same rental and confirm a successful
+   unit response is reused; confirm a failed unit request is retried.
+5. Fetch v9 rentals with populated `roomDetails` in both supported locales.
+6. Confirm room and bed labels are localized.
+7. Confirm a source bed amount of two produces two public bed entries on v9 and
+   v10.
+8. Confirm incomplete v9 rooms do not remove other usable rooms or fail the
+   rental.
+9. Confirm rentals without structured source rooms still omit `rooms`.