@wix/himalaya-cli 0.1350.0 → 0.1352.0

package/guides/himi-json-output.md

@@ -6,7 +6,7 @@ repurposed when human wording changes. New codes may be added; consumers must
 handle an unknown code as a failure, without parsing prose.
 
 **Rollout:** this contract is enforced for **`himi push`**, including `--only`,
-first, and for **`himi store iap connect`**. Other subcommands still have legacy failures without codes and are a
+first, for **`himi store iap connect`**, and for **`himi site member-app`**. Other subcommands still have legacy failures without codes and are a
 follow-up migration. This is an additive change: existing `error`, `errors`,
 `message`, `hint`, status, body, and gate-specific fields stay as they were.
 Some legacy envelopes have no singular `error` or `hint`; consumers must not
@@ -106,6 +106,31 @@ failure codes. A forced push still follows the existing override rules.
 | `config_not_applied` | `--content` was given, but the binding is not in its `config.ts` (no config file, a dynamic or symlinked config, an edit `himi validate` rolled back, or no validator); the `config` report or `note` says what to add by hand. |
 | `connect_failed` | An otherwise unclassified error stopped connect (for example an unreadable manifest, or a failed `--out` write). The original message is preserved. |
 
+## `himi site member-app` codes
+
+`himi site member-app set|clear|show <site>` prints one envelope. A refusal from the publishing service
+keeps the service's own `error` in `serverError` and its HTTP `status`; the CLI `code` is one of:
+
+| Code | Meaning |
+|---|---|
+| `invalid_usage` | Missing or malformed op, site id, `--app` or `--platform`. Nothing was sent. |
+| `insecure_target` | The target's control URL is not an https `wix.com` host (or loopback), so the Wix credential was neither minted nor sent. Nothing was sent. |
+| `control_token_required` | No control token for the target — run `himi login`. Nothing was sent. |
+| `wix_token_unavailable` | The account Wix token (`wix token`) could not be minted; the publishing service needs it to verify site ownership. Nothing was sent. |
+| `forbidden_site` | The publishing service could not verify that your account owns the site (403). |
+| `forbidden_app` | The app is not yours, or does not exist (403). Nothing was stored. |
+| `app_bound_to_other_site` | The app is another site's own app (403). |
+| `unauthorized` | The control token was refused or revoked (401). |
+| `control_unreachable` | The publishing service could not be reached. |
+| `request_failed` | Any other refusal; `status` and `serverError` say which. |
+
+`show` succeeds with `opens` (what members get: the picked app or `himi-branded-lite`), `compatible`
+(whether the picked release fits the Spaces host manifest, judged with `checkHostCompatibility`), and —
+whenever members get Branded Lite instead of the pick — `reason`. `opens` is Spaces' own decision, so a
+compatible pick that this Spaces build cannot host yet reports `compatible: true` with `opens:
+"himi-branded-lite"` and that reason. An incompatible pick is not a failure: it is `ok: true` with
+`compatible: false`.
+
 ## Follow-ups
 
 - Migrate failure envelopes in subcommands other than `push`, keeping this contract.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.1350.0",
+  "version": "0.1352.0",
   "type": "module",
   "description": "himi — the Himalaya authoring CLI. Build a Tier-5 content package on your own machine, push it to the production serve as a draft, preview it on web + Himi Player, and read worker logs back — the remote dev loop. Wraps @himalaya/serve-cli for transport.",
   "keywords": [
@@ -71,5 +71,5 @@
       "artifactId": "himalaya-cli"
     }
   },
-  "falconPackageHash": "d981bf37f0b886e4b2348f867e3514fb1f389475d9dfcd3857e8f87c"
+  "falconPackageHash": "3d6e10a135511ba6f09d842a8dd9aee9013e5b36a3f4d79fe5a3f266"
 }