@tinkerlandai/longplay-cli 0.3.19 → 0.3.20

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.3.20 — 2026-11-13
+
+- `longplay login` opens a browser page where you select several Apps, their Sandbox or Live environments and an access level, then approve the exact permissions. One login can cover several Apps; switch between them with `longplay context use`.
+- `longplay login --replace` logs the profile out and starts from its previous selection, so adding an App means selecting one more row.
+- The login result names each approved environment and gives the `longplay context use` command that selects it. The local context moves to an approved environment when the current one was not approved.
+- The selection page refuses a browser signed in to a different account from the one confirmed at sign-in and offers to switch.
+- Logins with `--permissions`, `--scope` or `--scopes-file` are unchanged.
+
 ## 0.3.19 — 2026-11-06
 
 - Publish through GitHub Actions Trusted Publishing, with the registry publisher identity verified before completing the release.

package/README.md

@@ -1,6 +1,6 @@
 # Longplay CLI
 
-Longplay CLI **0.3.19**, Node.js 22+. The executable is `longplay`. CLI versions are independent of the Customer SDKs.
+Longplay CLI **0.3.20**, Node.js 22+. The executable is `longplay`. CLI versions are independent of the Customer SDKs.
 
 Install the public npm package:
 
@@ -11,7 +11,7 @@ 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.19`. 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.20`. 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:
 
@@ -204,9 +204,11 @@ longplay projects list --profile work --json
 longplay logout --profile work
 ```
 
-Replace the host and UUIDs with the explicitly configured deployment and your authorized scope. `doctor` reads public metadata only, sends no credentials and refuses redirects. New login requires an available OAuth client, browser Code+PKCE approval and a selected Org/App/environment. The exact loopback callback remains `http://127.0.0.1:43187/callback`; port conflicts fail explicitly.
+Replace the host and UUIDs with the explicitly configured deployment and your authorized scope. `doctor` reads public metadata only, sends no credentials and refuses redirects. New login requires an available OAuth client and browser Code+PKCE approval; a login with explicit `--permissions` also requires a selected Org/App/environment. The exact loopback callback remains `http://127.0.0.1:43187/callback`; port conflicts fail explicitly.
 
-For resource commands, request only the necessary supported permissions with `login --permissions project.read,rewards.read`. Invalid, empty or duplicate permission entries are rejected before OAuth starts. Approval uses an immutable ordered scope list and does not widen the member's App allowlist or original role grants.
+`longplay login` opens a browser page where you select the Apps, Sandbox/Live environments and access level this device may use, then approve the exact permissions it lists. Several Apps can be approved in one login. The login result lists each approved environment with the `longplay context use` command that selects it; saving a context needs a project config (`longplay config init --server <origin>`) or a profile. To add or remove an App later, run `longplay login --replace`: it logs this profile out and starts from its previous selection.
+
+For scripts and narrowly scoped devices, request only the necessary supported permissions with `login --permissions project.read,rewards.read`. Invalid, empty or duplicate permission entries are rejected before OAuth starts. Approval uses an immutable ordered scope list and does not widen the member's App allowlist or original role grants.
 
 Scope priority is explicit flags → `longplay.config.json` → selected profile. Local selection remains `verified: false`. Profiles and credential storage bind to the exact management origin. Config files reject secrets and unknown fields; initialization never overwrites an existing file.
 

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

@@ -103,6 +103,7 @@ var localErrorRecovery = {
   HTTP_ERROR: "recover_operation",
   INVALID_RESPONSE: "recover_operation",
   NOT_IDENTIFIED: "authenticate",
+  CUSTOMER_SESSION_REQUIRED: "authenticate",
   INVALID_TOKEN: "authenticate",
   INVALID_URL: "fix_request",
   INVALID_TIMEOUT: "fix_request",
@@ -113,12 +114,17 @@ var localErrorRecovery = {
   EVENT_QUEUE_FULL: "retry_same_request",
   // The original command or decision still owns the outcome.
   COMMAND_PENDING: "recover_operation",
+  PURCHASE_PENDING: "recover_operation",
   DECISION_PENDING: "recover_operation",
   DECISION_ACCEPTANCE_UNKNOWN: "recover_operation",
   RUN_RECONCILIATION_REQUIRED: "recover_operation",
   DECISION_FAILED: "contact_support",
   COMMAND_STORAGE_CONFLICT: "resolve_conflict",
   COMMAND_STORAGE_INVALID: "fix_request",
+  PURCHASE_STORAGE_CONFLICT: "resolve_conflict",
+  // Missing purchase evidence cannot prove that the original attempt did not execute.
+  PURCHASE_STORAGE_INVALID: "recover_operation",
+  EXECUTION_POLICY_REFUSED: "fix_request",
   CONFIGURATION_UNAVAILABLE: "check_availability",
   CONFIGURATION_EXPIRED: "reload_state",
   CONFIGURATION_CHANGED: "reload_state",

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

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