@tinkerlandai/indiana-sdk 0.4.0 → 0.5.0

package/CHANGELOG.md

@@ -4,8 +4,16 @@ Release facts and artifact evidence: [SDK release ledger](../../docs/sdk-release
 
 ## Unreleased
 
+## 0.5.0 — 2026-10-19
+
+- Use protocol 0.5 for billing-window `anchor` responses and `sourceKind: manual` Invoices. The anchor semantics come from pinned Autumn; the Invoice source classification is an Indiana response adaptation. Add Invoice management methods and current subscription invoice-mode/anchor inputs. Requires a matching server/database release; package publication does not promote production.
+
 - Separate remote Screen navigation (10 seconds), bridge handshake (5 seconds) and first render (5 seconds) startup budgets. Count visible time only, identify the timed-out phase and cancel timers/listeners on render or disposal. A slow valid document no longer consumes the bridge budget before it loads.
 
+## Distribution tags — 2026-10-19
+
+- Point `latest` to the existing `0.4.0`; retain `beta = 0.4.0`. Default npm installation now resolves 0.4.0. Package bytes, protocol, and runtime are unchanged; no package was republished.
+
 ## 0.4.0 — 2026-10-18
 
 - Use protocol 0.4 with environment-scoped behavior, experiment-exposure and Feature-usage collection policies. New required delivery and tracking acknowledgement fields require a matching service release.

package/README.md

@@ -2,21 +2,21 @@
 
 [简体中文](./README.zh-CN.md)
 
-Version `0.4.0` uses protocol `0.4` for environment analytics collection controls and requires a matching Indiana server and database deployment. It is distributed on the `beta` tag; the `latest` tag remains unchanged.
+Version `0.5.0` uses protocol `0.5`. It adds billing-window `anchor` responses, standalone Invoice classification (`sourceKind: manual`), Invoice management methods and current subscription invoice-mode/anchor inputs. The anchor name, values and billing semantics come from pinned Autumn; the Invoice source classification is an Indiana adaptation.
 
-Indiana's JavaScript and TypeScript SDK for browsers, Node.js, screen rendering, and optional AI usage integrations. Version `0.4.0` uses protocol `0.4` and requires a matching Indiana server and database deployment.
+Indiana's JavaScript and TypeScript SDK supports browsers, Node.js, screen rendering and optional AI usage integrations. This package requires a server and database implementing protocol `0.5`; publishing the SDK does not deploy them. For a server still advertising protocol `0.3`, use SDK `0.3.1`.
 
-Protocol `0.4` includes collection policy in Feature/page/visual delivery and `skipped` tracking acknowledgements. Disabled collection keeps existing history and does not change billable usage. SDKs cache the policy for 30 seconds; the database checks each batch. Older `0.x` clients, including requests without a protocol header, are rejected before business operations run.
+Environment collection controls introduced in protocol `0.4` remain available. Disabled collection keeps existing history and does not change billable usage. SDKs cache the policy for 30 seconds; the database checks each batch. Older `0.x` protocols are rejected before business operations.
 
 ```sh
-npm install @tinkerlandai/indiana-sdk@0.4.0
+npm install --save-exact @tinkerlandai/indiana-sdk@0.5.0
 ```
 
 ## 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.4.0` 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.5.0` 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
 
@@ -121,7 +121,7 @@ unsubscribe();
 flags.destroy();
 ```
 
-In the unpublished 0.4 candidate, the selected environment's integration settings control behavior events, experiment exposures and Feature usage independently. New environments enable only exposure collection; existing environments retain all three. `flush()` includes a `skipped` count for intentionally disabled collection. The database rechecks every batch, including direct SDK/server and Funnel ingestion. Running experiment/Bandit dependencies prevent incompatible collection changes. These controls do not delete history or affect commercial usage accounting.
+Since protocol 0.4, the selected environment's integration settings control behavior events, experiment exposures and Feature usage independently. New environments enable only exposure collection; existing environments retain all three. `flush()` includes a `skipped` count for intentionally disabled collection. The database rechecks every batch, including direct SDK/server and Funnel ingestion. Running experiment/Bandit dependencies prevent incompatible collection changes. These controls do not delete history or affect commercial usage accounting.
 
 Flags default to local evaluation; Owner/Admin can switch each flag to server evaluation. Server-evaluated flags deliver only keys and results, using the caller's fallback until the first result arrives. Attribute changes immediately discard old results. List hashes are not a secrecy boundary. Local Funnels cannot depend on server-evaluated flags; mode switches also check active historical Runs. `identify` / `reset` release the previous identity's Feature instances and event queue.
 

package/README.zh-CN.md

@@ -2,14 +2,14 @@
 
 # @tinkerlandai/indiana-sdk
 
-SDK `0.4.0` 使用协议 `0.4`，通过 `beta` 标签分发，`latest` 保持不变。服务端与数据库必须使用匹配的版本。
+SDK `0.5.0` 使用协议 `0.5`，新增用量窗口 `anchor` 返回字段、独立发票 `sourceKind: manual` 分类、Invoice 管理方法及订阅 invoice-mode／anchor 输入。anchor 的名称、取值与账期语义来自固定版本 Autumn；发票来源分类是 Indiana 的适配。
 
-当前环境的接入设置分别控制行为事件、实验曝光和 Feature 求值记录。新环境默认只开启实验曝光，已有环境保持三类全部开启。`flush()` 的 `skipped` 表示配置明确关闭的采集；SDK 将配置缓存 30 秒，数据库对每批再次检查。运行中的实验／Bandit 所需采集不能关闭。开关不删除历史，也不影响业务计费用量。
+Indiana 的 JavaScript／TypeScript SDK 支持浏览器、Node.js、屏幕渲染及可选 AI 用量集成。此版本需要实现协议 `0.5` 的匹配服务端和数据库；发布 SDK 不会部署服务。服务仍声明协议 `0.3` 时使用 SDK `0.3.1`。
 
-Indiana 的 JavaScript／TypeScript SDK，包含浏览器、Node.js、屏幕渲染与可选 AI 用量集成。0.x 服务只接受当前协议；旧 0.x 请求和固定为 0.2 的无版本头请求会在业务执行前被拒绝。
+协议 0.4 引入的环境采集控制继续保留。当前环境的接入设置分别控制行为事件、实验曝光和 Feature 求值记录。`flush()` 的 `skipped` 表示明确关闭的采集；SDK 缓存配置 30 秒，数据库对每批再次检查。开关不删除历史，也不影响业务计费用量。旧 0.x 协议会在业务执行前被拒绝。
 
 ```sh
-npm install @tinkerlandai/indiana-sdk@0.4.0
+npm install --save-exact @tinkerlandai/indiana-sdk@0.5.0
 ```
 
 ## 版本兼容与支持

package/THIRD_PARTY_NOTICES.md

@@ -45,7 +45,6 @@ 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.
 
-
 # dom-mutator 0.7.0
 
 GrowthBook declarative DOM mutations use the original `dom-mutator` package.