npm - @bakapiano/ccsm - Versions diffs - 0.15.1 → 0.15.2 - Mend

@bakapiano/ccsm 0.15.1 → 0.15.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (5) hide show

package/CLAUDE.md CHANGED Viewed

@@ -443,6 +443,66 @@ fresh server. So `npm i -g @bakapiano/ccsm@latest && ccsm` is one
 seamless step. From the frontend, the About page's Upgrade button
 achieves the same thing without leaving the browser.
+### Release process
+Three artifacts ship per release: a git tag, a GitHub Release, and an
+npm publish. The whole thing is CI-driven — you never `npm publish`
+locally — but it requires you to drive three steps in order:
+1. **Commit + bump + push (local).** Stage everything, write a release
+   commit, then bump + tag + push:
+   ```powershell
+   git add -A
+   git commit -m "vX.Y.Z: <one-line summary>
+   <body>
+   Co-Authored-By: Claude ..."
+   npm --prefix . version <patch|minor|major> -m "v%s"
+   git push origin main
+   git push origin vX.Y.Z
+   ```
+   `npm version` writes the new version into `package.json` +
+   `package-lock.json`, creates its OWN commit, and tags it. The
+   `--prefix .` is needed on Windows where bare `npm version` errors on
+   the global `%APPDATA%\npm\package.json`. Push BOTH `main` and the
+   tag — pushing only main skips the tag-triggered draft-release
+   workflow.
+2. **Tag-push fires two workflows automatically:**
+   - `Deploy frontend to GitHub Pages` → publishes `pages-root/` → `/`
+     and `public/` → `/<X.Y.Z>/` on `gh-pages`. Old `/<X.Y.Z>/`
+     subdirs stay forever (`keep_files: true`).
+   - `Draft GitHub Release on tag push` → creates a **draft** release
+     for `vX.Y.Z`.
+3. **Publish the draft (manual one-liner):**
+   ```powershell
+   gh release edit vX.Y.Z --draft=false
+   ```
+   This flips the draft to "published", which fires the third workflow
+   — `Publish to npm` — using the `NPM_TOKEN` repo secret with
+   provenance. The runner needs ~30s; verify with
+   `gh run watch <run-id> --exit-status` or just refresh npmjs.com.
+The reason for the draft step instead of auto-publishing on tag push:
+gives you a chance to abort a half-baked tag (delete the draft +
+`git push --delete origin vX.Y.Z`) before it lands on the public
+registry.
+### Why we don't publish from the local box
+`npm publish` from a dev machine works in principle but skips
+provenance attestation (the sigstore + GitHub OIDC binding that npm
+displays as a "Provenance" badge on the package page). CI has the OIDC
+token; you don't. Local publish also wouldn't have the consistent
+runner state, so reproducible-build claims fall apart. The pipeline
+exists; use it.
 ## Cross-platform
 Today: Windows-first.

package/lib/cliActivity.js CHANGED Viewed

