@tinkerlandai/longplay-cli 0.3.16 → 0.3.18

package/CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog
 
+## 0.3.18 — 2026-11-06
+
+- Update from `cdn.longplayai.com`. Installed CLIs on the website channel keep working after the public site and Console moved to their own hosts.
+- Use `https://console.longplayai.com` in setup and login examples, and name the new host when a management service has moved.
+
+## 0.3.17
+
+Install only the `longplay` command. The curl installer retires its owned `indiana` alias after a successful installation while preserving unrelated commands, configuration and credentials. Previously published packages and archives remain immutable.
+
 ## 0.3.16 — 2026-10-31
 
 - Use `@tinkerlandai/longplay-cli` and the `longplay` command for new installations. Retain the `indiana` alias, existing configuration, keychain sessions and website installation state; IAM tooling uses `@tinkerlandai/longplay-iam` and `longplay-iam` with its old alias retained.

package/README.md

@@ -1,27 +1,27 @@
 # Longplay CLI
 
-Longplay CLI **0.3.14**, Node.js 22+. The executable is `longplay`. CLI versions are independent of the Customer SDKs.
+Longplay CLI **0.3.18**, Node.js 22+. The executable is `longplay`. CLI versions are independent of the Customer SDKs.
 
 Install the public npm package:
 
 ```sh
 npm install -g @tinkerlandai/longplay-cli
 longplay --version
-longplay doctor --server https://longplayai.com --json
-longplay login --server https://longplayai.com
+longplay doctor --server https://console.longplayai.com --json
+longplay login --server https://console.longplayai.com
 ```
 
-For a reproducible installation, use `npm install -g @tinkerlandai/longplay-cli@0.3.16`. Uninstall with `npm uninstall -g @tinkerlandai/longplay-cli`. Node.js 22+ must be on PATH; the package includes the `longplay` command and npm installs its runtime dependencies.
+For a reproducible installation, use `npm install -g @tinkerlandai/longplay-cli@0.3.18`. Uninstall with `npm uninstall -g @tinkerlandai/longplay-cli`. Node.js 22+ must be on PATH; the package includes the `longplay` command and npm installs its runtime dependencies.
 
 The existing website installation channel remains available on macOS and Linux:
 
 ```sh
-curl -fsSL https://longplayai.com/install.sh | sh
+curl -fsSL https://cdn.longplayai.com/install.sh | sh
 ```
 
-That channel uses six platform archives with dependencies included (macOS arm64/x64; Linux arm64/x64 glibc/musl), verifies SHA-256 and installs without npm or sudo. It has its own published version in [the website manifest](https://longplayai.com/downloads/cli/latest.json); an npm release does not deploy a new website archive. Its recommended executable is `~/.local/bin/longplay`, with the legacy `~/.local/bin/indiana` alias, with releases under `~/.local/share/indiana/releases/`. Absolute `INDIANA_BIN_DIR` and `INDIANA_INSTALL_ROOT` overrides remain supported. Configuration and credentials are retained on upgrade.
+That channel uses six platform archives with dependencies included (macOS arm64/x64; Linux arm64/x64 glibc/musl), verifies SHA-256 and installs without npm or sudo. It has its own published version in [the website manifest](https://cdn.longplayai.com/downloads/cli/latest.json); an npm release does not deploy a new website archive. Its recommended executable is `~/.local/bin/longplay`, with releases under `~/.local/share/indiana/releases/`. Absolute `INDIANA_BIN_DIR` and `INDIANA_INSTALL_ROOT` overrides remain supported. Configuration and credentials are retained on upgrade.
 
-The recommended npm package is `@tinkerlandai/longplay-cli`, with executable `longplay`; `indiana` remains an alias. If the legacy npm package owns a global `indiana` command, uninstall `@tinkerlandai/indiana-cli` before installing the new package. Keep existing configuration and keychain entries; no new login is required by the rename. New package publication is separate from this source change.
+The public package is `@tinkerlandai/longplay-cli` and installs only `longplay`. Existing configuration and keychain entries retain their internal names. The curl installer removes a former managed `indiana` alias only after the verified Longplay installation succeeds and leaves unrelated commands untouched. Historical published packages and archives remain immutable.
 
 ## Updates
 
@@ -55,7 +55,7 @@ Implemented remote command surfaces include `login`, `whoami`, `auth status`, `l
 
 Customer/Feature/Product management and Offering/Paywall/Funnel authoring now have connected scoped operations. Scoped balances, usage, ledger, billing controls, analytics and Sandbox Stripe refunds also use the original Console handlers. Organization governance, experimentation administration, profile images and compatible integration configuration use explicit layered grants. The generated catalog records connected operations individually; App Manifest/consent scope remains unconnected, browser-only previews stay unavailable, and Apple/Google provider configuration and native Product bindings remain deferred. Inspect the operation catalog for exact availability; it does not certify every provider/business branch.
 
-Production OAuth and the scoped business slice are deployed at `https://longplayai.com`; `https://dev.longplayai.com` remains the separate Indiana-test deployment. Credentials and native OAuth clients are origin-bound and cannot be shared between them. See production acceptance for exact verified coverage and remaining gaps.
+The canonical Console targets are `https://console.longplayai.com` for Production and `https://console.dev.longplayai.com` for Indiana-test. Their OAuth registrations and deployment aliases must be cut over separately; source changes alone do not activate either host. Credentials and native OAuth clients are origin-bound and cannot be shared between environments.
 
 ## Layered consent
 
@@ -125,13 +125,13 @@ CLI **0.3.5** adds a CI surface using a dedicated App/environment API Key, indep
 In a Feature's **Code references** tab, configure a GitHub repository, target branches, workflow path, included/excluded paths and static function names. Create a Key with exactly `code-references:read` and `code-references:write`, bind it to that repository, and store its secret as `INDIANA_CODE_REFERENCES_KEY` in the merchant repository. The SDK setup dialog has a preset for these two permissions. No private-source access is granted to Longplay.
 
 ```sh
-longplay code-references scan --server https://dev.longplayai.com \
+longplay code-references scan --server https://console.dev.longplayai.com \
   --app <app-uuid> --env sandbox --repository-id <repository-uuid> \
   --branch main --workflow .github/workflows/indiana-code-references.yml \
   --run-number 12 --run-attempt 1 --root . --out /tmp/new-report.json --upload --json
 
 # Recover an uncertain write with the exact saved input, scan ID and run sequence.
-longplay code-references upload --server https://dev.longplayai.com \
+longplay code-references upload --server https://console.dev.longplayai.com \
   --app <app-uuid> --env sandbox --file /tmp/new-report.json --json
 ```
 

package/dist/{chunk-OQVCOXPB.js → chunk-IS7R5ZK7.js}

@@ -61,6 +61,9 @@ var errorReasonSchema = z.enum([
   "IDEMPOTENCY_CONFLICT",
   "RESULT_UNKNOWN",
   "STATE_CHANGED",
+  "IDENTITY_CONTEXT_CHANGED",
+  "CUSTOMER_BINDING_CONFLICT",
+  "RUN_CONTRACT_MISMATCH",
   "OPERATION_IN_PROGRESS",
   /** The pinned published Version uses a retired format and can no longer run; publish a new Version. */
   "FUNNEL_VERSION_RETIRED"

package/dist/{io-OQAM4AR6.js → io-UMZNM4IY.js}

@@ -1,7 +1,7 @@
 import {
   readJsonFile,
   readJsonStream
-} from "./chunk-OQVCOXPB.js";
+} from "./chunk-IS7R5ZK7.js";
 export {
   readJsonFile,
   readJsonStream