@lotics/cli 0.171.0 → 0.172.1

package/dist/src/cli.js

@@ -45696,7 +45696,17 @@ function resultSideEffects(result) {
 }
 
 // src/version.ts
-var VERSION = "0.171.0";
+var VERSION = "0.172.1";
+
+// src/timezone.ts
+function machineTimezone() {
+  try {
+    const zone = Intl.DateTimeFormat().resolvedOptions().timeZone;
+    return zone !== void 0 && zone !== "" ? zone : void 0;
+  } catch {
+    return void 0;
+  }
+}
 
 // src/docs_command.ts
 import fs5 from "node:fs";
@@ -71683,6 +71693,17 @@ function runTar(args, cwd) {
     });
   });
 }
+function npmIsInstalled() {
+  return new Promise((resolve2) => {
+    const probe = spawn2("npm", ["--version"], {
+      shell: process.platform === "win32",
+      stdio: "ignore",
+      env: ipv4ChildEnv(process.env)
+    });
+    probe.on("error", () => resolve2(false));
+    probe.on("exit", (code) => resolve2(code === 0));
+  });
+}
 function runNpm(args, cwd) {
   const quiet = isMachineOutput();
   return new Promise((resolve2, reject2) => {
@@ -71714,12 +71735,27 @@ function runNpm(args, cwd) {
       proc.stdout?.on("data", collect);
       proc.stderr?.on("data", collect);
     }
-    proc.on("error", reject2);
+    proc.on("error", (error52) => void failed(error52, null));
     proc.on("exit", (code) => {
       if (code === 0) {
         resolve2();
         return;
       }
+      void failed(void 0, code);
+    });
+    async function failed(error52, code) {
+      if (!await npmIsInstalled()) {
+        reject2(
+          new Error(
+            "npm was not found, and building an app needs it.\n  Install Node.js 18 or newer (npm comes with it), then run this again:\n    https://nodejs.org/en/download\n  The Lotics CLI itself needs no Node \u2014 only this build step does."
+          )
+        );
+        return;
+      }
+      if (error52 !== void 0) {
+        reject2(error52);
+        return;
+      }
       const tail = captured.slice(-NPM_LOG_TAIL_BYTES).trim();
       reject2(
         new Error(
@@ -71728,7 +71764,7 @@ function runNpm(args, cwd) {
 ${tail}`)
         )
       );
-    });
+    }
   });
 }
 var NPM_LOG_TAIL_BYTES = 8e3;
@@ -103192,7 +103228,7 @@ Auth flags:
                          signup/api-key write a self-contained ./.lotics/config.json
                          (inline key) \u2014 for a hermetic worktree or CI.
   --name <name>          (signup) Display name (defaults to email prefix)
-  --timezone <timezone>  (signup) Workspace timezone (defaults to UTC, e.g. Asia/Ho_Chi_Minh)
+  --timezone <timezone>  (signup) Workspace timezone (defaults to this machine's, e.g. Asia/Ho_Chi_Minh)
 
 API keys are stored once per org as named profiles in ~/.lotics/config.json.
 Registering a second key adds a profile \u2014 it does not overwrite the first.
@@ -103234,7 +103270,8 @@ async function publicPost(path13, body) {
 async function signupAccount(args) {
   const body = { email: args.email };
   if (args.name) body.name = args.name;
-  if (args.timezone) body.timezone = args.timezone;
+  const timezone = args.timezone ?? machineTimezone();
+  if (timezone) body.timezone = timezone;
   const { ok, status, data: data2 } = await publicPost("/v1/cli/signup", body);
   if (!ok) {
     if (status === 409) {

package/docs/building_an_app.md

@@ -206,6 +206,17 @@ lotics app check                     # every pre-flight a deploy runs, without b
 lotics app deploy -m "<what changed + why>"
 ```
 
+**A green suite says nothing about how the screen LOOKS**, and that half has its own pass:
+`lotics docs reviewing` — render it, look at it, then measure what the look is telling you. Run it
+before the deploy, not as an audit someone schedules after a complaint.
+
+Every check above reads the SOURCE; none of them renders it. So the entire class of defect that
+lives in the pixels — wrong form for the subject, a treatment that contradicts what an element
+means, a surface that measures clean and still tells the reader nothing — passes all of them
+silently, and arrives later as "it looks bad", which is a report about a cause the reporter cannot
+name. That is what the review is for, and why it belongs here rather than in whoever remembers to
+ask for it.
+
 `-m` is optional; the deploy derives a message from what it pushed. Write one when the *why* is
 worth keeping.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/cli",
-  "version": "0.171.0",
+  "version": "0.172.1",
   "description": "Lotics SDK and CLI for AI agents",
   "type": "module",
   "bin": {