@raizn/cli 0.1.0 → 0.1.1

package/README.md

@@ -25,12 +25,24 @@ useless to anyone else, because it needs a secret that never leaves this process
 lasts 90 days and appears in Settings → AI assistant connection (MCP) as "raizn CLI — <computer>",
 where you can revoke it.
 
+**macOS: `EACCES: permission denied` on `npm i -g`.** Node's installer makes the global folder
+belong to the system. Don't use `sudo`. Either run commands through `npx @raizn/cli …`, or point
+npm's global folder at your home directory once:
+
+```sh
+mkdir -p ~/.npm-global
+npm config set prefix ~/.npm-global
+echo 'export PATH="$HOME/.npm-global/bin:$PATH"' >> ~/.zshrc && source ~/.zshrc
+npm i -g @raizn/cli
+```
+
 No browser on this machine (a server over SSH)? Create a token by hand in that Settings page and run
 `raizn login --token`, or pipe it in with `echo "$TOKEN" | raizn login`.
 
 **Releasing a new version** (maintainers): bump `version` in `packages/cli/package.json` in a PR,
-merge it, then run the **Publish raizn CLI** workflow (GitHub → Actions). It needs the repository
-secret `NPM_TOKEN`: an npm granular access token with read-and-write access to the `@raizn` scope.
+merge it, then run the **Publish raizn CLI** workflow (GitHub → Actions). There is no npm token to
+manage: npm trusts that workflow in this repo directly (trusted publishing, set on npmjs.com →
+`@raizn/cli` → Settings).
 
 Either way, `login` checks the token with the server before saving it, and prints who you are, the
 stores the token can reach and its permissions. A token the server rejects is not saved.
@@ -65,7 +77,10 @@ raizn theme submit -m "Ramadan homepage"  # send for approval; prints the admin
   prints a diff (server vs yours) and exits 1. Merge the changes and push again, or use `--force`
   to overwrite the server's copy.
 - **preview** prints the signed preview link, and `--open` opens it in your browser.
-- **submit** refuses while you have unpushed changes. It prints the request id and
+- **submit** refuses while you have unpushed changes. For **Raizn's own team** (a member of the Raizn
+  organisation with a @raizn.net / @raizn.com email) the server approves and publishes it in the same
+  step: `submit` says the change is **LIVE** and prints the request link, where Rollback is one click.
+  Everyone else's request waits for someone with publish rights. It prints the request id and
   `https://ecom.raizn.com/themes/requests/<id>`.
 
 ### Custom sections
@@ -114,8 +129,8 @@ is never pulled for editing.
 
 ## What this can never do
 
-- Publish, unpublish or roll back a theme or a section. `raizn theme publish` explains that
-  publishing happens in the admin after approval.
+- Publish, unpublish or roll back a theme or a section on its own. `raizn theme publish` explains
+  that publishing happens in the admin after approval (or, for the Raizn team, on `submit`).
 - Write to the live theme. The server refuses it (`not_a_draft`), and the CLI refuses first.
 - Reach anything but the theme: no orders, customers, staff or payments.
 - Talk to any host but the configured API. `*.vercel.app` is refused (Jordanian ISPs reset those

package/dist/commands/theme.js

@@ -287,11 +287,20 @@ export async function themeSubmit(s, opts) {
     }
     const client = await s.client(state);
     const r = await submitForApproval(client, state.store, state.themeId, title, opts.description);
-    s.out(`Submitted "${state.themeName}" for approval: request ${r.requestId}`);
-    s.out(`Review it: ${apiOrigin(client.url)}/themes/requests/${encodeURIComponent(r.requestId)}`);
-    if (r.sections && r.sections.length > 0) {
-        s.out(`These custom sections will go live with this request when it is published: ${r.sections.map((x) => `${x.type} v${x.version}`).join(", ")}.`);
+    const link = `${apiOrigin(client.url)}/themes/requests/${encodeURIComponent(r.requestId)}`;
+    const sections = r.sections && r.sections.length > 0 ? r.sections.map((x) => `${x.type} v${x.version}`).join(", ") : null;
+    if (r.published) {
+        // Raizn's own team skips review: the server approved and published it in the same step.
+        s.out(`Published "${state.themeName}" — it is LIVE now (Raizn team changes skip review). Request ${r.requestId}`);
+        if (sections)
+            s.out(`These custom sections went live with it: ${sections}.`);
+        s.out(`Something wrong? Roll it back in one click: ${link}`);
+        return 0;
     }
+    s.out(`Submitted "${state.themeName}" for approval: request ${r.requestId}`);
+    s.out(`Review it: ${link}`);
+    if (sections)
+        s.out(`These custom sections will go live with this request when it is published: ${sections}.`);
     s.out("Nothing is live yet. Someone with publish rights approves and publishes it in the Raizn admin.");
     return 0;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@raizn/cli",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "Edit a Raizn Commerce store's theme as local files, preview it on the real store domain and send it for approval.",
   "license": "UNLICENSED",
   "repository": {