@01.software/sdk 0.73.1 → 0.74.0

package/CHANGELOG.md

@@ -1,5 +1,44 @@
 # @01.software/sdk
 
+## 0.74.0
+
+### Minor Changes
+
+- a5ac520: **Additive response arm (0.x minor).** `cancelOrder()` already returned this body for an order paid entirely with customer credit; `CancelOrderResponse` now types it as `CancelOrderCreditOnlyCommittedResponse` (exported from `@01.software/sdk`): `cancelCommitted: true`, the restored purchase total as `refundedAmount`, `providerRefunded: false`, and no `transactionId` or `refundPending`. There is no PG refund to run. Runtime behavior is unchanged. Code that assumed a committed response without `transactionId` has `refundedAmount: 0`, or an exhaustive check over `CancelOrderResponse`, needs the new arm.
+- b01549e: Feature progress now supports `customers` and `community` in addition to `ecommerce`. `createServerClient().tenant.featureProgress({ feature })` returns the response for the requested feature (`TenantFeatureProgressResponseFor<F>`): the `ecommerce` response keeps `config.fulfillmentMode`, while `customers` and `community` responses have no `config`. `TenantFeatureProgressResponse` still names the ecommerce response and `TenantFeatureProgressInput` still defaults to `feature: 'ecommerce'`, so existing wrappers keep their types; use `TenantFeatureProgressInput<TenantFeatureProgressFeature>` and `TenantFeatureProgressResponseUnion` to handle every supported feature. `01 feature check customers|community` reports hosted customer sign-in and first public comment setup. Manual items still require an end-to-end check in the app.
+
+  BREAKING (0.x minor): `TenantFeatureProgressFeature` now also includes `'customers'` and `'community'`, so exhaustive handling of that type needs the new cases, and a hand-written `TenantIntrospectionClient` implementation must type `featureProgress` as generic over the requested feature.
+
+- 6b8a188: Feature progress now supports `events`. `createServerClient().tenant.featureProgress({ feature: 'events' })` and `01 feature check events` report whether the workspace event calendar is public and whether a scheduled, not-yet-ended occurrence accepts a free RSVP, plus a manual register, lookup, and cancel check. The check is read-only and does not evaluate remaining capacity or paid admission. The response has no `config`.
+
+  BREAKING (0.x minor): `TenantFeatureProgressFeature` now also includes `'events'`, so exhaustive handling of that type needs the new case.
+
+- f433dee: Feature progress now supports `membership`. `createServerClient().tenant.featureProgress({ feature: 'membership' })` and `01 feature check membership` report whether an active plan has an active price for new sign-ups, plus a manual sign-up, charge, renewal, and cancellation check. Apps that only read or cancel existing memberships can treat the sellable-plan item as optional. The response has no `config`, like `customers` and `community`.
+
+  BREAKING (0.x minor): `TenantFeatureProgressFeature` now also includes `'membership'`, so exhaustive handling of that type needs the new case.
+
+### Patch Changes
+
+- 6814052: Clarify generated Event location JSDoc about the public read visibility of stored online URLs and notes and the privacy of internal notes. Persisted location paths and public read behavior remain unchanged.
+- 65ed375: `Tenant` 생성 타입의 `defaultContentLocale` 설명 주석에 고객 메일도 이 언어로 발송한다는 내용이 추가됩니다. 타입 구조는 변경하지 않습니다.
+- eb457be: Regenerate Payload type documentation after clarifying guest-link expiry guidance in the Console Admin Panel. Only JSDoc changes; field types and API response shapes are unchanged.
+- e1c8158: Order variants by their fractional-indexing `_order` key (code-unit order, keyed before unkeyed; equal to the Admin Panel order for current-format `[0-9a-z]` keys) instead of a `Number()` conversion that turned every key into `NaN`, so listing-group representative variants and `fillDefaults` selections follow the Admin Panel variant order.
+- e0fcb45: Type `createServerClient().video` as non-optional so the documented `createServerClient(...).video.playback(id)` compiles under strict TypeScript without `?.` or `!`. The server client always sets `video` at runtime; `RootServerClient.video` stays optional for structural mocks. A hand-written mock typed as `RootServerClientWithEvents` (or a `withMarket()` stub returning it) now needs a `video` member.
+- 58f915b: `Customer`·`Product` 생성 타입에서 `customData` 속성의 선언 순서만 바뀝니다. 타입 구조는 변경하지 않습니다.
+- 0e826e1: Remove collection-level descriptions from the generated payload types; Console list screens no longer show collection descriptions.
+- 6dea486: Shorten or remove commerce field descriptions in the generated payload types to match the trimmed Console copy.
+- 8530c76: Align event and registration descriptions in the generated payload types with the Console public read terminology and clarify guest-token PII visibility under retention policies. Types and response shapes are unchanged.
+- 9c0c1d5: Point the generated `users.tenants` description at the renamed Settings > Workspace > Project destination.
+- 16b3229: Shorten or remove shared field descriptions (SEO, subtitle, summary, taxonomy, videos) in the generated payload types to match the trimmed Console copy.
+- a26270c: Keep internal profile record creation evidence out of public profile and profile-statistics types while synchronizing the generated storage schema. Ordinary API and GraphQL surfaces do not expose `recordCreatedAt`.
+- 1d52b00: Shorten or remove customer and membership field descriptions in the generated payload types to match the trimmed Console copy.
+- a16f609: Shorten or remove content, community and event field descriptions in the generated payload types to match the trimmed Console copy.
+- 4165ada: Add `voided` to the generated `MembershipUnappliedPaidEvidence.reason` values for late paid evidence on expired setup charges.
+- 27f0891: Shorten or remove workspace, settings and system field descriptions in the generated payload types to match the trimmed Console copy.
+- 5376b13: Fix product listing-page search requests to query title and slug only, avoiding HTTP 400 errors caused by querying the nonexistent Products handle field.
+- fb854bc: 생성 타입에서 입장 유형 `priceReference` 필드 설명 주석을 갱신한다. 런타임과 타입 시그니처 변경은 없다.
+- 809b7db: Clarify the generated Video viewCount documentation to reflect that views are not currently collected automatically. The type structure is unchanged.
+
 ## 0.73.1
 
 ### Patch Changes

