ticketlens 0.38.29 → 0.38.30

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ticketlens",
-  "version": "0.38.29",
+  "version": "0.38.30",
   "description": "Jira CLI for developers — fetch ticket context, triage your queue, and stop tab-switching. Zero dependencies, all local.",
   "type": "module",
   "bin": {

package/skills/jtb/hooks/recall-nudge-lib.mjs

@@ -118,9 +118,17 @@ export function hasRecentCapture(cwd, now = Date.now()) {
  * tool — for note-add. Missing the MCP path here was a real bug: it made
  * the Stop hook nudge even after a note was genuinely captured via MCP,
  * since only the Bash/CLI form was ever recognized.
+ *
+ * `ticketKey` carries the FIRST matched ticket key's literal text (or
+ * `null`), so callers can resolve a profile by ticket-key prefix the same
+ * way `resolveConnection()` does — see recall-nudge-stop.mjs. First match,
+ * not last: the primary ticket a session is about is normally established
+ * early, and picking one deterministic match keeps this function decoupled
+ * from profiles.json (it stays a pure transcript reader; profile lookup
+ * and its own fallback chain belong entirely to resolveProfile()).
  */
 export function scanTranscript(transcriptPath) {
-  const result = { sawTicketKey: false, sawRecallFlag: false, sawNoteAdd: false };
+  const result = { sawTicketKey: false, sawRecallFlag: false, sawNoteAdd: false, ticketKey: null };
   let lines;
   try {
     lines = fs.readFileSync(transcriptPath, 'utf8').split('\n').filter(Boolean);
@@ -136,10 +144,22 @@ export function scanTranscript(transcriptPath) {
       continue;
     }
 
-    // Ticket-key detection stays broad (whole entry, any role) — it's only
-    // the weaker "did ticket work happen at all" signal, and a rare false
-    // positive here just means an extra harmless once-per-session check.
-    if (TICKET_KEY_RE.test(JSON.stringify(entry))) result.sawTicketKey = true;
+    // Ticket-key detection stays broad (whole entry, any role) — for
+    // sawTicketKey alone, it's only the weaker "did ticket work happen at
+    // all" signal, so a rare false positive just means an extra harmless
+    // once-per-session check. The captured ticketKey text carries a bit
+    // more weight (it also selects which profile's recallStrictness
+    // applies, see recall-nudge-stop.mjs), but the ceiling is still just
+    // "the wrong local settings value governs one Stop-hook decision" — no
+    // credentials or ticket data are read using this key, so a false
+    // positive here stays low-consequence, not narrowed further for now.
+    if (!result.ticketKey) {
+      const match = TICKET_KEY_RE.exec(JSON.stringify(entry));
+      if (match) {
+        result.sawTicketKey = true;
+        result.ticketKey = match[0];
+      }
+    }
 
     if (entry.type !== 'assistant') continue;
     const blocks = entry.message?.content;

package/skills/jtb/hooks/recall-nudge-stop.mjs

@@ -21,14 +21,13 @@
  * profile's recallStrictness — see recall-nudge-lib.mjs's shouldNag() doc
  * comment for the calibration and why strict doesn't widen this further.
  *
- * Known limitation: resolveProfile(null, { cwd }) below has no ticket key to
- * match against, so it falls through to cwd/projectPaths then the default
- * profile — unlike the brief-injection lever (resolveConnection(ticketKey, ...)
- * in profile-resolver.mjs), which resolves by ticket-key prefix when one is
- * available. For a multi-profile user these two levers can genuinely resolve
- * different profiles in the same session, so the recallStrictness setting
- * doesn't reliably reweight both together outside the single-profile case.
- * Not fixed here — see design spec §6 for the follow-up.
+ * resolveProfile() below is given scanTranscript()'s matched ticket key (not
+ * null), so it resolves by ticket-key prefix the same way the brief-injection
+ * lever (resolveConnection(ticketKey, ...) in profile-resolver.mjs) does —
+ * both levers now agree on which profile's recallStrictness applies for a
+ * multi-profile user. When no ticket key was seen, or it matches no profile's
+ * ticketPrefixes, this falls through to cwd/projectPaths then the default
+ * profile, same as before (backlog #12, design spec §6).
  */
 
 import { readStdinJson, readState, writeState, scanTranscript, hasRecentCapture, writeLastCaptureAt, shouldNag } from './recall-nudge-lib.mjs';
@@ -41,7 +40,7 @@ const cwd = input?.cwd ?? process.cwd();
 
 if (!sessionId || !transcriptPath) process.exit(0);
 
-const { sawTicketKey, sawRecallFlag, sawNoteAdd } = scanTranscript(transcriptPath);
+const { sawTicketKey, sawRecallFlag, sawNoteAdd, ticketKey } = scanTranscript(transcriptPath);
 
 // Refreshed on every check, independent of the once-per-session gate below —
 // a capture that happens AFTER this session already nagged once must still
@@ -51,7 +50,7 @@ if (sawNoteAdd) writeLastCaptureAt(cwd, Date.now());
 const state = readState(sessionId);
 if (state.stopChecked) process.exit(0); // already asked once this session — respect the answer
 
-const profile = resolveProfile(null, { cwd });
+const profile = resolveProfile(ticketKey, { cwd });
 const recallStrictness = normalizeRecallStrictness(profile?.recallStrictness);
 
 if (!shouldNag({ sawTicketKey, sawRecallFlag, sawNoteAdd, recallStrictness })) {

package/skills/jtb/scripts/lib/api-utils.mjs

@@ -3,7 +3,7 @@
  * Centralised here to avoid triplicating the regex and warning logic.
  */
 
-export const DEFAULT_API_BASE = 'https://api.ticketlens.app';
+export const DEFAULT_API_BASE = 'http://api.ticketlens.test';
 export const DEFAULT_SITE_BASE = 'https://ticketlens.app';
 
 // Matches localhost, 127.0.0.1, and any hostname ending in .test or .local,