@wix/himalaya-cli 0.927.0 → 0.928.0

package/dist/cli.mjs

@@ -5241,6 +5241,7 @@ function resolveTranslation(value, catalog, sourceCatalog) {
 var BINDING_SIGILS, BINDING_SIGIL_RE, TRANSLATION_PREFIX, TRANSLATION_KEY_RE;
 var init_bindings = __esm({
   "../../core/ts/src/bindings.ts"() {
+    "use strict";
     BINDING_SIGILS = ["service", "flag", "item", "t"];
     BINDING_SIGIL_RE = new RegExp(
       `^\\$(?:${BINDING_SIGILS.filter((s) => s !== "t").join("|")})\\b|^\\$t:`
@@ -50995,6 +50996,15 @@ var ServeCliClient = class {
   //
   // The read is still the point of the pairing: it is the same handler and the same file the
   // write touched, which is what makes it able to contradict a 200.
+  /** The kill-list for an app (GET /v1/revocations?app=…) — the integrities devices refuse.
+   *
+   *  CONTROL, for the same reason `flags()` is: the route is serve-control's, and the process on
+   *  the local serve port answers it with a deliberate empty stub (core/serve/src/run-handler.ts
+   *  — "the kill-switch is INERT here"). Reading that would report every template as live,
+   *  including the ones somebody just killed, which is the one answer this must never give. */
+  revocations(app) {
+    return this.request("control", "GET", `/v1/revocations?app=${encodeURIComponent(app)}`);
+  }
   /** Flag definitions as the plane would serve them (GET /v1/flags/{app}). No credential. */
   flags(app) {
     return this.request("control", "GET", `/v1/flags/${encodeURIComponent(app)}`);

package/guides/releasing-with-himi-serve.md

@@ -88,12 +88,24 @@ published and promoted like any other. Withdrawing one, or killing it, is addres
 `himi init --template <name>` takes:
 
 ```
+himi-serve template list                       --target bo --control-token "$TOK"   # catalog + kill-state
+himi-serve template list     --revoked         --target bo --control-token "$TOK"   # only what is not fully live
 himi-serve template remove   --name <template> --target bo --control-token "$TOK"   # withdraw from the catalog
 himi-serve template revoke   --name <template> --target bo --control-token "$TOK"   # kill-switch its current release
 himi-serve template unrevoke --name <template> --target bo --control-token "$TOK"   # lift it again
 ```
 
-All three also take `--app <appId>` instead of `--name`. That exists for one case: a template
+**`list` is the read-back for the other three.** Nothing stores "this template is revoked" —
+`revoke` kills the bundle integrities of the catalog's release — so `list` derives it, reading
+each template's manifest and its app's `/v1/revocations` and comparing them. Each row reports
+`revoked` as `none`, `partial`, `all`, or `unknown` with the reason a read failed; `partial` is
+its own answer because `revoke` stops at the first failure, so a half-killed release is a state
+the plane really produces. **Any `unknown` row makes the command exit 1** (and `ok:false`, with
+an `unknown` count) — a script asking "is anything killed?" reads the exit code, and answering
+0 over rows it could not read would be the same silence-as-clean-bill this verb exists to stop. Before this verb existed neither the CLI nor the admin portal could
+tell you which templates were currently killed.
+
+The three WRITES also take `--app <appId>` instead of `--name`. That exists for one case: a template
 name may legally begin with `himi-template-` (the name pattern is lowercase alphanumerics and
 inner hyphens), and such a name publishes to a **doubly** prefixed app id — so `--name` cannot
 express it without becoming ambiguous. The CLI refuses the ambiguous form and points at `--app`. `--app` only accepts ids inside the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.927.0",
+  "version": "0.928.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": [
@@ -64,5 +64,5 @@
       "artifactId": "himalaya-cli"
     }
   },
-  "falconPackageHash": "5a9a78922aa072426bb6e4169693f0fdd84817367970c02f4e036483"
+  "falconPackageHash": "c7d75efc8f00421a7e0aea8773d9c1b0e968e2e7afcf8a4ae8bce93f"
 }