@v-office/website-sdk 2.8.0 → 2.10.0

package/dist/cli.mjs

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

package/dist/{client-BNbBfJtO.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-Dzzra6IW.mjs"),
+	try: () => import("./search-QlZrI7ue.mjs"),
 	catch: (cause) => new CoreSDKError({
 		source: "v10",
 		operation: "v9.search.runtime",
@@ -5315,7 +5315,7 @@ const DEFAULT_RENTAL_FEEDBACK_DATA_ATTRIBUTES = [
 	"avgRating"
 ];
 const loadV9RentalsRuntime = Effect.tryPromise({
-	try: () => import("./rentals-cCejb_2d.mjs"),
+	try: () => import("./rentals-CFod9H4m.mjs"),
 	catch: (cause) => new CoreSDKError({
 		source: "v10",
 		operation: "v9.rentals.runtime",

package/dist/index.d.mts

@@ -22,7 +22,26 @@ type WebsiteSDKOptions = {
   readonly translationOverrides?: TranslationOverrides$1; /** The validated registry returned by `defineCustomAttributes`. */
   readonly customAttributes?: CustomAttributeRegistrySnapshot$1;
   readonly customAttributeFilterDefinitions?: readonly CustomAttributeFilterDefinition$1[];
+  /**
+   * Selects and orders rental highlights. This is an ordered allowlist, not a sort
+   * over every available fact.
+   *
+   * Only listed keys are emitted, even when an omitted key has a source value.
+   * `undefined` uses the SDK default; `[]` emits no rental highlights. Duplicate
+   * keys are emitted once, and unknown, unsupported, or unresolved keys are ignored.
+   * When multiple listed view facts have values, only the first is emitted. This
+   * affects `highlights` only, not `attributes` or `vicinity`.
+   */
   readonly rentalHighlightPrioritization?: readonly RentalHighlightPrioritizationKey$1[];
+  /**
+   * Selects and orders v10 property highlights. This is an ordered allowlist, not
+   * a sort over every available fact.
+   *
+   * Only listed keys are emitted, even when an omitted key has a source value.
+   * `undefined` uses the SDK default; `[]` emits no property highlights. Duplicate
+   * keys are emitted once, and unknown, unsupported, or unresolved keys are ignored.
+   * This affects `highlights` only, not `attributes` or `vicinity`.
+   */
   readonly rentalPropertyHighlightPrioritization?: readonly RentalPropertyHighlightPrioritizationKey$1[];
   readonly rentalScope?: RentalScope;
   readonly shouldAddProposedAdditionalServiceAmount?: boolean;

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-BNbBfJtO.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.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.
 - `versions/2.6.0/CHANGELOG.md`: compatibility note for an unreleased version label.

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.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.
 - `versions/2.6.0/MIGRATION.md`: compatibility note for an unreleased version label.

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.8.0. Package versions remain unchanged until the release
+`@v-office/website-sdk` 2.10.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,8 @@ 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.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.
 - `versions/2.6.0/`: compatibility pointers for the unreleased 2.6.0 version label.
@@ -74,4 +76,4 @@ 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.8.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.10.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/creation.md

@@ -101,12 +101,24 @@ type WebsiteSDKOptions = {
 };
 ```
 
+`rentalHighlightPrioritization` and `rentalPropertyHighlightPrioritization` select
+which facts become highlights and set their order. They are ordered allowlists, not
+sorts over every available fact. A key that is not listed is not emitted even when
+the source contains a value. This affects `highlights` only, not `attributes` or
+`vicinity`. Property highlights are available only with v10 property data.
+
+For either option, `undefined` uses the SDK default and `[]` emits no highlights.
+Duplicate keys are emitted once; unknown, unsupported, or unresolved keys are
+ignored. When several configured rental view facts have values, only the first one
+in the ordered allowlist is emitted. View-type descriptors qualify a view and are
+not part of this strongest-view selection.
+
 Unset options are normalized by the SDK:
 
 - `customAttributes` defaults to an empty registry.
 - `customAttributeFilterDefinitions` defaults to `[]`.
-- `rentalHighlightPrioritization` defaults to the SDK default rental highlight order.
-- `rentalPropertyHighlightPrioritization` defaults to the SDK default property highlight order.
+- `rentalHighlightPrioritization` defaults to the SDK default rental highlight selection.
+- `rentalPropertyHighlightPrioritization` defaults to the SDK default property highlight selection.
 - `rentalScope` defaults to `{}`.
 - `shouldAddProposedAdditionalServiceAmount` defaults to `false`.
 - `translationOverrides` is omitted unless provided.
@@ -194,6 +206,9 @@ Supported sources:
   active backend, and no generated leaf is committed unless all leaves are valid.
   Nested compositions are rejected while recursive expansion is unsupported.
 
+For a new v9 `backendFilter` key, ask someone at be-on! with Hub access to add or
+confirm the backend filter before configuring it in the SDK.
+
 Exposure:
 
 - `internal: false` exposes searchable filters through `static.filter.getFilters(...)`.

package/dist/instructions/custom-attributes.md

@@ -279,7 +279,7 @@ them, so an advertised bound always round-trips.
 ## Highlights and Attributes
 
 A custom attribute appears in `highlights` only when its key is listed in
-`rentalHighlightPrioritization`, which owns order:
+`rentalHighlightPrioritization`, which is the ordered allowlist:
 
 ```ts
 const options = defineWebsiteSDKOptions({
@@ -382,6 +382,10 @@ These are **not** custom attributes and stay in `customAttributeFilterDefinition
   filters. Advertised only when every configured leaf can execute on the active
   backend with its configured value.
 
+Compositions may reference stable v9 built-ins directly; `backendFilter` is only for
+additional v9 keys. SDK configuration does not create those keys in Hub; ask someone
+at be-on! with Hub access to add or confirm the filter before configuring it.
+
 ```ts
 const options = defineWebsiteSDKOptions({
   customAttributes,

package/dist/instructions/filter.md

@@ -93,6 +93,14 @@ Filter variants:
 }
 ```
 
+v9 has a fixed built-in filter set. These filters are always advertised, parsed,
+and usable as composition leaves; do not repeat them as `backendFilter` definitions.
+
+- Numeric: `bedrooms`, `bathrooms`.
+- Boolean: `pool`, `wifi`, `pets`, `privateparking`, `ac`, `washer`, `dishwasher`,
+  `beachfront`, `seaview`, `balcony`, `terrace`, `garden`, `bbq`, `sauna`,
+  `fireplace`, `tv`, `childrenWelcome`, `nonsmoking`, `kitchen`.
+
 `v10` config:
 
 ```json
@@ -111,7 +119,10 @@ Custom attributes come from `customAttributes`, and a definition is advertised o
 when it has a public filter and the selected backend can execute it. v9 has no
 custom-attribute search path, so v9 never advertises one; see `custom-attributes.md`.
 
-Backend filters and compositions come from `customAttributeFilterDefinitions`:
+Backend filters and compositions come from `customAttributeFilterDefinitions`.
+SDK configuration cannot create a Hub filter: for another v9 key, first ask someone
+at be-on! with Hub access to add or confirm it, then configure that key as a
+`backendFilter`.
 
 ```json
 {

package/dist/instructions/rentals.md

@@ -167,7 +167,24 @@ Optional `WebsiteSDKOptions`:
 }
 ```
 
-`rentalHighlightPrioritization` controls the order of rental `highlights`. `rentalPropertyHighlightPrioritization` controls property highlights for v10 property data. Translation overrides affect localized labels.
+`rentalHighlightPrioritization` selects which facts become rental `highlights` and
+sets their order. It is an ordered allowlist, not a sort over every available fact.
+A key that is not listed is not emitted even when the source contains a value.
+`rentalPropertyHighlightPrioritization` has the same semantics for v10 property
+highlights. Both options affect `highlights` only, not `attributes` or `vicinity`.
+
+For either option, `undefined` uses the SDK default and `[]` emits no highlights.
+Duplicate keys are emitted once; unknown, unsupported, or unresolved keys are
+ignored. When several configured rental view facts have values, only the first one
+in the ordered allowlist is emitted. View-type descriptors qualify a view and are
+not part of this strongest-view selection. Translation overrides affect localized
+labels.
+
+The active defaults are exported as
+`DEFAULT_RENTAL_HIGHLIGHT_PRIORITIZATION` and
+`DEFAULT_RENTAL_PROPERTY_HIGHLIGHT_PRIORITIZATION` from
+`@v-office/sdk-core`. See `versions/2.9.0/CHANGELOG.md` for the release notes and
+`versions/2.9.0/MIGRATION.md` for the complete default lists and upgrade checks.
 
 In CLI JSON, `customAttributes` contains catalog and selection inputs; the CLI builds
 the validated registry. Typed applications normally call `defineCustomAttributes`

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.9.0/CHANGELOG.md

@@ -0,0 +1,37 @@
+# Changelog: 2.9.0
+
+This release makes highlight selection explicit, improves the default rental and
+property rankings across coastal, lake, and mountain portfolios, and removes
+duplicate rental views.
+
+## Changed
+
+- `rentalHighlightPrioritization` and
+  `rentalPropertyHighlightPrioritization` are documented as ordered allowlists,
+  not sorts over every available fact. A key that is not listed is not emitted as
+  a highlight even when the source contains a value.
+- The default rental allowlist now starts with capacity and size, moves distinctive
+  views and facilities ahead of common fittings, places `youthgroups` last, and
+  includes previously omitted terrain-specific and practical facts.
+- `outdoorPool`, `indoorPool`, lake, mountain, countryside, river, and secondary
+  views can now appear through the default rental highlights, alongside facilities
+  such as `spa`, `terrace`, `lift`, `garage`, `dryer`, and `skiBootWarmer`.
+- The default v10 property allowlist now prioritizes beach location and shared
+  facilities ahead of utilities. It also includes `locLake`, `lakedistance`,
+  `locMountain`, and `skidistance`.
+- Rental highlights now emit only the first configured view fact that has a value.
+  The configured order defines which view is strongest. View-type descriptors such
+  as `seaviewType` remain independent qualifiers.
+- Strongest-view selection applies consistently to v10 and legacy v9 rental
+  highlights. Keys unsupported by the active backend remain ignored.
+
+## Migration Impact
+
+- Sites using the SDK defaults may receive a different highlight order and more
+  highlight values.
+- Sites that displayed several simultaneous rental views now receive at most one
+  view highlight.
+- Explicit custom allowlists retain their configured order and membership, apart
+  from the new strongest-view rule.
+- No SDK construction, service-call, or output-type changes are required. Review
+  `versions/2.9.0/MIGRATION.md` before upgrading.

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

@@ -0,0 +1,153 @@
+# Migration: 2.8.0 to 2.9.0
+
+2.9.0 changes default highlight membership and order and emits at most one rental
+view highlight. Configuration and output types are unchanged.
+
+## 1. Treat Highlight Configuration as an Ordered Allowlist
+
+`rentalHighlightPrioritization` and
+`rentalPropertyHighlightPrioritization` select which facts become highlights and
+set their order. They do not sort a complete list generated elsewhere.
+
+- An omitted key is not emitted even when the source contains a value.
+- `undefined` uses the SDK default.
+- `[]` emits no highlights.
+- Duplicate keys are evaluated once.
+- Unknown, unresolved, or backend-unsupported keys are ignored.
+- These options affect `highlights`, not `attributes` or `vicinity`.
+
+Audit custom lists that were shortened only to express a preferred order. Add every
+fact that must remain eligible for highlight output.
+
+## 2. Review the New Rental Default
+
+The default rental allowlist is now:
+
+```ts
+[
+  "maxPersons",
+  "bedrooms",
+  "squareMeters",
+  "bathrooms",
+  "seaview",
+  "lakeview",
+  "mountainview",
+  "valleyView",
+  "countrysideView",
+  "riverView",
+  "outdoorPool",
+  "indoorPool",
+  "sauna",
+  "spa",
+  "whirlpool",
+  "balcony",
+  "terrace",
+  "garden",
+  "beachChair",
+  "landingStage",
+  "boatBerth",
+  "skiBootWarmer",
+  "detached",
+  "fireplace",
+  "bbq",
+  "gym",
+  "closedPlot",
+  "beachview",
+  "gardenView",
+  "poolView",
+  "cityView",
+  "quietStreetView",
+  "innerCourtView",
+  "washer",
+  "dryer",
+  "privateparking",
+  "garage",
+  "carport",
+  "wifi",
+  "lift",
+  "childrenWelcome",
+  "nonsmoking",
+  "kitchen",
+  "dishwasher",
+  "tv",
+  "ac",
+  "heating",
+  "fridge",
+  "microwave",
+  "oven",
+  "stove",
+  "coffeemaker",
+  "freezer",
+  "electricKettle",
+  "youthgroups",
+];
+```
+
+Capacity and size come first, followed by distinctive views, facilities, outdoor
+space, terrain-specific draws, practical confirmers, common fittings, and finally
+the minority booking rule `youthgroups`.
+
+## 3. Review the New Property Default
+
+Property highlights apply only to v10 property data. Their default allowlist is:
+
+```ts
+[
+  "beachfront",
+  "beachaccess",
+  "beachdistance",
+  "seadistance",
+  "locBeach",
+  "locLake",
+  "lakedistance",
+  "locMountain",
+  "skidistance",
+  "outdoorPool",
+  "indoorPool",
+  "garden",
+  "terrace",
+  "bbqFacilities",
+  "playground",
+  "pool4kids",
+  "familyRoomsAvailable",
+  "parking",
+  "wifi",
+  "washer",
+  "dryer",
+  "ac",
+  "heating",
+  "locGroceries",
+  "restaurantdistance",
+  "publictransportdistance",
+];
+```
+
+Location and terrain now precede shared facilities, family signals, utilities, and
+secondary map facts.
+
+## 4. Expect One Rental View Highlight
+
+When several configured view facts have values, only the first one in
+`rentalHighlightPrioritization` is emitted:
+
+```ts
+rentalHighlightPrioritization: ["mountainview", "lakeview", "seaview", "gardenView", "wifi"];
+```
+
+For this configuration, a rental with both mountain and lake views emits only the
+mountain view. If `mountainview` has no value, the lake view can emit instead.
+View-type descriptors such as `mountainviewType` and `seaviewType` qualify a view
+and do not compete for the single view slot.
+
+The rule applies to v10 and legacy v9. An unsupported v9 view key does not prevent
+a later supported view from being emitted.
+
+## Recommended Verification
+
+1. Check search cards and rental pages that truncate highlights.
+2. Compare coastal, lake, and mountain workspaces against the new defaults.
+3. Confirm capacity and size remain available to consumers that read them from
+   search highlights.
+4. Verify rentals with cumulative view facts emit the expected first configured
+   view.
+5. Review explicit custom allowlists for facts that were unintentionally omitted.

package/dist/{rentals-cCejb_2d.mjs → rentals-CFod9H4m.mjs}

@@ -1,4 +1,4 @@
-import { c as VofficeUnitDataFieldSchemas, d as VofficeUnitDataPropertyMetadata, f as parseVofficeFacilityData, i as toLocalizedString, l as VofficeUnitDataPropertyCategoryLabelKeys, m as parseVofficeUnitData, n as toImages, o as rentalsAllFeedbacksQuery, p as parseVofficeFeedbackData, r as toAddress, s as rentalsAllWithoutFeedbacksQuery, t as toRentalHighlights, u as VofficeUnitDataPropertyCategoryValues } from "./to-rental-highlights-OvNe9ZQS.mjs";
+import { c as VofficeUnitDataFieldSchemas, d as VofficeUnitDataPropertyMetadata, f as parseVofficeFacilityData, i as toLocalizedString, l as VofficeUnitDataPropertyCategoryLabelKeys, m as parseVofficeUnitData, n as toImages, o as rentalsAllFeedbacksQuery, p as parseVofficeFeedbackData, r as toAddress, s as rentalsAllWithoutFeedbacksQuery, t as toRentalHighlights, u as VofficeUnitDataPropertyCategoryValues } from "./to-rental-highlights-B6a_fi0j.mjs";
 import { makeTranslate, renderLabeledAttributeValue, renderResolvedCustomAttribute, toCustomAttributeList, toResolvedCustomAttributeCategoryTranslationKey } from "@v-office/sdk-core";
 import { Effect } from "effect";
 //#region src/legacy-v9/parser/rentals/to-description.ts

package/dist/{search-Dzzra6IW.mjs → search-QlZrI7ue.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-BNbBfJtO.mjs";
-import { a as searchQuery, c as VofficeUnitDataFieldSchemas, m as parseVofficeUnitData, n as toImages, r as toAddress, t as toRentalHighlights } from "./to-rental-highlights-OvNe9ZQS.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";
 //#region src/legacy-v9/parser/search/input/search-input-error.ts

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

@@ -5870,12 +5870,29 @@ const toV9RentalHighlightKey = (key) => {
 };
 //#endregion
 //#region src/legacy-v9/parser/rentals/to-rental-highlights.ts
+const RENTAL_VIEW_HIGHLIGHT_KEYS = /* @__PURE__ */ new Set([
+	"beachview",
+	"cityView",
+	"countrysideView",
+	"gardenView",
+	"innerCourtView",
+	"lakeview",
+	"mountainview",
+	"poolView",
+	"quietStreetView",
+	"riverView",
+	"seaview",
+	"valleyView"
+]);
 const toRentalHighlights = ({ locale, translations, highlightPrioritization, customAttributes, attributes }) => Effect.gen(function* () {
 	const highlights = [];
 	const seenKeys = /* @__PURE__ */ new Set();
 	const knownAttributes = attributes.known;
 	const translate = makeTranslate(translations, locale);
+	let hasViewHighlight = false;
 	for (const highlightKey of highlightPrioritization) {
+		const isViewHighlight = RENTAL_VIEW_HIGHLIGHT_KEYS.has(highlightKey);
+		if (isViewHighlight && hasViewHighlight) continue;
 		const v9Key = toV9RentalHighlightKey(highlightKey);
 		if (v9Key == null) {
 			if (seenKeys.has(highlightKey)) continue;
@@ -5888,7 +5905,10 @@ const toRentalHighlights = ({ locale, translations, highlightPrioritization, cus
 				locale,
 				value: binding === void 0 ? void 0 : knownAttributes[binding] ?? attributes.unknown[binding]
 			});
-			if (highlight != null) highlights.push(highlight);
+			if (highlight != null) {
+				highlights.push(highlight);
+				if (isViewHighlight) hasViewHighlight = true;
+			}
 			continue;
 		}
 		if (seenKeys.has(v9Key)) continue;
@@ -5900,7 +5920,10 @@ const toRentalHighlights = ({ locale, translations, highlightPrioritization, cus
 			locale,
 			value: knownAttributes[v9Key]
 		});
-		if (highlight != null) highlights.push(highlight);
+		if (highlight != null) {
+			highlights.push(highlight);
+			if (isViewHighlight) hasViewHighlight = true;
+		}
 	}
 	return highlights;
 });

package/instructions/CHANGELOG.md

@@ -4,6 +4,8 @@ This file is the versioned changelog index for the website SDK instructions.
 
 ## Versions
 
+- `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.
 - `versions/2.6.0/CHANGELOG.md`: compatibility note for an unreleased version label.

package/instructions/MIGRATION.md

@@ -4,6 +4,8 @@ This file is the versioned migration index for the website SDK instructions.
 
 ## Available Guides
 
+- `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.
 - `versions/2.6.0/MIGRATION.md`: compatibility note for an unreleased version label.

package/instructions/README.md

@@ -1,7 +1,7 @@
 # Website SDK Instructions
 
 These instructions describe the current source targeted for
-`@v-office/website-sdk` 2.8.0. Package versions remain unchanged until the release
+`@v-office/website-sdk` 2.10.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,8 @@ 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.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.
 - `versions/2.6.0/`: compatibility pointers for the unreleased 2.6.0 version label.
@@ -74,4 +76,4 @@ 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.8.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.10.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/creation.md

@@ -101,12 +101,24 @@ type WebsiteSDKOptions = {
 };
 ```
 
+`rentalHighlightPrioritization` and `rentalPropertyHighlightPrioritization` select
+which facts become highlights and set their order. They are ordered allowlists, not
+sorts over every available fact. A key that is not listed is not emitted even when
+the source contains a value. This affects `highlights` only, not `attributes` or
+`vicinity`. Property highlights are available only with v10 property data.
+
+For either option, `undefined` uses the SDK default and `[]` emits no highlights.
+Duplicate keys are emitted once; unknown, unsupported, or unresolved keys are
+ignored. When several configured rental view facts have values, only the first one
+in the ordered allowlist is emitted. View-type descriptors qualify a view and are
+not part of this strongest-view selection.
+
 Unset options are normalized by the SDK:
 
 - `customAttributes` defaults to an empty registry.
 - `customAttributeFilterDefinitions` defaults to `[]`.
-- `rentalHighlightPrioritization` defaults to the SDK default rental highlight order.
-- `rentalPropertyHighlightPrioritization` defaults to the SDK default property highlight order.
+- `rentalHighlightPrioritization` defaults to the SDK default rental highlight selection.
+- `rentalPropertyHighlightPrioritization` defaults to the SDK default property highlight selection.
 - `rentalScope` defaults to `{}`.
 - `shouldAddProposedAdditionalServiceAmount` defaults to `false`.
 - `translationOverrides` is omitted unless provided.
@@ -194,6 +206,9 @@ Supported sources:
   active backend, and no generated leaf is committed unless all leaves are valid.
   Nested compositions are rejected while recursive expansion is unsupported.
 
+For a new v9 `backendFilter` key, ask someone at be-on! with Hub access to add or
+confirm the backend filter before configuring it in the SDK.
+
 Exposure:
 
 - `internal: false` exposes searchable filters through `static.filter.getFilters(...)`.

package/instructions/custom-attributes.md

@@ -279,7 +279,7 @@ them, so an advertised bound always round-trips.
 ## Highlights and Attributes
 
 A custom attribute appears in `highlights` only when its key is listed in
-`rentalHighlightPrioritization`, which owns order:
+`rentalHighlightPrioritization`, which is the ordered allowlist:
 
 ```ts
 const options = defineWebsiteSDKOptions({
@@ -382,6 +382,10 @@ These are **not** custom attributes and stay in `customAttributeFilterDefinition
   filters. Advertised only when every configured leaf can execute on the active
   backend with its configured value.
 
+Compositions may reference stable v9 built-ins directly; `backendFilter` is only for
+additional v9 keys. SDK configuration does not create those keys in Hub; ask someone
+at be-on! with Hub access to add or confirm the filter before configuring it.
+
 ```ts
 const options = defineWebsiteSDKOptions({
   customAttributes,

package/instructions/filter.md

@@ -93,6 +93,14 @@ Filter variants:
 }
 ```
 
+v9 has a fixed built-in filter set. These filters are always advertised, parsed,
+and usable as composition leaves; do not repeat them as `backendFilter` definitions.
+
+- Numeric: `bedrooms`, `bathrooms`.
+- Boolean: `pool`, `wifi`, `pets`, `privateparking`, `ac`, `washer`, `dishwasher`,
+  `beachfront`, `seaview`, `balcony`, `terrace`, `garden`, `bbq`, `sauna`,
+  `fireplace`, `tv`, `childrenWelcome`, `nonsmoking`, `kitchen`.
+
 `v10` config:
 
 ```json
@@ -111,7 +119,10 @@ Custom attributes come from `customAttributes`, and a definition is advertised o
 when it has a public filter and the selected backend can execute it. v9 has no
 custom-attribute search path, so v9 never advertises one; see `custom-attributes.md`.
 
-Backend filters and compositions come from `customAttributeFilterDefinitions`:
+Backend filters and compositions come from `customAttributeFilterDefinitions`.
+SDK configuration cannot create a Hub filter: for another v9 key, first ask someone
+at be-on! with Hub access to add or confirm it, then configure that key as a
+`backendFilter`.
 
 ```json
 {

package/instructions/rentals.md

@@ -167,7 +167,24 @@ Optional `WebsiteSDKOptions`:
 }
 ```
 
-`rentalHighlightPrioritization` controls the order of rental `highlights`. `rentalPropertyHighlightPrioritization` controls property highlights for v10 property data. Translation overrides affect localized labels.
+`rentalHighlightPrioritization` selects which facts become rental `highlights` and
+sets their order. It is an ordered allowlist, not a sort over every available fact.
+A key that is not listed is not emitted even when the source contains a value.
+`rentalPropertyHighlightPrioritization` has the same semantics for v10 property
+highlights. Both options affect `highlights` only, not `attributes` or `vicinity`.
+
+For either option, `undefined` uses the SDK default and `[]` emits no highlights.
+Duplicate keys are emitted once; unknown, unsupported, or unresolved keys are
+ignored. When several configured rental view facts have values, only the first one
+in the ordered allowlist is emitted. View-type descriptors qualify a view and are
+not part of this strongest-view selection. Translation overrides affect localized
+labels.
+
+The active defaults are exported as
+`DEFAULT_RENTAL_HIGHLIGHT_PRIORITIZATION` and
+`DEFAULT_RENTAL_PROPERTY_HIGHLIGHT_PRIORITIZATION` from
+`@v-office/sdk-core`. See `versions/2.9.0/CHANGELOG.md` for the release notes and
+`versions/2.9.0/MIGRATION.md` for the complete default lists and upgrade checks.
 
 In CLI JSON, `customAttributes` contains catalog and selection inputs; the CLI builds
 the validated registry. Typed applications normally call `defineCustomAttributes`

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.9.0/CHANGELOG.md

@@ -0,0 +1,37 @@
+# Changelog: 2.9.0
+
+This release makes highlight selection explicit, improves the default rental and
+property rankings across coastal, lake, and mountain portfolios, and removes
+duplicate rental views.
+
+## Changed
+
+- `rentalHighlightPrioritization` and
+  `rentalPropertyHighlightPrioritization` are documented as ordered allowlists,
+  not sorts over every available fact. A key that is not listed is not emitted as
+  a highlight even when the source contains a value.
+- The default rental allowlist now starts with capacity and size, moves distinctive
+  views and facilities ahead of common fittings, places `youthgroups` last, and
+  includes previously omitted terrain-specific and practical facts.
+- `outdoorPool`, `indoorPool`, lake, mountain, countryside, river, and secondary
+  views can now appear through the default rental highlights, alongside facilities
+  such as `spa`, `terrace`, `lift`, `garage`, `dryer`, and `skiBootWarmer`.
+- The default v10 property allowlist now prioritizes beach location and shared
+  facilities ahead of utilities. It also includes `locLake`, `lakedistance`,
+  `locMountain`, and `skidistance`.
+- Rental highlights now emit only the first configured view fact that has a value.
+  The configured order defines which view is strongest. View-type descriptors such
+  as `seaviewType` remain independent qualifiers.
+- Strongest-view selection applies consistently to v10 and legacy v9 rental
+  highlights. Keys unsupported by the active backend remain ignored.
+
+## Migration Impact
+
+- Sites using the SDK defaults may receive a different highlight order and more
+  highlight values.
+- Sites that displayed several simultaneous rental views now receive at most one
+  view highlight.
+- Explicit custom allowlists retain their configured order and membership, apart
+  from the new strongest-view rule.
+- No SDK construction, service-call, or output-type changes are required. Review
+  `versions/2.9.0/MIGRATION.md` before upgrading.

package/instructions/versions/2.9.0/MIGRATION.md

@@ -0,0 +1,153 @@
+# Migration: 2.8.0 to 2.9.0
+
+2.9.0 changes default highlight membership and order and emits at most one rental
+view highlight. Configuration and output types are unchanged.
+
+## 1. Treat Highlight Configuration as an Ordered Allowlist
+
+`rentalHighlightPrioritization` and
+`rentalPropertyHighlightPrioritization` select which facts become highlights and
+set their order. They do not sort a complete list generated elsewhere.
+
+- An omitted key is not emitted even when the source contains a value.
+- `undefined` uses the SDK default.
+- `[]` emits no highlights.
+- Duplicate keys are evaluated once.
+- Unknown, unresolved, or backend-unsupported keys are ignored.
+- These options affect `highlights`, not `attributes` or `vicinity`.
+
+Audit custom lists that were shortened only to express a preferred order. Add every
+fact that must remain eligible for highlight output.
+
+## 2. Review the New Rental Default
+
+The default rental allowlist is now:
+
+```ts
+[
+  "maxPersons",
+  "bedrooms",
+  "squareMeters",
+  "bathrooms",
+  "seaview",
+  "lakeview",
+  "mountainview",
+  "valleyView",
+  "countrysideView",
+  "riverView",
+  "outdoorPool",
+  "indoorPool",
+  "sauna",
+  "spa",
+  "whirlpool",
+  "balcony",
+  "terrace",
+  "garden",
+  "beachChair",
+  "landingStage",
+  "boatBerth",
+  "skiBootWarmer",
+  "detached",
+  "fireplace",
+  "bbq",
+  "gym",
+  "closedPlot",
+  "beachview",
+  "gardenView",
+  "poolView",
+  "cityView",
+  "quietStreetView",
+  "innerCourtView",
+  "washer",
+  "dryer",
+  "privateparking",
+  "garage",
+  "carport",
+  "wifi",
+  "lift",
+  "childrenWelcome",
+  "nonsmoking",
+  "kitchen",
+  "dishwasher",
+  "tv",
+  "ac",
+  "heating",
+  "fridge",
+  "microwave",
+  "oven",
+  "stove",
+  "coffeemaker",
+  "freezer",
+  "electricKettle",
+  "youthgroups",
+];
+```
+
+Capacity and size come first, followed by distinctive views, facilities, outdoor
+space, terrain-specific draws, practical confirmers, common fittings, and finally
+the minority booking rule `youthgroups`.
+
+## 3. Review the New Property Default
+
+Property highlights apply only to v10 property data. Their default allowlist is:
+
+```ts
+[
+  "beachfront",
+  "beachaccess",
+  "beachdistance",
+  "seadistance",
+  "locBeach",
+  "locLake",
+  "lakedistance",
+  "locMountain",
+  "skidistance",
+  "outdoorPool",
+  "indoorPool",
+  "garden",
+  "terrace",
+  "bbqFacilities",
+  "playground",
+  "pool4kids",
+  "familyRoomsAvailable",
+  "parking",
+  "wifi",
+  "washer",
+  "dryer",
+  "ac",
+  "heating",
+  "locGroceries",
+  "restaurantdistance",
+  "publictransportdistance",
+];
+```
+
+Location and terrain now precede shared facilities, family signals, utilities, and
+secondary map facts.
+
+## 4. Expect One Rental View Highlight
+
+When several configured view facts have values, only the first one in
+`rentalHighlightPrioritization` is emitted:
+
+```ts
+rentalHighlightPrioritization: ["mountainview", "lakeview", "seaview", "gardenView", "wifi"];
+```
+
+For this configuration, a rental with both mountain and lake views emits only the
+mountain view. If `mountainview` has no value, the lake view can emit instead.
+View-type descriptors such as `mountainviewType` and `seaviewType` qualify a view
+and do not compete for the single view slot.
+
+The rule applies to v10 and legacy v9. An unsupported v9 view key does not prevent
+a later supported view from being emitted.
+
+## Recommended Verification
+
+1. Check search cards and rental pages that truncate highlights.
+2. Compare coastal, lake, and mountain workspaces against the new defaults.
+3. Confirm capacity and size remain available to consumers that read them from
+   search highlights.
+4. Verify rentals with cumulative view facts emit the expected first configured
+   view.
+5. Review explicit custom allowlists for facts that were unintentionally omitted.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@v-office/website-sdk",
-  "version": "2.8.0",
+  "version": "2.10.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.8.0",
+    "@v-office/sdk-core": "^1.10.0",
     "effect": "4.0.0-beta.85",
     "graphql": "16.14.2",
     "yaml": "^2.9.0"