srclawyer 0.6.2 → 0.6.3

package/README.md

@@ -2,7 +2,7 @@
 
 Static analysis engine that derives privacy policy documentation directly from source code, and keeps it in sync as the code changes.
 
-> **Beta.** The CLI (`init`, `scan`), the Layer 1 static analysis engine, and markdown privacy policy generation all work today. JavaScript/TypeScript (Express, Next.js) is the most tested path; Python (Flask) is newer, with FastAPI and Django explicitly detected and flagged as unsupported rather than silently skipped — see [Supported languages and frameworks](#supported-languages-and-frameworks) and [Known gaps](#known-gaps) below. LLM-assisted reasoning for ambiguous findings (Layer 2) is available now under the bring-your-own-key tier, documented below as one optional step in `init` — a managed (hosted) tier is planned but not yet available.
+> **Beta.** The CLI (`init`, `scan`), the Layer 1 static analysis engine, and markdown privacy policy generation all work today. JavaScript/TypeScript (Express, Next.js) is the most tested path; Python (Flask) is newer, with FastAPI and Django explicitly detected and flagged as unsupported rather than silently skipped — see [Supported languages and frameworks](#supported-languages-and-frameworks) and [Known gaps](#known-gaps) below. Optional AI-assisted review of ambiguous findings (Layer 2) is available as an advanced option with your own Anthropic API key — see [AI-assisted review](#ai-assisted-review-advanced) below; a hosted tier that needs no key is planned but not yet available.
 >
 > Scanning is manual-only (`srclawyer scan`, run on demand) — this is the free/solo tier's permanent behavior, not a placeholder. Automatic CI/CD updating (a scan that runs itself on every PR, or on a schedule) isn't available yet; it's scoped for a future paid/team tier. See `PRODUCT_SPEC.md` Section 8.5 for the plan.
 
@@ -93,9 +93,38 @@ Every finding traces back to a file and line (`src/engine/types.ts#Finding`).
 - **Flask support covers direct request reads and same-function aliases only.** It detects `request.form[...]`, `request.args.get(...)`, `request.json[...]` and the like, plus one assignment hop within a function (`data = request.get_json()`, then `data['x']`). Form classes — Flask-WTF/WTForms `FlaskForm` subclasses with `StringField`/`PasswordField` declarations read via `form.email.data` — are not detected, and neither are fields rendered by template helpers such as `{{ form.email() }}`. A Flask app that collects data through WTForms may therefore show fewer collected fields than it actually has.
 - **Server-side template syntax inside HTML is not analyzed.** Jinja, Django, ERB and similar delimiters (`{{`, `{%`, `<%`, `{#`) are not interpreted: an inline `<script>` that isn't valid JavaScript until the template engine runs is skipped (listed in `--json` as `template-syntax`, with a one-line note), and form fields that a template generates rather than spells out as `<input>` tags are not seen.
 
+## AI-assisted review (advanced)
+
+Off by default, and not part of `init`'s questions. `scan` already surfaces anything it can't confidently classify under "Items Requiring Manual Review"; with AI-assisted review enabled it first asks Anthropic, under **your own API key**, to classify each such item. For each item Anthropic receives: an opaque per-scan id, the item's data category, its short description (which names the field), and the one source line it was found on with secrets redacted — plus a fixed instruction prompt and the model name. **Not sent:** the file's path, its line number, or any surrounding code (the source line itself goes as written, apart from redacted secrets). Items the model declines stay in the manual-review list, and items involving children's data are never auto-resolved.
+
+Enable it when creating the config:
+
+```bash
+srclawyer init --enable-ai-review                              # asks which env var holds your key (default ANTHROPIC_API_KEY)
+srclawyer init --enable-ai-review --api-key-env-var MY_KEY     # same, non-interactive
+export ANTHROPIC_API_KEY=...                                   # or whichever name you chose
+srclawyer scan
+```
+
+or, for an existing config (`init` never overwrites one), add this to `.srclawyer.config.yml` by hand:
+
+```yaml
+tier: byok
+llm:
+  provider: anthropic
+  apiKeyEnvVar: ANTHROPIC_API_KEY
+```
+
+Only the variable's *name* is stored in the config — the key itself is never written to disk. When it's enabled, `scan` prints a notice that redacted snippets are being sent to Anthropic; `scan --no-llm` skips it for a single run. A hosted tier, where SrcLawyer supplies the model access and no key is needed, is planned but not yet available: a config with `tier: managed` gets a clear "not available yet" error rather than silently doing nothing.
+
 ## Network calls
 
-Detection itself is fully local and offline — no code leaves your machine for pattern matching. Once detection completes, `scan` makes one batched network call to grade the confidence of what it found (field names and derived yes/no signals only, never source code), and, for scans that use Zod schemas as request validators, one additional call sending a small redacted code fragment. This runs on every scan regardless of tier and is unrelated to the separate, optional LLM-assisted (Layer 2) reasoning described above. See `PRODUCT_SPEC.md`'s "Static Analysis Depth" section for the precise wording.
+Detection itself is fully local and offline — no code leaves your machine for pattern matching. Once detection completes, every `scan` makes these calls to a SrcLawyer-run service:
+
+- **Confidence grading** (one batched call). For each detected field: an opaque per-scan id (`f0`, `f1`, …), the data category its name maps to (e.g. `email`), and three derived signals — whether the name is ambiguous, whether it was read directly from the request in code (rather than inferred from a type), and how many confidently classified fields sit alongside it. **Not sent:** the field's name, file paths, line numbers, or source code.
+- **Zod-schema detection** (one more batched call, only for scans where Zod schemas appear to validate request data). Per schema: an opaque id (`c0`, `c1`, …) and a small, secret-redacted code fragment — the schema, the call that validates with it, and the imports it uses, as source text (so it includes the schema's field names and those import specifiers). **Not sent:** the schema's file path or line number.
+
+Ids are numbered per scan; the mapping back to files and lines never leaves your machine. Requests carry a shared API key (`x-api-key`) and the standard headers Node.js adds (such as `user-agent: node`); there is no install ID, machine information, or telemetry. These calls run on every scan, with or without the optional [AI-assisted review](#ai-assisted-review-advanced), and are separate from it. See `PRODUCT_SPEC.md`'s "Static Analysis Depth" section for the same wording.
 
 ## Secret handling
 

package/dist/cli.js

@@ -3,7 +3,7 @@ import { readFileSync } from "node:fs";
 import { dirname, join } from "node:path";
 import { fileURLToPath } from "node:url";
 import { Command } from "commander";
-import { runInit } from "./commands/init.js";
+import { isValidEnvVarName, runInit } from "./commands/init.js";
 import { runScan } from "./commands/scan.js";
 // Read from package.json rather than hardcoding, so --version can't silently drift out of sync with
 // the published version the way a literal string did through every prior release.
@@ -37,7 +37,15 @@ program
     .option("--minimum-age <number>", "minimum age required to use this product")
     .option("--sends-data-to-ai-services", "declare that user data is sent to third-party AI services")
     .option("--no-sends-data-to-ai-services", "declare that user data is not sent to third-party AI services")
+    .option("--enable-ai-review", "advanced: enable optional AI-assisted review of ambiguous findings with your own Anthropic API key (sets tier: byok)")
+    .option("--api-key-env-var <name>", "with --enable-ai-review: the environment variable holding your Anthropic API key (default ANTHROPIC_API_KEY)")
     .action(async (opts) => {
+    if (opts.apiKeyEnvVar !== undefined) {
+        if (!opts.enableAiReview)
+            program.error("error: --api-key-env-var requires --enable-ai-review");
+        if (!isValidEnvVarName(opts.apiKeyEnvVar))
+            program.error(`error: --api-key-env-var must be a valid environment variable name (got "${opts.apiKeyEnvVar}")`);
+    }
     let minimumAge;
     if (opts.minimumAge !== undefined) {
         const parsed = Number(opts.minimumAge);
@@ -60,6 +68,8 @@ program
         accountDeletionInstructions: opts.accountDeletionInstructions,
         minimumAge,
         sendsDataToAiServices: opts.sendsDataToAiServices,
+        enableAiReview: opts.enableAiReview,
+        apiKeyEnvVar: opts.apiKeyEnvVar,
     });
 });
 program

package/dist/cloud/protectedLogicClient.js

@@ -39,6 +39,22 @@ function chunkByCountAndBytes(items, maxCount, maxBytes) {
         batches.push(current);
     return batches;
 }
+/**
+ * The one place ids are assigned for anything sent to the Worker. Callers identify items by their own
+ * ids (finding ids embed file path, line and field name; Zod candidate ids ARE the file path), but
+ * those never leave this process: every item goes out under an opaque per-scan id (f0, f1, ... /
+ * c0, c1, ...), unique across all batches, and responses are mapped back here. The Worker only echoes
+ * ids (it never parses them), so nothing about the wire format depends on their shape.
+ */
+function toOpaque(items, prefix) {
+    const originalByOpaque = new Map();
+    const wire = items.map((item, i) => {
+        const opaque = `${prefix}${i}`;
+        originalByOpaque.set(opaque, item.id);
+        return { ...item, id: opaque };
+    });
+    return { wire, originalByOpaque };
+}
 function sleep(ms) {
     return new Promise((resolve) => setTimeout(resolve, ms));
 }
@@ -79,11 +95,15 @@ export async function scoreFields(items, options) {
     const batchMaxBytes = options.batchMaxBytes ?? DEFAULT_BATCH_MAX_BYTES;
     const timeoutMs = options.timeoutMs ?? DEFAULT_TIMEOUT_MS;
     let error = null;
-    for (const batch of chunkByCountAndBytes(items, batchSize, batchMaxBytes)) {
+    const { wire, originalByOpaque } = toOpaque(items, "f");
+    for (const batch of chunkByCountAndBytes(wire, batchSize, batchMaxBytes)) {
         try {
             const response = await postJson(`${options.baseUrl}/v1/score-fields`, options.apiKey, { fields: batch }, timeoutMs);
-            for (const result of response.results)
-                results.set(result.id, result);
+            for (const result of response.results) {
+                const original = originalByOpaque.get(result.id);
+                if (original !== undefined)
+                    results.set(original, { ...result, id: original });
+            }
         }
         catch (err) {
             error = err instanceof Error ? err.message : String(err);
@@ -99,11 +119,15 @@ export async function detectZodSchemas(items, options) {
     const batchMaxBytes = options.batchMaxBytes ?? DEFAULT_BATCH_MAX_BYTES;
     const timeoutMs = options.timeoutMs ?? DEFAULT_TIMEOUT_MS;
     let error = null;
-    for (const batch of chunkByCountAndBytes(items, batchSize, batchMaxBytes)) {
+    const { wire, originalByOpaque } = toOpaque(items, "c");
+    for (const batch of chunkByCountAndBytes(wire, batchSize, batchMaxBytes)) {
         try {
             const response = await postJson(`${options.baseUrl}/v1/detect-zod-schema`, options.apiKey, { candidates: batch }, timeoutMs);
-            for (const result of response.results)
-                results.set(result.id, result);
+            for (const result of response.results) {
+                const original = originalByOpaque.get(result.id);
+                if (original !== undefined)
+                    results.set(original, { ...result, id: original });
+            }
         }
         catch (err) {
             error = err instanceof Error ? err.message : String(err);

package/dist/commands/init.d.ts

@@ -12,5 +12,10 @@ export interface InitFlags {
     accountDeletionInstructions?: string;
     minimumAge?: number;
     sendsDataToAiServices?: boolean;
+    /** Advanced, opt-in: sets tier: byok. Never asked about in the default flow. */
+    enableAiReview?: boolean;
+    apiKeyEnvVar?: string;
 }
+export declare const DEFAULT_API_KEY_ENV_VAR = "ANTHROPIC_API_KEY";
+export declare function isValidEnvVarName(name: string): boolean;
 export declare function runInit(root: string, flags?: InitFlags): Promise<void>;

package/dist/commands/init.js

@@ -2,8 +2,13 @@ import { existsSync, readFileSync } from "node:fs";
 import { join } from "node:path";
 import { createInterface } from "node:readline/promises";
 import { CONFIG_FILENAME, DEFAULT_CONFIG, configPath, hasUnmigratedLegacyConfig, legacyConfigMessage, writeConfig, } from "../config/config.js";
-import { NETWORK_CALLS_NOTICE } from "../policy/legalNotices.js";
+import { NETWORK_CALLS_NOTICE, byokNetworkNotice } from "../policy/legalNotices.js";
 import { runScan } from "./scan.js";
+export const DEFAULT_API_KEY_ENV_VAR = "ANTHROPIC_API_KEY";
+const ENV_VAR_NAME = /^[A-Za-z_][A-Za-z0-9_]*$/;
+export function isValidEnvVarName(name) {
+    return ENV_VAR_NAME.test(name);
+}
 function guessIndustry(root) {
     const pkgPath = join(root, "package.json");
     if (!existsSync(pkgPath))
@@ -132,17 +137,22 @@ export async function runInit(root, flags = {}) {
     // Deliberately about the SCANNED PRODUCT's own behavior (does it send its end-users' data to AI
     // services as part of its own functionality) -- not about SrcLawyer's own, separately-documented
     // BYOK network calls described in NETWORK_CALLS_NOTICE above.
-    const sendsDataToAiServices = await resolveField(flags.sendsDataToAiServices, gateYes, () => askYesNoOptional(lines, "Does this product send user data to third-party AI services (e.g. OpenAI, Anthropic) as part of its own functionality?"));
-    // "managed" is deliberately not offered here -- it's a real SrcLawyerTier value and config.ts/
-    // resolveProviderForTier.ts both still support it fully (a hand-edited config with tier: managed
-    // still gets a clear, accurate error at scan time), but there's no advertised path to it from this
-    // prompt, so a tester reading the choices here can't select a dead end during setup.
-    const enableByokRaw = await ask(lines, "Enable optional AI-assisted review with your own Anthropic key? (advanced)", "n");
-    const tier = /^y(es)?$/i.test(enableByokRaw.trim()) ? "byok" : "free";
+    const sendsDataToAiServices = await resolveField(flags.sendsDataToAiServices, gateYes, () => askYesNoOptional(lines, "Does this product send user data to third-party AI services as part of its own functionality?"));
+    // AI-assisted review (tier: byok) is an advanced opt-in, reached only via --enable-ai-review (or by
+    // hand-editing the config) -- the default flow never asks about it or mentions an API key. "managed"
+    // is likewise not offered here: it's still a real SrcLawyerTier value that config.ts and
+    // resolveProviderForTier.ts support, so a hand-edited tier: managed keeps its clear "not available
+    // yet" error at scan time, but nothing advertises a path to it.
+    const tier = flags.enableAiReview ? "byok" : "free";
     let apiKeyEnvVar = null;
     if (tier === "byok") {
-        apiKeyEnvVar = await ask(lines, "Which environment variable holds your Anthropic API key?", "ANTHROPIC_API_KEY");
+        apiKeyEnvVar = flags.apiKeyEnvVar ?? (await ask(lines, "Which environment variable holds your Anthropic API key?", DEFAULT_API_KEY_ENV_VAR));
+        if (!isValidEnvVarName(apiKeyEnvVar)) {
+            console.log(`\n"${apiKeyEnvVar}" is not a valid environment variable name; using ${DEFAULT_API_KEY_ENV_VAR} instead. Edit ${CONFIG_FILENAME} to change it.`);
+            apiKeyEnvVar = DEFAULT_API_KEY_ENV_VAR;
+        }
         console.log(`\nNote: only the name "${apiKeyEnvVar}" is written to ${CONFIG_FILENAME} — the key itself is never written to disk. It's read from your environment at scan time.`);
+        console.log(byokNetworkNotice(apiKeyEnvVar));
     }
     const config = {
         entityLocation: entityLocation || null,

package/dist/commands/scan.js

@@ -60,7 +60,7 @@ export async function runScan(root, options) {
                 if (config.tier === "byok" && config.llm) {
                     console.log(byokNetworkNotice(config.llm.apiKeyEnvVar));
                 }
-                console.log(`Sending ${ambiguous.length} ambiguous item(s) to ${provider.name}...`);
+                console.log(`Sending ${ambiguous.length} ambiguous item(s) to ${provider.name} (an opaque id, category, description and one redacted source line each)...`);
                 const resolved = await resolveAmbiguousFindings(ambiguous, provider, {
                     // Preserves today's exact override behavior bit-for-bit: a missing/legacy key already
                     // behaved as false before collectsChildrensData became nullable. Only the generated
@@ -84,7 +84,7 @@ export async function runScan(root, options) {
         console.log(JSON.stringify({ ...finalResult, policyPath, llmError, protectedLogicWarning, legacyConfigWarning }, null, 2));
         return;
     }
-    console.log(formatText(finalResult));
+    console.log(formatText(finalResult, { aiReviewEnabled: config?.tier === "byok" }));
     if (protectedLogicWarning)
         console.log(`\n${protectedLogicWarning}`);
     if (legacyConfigWarning)

package/dist/llm/buildRequestItem.d.ts

@@ -6,5 +6,9 @@ import type { LlmRequestItem } from "./types.js";
  * they leave this function — LlmRequestItem has no raw-evidence field, so a
  * provider implementation is structurally incapable of receiving
  * unredacted content.
+ *
+ * `requestId` is an opaque per-scan identifier (f0, f1, ...), never finding.id: finding ids embed the
+ * file path, line number and field name, and none of those may reach the provider. The caller
+ * (resolveAmbiguousFindings) owns the mapping back to findings and never sends it anywhere.
  */
-export declare function buildRequestItem(finding: Finding, collectsChildrensData: boolean): LlmRequestItem;
+export declare function buildRequestItem(finding: Finding, collectsChildrensData: boolean, requestId: string): LlmRequestItem;

package/dist/llm/buildRequestItem.js

@@ -5,10 +5,14 @@ import { redactSecrets } from "../engine/secretRedaction.js";
  * they leave this function — LlmRequestItem has no raw-evidence field, so a
  * provider implementation is structurally incapable of receiving
  * unredacted content.
+ *
+ * `requestId` is an opaque per-scan identifier (f0, f1, ...), never finding.id: finding ids embed the
+ * file path, line number and field name, and none of those may reach the provider. The caller
+ * (resolveAmbiguousFindings) owns the mapping back to findings and never sends it anywhere.
  */
-export function buildRequestItem(finding, collectsChildrensData) {
+export function buildRequestItem(finding, collectsChildrensData, requestId) {
     return {
-        findingId: finding.id,
+        findingId: requestId,
         redactedEvidence: redactSecrets(finding.evidence),
         redactedDescription: redactSecrets(finding.description),
         dataCategories: finding.dataCategories,

package/dist/llm/resolveAmbiguousFindings.js

@@ -6,8 +6,11 @@ const DEFAULT_BATCH_CHAR_BUDGET = 6000;
 export async function resolveAmbiguousFindings(findings, provider, options) {
     const batches = chunkFindings(findings, options.batchSize ?? DEFAULT_BATCH_SIZE);
     const resolvedById = new Map();
+    // Opaque per-scan ids (f0, f1, ...), unique across all batches. Finding ids embed file paths and
+    // line numbers, so only these ever go on the wire; the mapping back lives here and nowhere else.
+    const requestIdOf = new Map(findings.map((finding, i) => [finding, `f${i}`]));
     for (const batch of batches) {
-        const items = batch.map((finding) => buildRequestItem(finding, options.collectsChildrensData));
+        const items = batch.map((finding) => buildRequestItem(finding, options.collectsChildrensData, requestIdOf.get(finding)));
         const isHighStakesById = new Map(items.map((item) => [item.findingId, item.isHighStakes]));
         let responses;
         try {
@@ -27,8 +30,9 @@ export async function resolveAmbiguousFindings(findings, provider, options) {
         }
         const responseById = new Map(responses.map((response) => [response.findingId, response]));
         for (const finding of batch) {
-            const response = responseById.get(finding.id);
-            const isHighStakes = isHighStakesById.get(finding.id) ?? false;
+            const requestId = requestIdOf.get(finding);
+            const response = responseById.get(requestId);
+            const isHighStakes = isHighStakesById.get(requestId) ?? false;
             resolvedById.set(finding.id, toResolution(response, isHighStakes, provider));
         }
     }

package/dist/llm/resolveProviderForTier.js

@@ -10,7 +10,7 @@ export function resolveProviderForTier(config) {
         if (!envVar) {
             return {
                 provider: null,
-                error: `Tier is "byok" but no API key environment variable is configured in ${CONFIG_FILENAME}. Run "srclawyer init" to set one.`,
+                error: `Tier is "byok" but no API key environment variable is configured in ${CONFIG_FILENAME}. Add "llm: { provider: anthropic, apiKeyEnvVar: <ENV_VAR_NAME> }" to it, or delete the file and re-run "srclawyer init --enable-ai-review".`,
             };
         }
         const apiKey = process.env[envVar];

package/dist/policy/legalNotices.js

@@ -8,16 +8,20 @@
 // notice and disclaimer, not a substitute for either.
 export const PRIVACY_POLICY_URL = "https://github.com/SrcLawyer/srclawyer#legal";
 export const TERMS_URL = "https://github.com/SrcLawyer/srclawyer#legal";
-// Verbatim from README.md's own "Network calls" section (minus markdown backticks, since this prints
-// to a terminal) -- one wording for this claim, not a second paraphrase that can drift from the first.
+// Mirrors README.md's own "Network calls" section (condensed, minus markdown backticks since this
+// prints to a terminal) -- the same claims in the same terms, not a second paraphrase that can drift.
+// What is actually on the wire is pinned by tests/requestBodiesNoPaths.test.ts.
 export const NETWORK_CALLS_NOTICE = [
     "Heads up: SrcLawyer makes network calls.",
     "",
     "Detection itself is fully local and offline — no code leaves your machine for pattern matching.",
-    "Once detection completes, scan makes one batched network call to grade the confidence of what it",
-    "found (field names and derived yes/no signals only, never source code), and, for scans that use Zod",
-    "schemas as request validators, one additional call sending a small redacted code fragment. This runs",
-    "on every scan regardless of tier.",
+    "Once detection completes, every scan makes one batched call to grade the confidence of what it",
+    "found. For each field it sends an opaque id (f0, f1, ...), the data category the field's name maps",
+    "to, and three derived signals (is the name ambiguous, was it read directly from the request, how",
+    "many similar fields sit alongside it) -- no field names, file paths, line numbers or source code.",
+    "Scans that use Zod schemas as request validators make one additional batched call, sending an",
+    "opaque id and a small secret-redacted code fragment per schema (the schema, its validation call",
+    "and the imports it uses) -- never a file path or line number.",
     "",
     `Legal notice and disclaimer: ${PRIVACY_POLICY_URL}`,
     "(A dedicated privacy policy and terms of service are coming; this points to what exists today.)",
@@ -25,5 +29,5 @@ export const NETWORK_CALLS_NOTICE = [
 export const SCAN_DISCLAIMER_REMINDER = "Reminder: this is automated analysis, not legal advice — review the generated policy before publishing it.";
 export function byokNetworkNotice(apiKeyEnvVar) {
     const keySource = apiKeyEnvVar ? `env var ${apiKeyEnvVar}` : "your configured key";
-    return `BYOK is configured: redacted code snippets for ambiguous findings will be sent to Anthropic under your own API key (${keySource}), for AI-assisted classification only.`;
+    return `BYOK is configured: for each finding scan couldn't classify, it will send Anthropic, under your own API key (${keySource}), an opaque id, the finding's data category and description (which names the field), and the one source line it was found on with secrets redacted — not the file's path or line number, and no other code — for AI-assisted classification only.`;
 }

package/dist/report/formatText.d.ts

@@ -1,2 +1,7 @@
 import type { ScanResult } from "../engine/types.js";
-export declare function formatText(result: ScanResult): string;
+export interface FormatTextOptions {
+    /** True when the config has AI-assisted review (tier: byok) turned on -- the hint about that
+     *  advanced option is only relevant when it isn't. */
+    aiReviewEnabled?: boolean;
+}
+export declare function formatText(result: ScanResult, options?: FormatTextOptions): string;

package/dist/report/formatText.js

@@ -1,5 +1,5 @@
 const BANNER_RULE = "=".repeat(72);
-export function formatText(result) {
+export function formatText(result, options = {}) {
     const lines = [];
     if (result.unsupportedStackWarning) {
         lines.push(BANNER_RULE);
@@ -54,7 +54,12 @@ export function formatText(result) {
     }
     else if (result.ambiguousCount > 0) {
         lines.push("");
-        lines.push(`${result.ambiguousCount} item(s) require deeper analysis before they can be included in a policy. Run "srclawyer scan" with the "byok" tier configured (bring your own Anthropic key) to attempt AI-assisted resolution, or resolve manually. A "managed" tier is planned but not yet available.`);
+        const base = `${result.ambiguousCount} item(s) require deeper analysis before they can be included in a policy; review them manually.`;
+        // Only worth mentioning when the advanced option isn't already on, and only as a pointer -- it is
+        // opt-in (init --enable-ai-review, or a hand-edited config), not something to recommend to everyone.
+        lines.push(options.aiReviewEnabled
+            ? base
+            : `${base} (Optional, advanced: AI-assisted resolution with your own Anthropic API key — see "AI-assisted review" in the README.)`);
     }
     return lines.join("\n");
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "srclawyer",
-  "version": "0.6.2",
+  "version": "0.6.3",
   "description": "Static analysis engine that derives privacy policy documentation directly from source code",
   "license": "SEE LICENSE IN LICENSE",
   "type": "module",