pi-lens 3.8.31 → 3.8.32

package/CHANGELOG.md

@@ -4,20 +4,111 @@ All notable changes to pi-lens will be documented in this file.
 
 ## [Unreleased]
 
+## [3.8.32] - 2026-04-26
+
+### Fixed
+
+- **`lspExpansionsHelped` counter undercounted in `/lens-health`** — `getSummary` used `reads.find(r => r.timestamp <= record.precedingReads[0]?.timestamp)` which always selected the first ever read for the file, so only sessions where the very first read used LSP expansion were counted. Fixed to `record.precedingReads.some(r => r.expandedByLsp)`, correctly checking all reads that preceded the specific edit.
+- **`preserveDiagnostics` incorrectly set when autofix also ran** — when a formatter and an autofix tool both modified a file, the LSP resync was still called with `preserveDiagnostics: true` because `formatChanged` was set, even though autofix changes can affect code semantics. Fixed by gating on `formatChanged && fixedCount === 0`, ensuring semantics-changing autofix always triggers a fresh diagnostics cycle.
+- **Empty-result message for `workspaceSymbol` had dangling "at"** — `"No results for workspaceSymbol at "` was produced when no `filePath` was given (workspace-scoped query with no file). Fixed by guarding the `" at <filename>"` segment on `filePath` being non-empty.
+
+### Fixed
+
+- **TypeScript LSP 5-second pipeline stall on every edit to clean files** — after biome or another formatter rewrote a file, `resyncLspFile` called `lsp.openFile` which deleted the diagnostics cache and sent `textDocument/didChange`. `waitForDiagnostics` then waited the full 5000ms timeout for TypeScript to re-publish what it already knew (formatting doesn't change semantics, so the error set is identical). Added `preserveDiagnostics` option to `openFile`/`handleNotifyOpen`: format-only resyncs no longer clear the cache, so `waitForDiagnostics` fast-paths immediately. For pi-free provider files this cuts per-edit pipeline time from ~12s to ~3-4s.
+- **`ktlint` formatter silently inactive when installed by the linter runner** — `ktlint` is both a smart-default formatter (`.kt`/`.kts`) and a smart-default linter with a managed GitHub-release install. The formatter's `detect()` used only `which("ktlint")`, never `getToolPath("ktlint")`, and the formatter was absent from `AUTO_INSTALLABLE_DEFAULT_FORMATTERS`. When the linter runner auto-installed `ktlint` to `~/.pi-lens/bin/`, the formatter was blind to it — Kotlin files got linted but never formatted. Fixed by adding `ktlint` to `AUTO_INSTALLABLE_DEFAULT_FORMATTERS`, adding `resolveCommand` that calls `ensureTool`, and making `detect` check `getToolPath` as fallback.
+- **Subagent process hangs indefinitely after completing work (issue #22)** — `scheduleLSPIdleReset` created a 240-second `setTimeout` without `.unref()`. Every `turn_end` with no file edits scheduled this timer, keeping the Node.js event loop alive for 4 full minutes. pi-subagents killed the child at the 5-second drain deadline and reported `exit code 1` / SIGTERM even though all work completed successfully. Confirmed: `--no-lsp` exited cleanly because the timer is gated on LSP being enabled. Fixed by calling `.unref()` on the timer (lets the process exit naturally if there is no other pending work) and by registering a `session_shutdown` handler that cancels the timer explicitly and calls `resetLSPService()`.
+- **Read-guard false-blocks multi-chunk reads** — `checkCoverage` checked each `ReadRecord` independently, so reading a 200-line file as two 100-line chunks and then Writing it was falsely blocked because neither chunk alone covered `[1, 200]`. Fixed by adding a second-pass union-merge of all read intervals: overlapping/adjacent ranges are merged in sorted order, and coverage is satisfied if any merged interval contains the edit range.
+- **`requestedLimit` field recorded as `effectiveReadLimit` instead of the agent's actual requested limit** — `ReadRecord.requestedLimit` was always the computed effective limit, not what the agent asked for. Fixed to record the raw requested limit (falling back to effective when not provided).
+- **Read-guard blocks legitimate full-file writes** — `write` tool calls were assigned the range `[1, Number.MAX_SAFE_INTEGER]`, which can never be covered by any prior read, so every full-file write on an existing file was incorrectly blocked with "Edit outside read range … lines 1–9007199254740991". Fixed by passing the file path into `getTouchedLinesForGuard` and using the actual on-disk line count (`countFileLines`) as the end of the write range. An agent that read all N lines of a file can now rewrite it without a false block.
+- **Read-guard false-blocks text replacement edits without explicit line ranges** — `edit` calls using `oldText` / `newText` matching but no `range` metadata were previously inferred as touching line `1`, producing bogus `"🔴 BLOCKED — Edit outside read range"` failures even when the agent had read the correct target region. Fixed touched-line inference so range-less replacement edits return `undefined` instead of defaulting to `1-1`, avoiding fabricated line-1 violations.
+- **`NEEDS_POSTINSTALL` broken for scoped npm packages** — `@biomejs/biome`, `@ast-grep/cli`, and `@ast-grep/napi` were incorrectly checked with `packageName.split("@")[0]` which always yields `""` for scoped packages; the nullish-coalescing fallback never fired. These packages always received `--ignore-scripts`, preventing native binary postinstall scripts from running and silently breaking their auto-installation. Fixed by checking the full package name directly.
+- **Silent formatter failures in pipeline** — when a formatter crashed (binary missing, timeout, or I/O error) the post-write pipeline never emitted a debug log; only `anyChanged` triggered output. Formatter errors are now surfaced via `dbg()` so they appear in debug/latency logs.
+- **`tryLazyInstallFormatterTool` failures logged** — lazy `gem install rubocop` and `rustup component add rustfmt` failures were silently swallowed with no log output anywhere. Both now emit a `[format] lazy-install <tool> failed: <reason>` message to stderr.
+- **`getFormattersByName` broken for hyphenated formatter names** — constructing the export key as `` `${name}Formatter` `` produced `"php-cs-fixerFormatter"` and `"clang-formatFormatter"` instead of the real camelCase exports (`phpCsFixerFormatter`, `clangFormatFormatter`). These formatters were silently filtered out when selected by name via the explicit `options.formatters` API. Fixed by converting hyphenated names to camelCase before appending `Formatter`.
+- **Read-before-edit guard correctness** — fixed `read.path` vs `read.filePath` mismatch, full-file read coverage tracking, read-guard range math, session reset leakage, and guard messaging so edit enforcement now correctly reflects actual reads
+- **First-read LSP warmup behavior** — first `read` now triggers non-blocking async LSP warmup once per file/session window, with retry-safe state tracking and reset handling
+- **Formatter selection bugs and drift** — formatter chooser now reliably selects exactly one formatter, no longer lets registry order accidentally block smart defaults, and keeps explicit config precedence over defaults
+- **Ruby auto-install policy mismatch** — `rubocop` policy and installer behavior are now aligned through managed gem install support
+- **Prettier dispatch redundancy** — removed `prettier-check` from the active dispatch path to avoid re-checking formatting after the authoritative autoformat pipeline has already run
+- **LSP race condition in `initLSPConfig`** — `configInFlight` Map deduplicates concurrent initialization calls for the same workspace; parallel session starts no longer double-initialize and race on `workspaceConfigs`
+- **`lsp_navigation` rejected accidentally quoted `operation` values at schema-validation time** — the tool previously declared `operation` as a `Type.Union` of string literals, so model outputs like `"workspaceDiagnostics"` were rejected before `execute()` ran, causing confusing retry loops with no recovery path. The tool now accepts a string, normalizes accidental surrounding quotes, validates against the allowed operation set inside `execute()`, and returns a clear error listing valid operations when the value is still invalid.
+- **`LSPService` use-after-shutdown** — `isDestroyed` flag added; all public methods (`getClientForFile`, `openFile`, `updateFile`, `waitForDiagnostics`, `getDiagnostics`, `shutdown`) return early once the service has been shut down
+- **`theme.fg` crash during session start** — `updateLspStatus` wraps theme calls in try/catch; theme may not be fully initialized during early session startup events
+- **`isCommandAvailable` hangs on slow tools** — added 5s timeout with `proc.kill()` and a double-resolve guard; probe commands that stall no longer block session startup indefinitely
+- **Tree-sitter `client_unavailable` log spam** — `TreeSitterClient.isAvailable()` now re-evaluates `grammarsDir` when the cached path goes missing, instead of caching an empty string forever. Added `resolveWebTreeSitterAsset()` helper with three strategies: (1) `createRequire` module resolution (hoisted installs — issue #20), (2) `resolvePackagePath(import.meta.url)` fallback (on-the-fly TS compilation by pi), (3) `process.cwd()` fallback. Fixes 108 skipped-runner log lines when the initial grammar probe failed transiently.
+- **Pipeline test assertion drift** — updated `tests/clients/pipeline.test.ts` to match the current auto-format warning text (`File was modified by auto-format/fix...`)
+
+### Added
+
+- **Autofix decision/attempt logging** — the post-write pipeline now logs autofix policy selection, preferred tools, attempted tools, explicit skip reasons, and the important distinction between “autofix skipped” vs “autofix ran but applied 0 fixes.” This makes it much easier to understand whether TypeScript files chose Biome or ESLint autofix and why.
+- **Dedicated read-guard trace log** — added `~/.pi-lens/read-guard.log` with structured events for read recording, LSP range expansion, touched-line derivation, edit checks, verdicts, and exemptions. This separates guard-policy debugging from the noisier general `latency.log` stream.
+- **Centralized formatter policy layer** — added normalized per-extension formatter policy with explicit config detection, smart-default selection, and managed-vs-toolchain default handling
+- **Centralized command spec / execution policy layer** — added shared tool command specs, execution policy, and resolver helpers used by dispatch runners and autofix paths
+- **Centralized linter policy layer** — added policy selectors for dispatch lint runner choice so config-first and smart-default lint behavior is now encoded centrally instead of only in individual runners
+- **Centralized autofix policy and capability metadata** — added policy selectors for safe pipeline autofix plus explicit capability metadata separating tool-level fix support from safe automatic post-write autofix
+- **Expanded smart-default formatter coverage** — added smart defaults across web/content formats and additional language ecosystems, including managed smart-default support for `prettier`, `shfmt`, and `taplo`
+- **LSP footer status indicator** — session start and turn end now show `LSP Active (N)` in green or `LSP Inactive` in red; count reflects alive (connected + initialized) clients via `getAliveClientCount()`
+- **Rust monorepo workspace root detection** — `RustServer` walks up from the detected crate root checking parent `Cargo.toml` files for a `[workspace]` section; rust-analyzer now resolves correctly in Cargo workspaces
+- **Opportunistic LSP read range expansion** — single-line `read` tool calls are silently expanded to the full enclosing symbol when a warm LSP client is available; best-effort, no-op if LSP is cold or the lookup doesn't resolve in time
+- **`workspaceSymbol` result filtering and cap** — `lsp_navigation` now filters and caps workspace symbol results at 15 entries to avoid overwhelming the context window
+
+### Performance
+
+- **LSP pre-edit touch bounded and file-kind gated** — `edit` / `write` tool calls now skip opportunistic LSP pre-touch for non-LSP-capable files (for example Markdown) and cap the warm-client wait with `PI_LENS_TOOLCALL_TOUCH_MS` (default `750ms`). This avoids pointless `no_clients` touch attempts and reduces edit-path stalls.
+- **Empty aggregate diagnostic waits shortened** — aggregate LSP diagnostics no longer wait the old hardcoded multi-second timeout just to confirm an empty result set. New settle/wait budgets (`PI_LENS_LSP_DIAGNOSTICS_AGGREGATE_WAIT_MS`, `PI_LENS_LSP_DIAGNOSTICS_SEMANTIC_THRESHOLD_MS`, `PI_LENS_LSP_DIAGNOSTICS_SEMANTIC_SETTLE_MS`) make clean-edit loops return faster.
+- **Tool path resolution fast path** — `getToolPath` checks the local managed install (`~/.pi-lens/tools/node_modules/.bin/`) before global PATH probes, npm/pip/GitHub lookups; eliminates 2–5s overhead per tool on session start
+- **`jscpd` availability fast path** — `ensureAvailable()` probes the local install with `fs.existsSync` before spawning a process, and deduplicates concurrent calls via `ensureInFlight`
+- **Concurrent project indexing** — `buildProjectIndex` processes files in batches of 8 with `Promise.all` instead of sequentially; large projects index significantly faster
+- **`buildFunctionMatrixFromNode` avoids re-parse** — walks the existing TypeScript AST directly instead of extracting function source text and creating a new `SourceFile`; removes per-function re-parse overhead from similarity indexing
+
+### Removed
+
+- **`prettier-check` runner fully removed** — the dead `clients/dispatch/runners/prettier-check.ts` file is now deleted entirely after its earlier removal from active dispatch plans; formatting remains owned by the autoformat pipeline instead of dispatch re-checks
+- **Worthless `diagnostic-logger` tests** — deleted `tests/clients/diagnostic-logger.test.ts` (5 tests that only asserted mock objects equaled what was just assigned; zero behavior coverage)
+- **Redundant circular-dependency regression tests** — removed 3 no-op import tests from `tests/clients/circular-deps-regression.test.ts` (`expect(module).toBeDefined()` after `await import(...)` adds no value; import failure throws before the assertion)
+
+### Changed
+
+- **Normal dispatch no longer runs `similarity` by default** — removed `similarity` from standard JS/TS write and full lint dispatch plans so targeted edits no longer pay its hot-path cost; similarity analysis remains available in explicit workflows like `/lens-booboo` and inline advisory logic.
+- **Cascade diagnostics prune stale cache entries earlier** — LSP diagnostic merging now drops TTL-expired and non-existent file entries before cascade aggregation, reducing stale-path noise and improving cache hygiene during long sessions.
+- **Autoformat policy normalized across supported languages** — formatter behavior is now: exactly one formatter runs, explicit config wins, otherwise smart default applies, and config-first file types do nothing when unconfigured
+- **JS/TS lint fallback normalized** — no-config JavaScript/TypeScript dispatch now consistently prefers `oxlint` with `biome-check-json` fallback, while explicit ESLint/Oxlint/Biome config still wins
+- **Safe autofix remains pipeline-owned** — autofix selection now flows through centralized policy and remains in the post-write pipeline, while dispatch runners stay diagnostics-only
+- **Dispatch runner gating centralized** — major runners (`stylelint`, `yamllint`, `markdownlint`, `htmlhint`, `hadolint`, `sqlfluff`, `rubocop`, `ktlint`, `taplo`, `golangci-lint`, `phpstan`, `ruff`) now consult centralized lint policy before running
+- **Kotlin safe autofix added** — `ktlint -F` is now treated as a safe pipeline autofix path for Kotlin files
+- **Fixability semantics clarified** — dispatch diagnostics now distinguish generic fixability from safe pipeline autofix availability and expected fix mode (`pipeline`, `manual`, `suggestion`), including suggestion/manual-fix runners like LSP, TS-LSP, shellcheck, shfmt, spellcheck, tree-sitter, architect, and ast-grep-napi
+- **Test runner moved to turn_end (non-blocking)** — previously fired inline on every write, blocking the pipeline for up to 60s mid-refactor and producing false failures while the codebase was in an inconsistent state. Tests now run once per turn after all edits complete: unique test targets are collected from modified files, fired concurrently as a fire-and-forget `Promise.allSettled`, and failures are written to cache for injection into the next turn's context. Results are discarded if the agent starts a new turn before tests finish, preventing stale failures from clobbering newer results.
+- **Similarity runner skips small edits** — when `modifiedRanges` total lines is below `MIN_FUNCTION_LINES` (8), the similarity runner exits early; a new function can't fit in fewer lines than that, so the ~1100ms scan is wasted on targeted fixes
+- **Stronger auto-format/fix re-read warning** — message now explicitly tells the agent it MUST re-read the file before any further edits, listing what may have changed (whitespace, indentation, quotes, code)
+- **Turn-end findings cap tightened** — reduced `maxLines` from 24 → 20 and `maxChars` from 1600 → 1000 to stay conservative with context budget
+
+### Tests
+
+- **Read-guard touched-line regression tests** — added `tests/clients/read-guard-tool-lines.test.ts` covering full-file writes and range-less text replacement edits so read-guard line inference no longer regresses to bogus `1-1` edits.
+- **Policy normalization regression coverage** — added and updated tests for read-guard fixes, runtime coordinator warm/reset behavior, formatter policy selection, command resolution, linter/autofix policy metadata, dispatch plan exposure, and runner status semantics across the formatter/linter/autofix normalization work
+- **LSP integration tests** — added `tests/clients/lsp/integration.test.ts` with a fake JSON-RPC server (`tests/fixtures/fake-lsp-server.mjs`) covering LSP client lifecycle: initialize handshake, file open/change notifications, diagnostics, and graceful shutdown
+- **Tree-sitter resolution regression tests** — added 3 tests to `tests/clients/tree-sitter-client-init.test.ts`:
+  - `TreeSitterClient.isAvailable returns true when grammars are installed` (smoke test)
+  - `falls back to resolvePackagePath when require.resolve fails` (on-the-fly compilation scenario)
+  - `re-evaluates grammarsDir when isAvailable is called after initial miss` (prevents cached-empty-string bug)
+
 ## [3.8.31] - 2026-04-23
 
 ### Fixed
+
 - **Duplicate inline feedback on edit arrays** — `tool_result` calls for the same file are now deduplicated within a turn using a `reportedThisTurn` set on `RuntimeCoordinator`, cleared on each `turn_start`; previously pi's sequential per-hunk `tool_result` firing caused the pipeline to re-run and feedback to repeat N times per edit array
 - **Double latency logging on pipeline completion** — removed redundant `logLatency` call in `pipeline.ts`; `runtime-tool-result.ts` already logs the outer `tool_result completed` with full duration including format, autofix, and cascade phases
 - **Modified range tracking broken for 3-digit+ line numbers** — `parseDiffRanges` regex changed from `\s+` to `\s*` to handle unpadded line numbers; the diff format right-pads to the file's max digit width so e.g. line 613 in a <1000-line file has no leading space and was silently dropped
 - **Stale gleam grammar entries** — removed dead `LANGUAGE_TO_GRAMMAR` and `getExtensionsForLanguage` entries for gleam; `tree-sitter-gleam.wasm` was never published in `tree-sitter-wasms@0.1.13`
 
 ### Changed
+
 - **TypeBox 0.34.x → 1.x migration** — updated `package.json` dependency from `@sinclair/typebox` to `typebox ^1.0.0` and updated imports in `tools/lsp-navigation.ts`, `tools/ast-grep-search.ts`, and `tools/ast-grep-replace.ts` to match pi-mono 0.69.0
 
 ## [3.8.30] - 2026-04-22
 
 ### Fixed
+
 - **lsp_navigation permanently disabled** — removed stale `lens-lsp` flag check (flag was removed in 3.8.29) that caused every `lsp_navigation` call to short-circuit with `lsp_disabled`; tool now only gates on `--no-lsp`
 - **ast_grep_search / ast_grep_replace auto-install** — switched availability check from sync `isAvailable()` to async `ensureAvailable()` so the auto-installer triggers when `sg` is missing
 - **@ast-grep/cli postinstall skipped** — added `@ast-grep/cli` to `NEEDS_POSTINSTALL`; without it `--ignore-scripts` left ASCII stubs in place of `sg.exe` / `ast-grep.exe` on Windows
@@ -37,6 +128,7 @@ All notable changes to pi-lens will be documented in this file.
 - **Pipeline deduplication** — `handleToolResult` now deduplicates concurrent pipeline calls for the same file; the pi framework fires `tool_result` once per hunk in an Edit array, causing duplicate pipeline runs and doubled agent output
 
 ### Changed
+
 - **Tuned false-positive thresholds across all runners** — reduced noise in `lens-booboo` and dispatch for all users:
   - Added `FACT_SEVERITY_FILTER` (`error`/`warning` only) and `MIN_TREE_SITTER_HITS_PER_RULE = 3`
   - Filtered entropy/AI-style warnings from complexity metrics
@@ -46,6 +138,7 @@ All notable changes to pi-lens will be documented in this file.
   - Unregistered `no-magic-numbers` and `high-entropy-string` fact rules globally
 
 ### Removed
+
 - **Dead code across 32 files** — removed 51 sites of unused imports, locals, and parameters flagged by `tsc --noUnusedLocals --noUnusedParameters`:
   - `clients/architect-client.ts`, `ast-grep-client.ts`, `biome-client.ts`, `complexity-client.ts`, `go-client.ts`, `rust-client.ts`, `scan-utils.ts`, `secrets-scanner.ts`, `subprocess-client.ts`, `test-runner-client.ts`, `tool-availability.ts`, `tree-sitter-cache.ts`, `tree-sitter-client.ts`, `type-coverage-client.ts`, `type-safety-client.ts`
   - `clients/dispatch/dispatcher.ts`, `runners/ast-grep-napi.ts`, `runners/golangci-lint.ts`, `runners/index.ts`, `runners/python-slop.ts`, `runners/ts-lsp.ts`, `runners/utils/diagnostic-parsers.ts`
@@ -54,6 +147,7 @@ All notable changes to pi-lens will be documented in this file.
   - `commands/booboo.ts`, `index.ts`
 
 ### Tests
+
 - **Pipeline regression tests** — `tests/clients/pipeline.test.ts` (11 tests): secrets blocking, format modification, LSP sync, dispatch blockers, autofix output, test runner skip, all-clear output
 - **Autofix helper tests** — `tests/clients/autofix-helpers.test.ts` (12 tests): config detection (eslint, stylelint, sqlfluff), malformed JSON handling, file change detection after command
 - **LSP lifecycle tests** — `tests/clients/lsp/lifecycle.test.ts` (4 tests): missing binary error, process spawn, immediate exit detection, process kill
@@ -65,17 +159,20 @@ All notable changes to pi-lens will be documented in this file.
 - **Tree-sitter hoisted-install tests** — `tests/clients/tree-sitter-client-init.test.ts` (3 tests): wasm resolution via `require.resolve`, `locateFile` directory derivation, `findGrammarsDir` external package resolution
 
 ### Refactored
+
 - **Extract `detectFileChangedAfterCommand`** — moved from `clients/pipeline.ts` to `clients/file-utils.ts` and exported for reuse/testing; imported back into `pipeline.ts`; `tests/clients/autofix-helpers.test.ts` now imports the real function instead of reimplementing a copy
 - **Export testable pipeline helpers** — exported `hasEslintConfig`, `hasStylelintConfig`, `hasSqlfluffConfig` from `clients/pipeline.ts` so config detection is testable
 - **Export LSP client internals** — exported `clientWaitForDiagnostics`, `handleNotifyOpen`, `handleNotifyChange`, and `LSPClientState` from `clients/lsp/client.ts` for direct testing with mocks
 - **Export `isCmdShimValid`** — exported from `clients/lsp/launch.ts` so the npm `.cmd` shim validator is unit-testable
 
 ### CI
+
 - **Dead-code gate** — `lint-and-typecheck` job now runs `tsc --noUnusedLocals --noUnusedParameters --noEmit` alongside `--noEmit` so dead code regressions fail CI immediately
 
 ## [3.8.29] - 2026-04-21
 
 ### Added
+
 - **New diagnostic commands** — added `/lens-tools` and `/lens-health` for system visibility:
   - `/lens-tools` — shows tool installation status: globally installed, pi-lens auto-installed, or npx fallback
   - `/lens-health` — shows runtime health: pipeline crashes, slow runners, diagnostic stats
@@ -92,6 +189,7 @@ All notable changes to pi-lens will be documented in this file.
   - Project-level logs (`{cwd}/.pi-lens/*`) intentionally excluded from cleanup
 
 ### Changed
+
 - **`/lens-tools` output improved** — added explanatory note when GitHub-release tools are shown as missing: "GitHub-release tools auto-install when you open files of those languages"
 - **Simplified agent prompts** — removed verbose prompt sections to reduce token burn:
   - Removed startup notes about project rules count (now just logged, not shown)
@@ -109,6 +207,7 @@ All notable changes to pi-lens will be documented in this file.
 - **Cross-platform line ending handling** — all `.split("\n")` changed to `.split(/\r?\n/)` for Windows CRLF compatibility (11 files updated)
 
 ### Fixed
+
 - **Biome VCS/ignore file errors eliminated** — disabled VCS integration in biome config to prevent "ignore file not found" errors:
   - Changed `vcs.enabled: true` → `vcs.enabled: false` in `config/biome/core.jsonc`
   - Biome was searching for `.gitignore` files that don't exist when running on arbitrary projects via pi-lens
@@ -153,6 +252,7 @@ All notable changes to pi-lens will be documented in this file.
   - Prevents false positives when env var names are used as placeholder strings
 
 ### Changed
+
 - **Biome check performance** — reduced lint latency from ~1.4s to ~100ms per file (92% improvement):
   - Removed redundant `--version` pre-check spawn (~200ms saved)
   - Switched from `biome check` to `biome lint` command (skip format validation)
@@ -166,6 +266,7 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.8.28] - 2026-04-19
 
 ### Fixed
+
 - **Session startup no longer blocks the Node event loop** — tool availability probes (biome, ast-grep, ruff, knip, jscpd, madge) now run via async `ensureAvailable()` in a fire-and-forget IIFE instead of `setImmediate` + `spawnSync`, eliminating ~8–10 s of main-thread freeze on startup.
 - **Biome binary lookup extended** — `getBiomeBinary()` now checks `~/.pi-lens/tools/node_modules/.bin/biome` so the async probe finds the pre-installed binary without falling back to `npx`.
 - **CSS roots and Windows LSP shims tightened** — improved root resolution for CSS language server on Windows.
@@ -177,6 +278,7 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.8.27] - 2026-04-19
 
 ### Added
+
 - **Review graph impact cascade** — turn-end cascade now renders a review-graph impact view showing which files were affected and how diagnostics propagated.
 - **Fact-rule pipeline in dispatch** — new `fact-rules` dispatch runner computes function-level facts (depth, cyclomatic complexity, call counts) and evaluates quality rules inline, replacing the bespoke tree-sitter booboo runner.
 - **Function facts: depth / CC / calls** — tree-sitter extracts per-function cyclomatic complexity, nesting depth, and outgoing call count for fact-rule evaluation.
@@ -214,6 +316,7 @@ All notable changes to pi-lens will be documented in this file.
 - **CI: tsx extension load check** — CI verifies that required extensions load correctly to catch missing dependency errors early.
 
 ### Changed
+
 - **Promote LSP-backed languages into dispatch** — languages with active LSP servers now route through dispatch's standard pipeline instead of ad-hoc paths.
 - **Dispatch language fallbacks aligned** — LSP-backed and fallback runner selection now uses consistent language-to-capability mapping.
 - **CSS / HTML / TOML / Elixir fallback wiring** — dispatch fallbacks now include CSS (stylelint), HTML (htmlhint), TOML (taplo), and Elixir (credo).
@@ -237,6 +340,7 @@ All notable changes to pi-lens will be documented in this file.
 - **Complexity reduction** — decomposed four highest-complexity functions (CC 75–153 → <20 each) for maintainability.
 
 ### Fixed
+
 - **Windows LSP startup fallback** — hardened spawn logic for `.cmd` wrappers, PATH resolution, and process creation on Windows.
 - **C# launch and secondary language fallbacks** — C# LSP and secondary language servers start reliably in more project layouts.
 - **Prettier-check / stylelint cwd overshoot** — both runners now find the project root correctly instead of silently skipping.
@@ -264,15 +368,18 @@ All notable changes to pi-lens will be documented in this file.
 - **Tree-sitter rule false positives** — fixed query syntax, scan scripts, and architect glob patterns that produced incorrect findings.
 
 ### Performance
+
 - **Startup: defer npm tool availability probes** — tool availability checks (Biome, ESLint, etc.) now run lazily out of the critical path, reducing session start latency.
 - **Defer TypeScript loading in similarity runner** — similarity detection lazily imports the TypeScript parser, eliminating cold-start cost on first call.
 
 ### Refactored
+
 - **LSP: collapse resolution into `resolveAndLaunch`** — unified four spawn mechanisms into one function with clear platform-aware fallbacks.
 - **Booboo: replace bespoke tree-sitter runner** — `/lens-booboo` tree-sitter checks now use the same fact-rule pipeline as dispatch, eliminating code duplication.
 - **Drop redundant async from LSP spawn** — removed unnecessary `async`/`await` from functions that already return Promises.
 
 ### Tests
+
 - **GitHub release asset selection and PATH tests** — installer asset URL construction and PATH resolution covered by unit tests.
 - **Rust-analyzer Windows .zip asset expectation** — test fixture updated for `.zip` extension on Windows.
 - **Async-noise test multi-statement function** — test rule updated to match multi-statement function bodies.
@@ -280,38 +387,46 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.8.26] - 2026-04-15
 
 ### Fixed
