@lifeaitools/clauth 2.10.0 → 2.10.1

package/cli/commands/serve.js

@@ -103,6 +103,16 @@ const __dirname = path.dirname(fileURLToPath(import.meta.url));
 const CLAUTH_ROOT_DIR = path.join(__dirname, "../..");
 const pkg = JSON.parse(fs.readFileSync(path.join(__dirname, "../../package.json"), "utf8"));
 const VERSION = pkg.version;
+// Computed ONCE per daemon process, at module load -- never polled. Answers
+// "what am I looking at": this build's commit date, and whether this
+// process is the live daemon (LIVE_PORT, not staged) or a dev/test instance.
+// A prior version of this polled a per-request HTTP route with a live git
+// shell-out every 30s, which is exactly the wrong shape for a fact that
+// only changes when the daemon itself restarts.
+let BUILD_DATE = null;
+try {
+  BUILD_DATE = execSyncTop("git log -1 --format=%cs HEAD", { cwd: CLAUTH_ROOT_DIR, encoding: "utf8", windowsHide: true }).trim() || null;
+} catch { /* not a git checkout, or git unavailable -- BUILD_DATE stays null */ }
 
 // Dashboard client CSS/JS ship as static assets (../dashboard/) rather than
 // inlined in dashboardHtml()'s template literal — read once at module load,
@@ -946,6 +956,8 @@ export function dashboardHtml(port, whitelist, isStaged = false, initWriteToken
 <script>
 window.__CLAUTH_VERSION__ = ${JSON.stringify(VERSION)};
 window.__CLAUTH_INIT_WRITE_TOKEN__ = ${JSON.stringify(initWriteToken)};
+window.__CLAUTH_BUILD_DATE__ = ${JSON.stringify(BUILD_DATE)};
+window.__CLAUTH_IS_LIVE__ = ${JSON.stringify(port === LIVE_PORT && !isStaged)};
 </script>
 <script src="/dashboard/panel-element.js"></script>
 <script src="/dashboard/panels/panel-registry.js"></script>
@@ -1814,32 +1826,6 @@ function createServer(initPassword, whitelist, port, tunnelHostnameInit = null,
     }
   });
   registerReadOnlyRoute("GET", "/builds", async (req, res) => ok(res, buildStatus));
