@tinkerlandai/indiana-sdk 0.6.3 → 0.7.0

package/CHANGELOG.md

@@ -2,9 +2,26 @@
 
 Release facts and artifact evidence: [SDK release ledger](../../docs/sdk-releases.md).
 
-## Unreleased — 0.6.3
+## Unreleased
 
-- Align JS, Python and Go SDK package versions at 0.6.3 and require matching source versions before publication. Keep HTTP protocol 0.6 and the existing public release artifacts unchanged.
+## 0.7.0 — 2026-10-23
+
+- Bundle the Funnel shell and shared renderer in iOS and Android; render independent Paywalls through the same SDK program.
+- Read reviewed Local Funnel and Paywall JSON from immutable CDN artifacts with scope, format, byte-length and SHA-256 checks. Keep personal data and commercial facts in authenticated APIs.
+- Separate presentation loading from Funnel command settlement and durable purchase recovery.
+- Use HTTP protocol 0.7 for the new Paywall delivery contract. Older 0.x protocols are refused before business execution.
+
+- Add the independent `@tinkerlandai/indiana-react-native` package and shared React Native core entry for Customer identity, holdings, entitlement checks and backend-mediated usage reporting.
+- Include SwiftPM and Maven distributions in the unified release, with generated native package versions and independent public installation checks.
+- Remove the live-page visual editor handshake: the `__indiana_visual_editor` query parameter no longer pauses page experiments. Visual changes are authored in the Console App page map.
+- Calculate Local Funnel segments (`evaluate_segment`) after `createFunnelClient().start()` and in the native WebView host. The packaged native shell has no network access; the Swift and Kotlin hosts read the public configuration it needs.
+- Give errors the SDK raises locally the `recovery` their message names instead of `contact_support`, for example `recover_operation` for `COMMAND_PENDING` and `DECISION_PENDING`, `reload_state` for `CONFIGURATION_EXPIRED` and `retry_same_request` for `EVENT_QUEUE_FULL`. Server error codes keep their recovery.
+
+## 0.6.3 — 2026-10-23
+
+- Align JS, Python and Go package versions at 0.6.3; retain HTTP protocol 0.6 and immutable earlier releases.
+- Bound optional persistent-cache reads and download the pinned Funnel and GB artifacts together, preserving the five-second initialization budget and artifact validation.
+- Wait for the original display acknowledgement to settle and read the current Run before processing the first action; retain the original request identity during recovery.
 
 ## 0.6.2 — 2026-10-22
 

package/README.md

@@ -2,23 +2,27 @@
 
 [简体中文](./README.zh-CN.md)
 
-Version **0.6.2 / protocol 0.6** requires a matching Indiana runtime and database. Remote Funnel responses contain the current page's `ScreenDocument` JSON; Local and Remote use the same renderer, canonical Run, business receipts and Queue recovery. Remote graphs and private rules stay on the server.
+Version **0.6.4 / protocol 0.6** requires a matching Indiana runtime and database. Remote Funnel responses contain the current page's `ScreenDocument` JSON; Local and Remote use the same renderer, canonical Run, business receipts and Queue recovery. Remote graphs and private rules stay on the server.
 
-Version 0.6.2 adds a shared deterministic hosted renderer shell and uses GitHub Actions with npm Trusted Publishing. It retains the 0.6.1 fixes for current-screen input patches, Local Feature dependency validation, original-command settlement during host polling and display acknowledgement recovery after Back. Complete production browser and Stripe acceptance remains separate; see the [repair report](../../docs/deployment-receipts/20261022-sdk-funnel-repair/README.md).
+Version 0.6.4 bounds optional persistent-cache reads, downloads the pinned Funnel and GB artifacts in parallel, and waits for the original display acknowledgement to settle before processing the first action. It preserves the five-second initialization budget, artifact verification, current-screen input patches and recovery after Back. Publication uses GitHub Actions with npm Trusted Publishing. Complete production browser and Stripe acceptance remains separate; see the [repair report](../../docs/deployment-receipts/20261022-sdk-funnel-repair/README.md).
 
 Pin this package to a matching protocol 0.6 service. The published npm 0.6.0 package passes 21 foundation operations through `https://api.dev.tinker.cash`, with readiness 200 and correlated Go request logs; remaining capabilities and production business dependencies have separate gates. npm publication does not extend that accepted scope. Actual publication, tags and environment state are recorded in the [release ledger](../../docs/sdk-releases.md).
 
 ```sh
-npm install --save-exact @tinkerlandai/indiana-sdk@0.6.2
+npm install --save-exact @tinkerlandai/indiana-sdk@0.6.4
 ```
 
 Indiana's JavaScript and TypeScript SDK supports browsers, Node.js, screen rendering and optional AI usage integrations. Environment collection controls and existing Invoice/billing-window contracts remain available. Older 0.x protocols are rejected before business execution.
 
