@wix/himalaya-cli 0.915.0 → 0.916.0

package/dist/cli.mjs

@@ -50953,6 +50953,17 @@ var ServeCliClient = class {
   revoke(app, integrity2, unrevoke = false) {
     return this.request("control", "POST", `/v1/admin/${unrevoke ? "unrevoke" : "revoke"}`, { body: { app, integrity: integrity2 }, headers: this.ctrlHeaders() });
   }
+  /**
+   * Withdraw an app from the serve plane entirely (POST /v1/admin/release/remove).
+   *
+   * Distinct from `revoke`, and the difference matters: revoke is a reversible kill-switch on one
+   * bundle integrity, while this unpublishes the app — which for a template is what "remove it from
+   * the catalog" means. The admin portal's Templates → Manage brokered to this exact route; this is
+   * the same call without the portal in front of it.
+   */
+  removeRelease(app) {
+    return this.request("control", "POST", "/v1/admin/release/remove", { body: { app }, headers: this.ctrlHeaders() });
+  }
   /** Write-through an OTA app-config patch (POST /v1/admin/app-config). */
   setAppConfig(app, patch) {
     return this.request("control", "POST", "/v1/admin/app-config", { body: { app, patch }, headers: this.ctrlHeaders() });

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

@@ -80,6 +80,32 @@ traffic until its gateway route was deleted on 2026-09-05; it now 404s with no r
    ```
    Kill-switch a bad bundle: `himi-serve release revoke --app <app> --integrity <sri> --target bo --control-token "$TOK"`.
 
+### Curating templates
+
+A starter template is an app in the reserved `himi-template-<name>` namespace, so it is
+published and promoted like any other. Withdrawing one, or killing it, is addressed by
+**template name** rather than app id — that is what the catalog shows and what
+`himi init --template <name>` takes:
+
+```
+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
+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
+reserved namespace: a non-template id is refused, so this group cannot unpublish or
+kill-switch an ordinary app by mistake — use the `release` group for those.
+
+`remove` unpublishes the app; `revoke` is the reversible kill-switch, and it resolves the
+bundle integrities from the template's current release manifest so you never paste an SRI. A
+template with no current release, or a release with no bundles, is **refused** rather than
+reported as a successful revocation — a kill-switch that silently switched nothing off is the
+one failure mode worth being loud about.
+
 ### Registry visibility (public | unlisted)
 
 Whether `GET /v1/apps` (and so the **Himi Player picker**) lists the app is a per-app,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wix/himalaya-cli",
-  "version": "0.915.0",
+  "version": "0.916.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": "8246d43c3041d1387f510848f691ef7d023c0ac9b2a85d096947e112"
+  "falconPackageHash": "06722d722ae5e9aac6226d4368df1778666b7b83737f0c449a0af142"
 }