cc-viewer 1.7.2 → 1.7.4

package/server/lib/ensure-hooks.js

@@ -78,7 +78,7 @@ function _looksStaleManagedCommand(cmd) {
 
 function _purgeStaleManagedHooks(settings) {
   let removed = 0;
-  for (const sectionKey of ['PreToolUse', 'Stop']) {
+  for (const sectionKey of ['PreToolUse', 'Stop', 'SessionStart']) {
     const arr = settings.hooks?.[sectionKey];
     if (!Array.isArray(arr)) continue;
     for (let i = arr.length - 1; i >= 0; i--) {
@@ -99,7 +99,7 @@ function _purgeStaleManagedHooks(settings) {
 // 调用方负责 atomic write-back。返回 removed 数量。
 export function removeAllManagedHooks(settings) {
   let removed = 0;
-  for (const sectionKey of ['PreToolUse', 'Stop']) {
+  for (const sectionKey of ['PreToolUse', 'Stop', 'SessionStart']) {
     const arr = settings.hooks?.[sectionKey];
     if (!Array.isArray(arr)) continue;
     for (let i = arr.length - 1; i >= 0; i--) {
@@ -129,6 +129,7 @@ export function ensureHooks() {
     if (!settings.hooks) settings.hooks = {};
     if (!Array.isArray(settings.hooks.PreToolUse)) settings.hooks.PreToolUse = [];
     if (!Array.isArray(settings.hooks.Stop)) settings.hooks.Stop = [];
+    if (!Array.isArray(settings.hooks.SessionStart)) settings.hooks.SessionStart = [];
 
     let changed = false;
     // 先一次性清掉「path 已 stale 但还带 cc-viewer-managed marker」的老条目，
@@ -214,6 +215,31 @@ export function ensureHooks() {
       changed = true;
     }
 
+    // SessionStart hook → session-start-bridge.js. Fires on startup/resume/
+    // clear/compact; no matcher (= all sources) — the bridge forwards `source`
+    // and the server gates on it. The `resume` source is the conversation-
+    // switch signal the V2Writer needs to re-bind routing after an in-terminal
+    // /resume (the wire session_id may not change, so no wire-level signal
+    // exists). Same CCVIEWER_PORT guard pattern as the other bridges.
+    const sessionStartBridgePath = resolve(SERVER_LIB, 'session-start-bridge.js');
+    const sessionStartCmd = `[ -n "$CCVIEWER_PORT" ] && node "${sessionStartBridgePath}" || true ${CCV_HOOK_MARKER}`;
+    const sessionStartDesired = _buildHookObj(sessionStartCmd);
+    const sessionStartExisting = settings.hooks.SessionStart.find(h => {
+      const cmd = h.hooks?.[0]?.command || '';
+      return cmd.includes('session-start-bridge.js');
+    });
+    if (sessionStartExisting) {
+      if (!_hookObjEqual(sessionStartExisting.hooks?.[0], sessionStartDesired)) {
+        sessionStartExisting.hooks = [_mergeHookObj(sessionStartExisting.hooks?.[0], sessionStartDesired)];
+        changed = true;
+      }
+    } else {
+      settings.hooks.SessionStart.push({
+        hooks: [sessionStartDesired],
+      });
+      changed = true;
+    }
+
     if (changed) {
       mkdirSync(claudeDir, { recursive: true });
       // Atomic write(): write to a sibling temp file then rename. Concurrent

package/server/lib/log-watcher.js

@@ -92,7 +92,12 @@ function _safeSseWrite(clients, client, payload) {
   return true;
 }
 
+// Zero-client short-circuit (all four senders): the payload template is built
+// BEFORE the client loop, so with no SSE consumer connected every broadcast
+// still paid a full JSON.stringify — for reconstructed entries carrying
+// cumulative messages that is a giant allocation for nothing.
 export function sendToClients(clients, entry) {
+  if (clients.length === 0) return;
   const payload = `data: ${JSON.stringify(entry)}\n\n`;
   for (let i = clients.length - 1; i >= 0; i--) {
     _safeSseWrite(clients, clients[i], payload);
@@ -100,6 +105,7 @@ export function sendToClients(clients, entry) {
 }
 
 export function sendEventToClients(clients, eventName, data) {
+  if (clients.length === 0) return;
   const payload = `event: ${eventName}\ndata: ${JSON.stringify(data)}\n\n`;
   for (let i = clients.length - 1; i >= 0; i--) {
     _safeSseWrite(clients, clients[i], payload);
@@ -109,6 +115,7 @@ export function sendEventToClients(clients, eventName, data) {
 /** Like sendEventToClients but `json` is an ALREADY-serialized JSON string —
  *  wire v3 forwards raw stored lines verbatim without a parse/stringify trip. */
 export function sendEventRawToClients(clients, eventName, json) {
+  if (clients.length === 0) return;
   const payload = `event: ${eventName}\ndata: ${json}\n\n`;
   for (let i = clients.length - 1; i >= 0; i--) {
     _safeSseWrite(clients, clients[i], payload);
@@ -116,6 +123,7 @@ export function sendEventRawToClients(clients, eventName, json) {
 }
 
 export function sendChunkToClients(clients, dataJson) {
+  if (clients.length === 0) return;
   const payload = `event: load_chunk\ndata: ${dataJson}\n\n`;
   for (let i = clients.length - 1; i >= 0; i--) {
     _safeSseWrite(clients, clients[i], payload);

package/server/lib/pid-alive.js

@@ -0,0 +1,15 @@
+// Process-liveness probe shared by pid-validity claims (session-owner.js).
+// Deliberately dependency-free: im-lock.js's identical helper drags findcc.js
+// (LOG_DIR env resolution, a top-level node:worker_threads threadId import)
+// into every importer's module graph — the stats worker's loader shim has no
+// threadId export, and the v2 writer's synchronous ingest path doesn't want
+// node:http along for the ride. im-lock.js / async-file-lock.js keep their
+// local copies (same semantics); consolidation is backlog.
+
+/** Is `pid` alive? Signal 0 probes without delivering; EPERM means the
+ *  process exists but belongs to another user (still alive). */
+export function isPidAlive(pid) {
+  if (!Number.isInteger(pid) || pid <= 0) return false;
+  try { process.kill(pid, 0); return true; }
+  catch (e) { return e && e.code === 'EPERM'; }
+}