+## React Native core
+
+Use the independent `@tinkerlandai/indiana-react-native` package. The `@tinkerlandai/indiana-sdk/react-native` subpath shares the same implementation. Both support Customer Token identity, holdings, entitlement checks and usage reporting through your authenticated backend. It requires no DOM or native UI/store bridge. See [mobile SDK installation and examples](../../docs/mobile-sdk.md).
+
 ## Version compatibility and support
 
 During `0.x`, only the current protocol is supported. Starting with `1.0`, compatibility is preserved within each stable major version. Once the next stable major is published, the preceding stable major remains supported for at least 12 calendar months, with at least 180 days' public notice before retirement. The later deadline applies. See the [support policy](https://tinker.cash/docs/release-notes#support-policy).
 
-Version `0.6.2` sends protocol and SDK version headers and validates the protocol declared by successful responses. Headerless historical clients retain the fixed identity `0.2`; they do not follow the current protocol automatically. Updating source code does not change an existing npm artifact or deploy a server.
+Version `0.6.4` sends protocol and SDK version headers and validates the protocol declared by successful responses. Headerless historical clients retain the fixed identity `0.2`; they do not follow the current protocol automatically. Updating source code does not change an existing npm artifact or deploy a server.
 
 ## One package, seven entry points
 

package/README.zh-CN.md

@@ -2,6 +2,10 @@
 
 # @tinkerlandai/indiana-sdk
 
+## React Native 核心入口
+
+React Native 使用独立包 `@tinkerlandai/indiana-react-native`，原 `@tinkerlandai/indiana-sdk/react-native` 子入口共用同一实现。两者均支持 Customer Token 身份接入、权益读取和经业务后端转发的用量上报。此入口无需 DOM，不包含原生 UI 或内购桥接。参见[移动端 SDK 安装与示例](../../docs/mobile-sdk.md)。
+
 ## Funnel Local / Remote 统一执行
 
 Local / Remote 只区分纯条件、Feature / 实验和 Feature 选择在哪里计算。正式流程都使用 Indiana 的同一个 Run、command/action 回执、业务服务、幂等和 Queue 恢复。Local SDK 计算结果并提交固定节点命令，后端领取并执行发券、等待、重试；Remote 在 Indiana 计算。Remote 不依赖公共 CDN 初始化。
@@ -12,12 +16,12 @@ Local / Remote 只区分纯条件、Feature / 实验和 Feature 选择在哪里
 
 步骤记录共用后端限制；历史 `report_progress` 仍是调用方观察，不能当成发券证明。原生渲染壳复用同一个 JS 纯求值器及原生 Run bridge；无界面 Swift/Kotlin 会明确返回待本地求值，不自动切换 Remote。详细使用和迁移边界见[英文说明](README.md#local-funnel-execution)及统一回执。安装本包不会自动迁移数据库或部署服务；浏览器、支付渠道、容量和原生商店验收分别记录。
 
-本包版本为 **0.6.2／协议 0.6**，须配套同协议运行时和数据库。Remote Funnel 返回当前页面 JSON，与 Local 共用渲染器，完整 Remote 图和私有规则仍在服务端。公开 npm 0.6.0 已通过 `api.dev.tinker.cash` 的 21 项基础操作，foundation readiness 为 200；Funnel、公共配置、支付执行和生产业务仍有独立验收边界。实际发布、标签和环境状态见[SDK 发布总账](../../docs/sdk-releases.md)。
+本包版本为 **0.6.4／协议 0.6**，须配套同协议运行时和数据库。Remote Funnel 返回当前页面 JSON，与 Local 共用渲染器，完整 Remote 图和私有规则仍在服务端。公开 npm 0.6.0 已通过 `api.dev.tinker.cash` 的 21 项基础操作，foundation readiness 为 200；Funnel、公共配置、支付执行和生产业务仍有独立验收边界。实际发布、标签和环境状态见[SDK 发布总账](../../docs/sdk-releases.md)。
 
-0.6.2 增加共享的确定性托管渲染 shell，并通过 GitHub Actions 与 npm Trusted Publishing 发布；继续包含 0.6.1 的当前 Screen 输入 patch、Local Feature 依赖校验、host 轮询时原命令结算和 Back 后展示确认恢复修复。完整生产浏览器与 Stripe 验收分别记录，见[修复报告](../../docs/deployment-receipts/20261022-sdk-funnel-repair/README.md)。
+0.6.4 限制可选持久缓存的读取等待，并行读取固定的 Funnel／GB 产物，在原展示命令结算后再处理首次点击。保留五秒初始化预算、产物校验、当前 Screen 输入 patch 和 Back 后恢复，通过 GitHub Actions 与 npm Trusted Publishing 发布。完整生产浏览器与 Stripe 验收分别记录，见[修复报告](../../docs/deployment-receipts/20261022-sdk-funnel-repair/README.md)。
 
 ```sh
-npm install --save-exact @tinkerlandai/indiana-sdk@0.6.2
+npm install --save-exact @tinkerlandai/indiana-sdk@0.6.4
 ```
 
 ## 版本兼容与支持

package/THIRD_PARTY_NOTICES.md

@@ -71,3 +71,31 @@ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
+
+# whatwg-url-minimum 0.2.0
+
+Bundled URL implementation from https://github.com/expo/whatwg-url-minimum.
+
+MIT License
+
+Copyright (c) Phil Pluckthun,
+Copyright (c) 650 Industries, Inc. (aka Expo),
+Copyright (c) Sebastian Mayr
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.