ticketlens 0.38.47 → 0.38.49

package/README.md

@@ -294,10 +294,14 @@ Flag validation provides actionable hints:
 ticketlens compliance <TICKET-KEY>                # Check ticket requirements against local diff [Pro/Free 3/mo]
 ticketlens compliance <TICKET-KEY> --profile=acme # Specify a profile
 ticketlens compliance <TICKET-KEY> --plain        # Plain markdown output
+ticketlens compliance <TICKET-KEY> --consensus    # Multi-agent AI review instead of the local matcher [Pro]
+ticketlens compliance <TICKET-KEY> --consensus -y # Same, skipping the cost-confirmation prompt
 ```
 
 Runs the same compliance check as `ticketlens CNV1-2 --compliance` but as a dedicated subcommand — useful when you want to check compliance without fetching the full ticket brief. Free accounts get 3 checks per month; Pro is unlimited.
 
+`--consensus` (Pro) replaces the local deterministic matcher with independent reviews from your team's AI provider pool, reconciled by majority vote after a disagreement-triggered refinement round. Requires `ticketlens login` and a "consensus" role set up at Console > Admin > AI Roles, with 2+ providers attached from your team's shared registry (Console > Admin > AI Provider Pool — any title/key/endpoint/model, not a fixed list). This is the only compliance path that sends your diff off-machine — to TicketLens's backend, which fans out to each provider (keys are encrypted server-side and never sent to the CLI). The diff is scanned for secrets before anything is sent; a detected secret blocks the run with no AI call made. Prompts for confirmation before spending your team's API credits unless `-y`/`--yes` is passed.
+
 ---
 
 ### Compliance Ledger
@@ -456,7 +460,7 @@ Every note is scanned before saving — anything shaped like a real secret (API
 
 **Removing a note:** `ticketlens note delete --id="..." [--ticket=KEY]` removes a note from your local vault. Local only — if it was already pushed to a team, teammates who pulled it keep their copy; deleting it there too is a manager action from the Console (Admin > Recall).
 
-**Any MCP-capable AI harness:** `ticketlens mcp` starts a stdio [MCP](https://modelcontextprotocol.io) server exposing `fetch`, `triage`, `compliance`, `review`, `standup`, `pr`, `stats`, `issue_types`, `history`, `collisions`, `ledger`, `doctor`, `recall_add`, `recall_update`, `recall_delete`, `recall_search`, `ticket_comment`, `ticket_transition`, `ticket_assign`, `ticket_duplicates`, `ticket_link`, `ticket_update`, and `ticket_create` as native tools — every CLI action now has an MCP tool, so any MCP-compatible AI assistant, not just Claude Code, can call them directly instead of constructing a shell command. It's a thin adapter over the exact same code as the CLI commands above — same license gate per tool, same secret scan/local vault/tracker writes, same team sync — nothing is reimplemented. `fetch`, `doctor`, and `standup` are Free; `triage`'s base scan is Free with some options gated Pro/Team, same as the CLI (`ticketlens triage --help`); `compliance` and `pr` are Free, sharing a 3-checks/month cap on their requirements-coverage section, Pro unlimited; `review` is Free for branch/files/ticket context, with its coverage/focus section requiring Pro as a plain license check — it does not draw from that same monthly counter; `stats` is Free with a 7-day lookback cap, Pro extends it to 30 days, same split as the CLI (`ticketlens stats --help`); `issue_types` is Free and Jira-only — pre-fetches and caches a profile's real creatable projects and issue types ahead of a `ticket_create` attempt, sharing its cache with that tool's own reactive enrichment; Linear/GitHub profiles get a clear "not available" instead of an empty result; `history` reads local triage history only (zero network) and requires Pro; `collisions` requires `ticketlens login` (Console access) plus a Team license; `ledger` exports the local, signed compliance audit trail (zero network) and requires Pro; every other tool needs Pro. `recall_update` overwrites an existing Recall note's body — internal plumbing for the note quality loop, not typically called directly; its `attachments` array appends new files to whatever the note already has, same as `recall_add`'s, never replacing existing ones. `recall_delete` is destructive and local-vault-only — requires `confirm: true` alongside `id` to actually execute; there is no interactive y/N prompt under MCP (no real terminal to prompt against), so omitting it always fails rather than silently blocking. Point your harness's MCP config at it: `{ "command": "ticketlens", "args": ["mcp"] }` — or run `ticketlens mcp install` in a project to write that entry into its `.mcp.json` for you (creates the file if it doesn't exist, merges in if it does — never touches any other entry already there; `--dry-run` to preview first).
+**Any MCP-capable AI harness:** `ticketlens mcp` starts a stdio [MCP](https://modelcontextprotocol.io) server exposing `fetch`, `triage`, `compliance`, `review`, `standup`, `pr`, `stats`, `issue_types`, `history`, `collisions`, `ledger`, `doctor`, `recall_add`, `recall_update`, `recall_delete`, `recall_search`, `ticket_comment`, `ticket_transition`, `ticket_assign`, `ticket_duplicates`, `ticket_link`, `ticket_update`, and `ticket_create` as native tools — every CLI action now has an MCP tool, so any MCP-compatible AI assistant, not just Claude Code, can call them directly instead of constructing a shell command. It's a thin adapter over the exact same code as the CLI commands above — same license gate per tool, same secret scan/local vault/tracker writes, same team sync — nothing is reimplemented. `fetch`, `doctor`, and `standup` are Free; `triage`'s base scan is Free with some options gated Pro/Team, same as the CLI (`ticketlens triage --help`); `compliance` and `pr` are Free, sharing a 3-checks/month cap on their requirements-coverage section, Pro unlimited; `compliance` additionally accepts `consensus: true` (Pro) to replace the local deterministic matcher with a multi-agent AI review, run server-side against a "consensus" role configured at Console > Admin > AI Roles (2+ providers from the team's shared pool), and always implies `--yes` under MCP since there's no TTY for the cost-confirmation prompt; `review` is Free for branch/files/ticket context, with its coverage/focus section requiring Pro as a plain license check — it does not draw from that same monthly counter; `stats` is Free with a 7-day lookback cap, Pro extends it to 30 days, same split as the CLI (`ticketlens stats --help`); `issue_types` is Free and Jira-only — pre-fetches and caches a profile's real creatable projects and issue types ahead of a `ticket_create` attempt, sharing its cache with that tool's own reactive enrichment; Linear/GitHub profiles get a clear "not available" instead of an empty result; `history` reads local triage history only (zero network) and requires Pro; `collisions` requires `ticketlens login` (Console access) plus a Team license; `ledger` exports the local, signed compliance audit trail (zero network) and requires Pro; every other tool needs Pro. `recall_update` overwrites an existing Recall note's body — internal plumbing for the note quality loop, not typically called directly; its `attachments` array appends new files to whatever the note already has, same as `recall_add`'s, never replacing existing ones. `recall_delete` is destructive and local-vault-only — requires `confirm: true` alongside `id` to actually execute; there is no interactive y/N prompt under MCP (no real terminal to prompt against), so omitting it always fails rather than silently blocking. Point your harness's MCP config at it: `{ "command": "ticketlens", "args": ["mcp"] }` — or run `ticketlens mcp install` in a project to write that entry into its `.mcp.json` for you (creates the file if it doesn't exist, merges in if it does — never touches any other entry already there; `--dry-run` to preview first).
 
 `note add`'s save confirmation and `recall`'s search results are styled by default in a terminal; add `--plain` to either for bare, pipe-safe output. `recall` always shows each note's file ID (e.g. `[1784135399545-fe01c4.md]`) so you can open it directly (`cat ~/.ticketlens/recall/<PREFIX>/<id>`), or pass `--full` to print the full body content inline instead. Each result shows a relative time (`2h ago`, `3d ago`) rather than a bare date — the full-precision timestamp is always in the note file's own frontmatter.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ticketlens",
-  "version": "0.38.47",
+  "version": "0.38.49",
   "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/SKILL.md

@@ -1,4 +1,4 @@
-<!-- jtb-skill-version: 0.42.6 -->
+<!-- jtb-skill-version: 0.43.0 -->
 ---
 name: jtb
 description: Fetch a Jira ticket's full context (description, comments, linked issues, code references) and assemble a structured TicketBrief for implementation planning. Use when user types /jtb, mentions a Jira ticket key, or wants to plan work from a Jira ticket.
@@ -529,12 +529,21 @@ Use this evaluation order:
 3. **Manual checklist** — list each requirement for the developer to verify manually
 
 ### Privacy
-`--compliance` never sends data anywhere. The diff stays local. All analysis is performed by Claude Code within your session context.
+`--compliance` never sends data anywhere. The diff stays local. All analysis is performed by Claude Code within your session context. (The standalone command's `--consensus` opt-in below is the one exception — see that section.)
 
 ### Standalone command
 The same tier-gated check also runs as its own command — `ticketlens compliance PROJ-123` — independent of a full ticket fetch. This is what `ticketlens install-hooks` wires into a pre-push git hook (`ticketlens compliance "$KEY" || exit 1`, gated on a configurable coverage threshold). It shares the same `FREE_LIMIT`/Pro gate and the same compliance ledger as the `--compliance` flag above.
 
-If this harness has TicketLens's MCP server configured (a tool named `compliance` — often shown as `mcp__ticketlens__compliance` — visible in your tool list), prefer it over the bash form: same tier gate (Free: 3 checks/month, Pro: unlimited), same report — just no shell command to construct or stdout to parse. It accepts `ticket`/`profile`, matching the standalone command's arguments above.
+If this harness has TicketLens's MCP server configured (a tool named `compliance` — often shown as `mcp__ticketlens__compliance` — visible in your tool list), prefer it over the bash form: same tier gate (Free: 3 checks/month, Pro: unlimited), same report — just no shell command to construct or stdout to parse. It accepts `ticket`/`profile`/`consensus`, matching the standalone command's arguments below.
+
+### --consensus: Multi-Agent AI Review (standalone command only, Pro)
+`ticketlens compliance PROJ-123 --consensus` replaces the local deterministic keyword-diff matcher with a multi-agent AI review, for a higher-confidence check on requirements that plain keyword matching tends to misjudge (paraphrased requirements, negative conditions, cross-file logic).
+
+- **Requires `ticketlens login`** and a **consensus role** configured at Console > Admin > AI Roles, with 2+ providers attached from your team's shared registry (Console > Admin > AI Provider Pool — any title/key/endpoint/model your team wants, not a fixed vendor list; managed by team managers, selected per-role by each teammate). Provider keys are encrypted server-side and never sent to the CLI, so the actual AI calls run on TicketLens's backend, not from your machine directly — **this is the one path in TicketLens where the diff leaves your machine, to TicketLens's own backend, which fans out to each provider.** Before anything is sent, the diff runs through the same secret scanner Recall notes use — a detected secret blocks the run entirely, before any AI call.
+- Each attached provider independently reviews every requirement; where agents disagree, a second refinement round shows each agent its peers' (anonymized) verdicts and lets it reconsider; final verdicts are reconciled by majority vote, ties broken toward the stricter verdict. The report always shows the full per-agent breakdown, including any round-1→round-2 change.
+- Prompts for confirmation before making any API calls (real cost against your team's provider keys) unless `-y`/`--yes` is passed. Over MCP, `consensus: true` always implies yes (no TTY to prompt).
+- The now-superseded first version (0.38.48, same-day) read `~/.ticketlens/credentials.json` and called Anthropic/OpenAI/Groq directly from the CLI — deprecated before any stable release once the dynamic, Console-managed provider registry replaced it.
+- `Phase 2` (not yet built): non-`anthropic`/`openai_compatible` provider shapes beyond the two `provider_type`s the registry supports today. `Phase 1.5` (not yet built): scored iterative refinement with a stronger-model arbiter judging consensus acceptability, instead of plain majority vote.
 
 ### Ledger export
 `ticketlens ledger [--format=json|csv]` exports the same local, signed compliance ledger these checks write to — entirely local, no network call. `[Pro]`. If this harness has TicketLens's MCP server configured (a tool named `ledger` — often shown as `mcp__ticketlens__ledger` — visible in your tool list), prefer it over the bash form: same tier gate, same export, just no shell command to construct or stdout to parse. It accepts `format` (`json`/`csv`, defaults to `json`).

package/skills/jtb/scripts/fetch-ticket.mjs

@@ -33,6 +33,7 @@ import { apiBase } from './lib/api-utils.mjs';
 import { isLicensed, showUpgradePrompt, readLicense } from './lib/license.mjs';
 import { detectVcs } from './lib/vcs-detector.mjs';
 import { runComplianceCheck } from './lib/compliance-checker.mjs';
+import { runConsensusCheck } from './lib/consensus-checker.mjs';
 import { fetchRemoteLinks, buildAuthHeader } from './lib/jira-client.mjs';
 import { fetchConfluencePage } from './lib/confluence-client.mjs';
 
@@ -683,13 +684,18 @@ export async function run(args, envOrOpts = process.env, fetcher = globalThis.fe
     const codeRefsC = extractCodeReferences(allTextC);
     const briefC = assembleBrief(ticketC, codeRefsC);
 
-    const complianceRunner = opts.runComplianceCheck ?? runComplianceCheck;
+    const useConsensus = args.includes('--consensus');
+    const forceYes = args.includes('--yes') || args.includes('-y');
+    const complianceRunner = useConsensus
+      ? (opts.runConsensusCheck ?? runConsensusCheck)
+      : (opts.runComplianceCheck ?? runComplianceCheck);
     const complianceResult = await complianceRunner({
       brief: briefC,
       description: ticketC.description,
       ticketKey: ticketKeyArg,
       configDir: resolvedConfigDir,
       stream: errStream,
+      ...(useConsensus ? { forceYes } : {}),
     });
 
     if (complianceResult === null) {

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,

package/skills/jtb/scripts/lib/compliance-checker.mjs

@@ -19,7 +19,7 @@ export function statusColor(status, s) {
 // Shared with matchColor in ticket-command.mjs (duplicates' match-confidence
 // tiers) — same 70/50 thresholds, same green/yellow/dim vocabulary, applied
 // here to overall requirement coverage instead of a single match score.
-function coverageColor(pct, s) {
+export function coverageColor(pct, s) {
   if (pct >= 70) return s.green;
   if (pct >= 50) return s.yellow;
   return s.dim;

package/skills/jtb/scripts/lib/consensus-checker.mjs

@@ -0,0 +1,192 @@
+/**
+ * ticketlens compliance TICKET --consensus — thin client over POST /v1/consensus.
+ *
+ * Superseded local-BYOK version (0.38.48): read ~/.ticketlens/credentials.json,
+ * called Anthropic/OpenAI/Groq directly from the CLI. Deprecated same session it
+ * shipped — provider keys now live in the group-shared, dynamic AiProviderPool
+ * registry (Console > Admin > AI Provider Pool / AI Roles), encrypted server-side
+ * and never sent to the CLI, so the actual AI calls must happen on the backend.
+ * The diff and requirements still only ever leave the machine to reach
+ * TicketLens's own backend now (not straight to each vendor) — see
+ * ConsensusController.php for the round-1/round-2/reconcile algorithm, a direct
+ * port of what used to run here.
+ */
+import { isLicensed, showUpgradePrompt } from './license.mjs';
+import { extractRequirements } from './requirement-extractor.mjs';
+import { findLinkedCommits } from './commit-linker.mjs';
+import { readCliToken } from './cli-auth.mjs';
+import { apiBase } from './api-utils.mjs';
+import { DEFAULT_CONFIG_DIR } from './config.mjs';
+import { createStyler } from './ansi.mjs';
+import { STATUS_ICON, statusColor, coverageColor } from './compliance-checker.mjs';
+
+const ROLES_PATH = '/v1/ai-provider-roles';
+const CONSENSUS_PATH = '/v1/consensus';
+const ROLES_TIMEOUT_MS = 10_000;
+const CONSENSUS_TIMEOUT_MS = 90_000; // two AI rounds across N providers — real work, not a quick API call
+
+/** Interactive y/N cost-confirmation gate — same non-interactive fallback shape as confirmDestructive. */
+async function confirmCost(providerCount, { stream = process.stderr, stdin = process.stdin } = {}) {
+  if (!stdin.isTTY || !stdin.setRawMode) {
+    stream.write('  Non-interactive mode: pass --yes/-y to run --consensus without a prompt.\n');
+    return false;
+  }
+  stream.write(`  --consensus will run ${providerCount} AI review(s) via your team's provider pool. Continue?  y/N  `);
+  return new Promise(resolve => {
+    stdin.setRawMode(true);
+    stdin.resume();
+    stdin.once('data', buf => {
+      stdin.setRawMode(false);
+      stdin.pause();
+      const confirmed = buf.toString().toLowerCase() === 'y';
+      stream.write(confirmed ? 'y\n' : 'N\n');
+      resolve(confirmed);
+    });
+  });
+}
+
+function formatNoCriteriaReport(ticketKey, s) {
+  return [
+    '',
+    `  Consensus Compliance Check — ${s.brand(s.bold(ticketKey))}`,
+    `  ${s.dim('─'.repeat(50))}`,
+    '',
+    '  No acceptance criteria found in ticket description.',
+    '  Add a "Acceptance Criteria" section or Given/When/Then statements.',
+    '',
+  ].join('\n');
+}
+
+function formatConsensusReport({ ticketKey, results, perAgent, disagreedCount, s }) {
+  const lines = [
+    '',
+    `  Consensus Compliance Check — ${s.brand(s.bold(ticketKey))}`,
+    `  ${s.dim('─'.repeat(50))}`,
+    `  ${s.dim(`${perAgent.length} agents: ${perAgent.map(a => a.title).join(', ')}`)}`,
+    '',
+  ];
+
+  for (const { requirement, status } of results) {
+    const icon = statusColor(status, s)(STATUS_ICON[status] ?? '?');
+    lines.push(`  ${icon} ${requirement}`);
+  }
+
+  lines.push('');
+  const found = results.filter(r => r.status === 'FOUND').length;
+  const coveragePercent = Math.round(((found + results.filter(r => r.status === 'PARTIAL').length * 0.5) / results.length) * 100);
+  lines.push(`  Coverage: ${coverageColor(coveragePercent, s)(`${coveragePercent}%`)}  (${found}/${results.length} requirements found)`);
+  if (disagreedCount > 0) {
+    lines.push(`  ${s.dim(`${disagreedCount} requirement(s) needed a refinement round (agents initially disagreed).`)}`);
+  }
+  lines.push('');
+  lines.push(`  ${s.bold('Per-agent breakdown:')}`);
+  for (const { title, verdicts, round1Verdicts } of perAgent) {
+    const parts = verdicts.map((v, i) => (round1Verdicts[i] !== v ? `${round1Verdicts[i]}→${v}` : v));
+    lines.push(`  ${s.dim(title)}: ${parts.join(', ')}`);
+  }
+  lines.push('');
+
+  return { report: lines.join('\n'), coveragePercent };
+}
+
+async function fetchJson(url, { fetcher, timeoutMs, ...init }) {
+  const res = await fetcher(url, { ...init, signal: AbortSignal.timeout(timeoutMs) });
+  let body = null;
+  try { body = await res.json(); } catch { /* non-JSON error page — body stays null */ }
+  return { ok: res.ok, status: res.status, body };
+}
+
+export async function runConsensusCheck({
+  brief,
+  description = null,
+  ticketKey,
+  configDir = DEFAULT_CONFIG_DIR,
+  stream = process.stderr,
+  outStream = process.stdout,
+  forceYes = false,
+  stdin = process.stdin,
+  cliToken,
+  isLicensedFn = isLicensed,
+  showUpgradeFn = showUpgradePrompt,
+  extractRequirementsFn = extractRequirements,
+  findLinkedCommitsFn = findLinkedCommits,
+  confirmCostFn = confirmCost,
+  readCliTokenFn = readCliToken,
+  fetcher = globalThis.fetch,
+}) {
+  if (!isLicensedFn('pro', configDir)) {
+    showUpgradeFn('pro', '--consensus', { stream });
+    return null;
+  }
+
+  const requirements = extractRequirementsFn(description ?? brief);
+  const s = createStyler({ isTTY: outStream.isTTY });
+
+  if (requirements.length === 0) {
+    return { report: formatNoCriteriaReport(ticketKey, s), results: [], coveragePercent: 0, noCriteria: true };
+  }
+
+  const token = cliToken ?? readCliTokenFn(configDir);
+  if (!token) {
+    stream.write('  ✖ --consensus requires a login. Run: ticketlens login\n');
+    return null;
+  }
+
+  // Pre-flight: know the provider count before prompting for cost, and give a
+  // specific, actionable error before ever touching /v1/consensus — the
+  // backend re-validates all of this too, this is purely a faster/clearer UX path.
+  const rolesRes = await fetchJson(`${apiBase()}${ROLES_PATH}`, {
+    fetcher, timeoutMs: ROLES_TIMEOUT_MS,
+    headers: { Authorization: `Bearer ${token}`, Accept: 'application/json' },
+  }).catch(err => ({ ok: false, status: 0, body: null, networkError: err }));
+
+  if (!rolesRes.ok) {
+    stream.write('  ✖ Could not reach TicketLens to check your consensus role. Try again, or check your connection.\n');
+    return null;
+  }
+
+  const consensusRole = (rolesRes.body?.roles ?? []).find(r => r.kind === 'consensus');
+  if (!consensusRole) {
+    stream.write('  ✖ No consensus role configured. Set one up in Console > Admin > AI Providers.\n');
+    return null;
+  }
+  if (consensusRole.providers.length < 2) {
+    stream.write(`  ✖ Your consensus role needs at least 2 providers — currently has ${consensusRole.providers.length}. Add more in Console > Admin > AI Roles.\n`);
+    return null;
+  }
+
+  if (!forceYes) {
+    const proceed = await confirmCostFn(consensusRole.providers.length, { stream, stdin });
+    if (!proceed) {
+      stream.write('  Aborted — no request made.\n');
+      return null;
+    }
+  }
+
+  const { diff } = findLinkedCommitsFn(ticketKey, { cwd: process.cwd() });
+
+  const runRes = await fetchJson(`${apiBase()}${CONSENSUS_PATH}`, {
+    fetcher, timeoutMs: CONSENSUS_TIMEOUT_MS,
+    method: 'POST',
+    headers: { 'Content-Type': 'application/json', Authorization: `Bearer ${token}`, Accept: 'application/json' },
+    body: JSON.stringify({ ticketKey, diff, requirements }),
+  }).catch(err => ({ ok: false, status: 0, body: null, networkError: err }));
+
+  if (!runRes.ok) {
+    const msg = runRes.body?.error
+      ?? (runRes.networkError?.name === 'TimeoutError' ? 'Request timed out.' : runRes.networkError?.message)
+      ?? `HTTP ${runRes.status}`;
+    stream.write(`  ✖ ${msg}\n`);
+    return null;
+  }
+
+  for (const warning of runRes.body.warnings ?? []) {
+    stream.write(`  Warning: ${warning}\n`);
+  }
+
+  const { report, coveragePercent } = formatConsensusReport({
+    ticketKey, results: runRes.body.results, perAgent: runRes.body.perAgent, disagreedCount: runRes.body.disagreedCount, s,
+  });
+
+  return { report, results: runRes.body.results, coveragePercent, noCriteria: false };
+}