+
 - **Silent crash on unhandled promise rejection** — the LSP crash guard's `unhandledRejection` handler was swallowing all non-ignorable rejections without rethrowing, causing silent process exits. The handler now rethrows so non-ignorable rejections surface as `uncaughtException` and are properly reported. Triggered most visibly when editing JSON files while Biome or another LSP server was active.
 
 ## [3.8.25] - 2026-04-13
 
 ### Changed
+
 - **Go LSP PATH augmentation on Windows** — LSP subprocess PATH now includes common Go install directories (`C:\Program Files\Go\bin`, `C:\Go\bin`) to prevent `gopls` startup/runtime failures when `go` is not in inherited shell PATH.
 - **Similarity runner cold-start behavior** — similarity now skips fast when no cached project index exists and for tiny/trivial files, reducing write/edit pipeline tail latency and eliminating frequent 30s timeout noise in scratch-file workflows.
 
 ### Fixed
+
 - **Non-git workspace commit lookup noise** — metrics snapshot commit detection now pre-checks repository context before invoking Git, preventing `fatal: not a git repository` terminal noise in non-repo folders.
 
 ## [3.8.24] - 2026-04-12
 
 ### Changed
+
 - **Lazy bootstrap client loading** — startup now defers heavy client initialization behind a shared bootstrap promise, reducing first-turn startup overhead while preserving tool behavior.
 - **LSP config discovery scope** — `.pi-lens/lsp.json` (and related config paths) are now resolved from the current directory up through parent directories, improving nested-workspace support.
 - **Ruby server fallback chain** — Ruby LSP startup now tries `ruby-lsp`, then `solargraph`, then `rubocop --lsp` for broader environment compatibility.
 
 ### Fixed
