claude-code-session-manager 0.124.0 → 0.124.1

package/dist-web/index.html

@@ -0,0 +1,16 @@
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="UTF-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+    <title>Claude Session Manager</title>
+    <link rel="preconnect" href="https://fonts.googleapis.com">
+    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
+    <link href="https://fonts.googleapis.com/css2?family=Newsreader:ital,opsz,wght@0,6..72,400;0,6..72,500;0,6..72,600;0,6..72,700;1,6..72,400&family=Geist:wght@300;400;500;600;700&family=IBM+Plex+Mono:wght@400;500;600&display=swap" rel="stylesheet">
+    <script type="module" crossorigin src="./assets/app.js"></script>
+    <link rel="stylesheet" crossorigin href="./assets/app.css">
+  </head>
+  <body class="bg-bg text-fg font-sans antialiased">
+    <div id="root"></div>
+  </body>
+</html>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-code-session-manager",
-  "version": "0.124.0",
+  "version": "0.124.1",
   "description": "Local cockpit for the Claude Code CLI — multi-tab terminal, full config surface, scheduler, voice dictation, and live observability.",
   "type": "module",
   "main": "src/main/index.cjs",
@@ -37,7 +37,7 @@
     "dev": "concurrently -k -n vite,electron -c magenta,cyan \"npm:dev:renderer\" \"npm:dev:electron\"",
     "dev:renderer": "vite",
     "dev:electron": "wait-on http://localhost:5173 && SM_DEV=1 electron .",
-    "build": "vite build",
+    "build": "vite build && vite build --config vite.web.config.ts",
     "build:web": "vite build --config vite.web.config.ts",
     "dist:stage": "npm run build && node scripts/package/stage.cjs",
     "dist:mac": "npm run dist:stage && electron-builder --config electron-builder.yml --mac --publish never",
@@ -47,7 +47,7 @@
     "typecheck": "tsc --noEmit && tsc --noEmit -p tsconfig.main.json",
     "start": "electron .",
     "prepack": "node scripts/write-build-info.cjs",
-    "prepublishOnly": "node scripts/write-build-info.cjs && vite build",
+    "prepublishOnly": "node scripts/write-build-info.cjs && npm run build",
     "test:unit": "vitest run",
     "test:unit:stability": "bash scripts/test-unit-stability.sh",
     "bench": "node scripts/bench/main-bench.cjs",

package/plugins/session-manager-dev/skills/builder/3-publish/SKILL.md

@@ -40,24 +40,37 @@ to ask for reconfirmation once `builder:gate` has passed.
 
 5. **Create the isolated worktree from that tag:**
    ```
-   git worktree add /tmp/sm-publish-v<version> v<version>
+   mkdir -p "$HOME/.cache/sm-publish"
+   git worktree add "$HOME/.cache/sm-publish/v<version>" v<version>
    ```
+   **Never under `/tmp`** (or anywhere under `os.tmpdir()`): the test suite treats such paths as
+   test fixtures, so `src/main/__tests__/opsErrorLog.test.cjs` ("a real project root is
+   refused") fails inside a `/tmp` worktree.
 
-6. **Move into the worktree and build clean:**
+6. **Move into the worktree, build clean, and run the in-tree gate:**
    ```
-   cd /tmp/sm-publish-v<version>
+   cd "$HOME/.cache/sm-publish/v<version>"
    npm ci
    npm run typecheck
+   npm run test:unit
    ```
    `npm ci` gives a fully clean `node_modules` from the lockfile — no leftover local state
-   from the dirty main repo can leak into the published artifact.
+   from the dirty main repo can leak into the published artifact. Typecheck and unit tests
+   must both pass here; stop before `npm publish` on any failure.
+
+   After the build step (run the project's build, e.g. `npm run build` plus any web build that
+   produces `dist-web/`), check that every `files` entry exists:
+   ```
+   test -f dist-web/index.html && test -f dist/index.html
+   ```
+   If either is missing, stop before `npm publish` and report.
 
 7. **Publish from inside the worktree:**
    ```
    npm publish
    ```
    This project's `prepublishOnly` script runs `vite build` — because step 6 already `cd`'d
-   into `/tmp/sm-publish-v<version>`, that build runs **inside the clean worktree**, never
+   into `$HOME/.cache/sm-publish/v<version>`, that build runs **inside the clean worktree**, never
    touching (or being affected by) the live/dirty working directory back in the main repo.
    This is the entire reason the worktree exists: it decouples "what's uncommitted in my
    editor right now" from "what gets built and shipped."
@@ -81,16 +94,21 @@ to ask for reconfirmation once `builder:gate` has passed.
 
 9. **Clean up the worktree:**
    ```
-   git worktree remove /tmp/sm-publish-v<version> --force
+   git worktree remove "$HOME/.cache/sm-publish/v<version>" --force
    ```
 
-10. **Verify the publish actually landed on the registry:**
+10. **Verify the publish actually landed on the registry.** `npm view` is cached and lags for
+    minutes after a real publish, so check a cache-busted packument and the tarball first:
     ```
+    curl -s "https://registry.npmjs.org/<packageName>?t=$(date +%s)"   # dist-tags.latest + versions
+    curl -sI <tarball URL from versions["<version>"].dist.tarball>      # expect HTTP 200
     npm view <packageName> version
     npm view <packageName> dist-tags
     ```
-    Confirm the reported version matches `<version>` and `latest` points to it (unless the
-    project intentionally publishes to a different dist-tag).
+    Confirm `dist-tags.latest` is `<version>`, `<version>` is in `versions`, and the tarball
+    returns 200 (unless the project intentionally publishes to a different dist-tag). If the
+    packument is current, an unchanged `npm view` for a few minutes is normal lag, not a
+    failure — do not republish.
 
 11. **Post-publish: verify the installer release.** Pushing `v<version>` (step 8) triggers
     `.github/workflows/release.yml`. Confirm the tag push succeeded, then poll (bounded: at most
@@ -109,7 +127,7 @@ to ask for reconfirmation once `builder:gate` has passed.
 Stop at that step. Do not proceed. Report which step failed and its output. If the worktree
 was already created (step 5+), leave it in place if its state is relevant evidence for
 diagnosing the failure; otherwise remove it (step 9) before reporting, so a retry doesn't
-collide with a stale `/tmp/sm-publish-v<version>` path.
+collide with a stale `$HOME/.cache/sm-publish/v<version>` path.
 
 ## Output
 

package/src/main/build-info.json

@@ -1,8 +1,8 @@
 {
-  "version": "0.124.0",
-  "gitSha": "9d159322bc6717eba697e3ff96379bc0876eda3f",
-  "gitShortSha": "9d159322",
+  "version": "0.124.1",
+  "gitSha": "604bae39a0da6417ec4f1ba2f92c81f4661c2dfd",
+  "gitShortSha": "604bae39",
   "gitBranch": "HEAD",
-  "builtAt": "2026-10-26T06:06:09.256Z",
+  "builtAt": "2026-10-26T07:38:06.859Z",
   "dirty": false
 }