ticketlens 0.38.55 → 0.38.57

package/README.md

@@ -1099,14 +1099,16 @@ npm test
 See [ROADMAP.md](ROADMAP.md) for the full plan.
 
 Recently shipped:
-- **Prefix & status pickers** (`ticketlens init` / `config`, v0.12.0) — ticket prefixes and triage statuses are picked from your Jira instance's live project/status lists via multi-select; editing pre-selects current values, unchecking removes them, and stale entries are flagged `(not on server)`
-- **Collision detection** (`ticketlens collisions`) — shows which files your branch shares with teammates' in-flight branches; `--push` auto-sends git branch data to the team snapshot. Team tier
-- **Shareable triage snapshot** (`ticketlens triage --share`) — generates a 24h signed URL; recipients open it in any browser, no account needed. Team tier
-- **Compliance push** (`ticketlens triage --push`) — enriches the team snapshot with per-ticket compliance status and coverage from the local ledger. Pro tier
-- **"TicketLens for PRs"** (`ticketlens review`) — assembles a code-review context brief from your current branch: linked tickets, changed files, and ticket context in one brief
-- **Confluence pages** — linked Confluence pages fetched automatically and included in the brief; origin-validated, non-fatal, capped at 10 pages
-- **Linear support** — `ticketlens init` → Linear; connects via GraphQL API key, fetches tickets, triage, and statuses
-- **GitHub Issues support** — `ticketlens init` → GitHub Issues; PAT-based, same normalized ticket shape
+- **Multi-agent AI consensus compliance** (`ticketlens compliance TICKET --consensus`) — routes requirements-vs-diff review through your team's AI provider pool, majority vote after a refinement round. Pro tier
+- **Dynamic AI Provider Registry** (Console > Admin > AI Provider Pool / AI Roles) — manage arbitrary AI providers and role-based routing, no fixed vendor list
+- **Full MCP tool coverage** (`ticketlens mcp`) — every CLI action (fetch, triage, compliance, recall, ticket writes) has a matching MCP tool
+- **`ticketlens issue-types`** — pre-fetches and caches a project's valid issue types, speeds up `ticket_create`
+- **Recall team sync** (`note add` / `recall`) — shared notes with Console verification, attachments, configurable capture strictness. Pro/Team tier
+- **`ticketlens doctor`** — diagnoses profile/connection/license/MCP problems; `--fix` for common issues
+- **Ticket write-back** (`comment`/`transition`/`assign`/`duplicates`/`link`/`update`/`create`) — write directly to Jira/GitHub/Linear from the CLI. Pro tier
+- **Stale status detection** — flags tickets stuck in a status too long, team-configurable thresholds. Pro tier
+- **Shared team Jira config** (Console > Admin > Jira) — manager sets the connection once, team inherits it. Pro+ tier
+- **Slack/Teams alerts** — needs-response, aging, and compliance-gap alerts plus a weekly digest. Team tier
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ticketlens",
-  "version": "0.38.55",
+  "version": "0.38.57",
   "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-auto-capture.mjs

@@ -33,6 +33,7 @@ import { buildCaptureExcerpt, privateTmpDir } from './recall-nudge-lib.mjs';
 import { autoCapture } from '../scripts/lib/summarizer.mjs';
 import { runNoteAdd } from '../scripts/lib/note-command.mjs';
 import { DEFAULT_CONFIG_DIR } from '../scripts/lib/config.mjs';