+
 - **LSP config activation timing** — LSP server config initialization now runs reliably at `session_start` and before LSP-backed `tool_call` operations, so server enable/disable overrides apply in one-shot and interactive sessions.
 
 ## [3.8.23] - 2026-04-12
 
 ### Added
+
 - **LSP auto-touch warm-up** — tool-call flow now proactively opens/syncs supported files (`read`/`write`/`edit`/`lsp_navigation`) so LSP clients warm up earlier and first semantic requests are less likely to return cold-start empties.
 
 ### Changed
+
 - **Ruby LSP spawn resilience on Windows** — Ruby command discovery now tries `ruby-lsp`/`solargraph` from PATH plus common Ruby install locations before marking servers unavailable.
 - **LSP diagnostics dedupe strategy** — multi-server diagnostics aggregation now dedupes using a simpler key (`line`, `character`, `message`) to better collapse equivalent findings across servers.
 - **Windows LSP PATH fallback** — language-server spawns now augment PATH with common user-level tool locations (`.cargo\bin`, `go\bin`, common Ruby bin dirs) to improve server discovery on Windows shells.
 
 ### Fixed
+
 - **LSP diagnostics key normalization** — publish diagnostics now store/update using normalized file-path keys, fixing Windows path mismatches that could hide diagnostics in some languages.
 - **Pull diagnostics fallback path** — when a server advertises pull diagnostics, `textDocument/diagnostic` is now attempted before push-wait fallback.
 - **Navigation diagnostics/health observability** — `lsp_navigation` and diagnostics aggregation now emit explicit `failureKind`/health metadata to latency logs and tool details for faster root-cause triage (`no_server`, `unsupported`, `empty_result`, `lsp_error`, etc.).
@@ -322,23 +437,28 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.8.22] - 2026-04-09
 
 ### Changed
+
 - **Quick startup path for one-shot print sessions** — `--print`/`-p` now auto-selects quick startup mode to skip heavy bootstrap work and reduce startup latency. Added `PI_LENS_STARTUP_MODE=full|minimal|quick` override for explicit control.
 
 ### Fixed
+
 - **Cascade diagnostics formatting clarity** — turn-end cascade entries now render source location as `line <n>, col <m> code=<id>:` so diagnostic codes (for example `TS2322`) are no longer formatted in a way that can be mistaken for file line numbers.
 
 ## [3.8.21] - 2026-04-08
 
 ### Changed
+
 - **Session guidance channeling** — session-start guidance is now injected as `system` context instead of synthetic `user` context, reducing acknowledgement-only first replies before task execution.
 - **Coverage warning dedupe** — "Pi-lens analysis unavailable" warnings are now shown once per file per session and reset on session baseline reset.
 
 ### Fixed
+
 - **Turn-end read-loop pressure** — turn-end findings now suppress duplicate persisted blocker prompts and avoid imperative "read this file" phrasing that could trigger repeated read loops.
 
 ## [3.8.20] - 2026-04-08
 
 ### Changed
+
 - **Session startup hardening** — background startup tasks now run with session-generation safety guards and startup in-flight tracking, preventing stale task writes across session boundaries.
 - **Turn-end overlap guardrails** — turn-end `knip`/`jscpd` checks now skip when the corresponding startup scan is still in-flight.
 - **Language-profile centralization** — startup and dispatch now share a centralized project language profile for supported language detection and LSP-capable kind policy.
@@ -346,6 +466,7 @@ All notable changes to pi-lens will be documented in this file.
 - **Language setup hints** — `session_start` now emits actionable install hints for detected Go/Rust/Ruby projects when key tools are missing.
 
 ### Fixed
+
 - **TODO baseline scan resilience** — unreadable files are now skipped safely instead of crashing TODO scanning in cloud-synced projects.
 - **Startup scan gating consistency** — TODO warmup now respects startup warm-cache gating and avoids unnecessary scan work in restricted startup contexts.
 - **Path exclusion coverage** — shared exclusion list now includes common agent/tooling directories (`.claude`, `.codex`, `.worktrees`, `.vscode`, and related dirs).
@@ -356,39 +477,47 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.8.19] - 2026-04-07
 
 ### Fixed
+
 - **Biome autofix gating** — Biome autofix/auto-install now runs only when the project has Biome configuration (`biome.json`/`biome.jsonc`) or `@biomejs/biome` in `devDependencies`, preventing unwanted Biome installs in non-Biome JS/TS projects.
 
 ## [3.8.18] - 2026-04-07
 
 ### Changed
+
 - **Similarity calibration tightened** — raised semantic similarity threshold to `0.96`, raised minimum transition signal to `40`, and added transition-ratio filtering to reduce boilerplate-wrapper false positives.
 - **Dispatch + booboo alignment** — similarity guardrails are now aligned between `/lens-booboo` reporting and the dispatch `similarity` runner.
 - **Tree-sitter structural dedupe in booboo** — advanced structural findings now dedupe repeated line-level matches by normalized matched scope so deep nesting/promise chain reports collapse to one representative issue.
 
 ### Tests
+
 - Added similarity runner guardrail assertions in `tests/clients/similarity-runner.test.ts`.
 
 ## [3.8.17] - 2026-04-07
 
 ### Changed
+
 - **Delta-only unused variable blocking** — diagnostics matching unused-value patterns are now promoted to blocking only when they are newly introduced in delta mode.
 - **Unused diagnostic heuristics** — improved detection covers TypeScript unused codes/messages and `no-unused*` rule identifiers, while preserving non-blocking behavior for pre-existing baseline debt.
 
 ### Tests
+
 - Added dispatch flow coverage for delta-mode unused-value promotion in `tests/clients/dispatch/dispatcher-flow.test.ts`.
 
 ## [3.8.16] - 2026-04-07
 
 ### Changed
+
 - **Ast-grep fix guidance upgraded** — ast-grep diagnostics now prefer explicit rule-level guidance from YAML (`fix` first, then `note`) before falling back to generic defect-class suggestions.
 - **Rule parser metadata support** — YAML rule parsing now supports top-level `note` and `fix` fields (including multiline values) for agent-facing remediation text.
 
 ### Tests
+
 - Added parser coverage for `note`/`fix` extraction in `tests/clients/dispatch/runners/yaml-rule-parser.test.ts`.
 
 ## [3.8.15] - 2026-04-07
 
 ### Added
