pi-lens 3.8.64 → 3.8.65

package/CHANGELOG.md

@@ -10,6 +10,16 @@ All notable changes to pi-lens will be documented in this file.
 
 ### Fixed
 
+## [3.8.65] - 2026-07-04
+
+### Added
+
+### Changed
+
+### Fixed
+
+- **Full-scan progress bar now actually renders** — the progress bar added in 3.8.64 was computed and streamed to the tool's `onUpdate`, but never displayed: `lens_diagnostics`/`lsp_diagnostics` define a custom `renderResult` (`compactRenderResult`), and the pi host renders a partial update through that renderer, which drove its summary off structured `details` and ignored the progress text in `content`. The summarizers now detect a streaming progress partial (`details.phase === "scanning"`, via the new `scanningSummaryLine` helper) and show the bar (`Scanning… [████░░░░░░] 62/123 (50%)`) during the scan, falling back to the normal diagnostic summary on completion. Also ran `npm pkg fix` to drop the `./` prefix from the `bin` paths, silencing an npm publish auto-correct warning (the published bins were already correct).
+
 ## [3.8.64] - 2026-07-04
 
 ### Added

package/dist/tools/lens-diagnostics.js

@@ -17,7 +17,7 @@ import { getLSPService } from "../clients/lsp/index.js";
 import { loadProjectDiagnosticsDeltaReport, loadProjectDiagnosticsSnapshot, reconcileProjectDiagnosticsSnapshot, } from "../clients/project-diagnostics/cache.js";
 import { scanProjectDiagnostics } from "../clients/project-diagnostics/scanner.js";
 import { getFileDiagnosticSummaries, reconcileStaleWidgetFiles, } from "../clients/widget-state.js";
-import { makeProgressReporter } from "./scan-progress.js";
+import { makeProgressReporter, scanningSummaryLine } from "./scan-progress.js";
 // The widget state exposes the full per-file diagnostic set; this is the tool's
 // own generous display budget per file (independent of the TUI's 12 cap), to
 // keep output bounded on a pathologically broken file.
@@ -61,6 +61,12 @@ flushPending = async () => { }) {
             "also scans cheap project runners (tree-sitter + fact-rules) and caches them.",
         promptSnippet: "Use lens_diagnostics mode=all to verify no blocking errors remain; use mode=full for expensive project-wide checks",
         renderResult: compactRenderResult(({ details, args, isError, text }) => {
+            // Streaming progress partials render the live bar (see scanningSummaryLine)
+            // instead of the details-driven summary, which would show "0 diagnostics"
+            // mid-scan.
+            const scanning = scanningSummaryLine(details, text);
+            if (scanning)
+                return scanning;
             const mode = details?.mode ?? (typeof args.mode === "string" ? args.mode : "delta");
             if (isError) {
                 return `lens_diagnostics ${mode} — ${text.split("\n")[0] ?? "error"}`;

package/dist/tools/lsp-diagnostics.js

@@ -11,7 +11,7 @@ import { getProjectIgnoreMatcher, isExcludedDirName, } from "../clients/file-uti
 import { getLSPService } from "../clients/lsp/index.js";
 import { combineAbortSignals } from "../clients/deadline-utils.js";
 import { baseName, compactRenderResult } from "./render-compact.js";
-import { makeProgressReporter } from "./scan-progress.js";
+import { makeProgressReporter, scanningSummaryLine } from "./scan-progress.js";
 const LANG_EXTENSIONS = {
     ".ts": [".ts", ".tsx", ".mts", ".cts"],
     ".tsx": [".ts", ".tsx", ".mts", ".cts"],
@@ -157,6 +157,10 @@ export function createLspDiagnosticsTool() {
             "Works on directories by auto-detecting file extensions and scanning all matching files.",
         promptSnippet: "Get LSP diagnostics for a file or directory (use before builds)",
         renderResult: compactRenderResult(({ details, args, isError, text }) => {
+            // Streaming progress partials render the live bar (see scanningSummaryLine).
+            const scanning = scanningSummaryLine(details, text);
+            if (scanning)
+                return scanning;
             if (isError) {
                 return `lsp_diagnostics — ${text.split("\n")[0] ?? "error"}`;
             }

package/dist/tools/scan-progress.js

@@ -4,6 +4,21 @@
  * are opaque for minutes; this streams a throttled progress bar to the tool's
  * `onUpdate` callback so the agent/user sees movement.
  */
+/**
+ * For a tool's `compactRenderResult` summarizer: when the result is a streaming
+ * progress partial (`details.phase === "scanning"`, emitted via `onUpdate` during
+ * a full scan), return the bar to display — the joined content `text` (which
+ * already holds `renderScanProgress` output), or a counts fallback. Returns
+ * `null` for a normal (non-progress) result so the caller falls through to its
+ * usual summary. Without this, the details-driven summarizer renders "0
+ * diagnostics" mid-scan and the bar never shows.
+ */
+export function scanningSummaryLine(details, text) {
+    const d = details;
+    if (d?.phase !== "scanning")
+        return null;
+    return text || `Scanning… ${d.completed ?? 0}/${d.total ?? 0}`;
+}
 /** A ≤20-char ASCII bar + counts, e.g. `Scanning… [████░░░░░░] 45/123 (37%)`. */
 export function renderScanProgress(completed, total, label = "Scanning project diagnostics") {
     const pct = total > 0 ? Math.min(100, Math.round((completed / total) * 100)) : 0;

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "pi-lens",
-	"version": "3.8.64",
+	"version": "3.8.65",
 	"type": "module",
 	"description": "Real-time code feedback for pi — LSP, linters, formatters, type-checking, structural analysis & booboo",
 	"repository": {
@@ -9,8 +9,8 @@
 	},
 	"main": "./dist/index.js",
 	"bin": {
-		"pi-lens-mcp": "./dist/mcp/server.js",
-		"pi-lens-analyze": "./dist/mcp/analyze-cli.js"
+		"pi-lens-mcp": "dist/mcp/server.js",
+		"pi-lens-analyze": "dist/mcp/analyze-cli.js"
 	},
 	"scripts": {
 		"build": "tsc --project tsconfig.build.json",