@@ -90,9 +90,20 @@ async function resolveTranscript(record, cliCfg) {
 async function probeActivity(record, cliCfg) {
   let s = state.get(record.id);
   if (!s) {
-    s = { resolvedPath: null, lastMtimeMs: 0, lastChangedAt: 0 };
+    s = { resolvedPath: null, lastMtimeMs: 0, lastChangedAt: 0, lastOutputAt: 0 };
     state.set(record.id, s);
   }
+  // PTY output (CLI is streaming text — thinking spinners, token output,
+  // status lines) is the strongest signal that the CLI is working. It's
+  // ALSO the only signal we have when the transcript file isn't being
+  // updated — claude/codex buffer reasoning + tool results for tens of
+  // seconds before flushing a turn, so mtime alone reports "idle"
+  // through long thinking phases. Check PTY first; short-circuit if the
+  // CLI is clearly active, skipping the fs.stat below.
+  const now = Date.now();
+  if (s.lastOutputAt && (now - s.lastOutputAt) < WORKING_WINDOW_MS) {
+    return 'working';
+  }
   if (!s.resolvedPath) {
     s.resolvedPath = await resolveTranscript(record, cliCfg);
     if (!s.resolvedPath) return 'unknown';
@@ -105,7 +116,6 @@ async function probeActivity(record, cliCfg) {
     s.resolvedPath = null;
     return 'unknown';
   }
-  const now = Date.now();
   if (mtimeMs !== s.lastMtimeMs) {
     s.lastMtimeMs = mtimeMs;
     s.lastChangedAt = now;
@@ -113,6 +123,17 @@ async function probeActivity(record, cliCfg) {
   return (now - s.lastChangedAt) < WORKING_WINDOW_MS ? 'working' : 'idle';
 }
+// Called from server.js's spawnCliSession onData hook. Cheap (timestamp
+// write); bound by how often the PTY emits, which is fine.
+function noteOutput(sessionId) {
+  let s = state.get(sessionId);
+  if (!s) {
+    s = { resolvedPath: null, lastMtimeMs: 0, lastChangedAt: 0, lastOutputAt: 0 };
+    state.set(sessionId, s);
+  }
+  s.lastOutputAt = Date.now();
+}
 function releaseSession(sessionId) { state.delete(sessionId); }
-module.exports = { probeActivity, releaseSession };
+module.exports = { probeActivity, noteOutput, releaseSession };

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@bakapiano/ccsm",
-  "version": "0.15.1",
+  "version": "0.15.2",
   "description": "Claude Code Session Manager — Windows web UI to manage many concurrent claude sessions: live list, snapshot/restore, focus existing window, new session in an isolated workspace with repo clones",
   "license": "MIT",
   "main": "server.js",

package/public/css/sidebar.css CHANGED Viewed

@@ -568,11 +568,52 @@ body.is-resizing-sidebar * {
 }
 .tree-session.is-running .tree-dot::after {
   background: var(--green);
+  /* Soft halo so the dot reads as "alive" even from across the sidebar.
+     Box-shadow uses currentColor isn't ideal here (the dot itself uses
+     background, not color), so we hardcode each state's halo color
+     below. */
+  box-shadow: 0 0 0 0 rgba(74, 138, 74, 0.55);
+  animation: tree-dot-breathe-idle 2.8s ease-in-out infinite;
 }
 /* Working = CLI is actively writing to its transcript (i.e. thinking
-   or printing tokens). Idle stays green; working flips to blue. */
+   or printing tokens). Idle stays green + slow breathe; working flips
+   to blue + faster, more obvious breathe. */
 .tree-session.is-running.is-working .tree-dot::after {
   background: var(--blue, #4a73a5);
+  box-shadow: 0 0 0 0 rgba(74, 115, 165, 0.65);
+  animation: tree-dot-breathe-working 1.4s ease-in-out infinite;
+}
+@keyframes tree-dot-breathe-idle {
+  0%, 100% {
+    box-shadow: 0 0 0 0 rgba(74, 138, 74, 0.45);
+    opacity: 0.85;
+  }
+  50% {
+    box-shadow: 0 0 0 4px rgba(74, 138, 74, 0);
+    opacity: 1;
+  }
+}
+@keyframes tree-dot-breathe-working {
+  0%, 100% {
+    box-shadow: 0 0 0 0 rgba(74, 115, 165, 0.65);
+    opacity: 0.9;
+    transform: scale(1);
+  }
+  50% {
+    box-shadow: 0 0 0 5px rgba(74, 115, 165, 0);
+    opacity: 1;
+    transform: scale(1.15);
+  }
+}
+/* Respect users who've asked for less motion — keep the color signal
+   but drop the pulse. */
+@media (prefers-reduced-motion: reduce) {
+  .tree-session.is-running .tree-dot::after,
+  .tree-session.is-running.is-working .tree-dot::after {
+    animation: none;
+    box-shadow: none;
+  }
 }
 .tree-label {
   flex: 1;

package/server.js CHANGED Viewed

@@ -221,7 +221,10 @@ function spawnCliSession({ cli, cwd, sessionId, meta, extraArgs = [] }) {
     cwd,
     env,
     meta: { ...meta, cliId: cli.id, cliName: cli.name },
-    onData: () => { persistedSessions.touch(sessionId).catch(() => {}); },
+    onData: () => {
+      persistedSessions.touch(sessionId).catch(() => {});
+      try { require('./lib/cliActivity').noteOutput(sessionId); } catch {}
+    },
     onExit: ({ exitCode }) => {
       persistedSessions.markExited(sessionId, exitCode).catch(() => {});
     },