+
 - **Security rule: no global eval** — added ast-grep rule to block `eval(...)`, `Function(...)`, and string-based `setTimeout`/`setInterval` execution.
 - **Security rule: no blank target** — added ast-grep rule to warn on `<a target="_blank">` without `rel=...`.
 - **Performance rule: no accumulating spread** — added ast-grep rule to warn on reduce patterns that repeatedly spread accumulators.
@@ -396,60 +525,72 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.8.14] - 2026-04-07
 
 ### Added
+
 - **YAML lint runner** — added `yamllint` dispatch support for `.yaml`/`.yml` files, with LSP prepended when enabled.
 - **SQL lint + format support** — added `sqlfluff` dispatch support for `.sql` files and `sqlfluff` formatter integration.
 - **SQL file kind support** — introduced `sql` file kind detection and language-id mapping.
 
 ### Changed
+
 - **Capability matrix coverage expanded** — YAML and SQL now map to dedicated lint runners in the centralized capability matrix.
 - **Lazy auto-install expansion** — added lazy-install support for `yamllint` and `sqlfluff` via installer-managed pip tools.
 - **Runner inventory docs updated** — README runner list now includes `yamllint` and `sqlfluff`.
 
 ### Tests
+
 - Added YAML/SQL runner parsing/semantics coverage in `tests/clients/dispatch/runners/yaml-sql-runners.test.ts`.
 - Updated dispatch plan/integration tests for YAML+SQL capability mapping and group ordering.
 
 ## [3.8.13] - 2026-04-07
 
 ### Changed
+
 - **Centralized capability matrix** — dispatch planning now derives from `LANGUAGE_CAPABILITY_MATRIX`, which defines per-language capability dimensions and write/full runner groups in one place.
 - **Plan generation simplified** — `TOOL_PLANS` (write path) and `FULL_LINT_PLANS` (full scans) are generated from matrix entries instead of duplicated hand-maintained plan objects.
 
 ### Tests
+
 - Extended dispatch plan exposure coverage to assert capability dimensions for main languages (`jsts`, `python`, `go`, `rust`, `ruby`) in `tests/clients/dispatch/plan-exposure.test.ts`.
 
 ## [3.8.12] - 2026-04-07
 
 ### Changed
+
 - **Excluded-dir policy consolidated** — scanners now share `isExcludedDirName(...)` matching logic from `file-utils` instead of ad-hoc `EXCLUDED_DIRS.includes(...)` checks.
 - **Pattern-aware exclusions** — exclusion matching now supports case-insensitive exact matches and lightweight glob patterns (for example `*.dSYM`).
 - **Cross-scanner consistency** — startup scan, source filter, jscpd precheck, tree-sitter file collection, slop scan, production-readiness scan, and legacy scan-utils path checks now use the same exclusion semantics.
 
 ### Tests
+
 - Added exclusion matcher coverage in `tests/clients/file-utils.test.ts`.
 - Expanded source-filter coverage for glob exclusions (`*.dSYM`) and case-insensitive directory exclusion in `tests/source-filter.test.ts`.
 
 ## [3.8.11] - 2026-04-07
 
 ### Added
+
 - **Experimental git guard flag** — added `--lens-guard` to gate commit/push attempts behind a blocker preflight check.
 - **Git guard commit preflight** — when enabled, `bash` calls containing `git commit` or `git push` are blocked if unresolved inline blockers or pending turn-end blockers exist.
 
 ### Changed
+
 - **Guard status tracking** — runtime now tracks blocker state/summary from post-write pipeline output so commit blocking messages stay concise and actionable.
 
 ### Tests
+
 - Added focused coverage for git guard command detection and block/allow behavior in `tests/clients/git-guard.test.ts`.
 - Updated runtime tool-result tests for guard status updates in `tests/clients/runtime-tool-result.test.ts`.
 
 ## [3.8.10] - 2026-04-07
 
 ### Changed
+
 - **LSP default-on** — `--lens-lsp` is now enabled by default to provide unified LSP diagnostics across supported file kinds.
 - **Capability-driven LSP dispatch** — dispatch now prepends LSP dynamically by file kind/flag state, while still using runtime `hasLSP(file)` checks for safe activation.
 - **Fallback safety switch clarified** — `--no-lsp` is documented and wired as the explicit opt-out path to language-specific fallbacks.
 
 ### Fixed
+
 - **`--no-lsp` consistency** — LSP sync/reset/navigation and runner gating now respect `--no-lsp` consistently, so fallback behavior is predictable.
 - **LSP/lint overlap noise** — non-blocking lint diagnostics overlapping with LSP on the same file/line are suppressed to keep inline output focused.
 - **turn_end actionability** — blocker summaries for jscpd/knip now include direct file hints to reduce path-guessing loops.
@@ -460,16 +601,19 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.8.9] - 2026-04-07
 
 ### Changed
+
 - **README restructured** — Expanded the "What It Does" section with write/edit, session_start, and turn_end behavior; added a complete runner list and a dependency table with auto-installed vs manual tools.
 - **Test runner strategy improved** — Added hybrid test targeting: rerun known failures first, otherwise run related tests for the edited file.
 
 ### Fixed
+
 - **Non-JSON test runner parsing** — Go/Cargo/Dotnet/Gradle/Maven/RSpec/Minitest now use generic parsing instead of returning "Unknown runner".
 - **Dispatch delta baseline compatibility** — Baseline lookups now support both normalized absolute and cwd-relative keys to prevent stale/new misclassification in mixed-key scenarios.
 
 ## [3.8.8] - 2026-04-07
 
 ### Changed
+
 - **README massively simplified** — Reduced the README to core purpose, install/run, key commands, and concise usage notes.
 - **Docs trimmed** — Removed deep internal documentation files from `docs/` to keep project docs minimal and focused.
 - **Positioning text clarified** — Updated wording to describe pi-lens as real-time inline feedback for AI agents.
@@ -477,6 +621,7 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.8.7] - 2026-04-06
 
 ### Fixed
+
 - **Baseline duplication in dispatch delta mode** — `ctx.baselines.set()` was called with `[...allDiagnostics, ...diagnostics]`, but `allDiagnostics` already contained `diagnostics` from the push below. Baseline inflated by N items per dispatch, causing `filterDelta` to misidentify issues on subsequent writes.
 - **No delta on warnings** — `DispatchResult.warnings` was cumulative (total warning count across all runs), so the `N warning(s) -> /lens-booboo` message never decreased even when the agent fixed warnings. Added `baselineWarningCount` to track the baseline separately. Message now shows `3 new (15 total) warning(s)` so the agent sees progress.
 - **LSP sync fire-and-forget** — Phase 3 (LSP file sync) was attached via `.then()` without being awaited, so dispatch lint (phase 5) and cascade diagnostics (phase 7) ran against stale LSP state. Now properly `await`ed before subsequent phases.
@@ -484,6 +629,7 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.8.6] - 2026-04-06
 
 ### Changed
+
 - **Remove new-TODO reporting from turn_end** — The agent writes TODOs intentionally;
   reporting them back at turn-end is noise. Removed the diff-against-baseline TODO
   injection from turn-end findings.
@@ -491,20 +637,22 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.8.5] - 2026-04-06
 
 ### Fixed
+
 - **Pyright CLI duplicates LSP under `--lens-lsp`** — The Pyright CLI runner now skips
   itself when `--lens-lsp` is active, mirroring the existing `ts-lsp` behaviour. The
   `lsp` runner (priority 4, Pyright language server) already covers Python type-checking
   in that mode; running the CLI in parallel was redundant.
 
-
 ## [3.8.2] - 2026-04-06
 
 ### Fixed
+
 - **npm publish bump** — 3.8.1 was already published with the broken postinstall; 3.8.2 contains the actual fix.
 
 ## [3.8.1] - 2026-04-06
 
 ### Fixed
+
 - **`console-statement` hijacking `no-console-in-tests`** — The keyword match for
   `console-statement` (`pattern.includes("console")`) was catching `no-console-in-tests`
   because both contain "console". The simpler rule always won, so both fired on every
@@ -557,20 +705,24 @@ All notable changes to pi-lens will be documented in this file.
 ### Added — New Rules (50+)
 
 **Structural safety (ast-grep, TypeScript + JavaScript):**
+
 - `unchecked-sync-fs` — `fs.statSync/readFileSync/writeFileSync/...` outside try/catch (error)
 - `unchecked-throwing-call` — `JSON.parse`, `new URL()`, `execSync` outside try/catch (error)
 - `no-nan-comparison` — `x === NaN` always false, use `Number.isNaN()` (error)
 - `no-discarded-error` — `new Error()` as standalone statement without throw (error)
 
 **Structural safety (ast-grep, Python):**
+
 - `unchecked-throwing-call-python` — `open()`, `json.loads()`, `os.stat()` etc. outside
   try/except (error)
 
 **Structural safety (ast-grep, Ruby):**
+
 - `unchecked-throwing-call-ruby` — `File.read`, `JSON.parse`, `Integer()` etc. outside
   begin/rescue (error)
 
 **Tree-sitter Python rules (new):**
+
 - `python-mutable-class-attr` — class-level `list`/`dict`/`set` shared across all instances (error)
 - `python-debugger` — `breakpoint()`, `pdb.set_trace()` left in code (error)
 - `python-print-statement` — `print()` debug output in production code (warning)
@@ -580,6 +732,7 @@ All notable changes to pi-lens will be documented in this file.
 - `python-raise-string` — `raise "string"` is TypeError in Python 3 (error)
 
 **Tree-sitter Ruby rules (new):**
+
 - `ruby-rescue-exception` — `rescue Exception` catches SystemExit and signals (error)
 - `ruby-empty-rescue` — rescue with no body silently swallows errors (error)
 - `ruby-debugger` — `binding.pry` / `binding.irb` left in code (error)
@@ -588,13 +741,14 @@ All notable changes to pi-lens will be documented in this file.
 - `ruby-unsafe-regex` — `Regexp.new(variable)` ReDoS risk (error)
 
 **Tree-sitter Go rules (new):**
+
 - `go-hardcoded-secrets` — hardcoded credentials in short/var/const declarations (error)
 
 **JavaScript coverage (38 new rules):**
-  All runtime-applicable TypeScript ast-grep rules now have JavaScript equivalents:
-  `strict-equality`, `empty-catch`, `no-throw-string`, `no-cond-assign`,
-  `no-async-promise-executor`, `toctou`, `no-hardcoded-secrets`, `no-inner-html`,
-  `no-insecure-randomness`, `no-sql-in-code`, `jwt-no-verify`, `weak-rsa-key`, and 26 more.
+All runtime-applicable TypeScript ast-grep rules now have JavaScript equivalents:
+`strict-equality`, `empty-catch`, `no-throw-string`, `no-cond-assign`,
+`no-async-promise-executor`, `toctou`, `no-hardcoded-secrets`, `no-inner-html`,
+`no-insecure-randomness`, `no-sql-in-code`, `jwt-no-verify`, `weak-rsa-key`, and 26 more.
 
 ### Changed — Severity Upgrades
 
@@ -671,6 +825,7 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.7.2] - 2026-04-05
 
 ### Added
+
 - **All-clear signal** — When the pipeline runs clean (no blockers, no test failures),
   the agent now receives a confirmation one-liner instead of silence:
   `✓ TypeScript clean · 12/12 tests · 847ms`
@@ -678,10 +833,12 @@ All notable changes to pi-lens will be documented in this file.
   Agents can now distinguish "checks ran clean" from "checks didn't run".
 
 ### Fixed
+
 - **Auto-fix message now names the tool** — `✅ Auto-fixed 3 issue(s) (eslint:2, biome:1)`
   instead of the vague `Auto-fixed 3 issue(s)`. Agents know exactly what was corrected.
 
 ### Security
+
 - **Remove `effect` dependency** — Used for 5 trivial `tryPromise` wrappers in one file,
   never consumed via Effect's runtime. Dead dependency removed.
 - **`--ignore-scripts` in auto-installer** — `npm install` for auto-installed tools now
@@ -700,12 +857,14 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.7.2] - 2026-04-05 (previous)
 
 ### Added
+
 - **ESLint `--fix` in autofix phase** — Projects with an ESLint config now have fixable
   issues auto-corrected (import ordering, jsx style, etc.) before dispatch runs, using
   `--fix-dry-run` to get the accurate fixed count then `--fix` to apply. Availability
   is cached per session. Only fires on JS/TS files with an ESLint config present.
 
 ### Fixed