-  // GET /deploy-status — this daemon's own environment identity, NOT the
-  // regen-root build pipeline /builds surfaces. Two independent axes:
-  //   live vs test  -- is this the daemon Dave uses directly (LIVE_PORT,
-  //                    not staged), or a test/isolated/staged instance?
-  //   local vs develop -- does the running checkout's HEAD match
-  //                    origin/develop with a clean working tree (what's
-  //                    actually published), or does it diverge (uncommitted
-  //                    changes, or a different commit)?
-  // Answers the dashboard's own "what am I looking at" question -- the
-  // thing that previously read as an unrelated, confusing status pulled
-  // from Supabase's regen-root build_status blob.
-  registerReadOnlyRoute("GET", "/deploy-status", async (req, res) => {
-    const isLive = port === LIVE_PORT && !isStaged;
-    let headSha = null;
-    let synced = null;
-    try {
-      headSha = execSyncTop("git rev-parse --short=7 HEAD", { cwd: CLAUTH_ROOT_DIR, encoding: "utf8" }).trim();
-      const dirty = execSyncTop("git status --porcelain", { cwd: CLAUTH_ROOT_DIR, encoding: "utf8" }).trim().length > 0;
-      let developSha = null;
-      try {
-        developSha = execSyncTop("git rev-parse --short=7 origin/develop", { cwd: CLAUTH_ROOT_DIR, encoding: "utf8" }).trim();
-      } catch { /* no origin/develop ref cached locally -- synced stays unknown */ }
-      synced = developSha !== null ? (!dirty && headSha === developSha) : null;
-    } catch { /* git unavailable -- headSha/synced stay null, panel shows "local" (unknown = not confirmed synced) */ }
-    return ok(res, { is_live: isLive, is_staged: isStaged, port, synced, head_sha: headSha });
-  });
   // GET /migrations — migration registry and last run result
   registerReadOnlyRoute("GET", "/migrations", async (req, res) => ok(res, {
     schema_version: CURRENT_SCHEMA_VERSION,

package/cli/dashboard/panels/build-status-panel.js

@@ -1,31 +1,37 @@
 // cli/dashboard/panels/build-status-panel.js
 // The "Deploy" identity badge, as a real Web Component: <clauth-build-status-panel>.
-// Answers ONE question: what am I looking at? Live (port 52437, the daemon
-// Dave uses directly) vs Test (any staged/isolated/other-port instance),
-// crossed with Local (this checkout diverges from origin/develop -- dirty
-// working tree, or a different commit) vs Develop (HEAD matches
-// origin/develop exactly, clean tree -- what's actually published).
+// Answers ONE question: what am I looking at? Version, build date, and
+// whether this is Live (port 52437, the daemon Dave uses directly) or a
+// dev/test instance.
 //
-// Previously this panel polled GET /builds, which is regen-root's OWN build
-// pipeline status (borrowed from Supabase's prt_storage.build_status blob) --
-// unrelated to clauth's own runtime identity, and the source of "not sure
-// what that sync message is" confusion. GET /deploy-status (serve.js) is
-// clauth's own answer instead. /builds and its backing poller are untouched
-// in case another consumer still needs regen-root's build status; this panel
+// These are all facts that only change when the daemon itself restarts --
+// serve.js computes VERSION/BUILD_DATE/is-live ONCE at module load and
+// injects them as window.__CLAUTH_*__ globals in the page's own inline
+// preamble (same mechanism as window.__CLAUTH_VERSION__). This panel just
+// reads those synchronously. An earlier version of this fetched GET
+// /deploy-status on a 30s poll, which ran three git shell-outs per call on
+// the server -- exactly the shape of "unexplained periodic activity" that
+// should never exist for a fact that doesn't change between daemon
+// restarts. No fetch, no poll, no server route.
+//
+// Previously (before that) this panel polled GET /builds, which is
+// regen-root's OWN build pipeline status (borrowed from Supabase's
+// prt_storage.build_status blob) -- unrelated to clauth's own runtime
+// identity, and the source of "not sure what that sync message is"
+// confusion. /builds and its backing poller are untouched in serve.js in
+// case another consumer still needs regen-root's build status; this panel
 // simply no longer surfaces it.
 //
 // Same conversion shape as every panel before it (tunnel-panel.js is the
 // reference implementation): a class extending window.ClauthPanelElement,
 // its own template()/mount(), instance state instead of module-level
-// globals, and mount() -- not connectedCallback() -- doing the real fetch
-// work. connectedCallback() (panel-element.js) fires during HTML parsing,
-// before dashboard.js (and its BASE global) has loaded; calling real logic
-// there throws a live "BASE is not defined" a vm-based test harness would
-// never catch. mount() is instead called explicitly by
-// ClauthPanelRegistry.mountAll(), after every script has loaded.
+// globals. connectedCallback() (panel-element.js) fires during HTML
+// parsing, before dashboard.js has loaded -- but this panel's mount() only
+// reads window globals the inline preamble already set before any panel
+// script runs, so there's no "BASE is not defined" hazard here the way
+// there was for panels that fetch.
 //
-// This panel owns none of WRITE_ACTIONS (it only reads GET /deploy-status),
-// so it needs no write-guard bridge -- unlike tunnel-panel.js/webdav-panel.js.
+// This panel owns none of WRITE_ACTIONS and needs no write-guard bridge.
 //
 // Loaded as a plain classic <script> (not type="module") BEFORE dashboard.js
 // -- same pattern as every other panel component.
@@ -44,41 +50,23 @@ class ClauthBuildStatusPanel extends window.ClauthPanelElement {
   }
 
   mount() {
-    this.pollTimer = null;
-    this.updateDeployStatus();
-    // A git-sync check is cheap but not free -- 30s keeps the badge honest
-    // (a fresh push or a new local edit shows up within half a minute)
-    // without polling as aggressively as a per-request build/test pipeline
-    // status would need.
-    this.pollTimer = setInterval(() => this.updateDeployStatus(), 30000);
-  }
-
-  async updateDeployStatus() {
-    try {
-      const data = await fetch(BASE + "/deploy-status").then(r => r.json());
-      const dot = this.$("#deploy-dot");
-      const label = this.$("#deploy-label");
-      const sha = this.$("#deploy-sha");
+    const dot = this.$("#deploy-dot");
+    const label = this.$("#deploy-label");
+    const sha = this.$("#deploy-sha");
 
-      const envWord = data.is_live ? "Live" : "Test";
-      // synced === null means git wasn't available or origin/develop has
-      // never been fetched locally -- treat as "Local" (unconfirmed is not
-      // the same claim as "matches develop").
-      const syncWord = data.synced === true ? "Develop" : "Local";
-      const text = envWord + " - " + syncWord;
+    const isLive = window.__CLAUTH_IS_LIVE__ === true;
+    const envWord = isLive ? "Live" : "Dev";
+    const version = window.__CLAUTH_VERSION__ || "?";
+    const buildDate = window.__CLAUTH_BUILD_DATE__;
 
-      dot.className = "deploy-dot " + (data.is_live ? "live" : "test") + " " + (data.synced === true ? "synced" : "local");
-      label.textContent = text;
-      sha.textContent = data.head_sha ? data.head_sha : "";
-    } catch {
-      const label = this.$("#deploy-label");
-      if (label) label.textContent = "unknown";
-    }
+    dot.className = "deploy-dot " + (isLive ? "live" : "test");
+    label.textContent = envWord + " · v" + version;
+    sha.textContent = buildDate ? "built " + buildDate : "";
   }
 
   // No data-action elements in this panel's template -- it is pure display,
-  // polled on a timer. Declared anyway so the contract is explicit rather
-  // than implicit-via-undefined.
+  // computed once from values the page already loaded with. Declared
+  // anyway so the contract is explicit rather than implicit-via-undefined.
   get actions() {
     return {};
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lifeaitools/clauth",
-  "version": "2.10.0",
+  "version": "2.10.1",
   "description": "Hardware-bound credential vault for the LIFEAI infrastructure stack",
   "type": "module",
   "bin": {