package/README.md

@@ -472,6 +472,8 @@ addendum in `docs/decisions/0012-sdk-public-commerce-contract.md`.
 
 ### Product Listing Pages (PLP) — join-safe queries
 
+`search` trims surrounding whitespace and matches product `title` or `slug`.
+
 **Recommended path:** Use `commerce.product.listingPage()` (or
 `createQueryHooks(client).useProductListingPage()`) for greenfield storefront
 PLPs. It wraps the cacheable listing-groups query endpoint, keeps the raw
@@ -1660,9 +1662,24 @@ customer already owns returns `resolution: 'unchanged'` and writes nothing, so
 the revision you last observed stays valid for the next mutation. Because it
 writes nothing, such a merge does not count as Cart activity for stale-Cart
 cleanup.
+`carts.merge` rejects an unknown or wrong `guestCartToken`, or a Cart belonging to another
+customer or tenant, with the same `404/not_found` envelope without writes.
+The response does not reveal which case occurred. Branch on
+`reason`, and use `requestId` for support correlation rather than comparing error text.
 Treat a replayed Cart result as an operation receipt: never replace a newer
 cached Cart with a lower `revision`; retrieve when response ordering is unclear.
 
+A customer can have more than one active Cart, because `carts.create` always
+creates a new Cart. `carts.mine` returns the active Cart with the latest
+`createdAt`, and `carts.merge` merges a guest Cart into that same Cart. When
+`createdAt` is equal, the Cart with the higher `id` is chosen. Merging an active
+Cart the customer already owns returns that Cart `unchanged`, even when it is an
+older Cart.
+
+If the guest Cart's market differs from that chosen Cart, `carts.merge` returns
+`409 cart_market_mismatch`. It does not merge into an older Cart in the guest
+Cart's market instead.
+
 Shipping Checkout creation requires a request `shippingAddress` or a valid
 stored Cart address whenever any line has `requiresShipping !== false`.
 `recipientName`, `phone`, `postalCode`, `address`, and `detailAddress` must be nonblank after trimming. Otherwise,