package/skills/jtb/scripts/lib/help.mjs

@@ -658,6 +658,9 @@ export function printMcpHelp({ stream = process.stdout } = {}) {
     `  ${s.cyan('fetch')}, ${s.cyan('doctor')}, and ${s.cyan('standup')} are Free; ${s.cyan('triage')} is Free with some Pro/Team-gated`,
     `  options (see ${s.cyan('ticketlens triage --help')}); ${s.cyan('compliance')} and ${s.cyan('pr')} are Free, sharing a`,
     `  3-checks/month cap on their requirements-coverage section, Pro unlimited;`,
+    `  ${s.cyan('compliance')}'s \`consensus: true\` (Pro) runs a multi-agent review server-side against`,
+    `  a "consensus" role configured at Console > Admin > AI Roles, and always implies`,
+    `  \`--yes\` under MCP, since there is no TTY for the cost-confirmation prompt;`,
     `  ${s.cyan('review')} is Free for branch/files/ticket context — its coverage/focus section`,
     `  requires Pro as a plain license check, not a draw on that same counter;`,
     `  ${s.cyan('stats')} is Free with a 7-day lookback, Pro extends it to 30 days, same split`,
@@ -1089,7 +1092,7 @@ export function printComplianceHelp({ stream = process.stdout } = {}) {
   const s = createStyler({ isTTY: stream.isTTY });
   const lines = [
     '',
-    `  ${s.bold(s.brand('ticketlens'))} ${s.bold('compliance')} ${s.dim('<TICKET-KEY> [--profile=NAME]')}  ${s.dim('[Pro/Free 3/mo]')}`,
+    `  ${s.bold(s.brand('ticketlens'))} ${s.bold('compliance')} ${s.dim('<TICKET-KEY> [--profile=NAME] [--consensus [-y]]')}  ${s.dim('[Pro/Free 3/mo]')}`,
     '',
     `  Check your current branch's diff against the ticket's requirements.`,
     `  Extracts candidate requirements from the ticket description and diffs`,
@@ -1102,12 +1105,23 @@ export function printComplianceHelp({ stream = process.stdout } = {}) {
     `  ${s.bold('OPTIONS')}`,
     '',
     `    ${s.brand('--profile')}=${s.dim('NAME')}  Use a specific Jira profile`,
+    `    ${s.brand('--consensus')}      Replace the local matcher with a multi-agent AI review ${s.dim('[Pro]')}`,
+    `    ${s.dim('               ')}    — requires ${s.cyan('ticketlens login')} and a "consensus" role configured`,
+    `    ${s.dim('               ')}    at Console > Admin > AI Roles (2+ providers from your team's`,
+    `    ${s.dim('               ')}    shared pool, Console > Admin > AI Provider Pool). Runs server-side`,
+    `    ${s.dim('               ')}    — the diff and requirements are sent to TicketLens's backend,`,
+    `    ${s.dim('               ')}    scanned for secrets first, then to each provider. Reconciles`,
+    `    ${s.dim('               ')}    disagreements with a refinement round, then a majority vote.`,
+    `    ${s.dim('               ')}    Prompts for confirmation before spending your team's API credits.`,
+    `    ${s.brand('-y')}, ${s.brand('--yes')}       Skip the --consensus cost confirmation prompt`,
     `    ${s.brand('-h')}, ${s.brand('--help')}   Show this help`,
     '',
     `  ${s.bold('EXAMPLES')}`,
     '',
     `    ${s.dim('$')} ticketlens compliance PROJ-123`,
     `    ${s.dim('$')} ticketlens compliance PROJ-123 --profile=myteam`,
+    `    ${s.dim('$')} ticketlens compliance PROJ-123 --consensus`,
+    `    ${s.dim('$')} ticketlens compliance PROJ-123 --consensus -y`,
     '',
   ];
   stream.write(lines.join('\n') + '\n');

package/skills/jtb/scripts/lib/mcp-server.mjs

@@ -174,9 +174,12 @@ async function callTriage(args, { configDir, runTriageFn }) {
  * printErr through it before this tool existed — see the fetch tool's own
  * shipping notes for why that treatment was deferred per-tool).
  */
-function buildComplianceArgs({ ticket, profile }) {
+function buildComplianceArgs({ ticket, profile, consensus }) {
   const args = ['compliance', ticket];
   if (profile) args.push(`--profile=${profile}`);
+  // MCP has no TTY to answer the interactive cost-confirmation prompt, so --consensus
+  // always implies --yes here — the caller already opted in by setting consensus: true.
+  if (consensus) args.push('--consensus', '--yes');
   return args;
 }
 

package/skills/jtb/scripts/lib/mcp-tool-schemas.mjs

@@ -42,12 +42,13 @@ export const TOOLS = [
   },
   {
     name: 'compliance',
-    description: 'Check a ticket\'s acceptance-criteria coverage against the current git diff — extracts requirements from the ticket description, matches them against code changes, and reports a coverage percentage plus what\'s missing. Read-only; the same check `ticketlens install-hooks` runs automatically. Free tier: 3 checks per month; TicketLens Pro removes the limit.',
+    description: 'Check a ticket\'s acceptance-criteria coverage against the current git diff — extracts requirements from the ticket description, matches them against code changes, and reports a coverage percentage plus what\'s missing. Read-only; the same check `ticketlens install-hooks` runs automatically. Free tier: 3 checks per month; TicketLens Pro removes the limit. Set `consensus: true` (TicketLens Pro) to replace the local matcher with a multi-agent AI review, run server-side — requires `ticketlens login` and a "consensus" role configured at Console > Admin > AI Roles (2+ providers attached from the team\'s shared pool, Console > Admin > AI Provider Pool). The diff is scanned for secrets before it is sent. Automatically skips the interactive cost-confirmation prompt since MCP has no TTY.',
     inputSchema: {
       type: 'object',
       properties: {
         ticket: { type: 'string', description: 'Ticket key, e.g. PROJ-123.' },
         profile: { type: 'string', description: 'Connection profile to target, overriding folder-based inference and the default profile.' },
+        consensus: { type: 'boolean', description: 'Use multi-agent AI consensus instead of the local deterministic matcher. Requires TicketLens Pro and 2+ configured AI provider keys.' },
       },
       required: ['ticket'],
     },

package/skills/jtb/scripts/lib/summarizer.mjs

@@ -116,7 +116,10 @@ async function callGroq({ brief, apiKey, fetcher, timeoutMs, prompt, maxTokens }
       'Authorization': `Bearer ${apiKey}`,
     },
     body: JSON.stringify({
-      model: 'llama-3.1-8b-instant',
+      // llama-3.1-8b-instant was decommissioned by Groq 2026-08-16 (HTTP 404 on
+      // every call since) — openai/gpt-oss-20b is Groq's own recommended
+      // replacement. See console.groq.com/docs/deprecations.
+      model: 'openai/gpt-oss-20b',
       max_tokens: maxTokens,
       messages: [{ role: 'user', content: prompt + brief }],
     }),