npm - claude-code-session-manager - Versions diffs - 0.35.14 → 0.35.16 - Mend

claude-code-session-manager 0.35.14 → 0.35.16

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 (8) hide show

package/dist/index.html CHANGED Viewed

@@ -7,10 +7,10 @@
     <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/index-DqWSSMkp.js"></script>
+    <script type="module" crossorigin src="./assets/index-C6ep3yfh.js"></script>
     <link rel="modulepreload" crossorigin href="./assets/monaco-editor-BW5C4Iv1.js">
     <link rel="stylesheet" crossorigin href="./assets/monaco-editor-BTnBOi8r.css">
-    <link rel="stylesheet" crossorigin href="./assets/index-B39Qiq0n.css">
+    <link rel="stylesheet" crossorigin href="./assets/index-BwFHVuSk.css">
   </head>
   <body class="bg-bg text-fg font-sans antialiased">
     <div id="root"></div>

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "claude-code-session-manager",
-  "version": "0.35.14",
+  "version": "0.35.16",
   "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",
@@ -120,6 +120,7 @@
     "@vitejs/plugin-react": "^4.3.3",
     "autoprefixer": "^10.4.20",
     "concurrently": "^9.1.0",
+    "jsdom": "^29.1.1",
     "postcss": "^8.4.49",
     "react": "^18.3.1",
     "react-dom": "^18.3.1",

package/plugins/session-manager-dev/skills/process-feedback/SKILL.md CHANGED Viewed

@@ -1,16 +1,20 @@
 ---
 name: process-feedback
 description: >-
-  Process the current project's inbound feedback folder end-to-end: read every
-  open item, evaluate it against real code, and for work that belongs to this
+  Process the current project's inbound feedback folder end-to-end: first sync
+  any open GitHub issues on the project's repo into the intake as new feedback
+  files (deduped against already-tracked issues), then read every open item,
+  evaluate it against real code, and for work that belongs to this
   project queue it as scheduled PRDs via /develop (never implement inline),
   archive the item as processed **the moment it is queued** (the scheduler owns
   execution from there), and fold lessons back into the folder's README so
-  future feedback (written by other agents/projects) gets better. Use whenever the user says "/process-feedback",
+  future feedback (written by other agents/projects, or GitHub issue filers)
+  gets better. Use whenever the user says "/process-feedback",
   "review the feedback folder", "work through the feedback", "any open
-  feedback?", or drops new files into session-manager-operations/feedback/.
+  feedback?", "check the GitHub issues", "triage the GitHub repo", or drops
+  new files into session-manager-operations/feedback/.
   Keywords: feedback, intake, cross-project requests, process feedback, triage
-  feedback.
+  feedback, GitHub issues.
 model: opus
 ---
@@ -68,7 +72,49 @@ Before anything else, check for the pre-migration layout: if a legacy
 `git mv feedback session-manager-operations/feedback` when the repo is
 git-tracked, else a plain `mv`. This converges any project this skill runs in
 to the new layout even if its bulk-relocation PRD hasn't landed yet. Only then
