@tinkerlandai/longplay-sdk 0.10.18 → 0.10.19

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.10.19 — 2026-11-06
+
+- Restore explicit confirmation for the original unconfirmed Paywall quote after interruption or reload, retaining request identity and the existing recovery path for confirmed purchases.
+- Queue Paywall actions behind the settled Funnel display receipt. Repeated Subscribe clicks return to the existing confirmation, and busy transitions preserve disabled controls, including expired quotes.
+
+- Add `grantModelBenefit` and `readModelBenefit` for Server clients, merchant-prepared confirmation terms for Paywalls and the Merchant Bridge v4 protocol. **Not on production yet:** these calls need a Longplay runtime and database release that follows this SDK, so they fail until it ships. Existing calls are unaffected.
+- The Go SDK no longer carries unused streaming, polling and tracking code, and drops its `go-sse` dependency.
+
 ## 0.10.18 — 2026-11-06
 
 - Report a Funnel view that cannot start. On Android and iOS, `FunnelView` now calls `onError` when a Local Funnel cannot read its public configuration, instead of showing a blank screen. A brief service fault is retried up to three times before it is reported, and permanent refusals are not retried.

package/README.md

@@ -6,7 +6,7 @@
 
 # @tinkerlandai/longplay-sdk
 
-This source checkout is SDK 0.10.14, protocol 0.10. These examples use `https://api.longplayai.com` with a Sandbox App and credentials issued by the production deployment. Sandbox still contains production data; do not reuse credentials from the separate test deployment. Confirm runtime readiness in [environment state](../../docs/development-status.md) before running them.
+The SDK release version is the `version` field in [`package.json`](package.json); the wire protocol is 0.10. These examples use `https://api.longplayai.com` with a Sandbox App and credentials issued by the production deployment. Sandbox still contains production data; do not reuse credentials from the separate test deployment. Confirm runtime readiness in [environment state](../../docs/development-status.md) before running them.
 
 [简体中文](./README.zh-CN.md)
 
@@ -161,9 +161,9 @@ On Web, an independent first-party installation cookie can retain the signal. Cl
 
 ## Funnel, Feature, and standalone Paywall
 
-A trusted backend calls `createFunnelStartClient().start()` with `funnelId`, a retained `requestId`, `customer`, `locale`, and `parameters`. The Customer reference is `{ type: "id", value: customerId }` or `{ type: "externalUserId", value: verifiedUser.id }`. The latter supports creation-only `customerData` and requires `customers:write`; an existing Customer is not updated. The response includes `customerId`, which your backend can use to issue a Customer Session. Historical start-body `customerToken` and decision-body `customerId` inputs are rejected.
+A trusted backend calls `createFunnelStartClient().start()` with `funnelId`, a retained `requestId`, `customer`, `locale`, and `parameters`. The Customer reference is `{ type: "id", value: customerId }` or `{ type: "externalUserId", value: verifiedUser.id }`. The latter supports creation-only `customerData` and requires `customers:write`; an existing Customer is not updated. The response includes `customerId`, which your backend can use to issue a Customer Session. A Funnel that shows a Paywall requires `parameters.commerce` with `provider` and `currency`, for example `{ provider: "stripe", currency: "USD" }`; without it the start returns `INVALID_REQUEST` and creates no Run. Historical start-body `customerToken` and decision-body `customerId` inputs are rejected.
 
-`createFunnelClient({ customerToken, ...options })` is for clients that already hold a Customer credential. Its `start()` omits `customer` and `customerData` and runs as the credential's Customer. After response loss, retry with the same request ID and input. Put commercial parameters in `parameters.commerce`. Each Run has its own Run Token, which cannot switch Customer identity.
+`createFunnelClient({ customerToken, ...options })` is for clients that already hold a Customer credential. Its `start()` omits `customer` and `customerData` and runs as the credential's Customer. After response loss, retry with the same request ID and input. Each Run has its own Run Token, which cannot switch Customer identity.
 
 `createFunnelDecisionClient.submit/decide` and the server entry's `createFunnelCampaignClient` use the same explicit Customer reference. Campaign `decide()` waits for a `FunnelDecision`; a lookup can return the original accepted decision and its original request ID. Campaign `start()` returns either Run credentials or `{ suppressed: true, reason, retryAt }` when frequency or an active Run blocks a new start, without fabricating Run credentials. Report `shown` only after the Run is actually displayed; page closure or local storage cannot replace a durable presentation fact.
 
@@ -530,3 +530,9 @@ In `record_only` mode your backend owns payment execution, verifies its results
 The Server entry exports `createMerchantBridgeHandler`, `createMerchantBridgeAuthorityResolver`, `signMerchantBridgeMessage` and `verifyMerchantBridgeMessage`. Supply backend signing keys, native authorization/CSRF, implemented capabilities/profiles and typed handlers. Set `resolveOperationAuthority: createMerchantBridgeAuthorityResolver(server)` so every financial/read command obtains fresh Longplay authority from the original operation API. A signed service request still requires confirmation and exact scope/Customer ownership; it cannot issue user sessions.
 
 Handlers must durably reserve the original operation before external effects and retain the same provider idempotency key. The SDK's preceding lookup is not a concurrency lock. `operation.read` returns `found` or `not_received` without creating effects. Recover `RESULT_UNKNOWN` through that original operation; never infer permission from a browser quote or `pending`. Console discovery is configuration validation, not commercial completion. See the [merchant specification](https://www.longplayai.com/docs/guides/merchant-execution) for exact fields and recovery.