+
 - **Misleading infinite-loop comment in biome/ruff runners** — The comment incorrectly
   stated that writing files from runners would trigger infinite loops (formatters already
   prove this isn't true). Updated to explain the real reason: dispatch runners report
@@ -717,6 +876,7 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.7.1] - 2026-04-05
 
 ### Added
+
 - **ESLint dispatch runner** — Projects with `.eslintrc` / `eslint.config.js` (any variant)
   now run ESLint automatically on every JS/TS file write. Prefers local
   `node_modules/.bin/eslint` over global. Skips silently on projects using Biome/OxLint
@@ -739,6 +899,7 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.7.0] - 2026-04-05
 
 ### Added
+
 - **Test runner in pipeline** — After every file write/edit, pi-lens now automatically detects and
   runs the corresponding test file (vitest, jest, pytest). Results surface inline so the agent sees
   failures immediately without a separate test step. Supports TypeScript/JS/Python; file-level
@@ -749,6 +910,7 @@ All notable changes to pi-lens will be documented in this file.
   Typical wall-clock savings: 500–1500ms per file write (`parallelGainMs` logged in latency log).
 
 ### Fixed
+
 - **`semantic: "none"` when 0 diagnostics** — LSP, Pyright, and type-safety runners were returning
   `semantic: "warning"` even when `diagnosticCount` was 0 (clean file). Now correctly returns
   `"none"` when no diagnostics are present, `"warning"` when warnings exist, `"blocking"` on errors.
@@ -779,6 +941,7 @@ All notable changes to pi-lens will be documented in this file.
   silent skip.
 
 ### Changed
+
 - **`startedAt` added to latency log runner entries** — Every runner entry now records when it
   started, making wall-clock vs. sequential comparisons accurate. `dispatch_complete` also logs
   `parallelGainMs = sumMs - wallClockMs` to quantify parallelism benefit.
@@ -787,6 +950,7 @@ All notable changes to pi-lens will be documented in this file.
   for runner loading; all imports are static, eliminating ~50ms warm-up latency on first dispatch.
 
 ### Tests
+
 - Added formatter venv/vendor resolution and interactive-install coverage
 - Added LSP lifecycle test suite with mock LSP server (process spawn, open/change/close, shutdown)
 
@@ -795,6 +959,7 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.6.7] - 2026-04-04
 
 ### Fixed
+
 - **LSP `ERR_STREAM_DESTROYED` crash** — When an LSP process (e.g. rust-analyzer) exits, Node.js emits
   `'error'` events on the destroyed stdio streams. Without listeners these became uncaught exceptions
   that crashed the extension. Added persistent `error` listeners to `stdin`, `stdout`, and `stderr`
@@ -802,6 +967,7 @@ All notable changes to pi-lens will be documented in this file.
   Same guard added to `NativeRustCoreClient` stdin writes.
 
 ### Added
+
 - **Rust performance core (`pi-lens-core`)** — Optional Rust binary for CPU-intensive operations.
   All features fall back to TypeScript automatically if the binary is not available (it is **not**
   built automatically on `npm install` — run `npm run rust:build` once if you have Rust installed).
@@ -819,6 +985,7 @@ All notable changes to pi-lens will be documented in this file.
   failure. Feature flag `USE_RUST = true` at top of file.
 
 ### Changed
+
 - **Similarity threshold raised from 0.75 → 0.90** — Empirical evaluation showed that below 0.90
   false positives (structurally similar but semantically unrelated functions) outnumber true
   positives with the current 57×72 matrix resolution. Applies to both the dispatch runner and
@@ -830,6 +997,7 @@ All notable changes to pi-lens will be documented in this file.
   unnamed tokens no longer pollute named slots.
 
 ### Fixed (Rust)
+
 - `tree_sitter_rust::language_rust()` → `language()` (correct API for tree-sitter-rust 0.21)
 - `FunctionInfo` missing `#[derive(Clone)]` — caused compile error in `find_similar_to`
 - `export function foo()` was missed by the index builder — TypeScript wraps exported functions
@@ -839,6 +1007,7 @@ All notable changes to pi-lens will be documented in this file.
 - Deleted orphan `test_lsp.rs` (intentional type errors caused rust-analyzer to crash the LSP stream)
 
 ### Repository
+
 - Rust source (`rust/src/`, `rust/Cargo.toml`) added to npm `files` whitelist so users can build
   the binary from an npm-installed package
 - Removed stale `src/main.rs` rule from root `.gitignore` (no such file at repo root)
@@ -849,11 +1018,11 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.6.3] - 2026-04-03
 
 ### Removed (Dead Code Cleanup)
+
 - **Deleted unused interviewer tool** — Browser-based interview with diff confirmation was never used:
   - Removed `clients/interviewer.ts` (290 lines)
   - Removed `clients/interviewer-templates.ts` (240 lines)
   - Removed initialization from `index.ts`
-  
 - **Deleted deprecated commands** — All were superseded by `/lens-booboo`:
   - `/lens-booboo-fix` command (fix-from-booboo.ts, 430 lines) — showed warning to use `/lens-booboo`
   - `/lens-fix-simplified` command (fix-simplified.ts, 770 lines) — never registered, unused
@@ -865,13 +1034,13 @@ All notable changes to pi-lens will be documented in this file.
   - All imports already used `safe-spawn.ts`, making `safe-spawn-async.ts` pure dead code
 
 ### Test Suite Overhaul
+
 - **Removed ~85 wasteful/broken test files**:
   - "Is tool available" tests (8 files) — just checked if external CLIs installed
   - Heavy integration tests (2 files) — 5s timeouts, full codebase scans
   - Broken LSP tests (7 files) — import path errors
   - Broken runner tests (7 files) — thin CLI wrappers with wrong imports
   - Trivial utility tests (5 files) — file extension parsing, string sanitization
-  
 - **Added meaningful integration tests**:
   - `tests/clients/dispatch/dispatcher-flow.test.ts` — Runner registration, execution, delta mode, conditional runners
   - `tests/extension-hooks.test.ts` — pi API: tool/command/flag registration, event handlers
@@ -882,12 +1051,14 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.6.2] - 2026-04-02
 
 ### Added
+
 - **Condensed skill auto-loading** — Injects ~70-token tool selection guidance at session start (vs 1,355 for full skills):
   - Quick reference for when to use lsp_navigation vs ast_grep_search vs grep
   - References full skills for lazy loading (ast-grep, lsp-navigation)
   - Prevents common tool selection errors without loading full skill content
 
 ### Changed
+
 - **Streamlined session start injection** — Removed TODO/Knip/jscpd reports from initial context:
   - Scans still run and cache for on-demand access via `/lens-booboo`
   - Reduces session start noise (only active tools list, error reminder, skill guidance remain)
@@ -896,15 +1067,18 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.6.1] - 2026-04-02
 
 ### Changed
+
 - **Updated package description** — More concise: "Real-time code feedback for pi — LSP, linters, formatters, type-checking, structural analysis & booboo"
 
 ### Repository
+
 - **AGENTS.md is now local-only** — Removed from git repo and added to `.gitignore` so it stays local to each developer's environment
 - **Cleaned up debug files** — Removed old test files (`_debug-*.ts`, `_trigger-test.ts`, `_test-*.ts`) from repo
 
 ## [3.6.0] - 2026-04-02
 
 ### Added
+
 - **LSP Call Hierarchy Support** — Added 3 new operations to `lsp_navigation` tool:
   - `prepareCallHierarchy` — Get callable item at position
   - `incomingCalls` — Find all functions/methods that CALL this function
@@ -923,6 +1097,7 @@ All notable changes to pi-lens will be documented in this file.
   - New thresholds: MaxCyc >10 bad, >30 critical; Entropy >4.0 bits risky, >7.0 critical
 
 ### Removed
+
 - **TDR (Technical Debt Ratio)** — Removed orphaned metric tracking system:
   - Deleted `TDREntry`, `TDRCategory` types, `tdrFindings` Map, `updateTDR()` method
   - Removed `convertDiagnosticsToTDREntries()` helper and all `tdrCategory` assignments
@@ -930,6 +1105,7 @@ All notable changes to pi-lens will be documented in this file.
   - TDI is sufficient for code health tracking; inline diagnostics provide immediate feedback
 
 ### Changed