-continue with step 0.
+continue with step 0b.
+### 0b. Sync open GitHub issues into the intake (source sync)
+For a project with a GitHub remote, pull open issues and materialize any not already tracked as a
+new feedback file — **before** the quick-exit check below evaluates what's open, since this step
+can create new open items that check needs to see. This lets a repo's GitHub issue tracker feed
+the same triage → queue pipeline without a human manually copying issues into the feedback folder.
+- Skip silently (no error, no report) if `gh repo view --json nameWithOwner -q .nameWithOwner`
+  fails — no GitHub remote or `gh` unauthenticated. This step is opportunistic, not required.
+- Fetch open issues via `gh api repos/<owner>/<repo>/issues --paginate --jq '...'` (per-issue
+  `number,title,body,labels`) rather than `gh issue list`/`gh issue view` — the latter two can hit
+  a known `gh` CLI bug on repos with legacy GitHub Projects (classic) boards
+  (`GraphQL: Projects (classic) is being deprecated ... (repository.issue.projectCards)`,
+  documented in `standards.md`'s Execution discipline section); `gh api` sidesteps it outright by
+  never touching the deprecated field. Note `gh api .../issues` also returns pull requests (they
+  have an `issue.pull_request` key) — filter those out, this step is issues only.
+- **Dedup before creating anything.** An issue already tracked has a feedback file (open OR
+  already in `processed/`) containing the token `gh-issue-<N>` — `grep -rl "gh-issue-<N>"
+  session-manager-operations/feedback/` (recursive, covers both the inbox and `processed/`) before
+  materializing issue `N`. Skip any issue that already has a match.
+- For each untracked open issue, create
+  `session-manager-operations/feedback/<yyyy-mm-dd>-gh-issue-<N>-<slug>.md` following the folder's
+  normal frontmatter convention (see `README.md`):
+  - `title`: the issue title, verbatim.
+  - `source`: `GitHub issue gh-issue-<N> (<issue URL>)` — the `gh-issue-<N>` token here is what
+    the dedup grep matches on next run; don't reword it out.
+  - `type`: infer from labels (`bug` label → `bug`; `enhancement`/no matching label → `enhancement`;
+    `security` → `security`; `performance` → `performance`).
+  - `severity`: `normal` unless the issue's own labels/title clearly indicate `blocker`/`high`
+    (data loss, crash, security hole, or an unusable feature with no workaround — same bar as the
+    README's own severity guidance; don't inflate).
+  - Body: `# What happens / what's missing` = the issue body (verbatim, or a faithful trim if very
+    long — don't paraphrase away specifics); `# Evidence` = the issue URL + number, plus any
+    screenshot/repro references already in the issue body; `# Suggested direction (optional)` =
+    any proposed-solution section already present in the issue body.
+- Synced files then flow through steps 1–6 below exactly like any other feedback file — no
+  special-casing after creation, same evaluate → queue → disposition → archive pipeline.
+- When step 4 dispositions a synced issue by queuing a PRD, the `## RESOLUTION` must also state
+  the originating issue number/URL. This skill does **not** auto-close or auto-comment on the
+  GitHub issue — that stays a human (or a later, deliberate step) decision once the fix actually
+  ships, not something this sync step does on queue.
 ### 0. Quick-exit — bail in milliseconds if there's nothing to do

package/src/main/__tests__/scheduler-force-tick-outcome.test.cjs ADDED Viewed

@@ -0,0 +1,46 @@
+/**
+ * scheduler-force-tick-outcome.test.cjs — unit tests for forceTickOutcome().
+ *
+ * Covers the "No pending jobs" vs "Already running" ambiguity: when
+ * pickNextBatch() returns an empty batch with no hold reason, that's only
+ * genuinely "no pending jobs" if nothing is running either — if a job
+ * already transitioned to running (e.g. the when-available poll won a race
+ * against a manual force-tick click), the message must say so instead of
+ * flatly claiming nothing is pending.
+ *
+ * Run: timeout 120 node --test src/main/__tests__/scheduler-force-tick-outcome.test.cjs
+ */
+'use strict';
+const { test } = require('node:test');
+const assert = require('node:assert/strict');
+const { forceTickOutcome } = require('../scheduler.cjs');
+test('forceTickOutcome: null result → No pending jobs', () => {
+  const outcome = forceTickOutcome(null);
+  assert.strictEqual(outcome.message, 'No pending jobs');
+});
+test('forceTickOutcome: fired → Fired N job(s)', () => {
+  const outcome = forceTickOutcome({ fired: true, count: 2, group: 0 });
+  assert.strictEqual(outcome.message, 'Fired 2 job(s) (group g0)');
+});
+test('forceTickOutcome: reason=drained (genuinely nothing pending or running) → No pending jobs', () => {
+  const outcome = forceTickOutcome({ fired: false, reason: 'drained' });
+  assert.strictEqual(outcome.message, 'No pending jobs');
+});
+test('forceTickOutcome: reason=already-running (race: poll fired it first) → Already running message, not "No pending jobs"', () => {
+  const outcome = forceTickOutcome({ fired: false, reason: 'already-running', runningCount: 1 });
+  assert.strictEqual(outcome.message, 'Already running — 1 job(s) in flight');
+  assert.notStrictEqual(outcome.message, 'No pending jobs');
+});
+test('forceTickOutcome: reason=held → detail message surfaces', () => {
+  const outcome = forceTickOutcome({ fired: false, reason: 'held', detail: '[scheduler] concurrency [/a]: cap reached, no slots' });
+  assert.strictEqual(outcome.message, 'cap reached, no slots');
+});
+console.log('scheduler-force-tick-outcome tests: PASS');

package/src/main/scheduler.cjs CHANGED Viewed

@@ -1697,6 +1697,20 @@ function tickQueue() {
         console.log(`[scheduler] dod-drain: ${err?.message ?? String(err)}`);
       });
       if (holdReason) return { fired: false, reason: 'held', detail: holdReason };
+      // Distinguish "genuinely nothing to do" from "the batch was already
+      // fired by a concurrent tickQueue() call" (e.g. the periodic
+      // when-available poll winning a race against a manual force-tick —
+      // pickNextBatch correctly returns reason:null in both cases since
+      // neither is a hold; the caller-facing message needs to tell them
+      // apart so "No pending jobs" doesn't read as wrong next to a job
+      // that is visibly running).
+      const runningCount = Math.max(
+        runningSet.size,
+        state.jobs.filter((j) => j.status === 'running').length,
+      );
+      if (runningCount > 0) {
+        return { fired: false, reason: 'already-running', runningCount };
+      }
       return { fired: false, reason: 'drained' };
     }