+
+### Merchant protocol v4 source
+
+The Server entry adds `createMerchantBridgeProtocol` for the explicit v4 T0 wire slice: signed discovery, `requirement.check` and `operation.prepare`. It encodes/validates bounded messages and correlates replies; it performs no HTTP, confirmation or native execution. Supply the scoped v4 Manifest and backend HMAC credentials. The Server entry also exports `merchantPreparationRequestDigest`, `merchantQuoteTermsDigest` and `entitlementRequirementDigest` so adapters use the same normalized digest rules. The signed, read-only preparation request carries the saved preparation authority and complete intent so the merchant can quote its original selection. Responses bind to that request, quote digest and validity; preparation never supplies user confirmation or execution authority. Prepared `subscriptionTerms` carries the merchant's recurring amounts, intervals and shared trial terms independently of the operation's money lines. Zero-charge subscription changes may have no money lines; full refunds ask the merchant for the remaining amount, while partial refunds preserve the explicitly chosen amount. These terms are covered by the same confirmation digest. The existing `createMerchantBridge` and receiver remain v3; there is no automatic protocol fallback.
+
+`checkEntitlement` remains the shared Customer/Server API for every payment provider. Its optional `observation` contains the authoritative subject, source, revision, observation time and complete requirement digest; v4 merchant checks require that group. Standalone and embedded Offering/Paywall/Funnel checks share the original-requirement validation; a requested embedded check must be present. Enriched responses are checked against the original requirement, and Paywall rechecks reject changed subject/authority/requirements or missing previously supplied observation metadata. Current runtime responses without observations remain readable. Business ownership selects authority; `commerce.provider` only selects purchase presentment. Shared quote responses and operation authority expose full `merchantTerms`; the Paywall confirmation presents the merchant charge, recurring/trial terms, expected effects and required consents. The [GOP runtime source](../../../Indianapolis/docs/sdk-runtime.md#merchant-execution-and-billing) owns quote preparation, confirmation and execution. SDK generation does not install SQL, update GOP’s pinned artifact or deploy a merchant adapter. See the [generic contract](../../docs/growth-integration.md#merchant-executed-orchestration).

package/README.zh-CN.md

@@ -6,7 +6,7 @@
 
 [English](./README.md)
 
-当前源码为 SDK 0.10.14、协议 0.10。本页示例使用 `https://api.longplayai.com` 以及生产部署内签发的 Sandbox App／凭据。Sandbox 仍属于生产数据，不能复用独立测试部署的凭据。运行前核对[环境状态](../../docs/development-status.md)，确认服务已就绪。
+SDK 版本以 [`package.json`](package.json) 的 `version` 字段为准，HTTP 协议为 0.10。本页示例使用 `https://api.longplayai.com` 以及生产部署内签发的 Sandbox App／凭据。Sandbox 仍属于生产数据，不能复用独立测试部署的凭据。运行前核对[环境状态](../../docs/development-status.md)，确认服务已就绪。
 
 # @tinkerlandai/longplay-sdk
 

package/dist/{ai-usage-D7BUuP1H.d.ts → ai-usage-DPGx5otD.d.ts}

@@ -1,5 +1,5 @@
 import { LanguageModelV4Usage, LanguageModelV4Middleware } from '@ai-sdk/provider';
-import { F as FoundationApi, A as ApiInput } from './api-CIbhe8RY.js';
+import { F as FoundationApi, A as ApiInput } from './api-G8EA_ueL.js';
 import { z } from 'zod';
 
 declare const tokenCounts: z.ZodObject<{
@@ -102,7 +102,7 @@ declare function createAiPricing(options?: AiPricingOptions): {
             originalId: string | null;
             quantity: string;
             accepted: boolean;
-            reason: "expired" | "unavailable" | "insufficient_balance" | "limit_exceeded" | "awaiting_topup" | "authorization_required" | "payment_blocked" | "cash_budget_exceeded" | null;
+            reason: "expired" | "insufficient_balance" | "limit_exceeded" | "awaiting_topup" | "authorization_required" | "payment_blocked" | "cash_budget_exceeded" | "unavailable" | null;
             createdAt: string;
             reservationStatus: "pending" | "expired" | "confirmed" | "released" | null;
             expiresAt: string | null;
@@ -173,7 +173,7 @@ declare function createConfiguredAiPricing(client: Pick<FoundationApi, "readAiPr
             originalId: string | null;
             quantity: string;
             accepted: boolean;
-            reason: "expired" | "unavailable" | "insufficient_balance" | "limit_exceeded" | "awaiting_topup" | "authorization_required" | "payment_blocked" | "cash_budget_exceeded" | null;
+            reason: "expired" | "insufficient_balance" | "limit_exceeded" | "awaiting_topup" | "authorization_required" | "payment_blocked" | "cash_budget_exceeded" | "unavailable" | null;
             createdAt: string;
             reservationStatus: "pending" | "expired" | "confirmed" | "released" | null;
             expiresAt: string | null;