+
 - **Updated `/lens-tdi` display** — Shows 5 category breakdown with descriptions:
   ```
   Debt breakdown:
@@ -946,6 +1122,7 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.5.0] - 2026-04-02
 
 ### Added
+
 - **Tree-sitter query compilation cache** — 10× performance improvement for structural analysis. Query files (`.yml`) are compiled to binary `.wasm-cache` format once and cached to disk. Subsequent loads use the compiled cache directly, reducing tree-sitter startup from ~50ms to ~5ms per query. Cache uses mtime-based invalidation — automatically recompiles when source `.yml` changes.
 - **Rule cache infrastructure** (`clients/cache/`) — New disk-backed cache system with:
   - `RuleCache` class for storing compiled artifacts
@@ -954,6 +1131,7 @@ All notable changes to pi-lens will be documented in this file.
   - TTL and integrity validation
 
 ### Fixed
+
 - **YAML parser colon truncation** — Fixed regex-based parser that incorrectly truncated values containing colons. Changed from `split(':', 2)` to `indexOf(':')` for proper value extraction.
 - **Tree-sitter rules directory resolution** — Fixed path resolution to use `ctx.cwd` instead of hardcoded `.pi-lens/rules/` path. Rules now load correctly from the actual project root regardless of where pi is invoked.
 - **Tree-sitter post_filter support** — Implemented missing `post_filter` functionality for tree-sitter queries. Rules with post-filters (e.g., semantic validation for `bare-except` vs specific exception handlers) now work correctly instead of being silently skipped.
@@ -961,6 +1139,7 @@ All notable changes to pi-lens will be documented in this file.
 - **Latency logging restored** — Fixed missing latency logging in `tool_result` handler. Runner timing data now correctly flows to `~/.pi-lens/latency.log` again.
 
 ### Removed
+
 - **Broken ast-grep rules** — Removed overlapping rules that were causing false positives or conflicts with tree-sitter coverage.
 
 ---
@@ -968,10 +1147,12 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.4.0] - 2026-04-02
 
 ### Fixed
+
 - **Delta mode was broken** — `dispatchLint()` created a fresh empty baseline store on every call, making delta filtering a complete no-op. Every issue looked "new" every time. Now uses a persistent session-level baseline store. First write captures baseline, subsequent writes only show NEW issues.
 - **Duplicate type-checking with `--lens-lsp`** — Both the `lsp` runner (priority 4) and `ts-lsp` runner (priority 5) were calling the same LSP service for TypeScript files. `ts-lsp` now skips when `--lens-lsp` is active.
 
 ### Added
+
 - **Inline security rules via ast-grep-napi** — Re-enabled the ast-grep-napi runner for real-time blocking on security violations (`no-eval`, `jwt-no-verify`, `no-hardcoded-secrets`, `weak-rsa-key`, `no-open-redirect`, etc.). Only error-severity rules fire inline; warnings remain in `/lens-booboo`. Skips 5 rules already covered by tree-sitter to avoid duplicates. ~9ms execution time.
 - **Pre-write duplicate detection (two layers):**
   - **Exact name match** — Checks exported names in new content against the session’s cached export index. If a function/class/type already exists in another file, blocks the write: `🔴 STOP — function X already exists in utils.ts. Import instead.`
@@ -979,6 +1160,7 @@ All notable changes to pi-lens will be documented in this file.
 - **Project similarity index at session start** — Builds 57×72 state matrices for all TS functions at session start (cached to `.pi-lens/index.json`). Makes pre-write similarity checks ~50ms instead of seconds.
 
 ### Changed
+
 - **Extracted post-write pipeline** — Moved the entire post-write pipeline (secrets, format, autofix, dispatch, tests, cascade diagnostics) from `index.ts` into `clients/pipeline.ts`. `index.ts` reduced from 1764 to 1439 lines.
 - **Removed inline complexity warnings** — `⚠️ Complexity increased: +4 cognitive` no longer shown on every write. No agent acts on this mid-task. Complexity data still captured for `/lens-booboo` and `/lens-tdi`.
 - **Simplified pre-write handler** — Removed pre-write TypeScript and LSP diagnostics checks (checked old content before write landed — post-write catches everything). Kept only complexity baseline capture and duplicate detection.
@@ -988,6 +1170,7 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.3.1] - 2026-04-02
 
 ### Fixed
+
 - **LSP spawn `EINVAL` on Windows** — `.cmd` files (e.g. `vscode-json-language-server.cmd`) found via npm global lookup were spawned without `shell: true`, causing `EINVAL` from `CreateProcess`. The `needsShell` recomputation for npm global paths incorrectly treated `.cmd` the same as `.exe`. Fixed in both primary and fallback spawn paths.
 - **Unhandled `EINVAL` rejection** — LSP error handlers only caught `ENOENT` (binary not found). `EINVAL` (binary found but can't execute directly) now caught alongside `ENOENT` in both `launchLSP` and `launchViaPackageManager`.
 
@@ -996,11 +1179,13 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.3.0] - 2026-04-02
 
 ### Removed
+
 - **`--lens-bus`**: Removed the experimental event bus system (Phase 1). The sequential dispatcher has richer features (delta mode, per-runner latency, baseline tracking) that the bus system never had.
 - **`--lens-bus-debug`**: Removed alongside `--lens-bus`.
 - **`--lens-effect`**: Removed the Effect-TS concurrent runner execution system (Phase 2). The sequential `dispatchForFile` is the authoritative implementation — it has delta mode, async `when()` handling, and latency tracking that the effect system lacked.
 
 ### Changed
+
 - **LSP client**: `waitForDiagnostics` in `clients/lsp/client.ts` now uses a local `EventEmitter` scoped to the client instance instead of the global bus for internal diagnostic signalling.
 
 ---
@@ -1008,11 +1193,13 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.2.0] - 2026-04-02
 
 ### Fixed
+
 - **LSP server initialization errors** — Fixed `workspaceFolders` capability format that caused gopls and rust-analyzer to crash with JSON RPC parse errors. Changed from object `{supported: true, changeNotifications: true}` to simple boolean `true` for broader compatibility.
 - **Formatter cwd not passed** — `formatFile` now passes `cwd` to `safeSpawn`, fixing Biome's "nested root configuration" error when formatting files in subdirectories.
 - **LSP runner error handling** — Added try-catch around LSP operations to properly detect and report server spawn/connection failures instead of silently returning empty success.
 
 ### Changed
+
 - **Go/Rust LSP initialization** — Added server-specific initialization options for better compatibility.
 
 ---
@@ -1020,6 +1207,7 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.1.3] - 2026-04-02
 
 ### Fixed
+
 - **Biome autofix: removed `--unsafe` flag** — `--unsafe` silently deleted unused variables
   and interfaces, removing code the agent was mid-way through writing (e.g. a new interface
   not yet wired up). Only safe fixes (`--write`) are now applied automatically on every write.
@@ -1041,6 +1229,7 @@ All notable changes to pi-lens will be documented in this file.
   of the actual condition. The check is now awaited properly inside `runRunner()`.
 
 ### Performance
+
 - **Biome: local binary instead of npx** — `BiomeClient` now resolves
   `node_modules/.bin/biome.cmd` (Windows) or `node_modules/.bin/biome` before falling back
   to `npx @biomejs/biome`. Eliminates ~1 s npx startup overhead per invocation.
@@ -1063,6 +1252,7 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.1.1] - 2026-04-01
 
 ### Added
+
 - **File-based latency logging** — Performance analysis via `~/.pi-lens/latency.log`
   - New `latency-logger.ts` module for centralized logging
   - Logs every runner's timing (ts-lsp, ast-grep-napi, biome, test-runner, etc.)
@@ -1075,6 +1265,7 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.1.0] - 2026-04-01
 
 ### Changed
+
 - **Consolidated ast-grep runners** — Unified CLI and NAPI runners with shared rule set
   - NAPI runner now primary for dispatch (100x faster than CLI spawn)
   - Merged ts-slop-rules (21 files) into ast-grep-rules/slop-patterns.yml (33 patterns)
@@ -1083,6 +1274,7 @@ All notable changes to pi-lens will be documented in this file.
   - CLI ast-grep kept only for `ast_grep_search` / `ast_grep_replace` tools
 
 ### Fixed
+
 - **ast-grep-napi stability** — Fixed stack overflow crashes in AST traversal
   - Added `_MAX_AST_DEPTH = 50` depth limit to `findByKind()` and `getAllNodes()`
   - Added `_MAX_RULE_DEPTH = 5` recursion limit for structured rules
@@ -1095,12 +1287,14 @@ All notable changes to pi-lens will be documented in this file.
 ## [3.0.1] - 2026-03-31
 
 ### Changed
+
 - **Documentation refresh**: Updated npm and README descriptions for v3.0.0 features
   - New tagline: "pi extension for real-time code quality"
   - Highlights 31 LSP servers, tree-sitter analysis, auto-install capability
   - Clarified blockers vs warnings split (inline vs `/lens-booboo`)
 
 ### Fixed
+
 - **Entropy threshold**: Increased from 3.5 → 5.5 bits to reduce false positives
   - Previous threshold was too sensitive for tooling codebases
   - Eliminates ~70-80% of "High entropy" warnings on legitimate complex code
@@ -1112,7 +1306,9 @@ All notable changes to pi-lens will be documented in this file.
 ### Breaking Changes
 
 #### Removed - Deprecated Commands
+
 The following deprecated commands have been removed:
+
 - `/lens-booboo-fix` → Use `/lens-booboo` with autofix capability
 - `/lens-booboo-delta` → Delta mode now automatic
 - `/lens-booboo-refactor` → Use `/lens-booboo` findings
@@ -1120,20 +1316,25 @@ The following deprecated commands have been removed:
 - `/lens-rate` → Use `/lens-booboo` quality scoring
 
 #### Changed - Blockers vs Warnings Architecture
+
 - **🔴 Blockers** (type errors, secrets, empty catch blocks) → Appear **inline** and stop the agent
 - **🟡 Warnings** (complexity, code smells) → Go to **`/lens-booboo`** only (not inline)
 - Tree-sitter rules with `severity: error` now properly block inline
 - Dispatcher checks individual diagnostic semantic, not just group default
 
 ### Added - Tree-Sitter Runner
+
 New structural analysis runner at priority 14:
+
 - **18 YAML query files** for TypeScript and Python patterns
 - TypeScript: empty-catch, eval, debugger, console-statement, hardcoded-secrets, deep-nesting, deep-promise-chain, mixed-async-styles, nested-ternary, long-parameter-list, await-in-loop, dangerously-set-inner-html
 - Python: bare-except, eval-exec, wildcard-import, is-vs-equals, mutable-default-arg, unreachable-except
 - Blockers appear inline (severity: error), warnings go to `/lens-booboo` (severity: warning)
 
 ### Added - Auto-Install for Core Tools
+
 Four tools now auto-install on first use (no manual setup required):
+
 1. **TypeScript Language Server** (`typescript-language-server`) — TS/JS type checking
 2. **Pyright** — Python type checking (`pip install pyright`)
 3. **Ruff** — Python linting (`pip install ruff`)
@@ -1142,12 +1343,15 @@ Four tools now auto-install on first use (no manual setup required):
 Installs to `.pi-lens/tools/` with verification step (`--version` check).
 
 ### Added - NAPI Security Rules
+
 Migrated 20 critical security rules to NAPI (fast native execution):
+
 - Rules with `weight >= 4` are **blocking** (stop the agent)
 - Includes: no-eval, no-hardcoded-secrets, no-implied-eval, no-inner-html, no-dangerously-set-inner-html, no-debugger, no-javascript-url, no-open-redirect, no-mutable-default, weak-rsa-key, jwt-no-verify, and more
 - NAPI runs at priority 15 (after tree-sitter, before slop rules)
 
 ### Fixed
+
 - **Tree-sitter query loading**: Added missing `loadQueries()` call before `getAllQueries()`
 - **Windows path handling**: Changed from `lastIndexOf("/")` to `path.dirname()` for cross-platform compatibility
 - **Dispatcher blocker detection**: Now checks if any individual diagnostic has `semantic === "blocking"`
@@ -1158,6 +1362,7 @@ Migrated 20 critical security rules to NAPI (fast native execution):
 - **Biome/Prettier race**: Biome is now default (priority 10), Prettier is fallback only
 
 ### Changed
+
 - **README reorganization**: Removed redundant sections (Architecture, Language Support, Rules, Delta-mode, Slop Detection)
 - **Consolidated Additional Safeguards** into Features section with Runners table
 - **Updated .gitignore**: Local tracking files stay out of repo
@@ -1196,6 +1401,7 @@ Three new lint runners with full test coverage:
   - Flag: `--no-shellcheck` to disable
 
 ### Changed
+
 - Updated README.md with new runners in dispatcher diagram and available runners table
 - Added installation instructions for new tools in Dependent Tools section
 - Added new flags to Flag Reference
@@ -1205,6 +1411,7 @@ Three new lint runners with full test coverage:
 ## [2.6.0] - 2026-03-30
 
 ### Added - Phase 1: Event Bus Architecture
+
 - **Event Bus System** (`clients/bus/`): Decoupled pub/sub for diagnostic events
   - `bus.ts` — Core publish/subscribe with `once()`, `waitFor()`, middleware support
   - `events.ts` — 12 typed event definitions (DiagnosticFound, RunnerStarted, LspDiagnostic, etc.)
@@ -1213,6 +1420,7 @@ Three new lint runners with full test coverage:
 - **New flags**: `--lens-bus`, `--lens-bus-debug` for event system control
 
 ### Added - Phase 2: Effect-TS Service Layer
+
 - **Effect-TS infrastructure** (`clients/services/`): Composable async operations
   - `runner-service.ts` — Concurrent runner execution with timeout handling
   - `effect-integration.ts` — Bus-integrated Effect dispatch
@@ -1221,6 +1429,7 @@ Three new lint runners with full test coverage:
 - **New flag**: `--lens-effect` for concurrent execution
 
 ### Added - Phase 3: Multi-LSP Client (31 Language Servers)
+
 - **LSP Core** (`clients/lsp/`): Full Language Server Protocol support
   - `client.ts` — JSON-RPC client with debounced diagnostics (150ms)
   - `server.ts` — 31 LSP server definitions with root detection
@@ -1242,6 +1451,7 @@ Three new lint runners with full test coverage:
 - **Deprecated**: Old `ts-lsp` runner falls back to built-in TypeScriptClient when `--lens-lsp` not set
 
 ### Added - Phase 4: Auto-Installation System
+
 - **Auto-installer** (`clients/installer/`): Automatic tool installation
   - `index.ts` — Core installation logic for npm/pip packages
   - `isToolInstalled()` — Check global PATH or local `.pi-lens/tools/`
@@ -1253,22 +1463,26 @@ Three new lint runners with full test coverage:
 - **LSP integration**: TypeScript and Python servers now use `ensureTool()` before spawning
 
 ### Changed - Commands
+
 - **Disabled**: `/lens-booboo-fix` — Now shows warning "currently disabled. Use /lens-booboo"
 - **Disabled**: `/lens-booboo-delta` — Now shows warning "currently disabled. Use /lens-booboo"
 - **Disabled**: `/lens-booboo-refactor` — Now shows warning "currently disabled. Use /lens-booboo"
 - **Active**: `/lens-booboo` — Full codebase review (only booboo command now)
 
 ### Changed - Architecture
+
 - **Three-phase system**: Bus → Effect → LSP can be enabled independently
 - **Dispatcher priority**: `lens-effect` > `lens-bus` > default (sequential)
 - **LSP deprecation**: Old built-in TypeScriptClient deprecated, LSP client preferred
 
 ### Documentation
+
 - **LSP configuration guide**: `docs/LSP_CONFIG.md` — How to add custom LSP servers
 - **README updated**: Added LSP section, three-phase architecture, 31 language matrix
 - **CHANGELOG restructured**: Now organized by Phase 1/2/3/4
 
 ### Technical Details
+
 - **New dependencies**: `effect` (Phase 2), `vscode-jsonrpc` (Phase 3)
 - **Lines added**: ~6,000 across 4 phases
 - **Test status**: 617 passing (3 flaky unrelated tests)
@@ -1277,6 +1491,7 @@ Three new lint runners with full test coverage:
 ## [2.5.0] - 2026-03-30
 
 ### Added
+
 - **Python tree-sitter support**: 6 structural patterns for Python code analysis
   - `bare-except` — Detects `except:` that catches SystemExit/KeyboardInterrupt
   - `mutable-default-arg` — Detects mutable defaults like `def f(x=[])`
@@ -1291,10 +1506,12 @@ Three new lint runners with full test coverage:
 - **Query file extraction**: Moved TypeScript patterns from embedded code to `rules/tree-sitter-queries/typescript/*.yml`
 
 ### Changed
+
 - **README updated**: Added Python patterns to structural analysis section
 - **Architect client**: Fixed TypeScript errors (`configPath` property declaration)
 
 ### Technical Details
+
 - Downloaded `tree-sitter-python.wasm` (458KB) for Python AST parsing
 - Post-filters for semantic validation (e.g., distinguishing bare except from specific handlers)
 - ~50ms analysis time per file for Python
@@ -1302,6 +1519,7 @@ Three new lint runners with full test coverage:
 ## [2.4.0] - 2026-03-30
 
 ### Added
+
 - **`safeSpawn` utility**: Cross-platform spawn wrapper that eliminates `DEP0190` deprecation warnings on Windows. Uses command string construction instead of shell+args array.
 - **Runner tracking for `/lens-booboo`**: Each runner now reports execution time and findings count. Summary shows `[1/10] runner name...` progress and final table with `| Runner | Status | Findings | Time |`.
 - **Shared runner utilities**: Extracted `runner-helpers.ts` with:
@@ -1317,6 +1535,7 @@ Three new lint runners with full test coverage:
 - **Type extraction**: Created `clients/ast-grep-types.ts` to break circular dependencies between `ast-grep-client`, `ast-grep-parser`, and `ast-grep-rule-manager`.
 
 ### Changed
+
 - **26 files refactored to use `safeSpawn`**: Eliminated `shell: process.platform === "win32"` deprecation pattern across all clients and runners.
 - **Updated runners to use shared utilities**:
   - `ruff.ts`, `pyright.ts` → use `createAvailabilityChecker()`
@@ -1330,16 +1549,19 @@ Three new lint runners with full test coverage:
 - **Test cleanup safety**: Fixed all test files to use `fs.existsSync()` before `fs.unlinkSync()` to prevent ENOENT errors.
 
 ### Fixed
+
 - **Circular dependencies**: Eliminated 2 cycles (`ast-grep-client` ↔ `ast-grep-parser`, `ast-grep-client` ↔ `ast-grep-rule-manager`) by extracting shared types.
 - **Test flakiness**: All 70 test files now pass consistently (666 tests total).
 
 ### Code Quality
+
 - **Lines saved**: ~350 lines of duplicated code removed across utilities and parsers.
 - **Architect violations**: Reduced from 404 to ~50-80 (after test file exclusion + relaxed rules).
 
 ## [2.3.0] - 2026-03-30
 
 ### Added
+
 - **NAPI-based runner (`ast-grep-napi`)**: 100x faster TypeScript/JavaScript analysis (~9ms vs ~1200ms). Uses `@ast-grep/napi` for native-speed structural pattern matching. Priority 15, applies to TS/JS files only.
 - **Python slop detection (`python-slop`)**: New CLI runner with ~40 AI slop patterns from slop-code-bench research. Detects chained comparisons, manual min/max, redundant if/else, list comprehension opportunities, etc.
 - **TypeScript slop detection (`ts-slop-rules`)**: ~30 patterns for TS/JS slop detection including `for-index-length`, `empty-array-check`, `redundant-filter-map`, `double-negation`, `unnecessary-array-from`.
@@ -1348,29 +1570,35 @@ Three new lint runners with full test coverage:
 - **Codebase self-scan**: `scan_codebase.test.ts` for testing the NAPI runner against the pi-lens codebase itself.
 
 ### Changed
+
 - **Architecture documentation**: Updated README with complete architecture overview, runner system diagram, and language support matrix.
 - **Disabled problematic slop rules**: `ts-for-index-length` and `ts-unnecessary-array-isarray` disabled due to false positives on legitimate index-based operations.
 - **Runner registration**: Updated `clients/dispatch/runners/index.ts` with new runner priorities (ts-lsp/pyright at 5, ast-grep-napi at 15, python-slop at 25).
 - **TS slop runner disabled**: CLI runner `ts-slop.ts` disabled in favor of NAPI-based detection (faster, same rules).
 
 ### Deprecated
+
 - **`/lens-rate` command**: Now shows deprecation warning. Needs re-structuring. Users should use `/lens-booboo` instead.
 - **`/lens-metrics` command**: Now shows deprecation warning. Temporarily disabled, will be restructured. Users should use `/lens-booboo` instead.
 
 ### Removed
+
 - **Old implementations removed**: 259 lines of deprecated command code removed from `index.ts`.
 
 ### Repository Cleanup
+
 - **Local-only files removed from GitHub**: `.pisessionsummaries/` and `refactor.md` removed from repo (still in local `.gitignore`).
 
 ## [2.1.1] - 2026-03-29
 
 ### Added
+
 - **Content-level secret scanning**: Catches secrets in ANY file type on write/edit (`.env`, `.yaml`, `.json`, not just TypeScript). Blocks before save with patterns for `sk-*`, `ghp_*`, `AKIA*`, private keys, hardcoded passwords.
 - **Project rules integration**: Scans for `.claude/rules/`, `.agents/rules/`, `CLAUDE.md`, `AGENTS.md` at session start and surfaces in system prompt.
 - **Grep-ability rules**: New ast-grep rules for `no-default-export` and `no-relative-cross-package-import` to improve agent searchability.
 
 ### Changed
+
 - **Inline feedback stripped to blocking only**: Warnings no longer shown inline (noise). Only blocking violations and test failures interrupt the agent.
 - **booboo-fix output compacted**: Summary in terminal, full plan in `.pi-lens/reports/fix-plan.tsv`.
 - **booboo-refactor output compacted**: Top 5 worst offenders in terminal, full ranked list in `.pi-lens/reports/refactor-ranked.tsv`.
@@ -1383,12 +1611,14 @@ Three new lint runners with full test coverage:
 ## [2.0.40] - 2026-03-27
 
 ### Changed
+
 - **Passive capture on every file edit**: `captureSnapshot()` now called from `tool_call` hook with 5s debounce. Zero latency — reuses complexity metrics already computed for real-time feedback.
 - **Skip duplicate snapshots**: Same commit + same MI = no write (reduces noise).
 
 ## [2.0.39] - 2026-03-27
 
 ### Added
+
 - **Historical metrics tracking**: New `clients/metrics-history.ts` module captures complexity snapshots per commit. Tracks MI, cognitive complexity, and nesting depth across sessions.
 - **Trend analysis in `/lens-metrics`**: New "Trend" column shows 📈/📉/➡️ with MI delta. "Trend Summary" section aggregates improving/stable/regressing counts with worst regressions.
 - **Passive capture**: Snapshots captured on every file edit (tool_call hook) + `/lens-metrics` run. Max 20 snapshots per file (sliding window).
@@ -1396,6 +1626,7 @@ Three new lint runners with full test coverage:
 ## [2.0.38] - 2026-03-27
 
 ### Changed
+
 - **Refactored 4 client files** via `/lens-booboo-refactor` loop:
   - `biome-client.ts`: Extracted `withValidatedPath()` guard pattern (4 methods consolidated)
   - `complexity-client.ts`: Extracted `analyzeFile()` pipeline into `readAndParse()`, `computeMetrics()`, `aggregateFunctionStats()`
@@ -1405,28 +1636,34 @@ Three new lint runners with full test coverage:
 ## [2.0.29] - 2026-03-26
 
 ### Added
+
 - **`clients/ts-service.ts`**: Shared TypeScript service that creates one `ts.Program` per session. Both `complexity-client` and `type-safety-client` now share the same program instead of creating a new one per file. Significant performance improvement on large codebases.
 
 ### Removed
+
 - **3 redundant ast-grep rules** that overlap with Biome: `no-var`, `prefer-template`, `no-useless-concat`. Biome handles these natively with auto-fix. ast-grep no longer duplicates this coverage.
 - **`prefer-const` from RULE_ACTIONS** — no longer needed (Biome handles directly).
 
 ### Changed
+
 - **Consolidated rule overlap**: Biome is now the single source of truth for style/format rules. ast-grep focuses on structural patterns Biome doesn't cover (security, design smells, AI slop).
 
 ## [2.0.27] - 2026-03-26
 
 ### Added
+
 - **`switch-exhaustiveness` check**: New type safety rule detects missing cases in union type switches. Uses TypeScript compiler API for type-aware analysis. Reports as inline blocker: `🔴 STOP — Switch on 'X' is not exhaustive. Missing cases: 'Y'`.
 - **`clients/type-safety-client.ts`**: New client for type safety checks. Extensible for future checks (null safety, exhaustive type guards).
 
 ### Changed
+
 - **Type safety violations added to inline feedback**: Missing switch cases now block the agent mid-task, same as TypeScript errors.
 - **Type safety violations in `/lens-booboo-fix`**: Marked as agent-fixable (add missing case or default clause).
 
 ## [2.0.26] - 2026-03-26
 
 ### Added
+
 - **5 new ast-grep rules** for AI slop detection:
   - `no-process-env`: Block direct `process.env` access (use DI or config module) — error level
   - `no-param-reassign`: Detect function parameter reassignment — warning level
@@ -1435,6 +1672,7 @@ Three new lint runners with full test coverage:
   - `no-architecture-violation`: Block cross-layer imports (models/db) — error level
 
 ### Changed
+
 - **RULE_ACTIONS updated** for new rules:
   - `agent` type (inline + booboo-fix): `no-param-reassign`, `switch-without-default`, `switch-exhaustiveness`
   - `skip` type (booboo-refactor only): `no-process-env`, `no-single-char-var`, `no-architecture-violation`
@@ -1442,12 +1680,14 @@ Three new lint runners with full test coverage:
 ## [2.0.24] - 2026-03-26
 
 ### Changed
+
 - **Simplified `/lens-booboo-refactor` confirmation flow**: Post-change report instead of pre-change gate. Agent implements first, then shows what was changed (git diff + metrics delta). User reviews and can request refinements via chat. No more temp files or dry-run diffs.
 - **Confirmation screen**: "✅ Looks good — move to next offender" / "💬 Request changes" (chat textarea). Diff display is optional.
 
 ## [2.0.23] - 2026-03-26
 
 ### Changed
+
 - **Extracted interviewer and scan modules from `index.ts`**: `index.ts` reduced by 460 lines.
   - `clients/interviewer.ts` — all browser interview infrastructure (HTML generation, HTTP server, browser launch, option selection, diff confirmation screen)
   - `clients/scan-architectural-debt.ts` — shared scanning utilities (`scanSkipViolations`, `scanComplexityMetrics`, `scoreFiles`, `extractCodeSnippet`)
@@ -1456,6 +1696,7 @@ Three new lint runners with full test coverage:
 ## [2.0.22] - 2026-03-26
 
 ### Added
+
 - **Impact metrics in interview options**: Each option now supports an `impact` object (`linesReduced`, `miProjection`, `cognitiveProjection`) rendered as colored badges in the browser form. Agent estimates impact when presenting refactoring options.
 - **Iterative confirmation loop**: Confirmation screen now includes "🔄 Describe a different approach" option with free-text textarea. Agent regenerates plan+diff based on feedback, re-opens confirmation. Repeat until user confirms or cancels.
 - **Auto-close on confirm**: Browser tab closes automatically after user submits.
@@ -1463,42 +1704,50 @@ Three new lint runners with full test coverage:
 ## [2.0.21] - 2026-03-26
 
 ### Added
+
 - **Two-step confirmation for `/lens-booboo-refactor`**: Agent implements changes, then calls `interviewer` with `confirmationMode=true` to show plan (markdown) + unified diff (green/red line coloring) + line counts at the top. User can Confirm, Cancel, or describe a different approach.
 - **Plan + diff confirmation screen**: Plan rendered as styled markdown, diff rendered with syntax-colored `+`/`-` lines. Line counts (`+N / −N`) shown in diff header.
 
 ## [2.0.20] - 2026-03-26
 
 ### Added
+
 - **Impact metrics in interview options**: Structured `impact` field per option with `linesReduced`, `miProjection`, `cognitiveProjection`. Rendered as colored badges (green for lines reduced, blue for metric projections) inside each option card.
 
 ## [2.0.19] - 2026-03-26
 
 ### Changed
+
 - **`/lens-booboo-fix` jscpd filter**: Only within-file duplicates shown in actionable section. Cross-file duplicates are architectural — shown in skip section only.
 - **AI slop filter tightened**: Require 2+ signals per file (was 1+). Single-issue flags on small files are noise — skip them.
 
 ## [2.0.18] - 2026-03-26
 
 ### Fixed
+
 - **`/lens-booboo-fix` max iterations**: Session file auto-deletes when hitting max iterations. Previously blocked with a manual "delete .pi-lens/fix-session.json" message.
 
 ## [2.0.17] - 2026-03-26
 
 ### Changed
+
 - **Agent-driven option generation**: `/lens-booboo-refactor` no longer hardcodes refactoring options per violation type. The command scans and presents the problem + code to the agent; the agent analyzes the actual code and generates 3-5 contextual options with rationale and impact estimates. Calls the `interviewer` tool to present them.
 - **`interviewer` tool**: Generic, reusable browser-based interview mechanism. Accepts `question`, `options` (with `value`, `label`, `context`, `recommended`, `impact`), and `confirmationMode`. Zero dependencies — Node's built-in `http` module + platform CLI `open`/`start`/`xdg-open`.
 
 ## [2.0.16] - 2026-03-26
 
 ### Added
+
 - **`/lens-booboo-refactor`**: Interactive architectural refactor session. Scans for worst offender by combined debt score (ast-grep skip violations + complexity metrics). Opens a browser interview with the problem, code context, and AI-generated options. Steers the agent to propose a plan and wait for user confirmation before making changes.
 
 ### Changed
+
 - **Inline tool_result suppresses skip-category rules**: `long-method`, `large-class`, `long-parameter-list`, `no-shadow`, `no-as-any`, `no-non-null-assertion`, `no-star-imports` no longer show as hard stops in real-time feedback. They are architectural — handled by `/lens-booboo-refactor` instead.
 
 ## [2.0.15] - 2026-03-26
 
 ### Removed
+
 - **Complexity metrics from real-time feedback**: MI, cognitive complexity, nesting depth, try/catch counts, and entropy scores removed from tool_result output. These were always noise — the agent never acted on "MI dropped to 5.6" mid-task. Metrics still available via `/lens-metrics` and `/lens-booboo`.
 - **Session summary injection**: The `[Session Start]` block (TODOs, dead code, jscpd, type-coverage) is no longer injected into the first tool result. Scans still run for caching purposes (exports, clones, baselines). Data surfaced on-demand via explicit commands.
 - **`/lens-todos`**: Removed (covered by `/lens-booboo`).
@@ -1506,12 +1755,14 @@ Three new lint runners with full test coverage:
 - **`/lens-deps`**: Removed — circular dep scan added to `/lens-booboo` as Part 8.
 
 ### Changed
+
 - **Hardened stop signals**: New violations (ast-grep, Biome, jscpd, duplicate exports) now all use `🔴 STOP` framing. The agent is instructed to fix these before continuing.
 - **`/lens-booboo` now includes circular dependencies**: Added as Part 8 (after type coverage) using `depChecker.scanProject`.
 
 ## [2.0.14] - 2026-03-26
 
 ### Fixed
+
 - **`/lens-booboo-fix` excludes `.js` compiled output**: Detects `tsconfig.json` and excludes `*.js` from jscpd, ast-grep, and complexity scans. Prevents double-counting of the same code in `.ts` and `.js` forms.
 - **`raw-strings` rule added to skip list**: 230 false positives in CLI/tooling codebases.
 - **`typescript-client.ts` duplication**: Extracted `resolvePosition()`, `resolveTree()`, and `toLocations()` helpers, deduplicating 6+ LSP methods.
@@ -1520,36 +1771,44 @@ Three new lint runners with full test coverage:
 ## [2.0.13] - 2026-03-26
 
 ### Removed
+
 - **`raw-strings` ast-grep rule**: Not an AI-specific pattern. Humans write magic strings too. Biome handles style. Generated 230 false positives on first real run.
 
 ## [2.0.12] - 2026-03-26
 
 ### Fixed
+
 - **`/lens-booboo-fix` sequential scan order**: Reordered to Biome/Ruff → jscpd (duplicates) → knip (dead code) → ast-grep → AI slop → remaining Biome. Duplicates should be fixed before violations (fixing one fixes both). Dead code should be deleted before fixing violations in it.
 
 ### Changed
+
 - **Remaining Biome section rephrased**: "These couldn't be auto-fixed even with `--unsafe` — fix each manually."
 
 ## [2.0.11] - 2026-03-26
 
 ### Added
+
 - **Circular dependency scan to `/lens-booboo`**: Added as Part 8, using `depChecker.scanProject()` to detect circular chains across the codebase.
 
 ### Removed
+
 - **`/lens-todos`**, **`/lens-dead-code`**, **`/lens-deps`**: Removed standalone commands — all covered by `/lens-booboo`.
 
 ## [2.0.10] - 2026-03-26
 
 ### Changed
+
 - **Session summary injection removed**: The `[Session Start]` block is no longer injected into the first tool result. Scans still run silently for caching (exports for duplicate detection, clones for jscpd, complexity baselines for deltas).
 
 ## [2.0.1] - 2026-03-25
 
 ### Fixed
+
 - **ast-grep in `/lens-booboo` was silently dropping all results** — newer ast-grep versions exit `0` with `--json` even when issues are found; fixed the exit code check.
 - **Renamed "Design Smells" to "ast-grep"** in booboo report — the scan runs all 65 rules (security, correctness, style, design), not just design smells.
 
 ### Changed
+
 - **Stronger real-time feedback messages** — all messages now use severity emoji and imperative language:
   - `🔴 Fix N TypeScript error(s) — these must be resolved`
   - `🧹 Remove N unused import(s) — they are dead code`
@@ -1564,6 +1823,7 @@ Three new lint runners with full test coverage:
 ## [2.0.0] - 2026-03-25
 
 ### Added
+
 - **`/lens-metrics` command**: Measure complexity metrics for all files. Exports a full `report.md` with A-F grades, summary stats, AI slop aggregate table, and top 10 worst files with actionable warnings.
 - **`/lens-booboo` saves full report**: Results saved to `.pi-lens/reviews/booboo-<timestamp>.md` — no truncation, all issues, agent-readable.
 - **AI slop indicators**: Four new real-time and report-based detectors:
@@ -1575,7 +1835,8 @@ Three new lint runners with full test coverage:
 - **Shared test utilities**: `createTempFile` and `setupTestEnvironment` extracted to `clients/test-utils.ts`, eliminating copy-paste across 13 test files.
 
 ### Changed
-- **Delta mode for real-time feedback**: ast-grep and Biome now only show *new* violations introduced by the current edit — not all pre-existing ones. Fixed violations shown as `✓ Fixed: rule-name (-N)`. No change = silent.
+
+- **Delta mode for real-time feedback**: ast-grep and Biome now only show _new_ violations introduced by the current edit — not all pre-existing ones. Fixed violations shown as `✓ Fixed: rule-name (-N)`. No change = silent.
 - **Removed redundant pre-write hints**: ast-grep and Biome pre-write counts removed (delta mode makes them obsolete). TypeScript pre-write warning kept (blocking errors).
 - **Test files excluded from AI slop warnings**: MI/complexity thresholds are inherently low in test files — warnings suppressed for `*.test.ts` / `*.spec.ts`.
 - **Test files excluded from TODO scanner**: Test fixture annotations (`FIXME`, `BUG`, etc.) no longer appear in TODO reports.
@@ -1584,12 +1845,14 @@ Three new lint runners with full test coverage:
 - **Removed unused dependencies**: `vscode-languageserver-protocol` and `vscode-languageserver-types` removed; `@sinclair/typebox` added (was unlisted).
 
 ### Fixed
+
 - Removed 3 unconditional `console.log` calls leaking `[scan_exports]` to terminal.
 - Duplicate Biome scan in `tool_call` hook eliminated (was scanning twice for pre-write hint + baseline).
 
 ## [1.3.14] - 2026-03-25
 
 ### Added
+
 - **Actionable feedback messages**: All real-time warnings now include specific guidance on what to do.
 - **Code entropy metric**: Shannon entropy in bits (threshold: >3.5 indicates risky AI-induced complexity).
 - **Advanced pattern matching**: `/lens-booboo` now finds structurally similar functions (e.g., `formatDate` and `formatTimestamp`).
@@ -1599,31 +1862,37 @@ Three new lint runners with full test coverage:
 ## [1.3.10] - 2026-03-25
 
 ### Added
+
 - **Actionable complexity warnings**: Real-time feedback when metrics break limits with specific fix guidance.
 
 ## [1.3.9] - 2026-03-25
 
 ### Fixed
+
 - **Entropy calculation**: Corrected to use bits with 3.5-bit threshold for AI-induced complexity.
 
 ## [1.3.8] - 2026-03-25
 
 ### Added
+
 - **Code entropy metric**: Shannon entropy to detect repetitive or unpredictable code patterns.
 
 ## [1.3.7] - 2026-03-25
 
 ### Added
+
 - **Advanced pattern matching in `/lens-booboo`**: Finds structurally similar functions across the codebase.
 
 ## [1.3.6] - 2026-03-25
 
 ### Added
+
 - **Duplicate export detection on write**: Warns when defining a function that already exists elsewhere.
 
 ## [1.3.5] - 2026-03-25
 
 ### Changed
+
 - **Consistent command prefix**: All commands now start with `lens-`.
   - `/find-todos` → `/lens-todos`
   - `/dead-code` → `/lens-dead-code`
@@ -1634,10 +1903,12 @@ Three new lint runners with full test coverage:
 ## [1.5.0] - 2026-03-23
 
 ### Added
+
 - **Real-time jscpd duplicate detection**: Code duplication is now detected on every write. Duplicates involving the edited file are shown to the agent in real-time.
 - **`/lens-review` command**: Combined code review: design smells + complexity metrics in one command.
 
 ### Changed
+
 - **Consistent command prefix**: All commands now start with `lens-`.
   - `/find-todos` → `/lens-todos`
   - `/dead-code` → `/lens-dead-code`
@@ -1648,6 +1919,7 @@ Three new lint runners with full test coverage:
 ## [1.4.0] - 2026-03-23
 
 ### Added
+
 - **Test runner feedback**: Runs corresponding test file on every write (vitest, jest, pytest). Silent if no test file exists. Disable with `--no-tests`.
 - **Complexity metrics**: AST-based analysis: Maintainability Index, Cyclomatic/Cognitive Complexity, Halstead Volume, nesting depth, function length.
 - **`/lens-metrics` command**: Full project complexity scan.
@@ -1657,38 +1929,46 @@ Three new lint runners with full test coverage:
 - **Rust language support**: New Rust client for Rust projects.
 
 ### Changed
+
 - **Improved ast-grep tool descriptions**: Better pattern guidance to prevent overly broad searches.
 
 ## [2.2.1] - 2026-03-29
 
 ### Fixed
+
 - **No auto-install**: Runners (biome, pyright) now use direct CLI commands instead of `npx`. If not installed, gracefully skip instead of attempting to download.
 
 ## [2.2.0] - 2026-03-29
 
 ### Added
+
 - **`/lens-rate` command**: Visual code quality scoring across 6 dimensions (Type Safety, Complexity, Security, Architecture, Dead Code, Tests). Shows grade A-F and colored progress bars.
 - **Pyright runner**: Real Python type-checking via pyright. Catches type errors like `result: str = add(1, 2)` that ruff misses. Runs alongside ruff (pyright for types, ruff for linting).
 - **Vitest config**: Increased test timeout to 15s for CLI spawn tests. Fixes flaky test failures when npx downloads packages.
 
 ### Fixed
+
 - **Test flakiness**: Availability tests (biome, knip, jscpd) no longer timeout when npx is downloading packages.
 
 ## [1.3.0] - 2026-03-23
 
 ### Changed
+
 - **Biome auto-fix disabled by default**: Biome still provides linting feedback, but no longer auto-fixes on write. Use `/format` to apply fixes or enable with `--autofix-biome`.
 
 ### Added
+
 - **ast-grep search/replace tools**: New `ast_grep_search` and `ast_grep_replace` tools for AST-aware code pattern matching. Supports meta-variables and 24 languages.
 - **Rule descriptions in diagnostics**: ast-grep violations now include the rule's message and note, making feedback more actionable for the agent.
 
 ### Changed
+
 - **Reduced console noise**: Extension no longer prints to console by default. Enable with `--lens-verbose`.
 
 ## [1.2.0] - 2026-03-23
 
 ### Added
+
 - GitHub repository link in npm package
 
 ## [1.1.2] - Previous