+import { apiBase } from '../scripts/lib/api-utils.mjs';
 
 /** Buffers stream.write() calls instead of touching a real stream — same shape mcp-server.mjs's own capturingStream() uses, this process has no real stdout/stderr worth writing to. */
 function capturingStream() {
@@ -40,9 +41,12 @@ function capturingStream() {
   return { write(s) { parts.push(s); return true; }, get text() { return parts.join(''); } };
 }
 
+// backlog #33: every outcome logs its resolved backend URL — "Unauthorized"/
+// "not logged in" reports had no way to attribute which backend was hit
+// (ngrok tunnel rotation and local-dev fallback both silently swap it).
 function logLine(message) {
   try {
-    const line = `${new Date().toISOString()} ${message}\n`;
+    const line = `${new Date().toISOString()} ${message} [api=${apiBase()}]\n`;
     appendFileSync(join(privateTmpDir(), 'auto-capture.log'), line);
   } catch { /* best-effort — losing a debug log line is not worth failing over */ }
 }
@@ -85,7 +89,7 @@ export async function runAutoCapture({
   try {
     result = await autoCaptureFn({ excerpt, ticketKey, cliToken });
   } catch (err) {
-    logLine(`error: ${err.message}`);
+    logLine(`error: ${err.message}${err.status ? ` (status=${err.status})` : ''}`);
     return { outcome: 'error', error: err.message };
   }
 

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

@@ -68,8 +68,10 @@ export function writeState(sessionId, state) {
   } catch { /* best-effort — a lost nudge counter is not worth failing the hook over */ }
 }
 
-// Two hours — how long a real capture in one directory counts as "recent
-// enough" to skip the Stop hook's nag, even from a brand-new session_id.
+// Two hours of IDLE time — how long a real capture in one directory counts as
+// "recent enough" to skip the Stop hook's nag, even from a brand-new session_id.
+// Sliding, not fixed: ongoing ticket work renews the marker (see
+// recall-nudge-stop.mjs, backlog #24), so only a full idle window lets it lapse.
 export const CAPTURE_FRESHNESS_MS = 2 * 60 * 60 * 1000;
 
 /**

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

@@ -24,7 +24,9 @@
  * the same boundary for a DISMISSED nag: without it, a session that already
  * got its one nag and was told "genuinely nothing qualified" would nag
  * again after the next compaction/resume rollover, since that dismissal
- * was never recorded anywhere — only a real capture was.
+ * was never recorded anywhere — only a real capture was. Both markers slide:
+ * ongoing ticket work renews them while fresh, so only a full idle window
+ * (CAPTURE_FRESHNESS_MS) lets either lapse (backlog #24).
  *
  * Which of the two cases above actually blocks is governed by the effective
  * recallStrictness — the active profile's own explicit config-set value, or
@@ -102,7 +104,19 @@ if (isLicensed('pro') && cliToken && !hasRecentAutoCaptureAttempt(cwd)) {
 // Refreshed on every check, independent of the once-per-session gate below —
 // a capture that happens AFTER this session already nagged once must still
 // update the marker, or a later session_id rollover would find it stale.
-if (sawNoteAdd) writeLastCaptureAt(cwd, Date.now());
+//
+// Sliding window (backlog #24, 7th report): ongoing ticket work also renews a
+// marker that is still fresh, so it measures idle time, not time since the
+// last capture/nag. A fixed window expired mid-work (capture 17:48, nag 19:48
+// in a session with 23 silent Stops before it) and falsely claimed "nothing
+// was ever captured". Only a session that could itself nag (fetch + mutation)
+// renews, so non-ticket work and read-only lookups in the same cwd can't keep
+// a marker alive; a lapsed marker is never revived. Accepted trade-off: such
+// sessions chained in one cwd with gaps under the window keep suppressing.
+const now = Date.now();
+const isActiveTicketWork = sawFetch && sawMutatingAction;
+if (sawNoteAdd || (isActiveTicketWork && hasRecentCapture(cwd, now))) writeLastCaptureAt(cwd, now);
+if (isActiveTicketWork && hasRecentNag(cwd, now)) writeLastNagAt(cwd, now);
 
 const state = readState(sessionId);
 if (state.stopChecked) process.exit(0); // already asked once this session — respect the answer

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 = 'http://api.ticketlens.test';
+export const DEFAULT_API_BASE = 'https://api.ticketlens.app';
 export const DEFAULT_SITE_BASE = 'https://ticketlens.app';
 
 // Matches localhost, 127.0.0.1, and any hostname ending in .test or .local,