@@ -1748,6 +1762,8 @@ function forceTickOutcome(result) {
   switch (result.reason) {
     case 'drained':
       return { ok: true, kind: 'info', message: 'No pending jobs' };
+    case 'already-running':
+      return { ok: true, kind: 'info', message: `Already running — ${result.runningCount} job(s) in flight` };
     case 'paused':
       return { ok: true, kind: 'warn', message: 'Scheduler is paused' };
     case 'cancelled':
@@ -2403,10 +2419,10 @@ function registerScheduleHandlers() {
     });
     await broadcast();
     let message;
-    if (added === 0 && removed === 0) message = 'Rescanned — no changes';
-    else if (added > 0 && removed === 0) message = `Rescanned — ${added} new PRD(s) picked up`;
-    else if (added === 0 && removed > 0) message = `Rescanned — ${removed} PRD(s) removed from disk`;
-    else message = `Rescanned — ${added} new PRD(s) picked up, ${removed} removed from disk`;
+    if (added === 0 && removed === 0) message = 'Rescanned — no new/removed PRD files';
+    else if (added > 0 && removed === 0) message = `Rescanned — ${added} new PRD file(s) picked up`;
+    else if (added === 0 && removed > 0) message = `Rescanned — ${removed} PRD file(s) removed from disk`;
+    else message = `Rescanned — ${added} new PRD file(s) picked up, ${removed} removed from disk`;
     return { ok: true, kind: 'info', message };
   });
@@ -2825,4 +2841,4 @@ const remote = {
   },
 };
-module.exports = { registerScheduleHandlers, attachWindow, init, ROOT, PRDS_DIR, selectHistoryJobs, parsePorcelain, FINISH_PROTOCOL, remote, pickNextBatch, pickForProject, reapDeadRunningJobs, pollRecoveryClearSource, memoryLimitedBatchSize, availableForJobs, reverifyNeedsReview, isRescanCandidate, isPromotableOriginal, selectAutoFixTargets, isEligibleForImmediateAutoFix, resolveRunId, isUnresolvableNeedsReview, healTargetForFix, buildInvestigationPrompt, committedInWindow, isFixPlanSlug, isFixPlanBeyondDepthCap, MAX_INVESTIGATION_DEPTH };
+module.exports = { registerScheduleHandlers, attachWindow, init, ROOT, PRDS_DIR, selectHistoryJobs, parsePorcelain, FINISH_PROTOCOL, remote, pickNextBatch, pickForProject, reapDeadRunningJobs, pollRecoveryClearSource, memoryLimitedBatchSize, availableForJobs, reverifyNeedsReview, isRescanCandidate, isPromotableOriginal, selectAutoFixTargets, isEligibleForImmediateAutoFix, resolveRunId, isUnresolvableNeedsReview, healTargetForFix, buildInvestigationPrompt, committedInWindow, isFixPlanSlug, isFixPlanBeyondDepthCap, MAX_INVESTIGATION_DEPTH, forceTickOutcome };