@@ -1957,9 +1974,12 @@ Customer order reads remain available through
 The SDK root no longer exports raw generated `Order`, `Transaction`, `Cart`, or
 `CartItem` Payload documents. Use the canonical `PublicOrder` / `PublicCart`
 DTOs for storefront code and explicit server collection types only inside
-trusted operational code. Order cancellation no longer returns the deprecated
-inline provider-refund branch. `refundPending` is a local financial marker, not
-authority for caller provider I/O:
+trusted operational code. SDK types no longer include the retired inline
+provider-refund flow. An order whose cancellation started through that flow can
+still return `providerRefunded: true` with `refundSeq`, or an uncommitted body
+with `reconciliationRequired: true`. These bounded legacy bodies remain outside
+`CancelOrderResponse`. `refundPending` is a local financial marker, not authority
+for caller provider I/O:
 
 | Captured payment lane                                   | Provider refund owner        | `resolveCancelRefund`                                                               |
 | ------------------------------------------------------- | ---------------------------- | ----------------------------------------------------------------------------------- |
@@ -1982,6 +2002,13 @@ as a committed cancellation and never start a provider refund from your
 storefront or BFF. A retry reads or resumes the same Console refund. Registered
 PortOne and credit-funded managed orders still return the pending marker.
 
+For an order paid entirely with customer credit, `cancelOrder()` restores credit
+inside the cancel commit and returns `CancelOrderCreditOnlyCommittedResponse`:
+`cancelCommitted: true`, the positive restored purchase total as
+`refundedAmount`, and `providerRefunded: false`, with neither `transactionId`
+nor `refundPending`. There is no PG refund to run. A later domain retry uses the
+ordinary `alreadyCanceled` arm with the same `refundedAmount`.
+
 Managed ownership follows the captured Transaction's exact tenant-bound
 PaymentSession and historical registered account. Order/provider/environment
 drift remains Console-owned corruption. Unresolved or cross-tenant identity

package/dist/client.cjs

@@ -1386,6 +1386,10 @@ var EMBEDDED_ADMIN_ENDPOINT_OPERATIONS = {
   configure: operation("tenants", "patch", "/embedded-admin-app"),
   disable: operation("tenants", "delete", "/embedded-admin-app")
 };
+var FIELD_CONFIG_ENDPOINT_OPERATIONS = {
+  list: operation("field-configs", "get", "/list"),
+  save: operation("field-configs", "post", "/save")
+};
 var EVENTS_ENDPOINT_OPERATIONS = {
   registrations: {
     register: operation("event-registrations", "post", "/register"),
@@ -6223,10 +6227,13 @@ function buildProductHref(product, group, options = {}) {
   return params.size > 0 ? `${path}?${params.toString()}` : path;
 }
 function compareVariantOrder(a, b) {
-  const aOrder = Number(a._order ?? Number.MAX_SAFE_INTEGER);
-  const bOrder = Number(b._order ?? Number.MAX_SAFE_INTEGER);
-  if (Number.isFinite(aOrder) && Number.isFinite(bOrder) && aOrder !== bOrder) {
-    return aOrder - bOrder;
+  const aOrder = a._order || null;
+  const bOrder = b._order || null;
+  if (aOrder !== bOrder) {
+    if (aOrder === null) return 1;
+    if (bOrder === null) return -1;
+    const byOrder = compareOrdinal(aOrder, bOrder);
+    if (byOrder !== 0) return byOrder;
   }
   const aId = String(getRelationID(a.id) ?? "");
   const bId = String(getRelationID(b.id) ?? "");
@@ -6477,11 +6484,7 @@ function buildProductListingPageWhere(params) {
   const search = params.search?.trim();
   if (search) {
     clauses.push({
-      or: [
-        { title: { like: search } },
-        { slug: { like: search } },
-        { handle: { like: search } }
-      ]
+      or: [{ title: { like: search } }, { slug: { like: search } }]
     });
   }
   const filters = params.filters;