pi-lens 4.4.7 → 4.4.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (186) hide show
  1. package/CHANGELOG-USER.md +31 -0
  2. package/CHANGELOG.md +327 -0
  3. package/README.md +13 -2
  4. package/config/dependency-cruiser-eager-allowlist.json +1 -1
  5. package/config/markdownlint/run-no-fix.mjs +36 -0
  6. package/dist/{chunk-4LM3VAZH.js → chunk-2VZ3VN3N.js} +2 -2
  7. package/dist/{chunk-PUZ3E2J4.js → chunk-3HTZDY3C.js} +8 -6
  8. package/dist/{chunk-RORGS5II.js → chunk-3NPWO5UO.js} +7 -13
  9. package/dist/{chunk-MNJIXFX4.js → chunk-47UCC4MM.js} +1 -1
  10. package/dist/chunk-4ENEJHF4.js +198 -0
  11. package/dist/chunk-5GEYJJHG.js +22 -0
  12. package/dist/{chunk-U6VN4NVL.js → chunk-5YSEQHJN.js} +3 -3
  13. package/dist/{chunk-6IR3ZYIB.js → chunk-6GPB3JLL.js} +3 -3
  14. package/dist/{chunk-MB6PXBUA.js → chunk-7R5GZIA6.js} +7 -15
  15. package/dist/{chunk-DH5JPM3K.js → chunk-7UTSNTWM.js} +10 -9
  16. package/dist/{chunk-24BILSZW.js → chunk-7YTRG6YW.js} +2 -2
  17. package/dist/{chunk-KW5JQPO5.js → chunk-AACN5GNE.js} +2 -2
  18. package/dist/{chunk-PKES3ISE.js → chunk-ACRJ2GZ5.js} +2 -2
  19. package/dist/{chunk-4ZYJHQMB.js → chunk-C3YRO3EU.js} +10 -12
  20. package/dist/{chunk-PQJFG24Z.js → chunk-CB7PEVOJ.js} +1300 -946
  21. package/dist/{chunk-ABPKUVA4.js → chunk-CDFJF5YD.js} +1 -1
  22. package/dist/{chunk-T7A2HK2B.js → chunk-CJS6WE66.js} +17 -18
  23. package/dist/{chunk-3YY7IXIL.js → chunk-CM6BDY4E.js} +14 -60
  24. package/dist/{chunk-RZOXUSPC.js → chunk-CZCAZVTD.js} +16 -2
  25. package/dist/chunk-DGKFWQK4.js +23 -0
  26. package/dist/{chunk-NA7SEXHE.js → chunk-E65WJVI5.js} +7 -9
  27. package/dist/{chunk-2TF6RXWB.js → chunk-EKNYSXFB.js} +8 -10
  28. package/dist/{chunk-RRV3FNNM.js → chunk-EY6LY2HO.js} +27 -30
  29. package/dist/{chunk-LBLBAFG3.js → chunk-F6BEQWAK.js} +17 -5
  30. package/dist/{chunk-4L36HG27.js → chunk-FGNSESAC.js} +12 -14
  31. package/dist/{chunk-3FRLWYBG.js → chunk-FRUBVFXV.js} +39 -42
  32. package/dist/{chunk-FB5SCCPT.js → chunk-G22UNQID.js} +14 -15
  33. package/dist/{chunk-LV4UMYVH.js → chunk-GQTQUNCG.js} +26 -27
  34. package/dist/{chunk-E7HJ56Y7.js → chunk-H3BVMK47.js} +64 -73
  35. package/dist/chunk-H6FLQ5NW.js +28 -0
  36. package/dist/{chunk-QHSNL7B2.js → chunk-HEA3EM23.js} +15 -19
  37. package/dist/{chunk-AWDSEDER.js → chunk-HSOBIN22.js} +2 -2
  38. package/dist/{chunk-EAOK7MIZ.js → chunk-HYSKJMZK.js} +17 -4
  39. package/dist/{chunk-VUZWQ7UG.js → chunk-IICERRFF.js} +46 -72
  40. package/dist/{chunk-OXOI55RU.js → chunk-IILEH3ZC.js} +8 -10
  41. package/dist/{chunk-ZKXQKGWZ.js → chunk-J3Q2NYJR.js} +4 -3
  42. package/dist/{chunk-YHC2O2WO.js → chunk-JUZ67QZQ.js} +20 -9
  43. package/dist/chunk-KR5VGMVT.js +25 -0
  44. package/dist/{chunk-F7K5IBZG.js → chunk-KV6GQOGN.js} +41 -44
  45. package/dist/{chunk-SNDXCFRS.js → chunk-KXMJLOZF.js} +25 -23
  46. package/dist/{chunk-CB4WHS4H.js → chunk-L4Y3ROKQ.js} +3 -3
  47. package/dist/{chunk-3F6BMY53.js → chunk-L6WBJGQS.js} +1 -1
  48. package/dist/{chunk-MPKRJBPK.js → chunk-L7O774U7.js} +30 -32
  49. package/dist/{chunk-URCQWAQ4.js → chunk-LAHHGNAY.js} +21 -21
  50. package/dist/{chunk-V63BC55Q.js → chunk-LT62P654.js} +1 -1
  51. package/dist/{chunk-ZMAUPOMG.js → chunk-LWOM6LVS.js} +34 -34
  52. package/dist/{chunk-HO6LWE2E.js → chunk-MKPDIAZH.js} +21 -1
  53. package/dist/{chunk-2PHMIAKO.js → chunk-MN635QYA.js} +3 -4
  54. package/dist/{chunk-KDX35VXP.js → chunk-MQ4PPCJB.js} +166 -149
  55. package/dist/{chunk-QOE342SU.js → chunk-MRLH4MYU.js} +2 -2
  56. package/dist/{chunk-CE6VMBCB.js → chunk-N56BNAA6.js} +20 -21
  57. package/dist/{chunk-L3CMBQMH.js → chunk-N5CEGQPG.js} +14 -17
  58. package/dist/{chunk-7E2563GA.js → chunk-NCLO6E6N.js} +13 -33
  59. package/dist/{chunk-J6JP25XU.js → chunk-NL5LSKVD.js} +4 -3
  60. package/dist/{chunk-U7BD2QL7.js → chunk-NMUSOZ2D.js} +10 -12
  61. package/dist/{chunk-BZARLRJW.js → chunk-NOWH2VA2.js} +8 -33
  62. package/dist/{chunk-U2SDMG7C.js → chunk-NUSXS6YB.js} +6 -5
  63. package/dist/{chunk-ZJTT47IG.js → chunk-OSEKJEUU.js} +2 -2
  64. package/dist/{chunk-FZKFVUEC.js → chunk-OUYAUXAT.js} +647 -355
  65. package/dist/{chunk-ZE3KXHS7.js → chunk-PBZNYHMM.js} +84 -4
  66. package/dist/{chunk-U5HPROLA.js → chunk-PIIUNJIT.js} +2 -4
  67. package/dist/chunk-PKLB2XJL.js +8 -0
  68. package/dist/{chunk-RC2Z6K47.js → chunk-PRHYIA6X.js} +15 -6
  69. package/dist/{chunk-RQS4QQSD.js → chunk-PXQ45SGD.js} +2 -2
  70. package/dist/chunk-Q6JQKWPK.js +25 -0
  71. package/dist/{chunk-F6X3YJWD.js → chunk-QB7T2PHK.js} +2 -2
  72. package/dist/{chunk-TIQJPRDD.js → chunk-QGITU23N.js} +3 -2
  73. package/dist/chunk-QJJKOHLH.js +57 -0
  74. package/dist/{chunk-4LOE5R5P.js → chunk-QP33NKYC.js} +18 -15
  75. package/dist/{chunk-N5WSK2K7.js → chunk-QVBOXT3L.js} +12 -17
  76. package/dist/{chunk-DPGEAHZT.js → chunk-RNJFRXEN.js} +10 -18
  77. package/dist/{chunk-EKWX4WD3.js → chunk-RNXOWDM6.js} +10 -10
  78. package/dist/{chunk-O4BJFESU.js → chunk-RTFMDIKV.js} +1 -1
  79. package/dist/{chunk-LS3QJRUB.js → chunk-SIQHOB6P.js} +11 -13
  80. package/dist/{chunk-3K2F6UDZ.js → chunk-SLSMJPEF.js} +43 -42
  81. package/dist/chunk-T5QSLSMM.js +50 -0
  82. package/dist/chunk-TGQDAG4B.js +88 -0
  83. package/dist/{chunk-4YHYPW2G.js → chunk-THYHUIDR.js} +44 -13
  84. package/dist/{chunk-YVHBNSME.js → chunk-TMNUTMT5.js} +1099 -1100
  85. package/dist/{chunk-WDBICWH3.js → chunk-TOE2RRCS.js} +1 -1
  86. package/dist/chunk-TYHPVE5H.js +25 -0
  87. package/dist/chunk-UAKO2M6B.js +73 -0
  88. package/dist/chunk-UC5AXW5Z.js +20 -0
  89. package/dist/chunk-UTJP6WOS.js +28 -0
  90. package/dist/{chunk-DQZFQSR5.js → chunk-UXTQ3QPD.js} +4 -4
  91. package/dist/chunk-UYXV5NIS.js +20 -0
  92. package/dist/{chunk-KKCK636N.js → chunk-V2WDBOLZ.js} +10 -12
  93. package/dist/{chunk-PR6PO3ES.js → chunk-V67D6TMU.js} +22 -20
  94. package/dist/{chunk-VSFLRN5Y.js → chunk-VCRVNLE7.js} +135 -2
  95. package/dist/{chunk-CPSR3AVL.js → chunk-VO4JFPTV.js} +2 -2
  96. package/dist/{chunk-XT2HTCJ5.js → chunk-VWLSU3XV.js} +6 -5
  97. package/dist/{chunk-WME2OQST.js → chunk-W5E72HJA.js} +66 -24
  98. package/dist/{chunk-LLS45EWB.js → chunk-W7TY6HYX.js} +6 -8
  99. package/dist/{chunk-CCV2EU7T.js → chunk-WSSLVMDA.js} +12 -13
  100. package/dist/{chunk-YISME6ON.js → chunk-WTB4GKMH.js} +10 -1
  101. package/dist/{chunk-KPPJTH44.js → chunk-X5BJ3G2P.js} +64 -35
  102. package/dist/{chunk-JMEKXFOL.js → chunk-XKFO2SZV.js} +39 -34
  103. package/dist/{chunk-HR3OJ3TH.js → chunk-XLAI7UYY.js} +84 -31
  104. package/dist/{chunk-H7OR7DFZ.js → chunk-XO756WE5.js} +53 -37
  105. package/dist/{chunk-F5Z6URKM.js → chunk-XVB3Q2PG.js} +2 -4
  106. package/dist/{chunk-R5MOQM2H.js → chunk-YOXCCJDF.js} +607 -366
  107. package/dist/{chunk-ZGSJDWQU.js → chunk-ZCQBNPRH.js} +2 -2
  108. package/dist/chunk-ZD4KVFXI.js +234 -0
  109. package/dist/{chunk-WGRJOXED.js → chunk-ZDMFGACN.js} +1295 -966
  110. package/dist/{chunk-OSTKYB55.js → chunk-ZMMHHXSW.js} +1 -1
  111. package/dist/{chunk-75GAYVNO.js → chunk-ZPM7ZIFL.js} +6 -6
  112. package/dist/{chunk-LUBPZN36.js → chunk-ZVCDHYWZ.js} +9 -11
  113. package/dist/{chunk-Y7F7IEE3.js → chunk-ZZN74OGD.js} +102 -7
  114. package/dist/{chunk-L5JYIU47.js → chunk-ZZSJAR76.js} +39 -20
  115. package/dist/index.js +10933 -8644
  116. package/dist/mcp/analyze-cli.js +12 -17
  117. package/dist/mcp/cli.js +43 -42
  118. package/dist/mcp/server.js +3073 -1147
  119. package/dist/mcp/worker.js +61 -61
  120. package/dist/probes/installer.js +18 -19
  121. package/docs/adr/0003-git-guard-latch-writer.md +11 -6
  122. package/docs/agent-tools.md +58 -16
  123. package/docs/alignment-families.md +29 -0
  124. package/docs/analysisall.md +1 -1
  125. package/docs/ast-grep_rules_catalog.md +6 -4
  126. package/docs/ci-bot-pr-checks.md +128 -0
  127. package/docs/configuration.md +150 -12
  128. package/docs/defect-shapes.md +107 -15
  129. package/docs/engineering-principles.md +27 -2
  130. package/docs/environment-variables.md +18 -1
  131. package/docs/features.md +14 -7
  132. package/docs/globalconfig.md +11 -3
  133. package/docs/invariants/git-guard-host.md +7 -3
  134. package/docs/invariants/language-config.md +15 -4
  135. package/docs/invariants/lsp-trust-exec.md +25 -4
  136. package/docs/invariants/paths-os.md +4 -2
  137. package/docs/invariants/session-telemetry.md +2 -2
  138. package/docs/language-coverage.md +1 -0
  139. package/docs/lsp-capability-matrix.md +167 -65
  140. package/docs/lsp-idle-eviction.md +4 -1
  141. package/docs/merge-queue-rollout.md +10 -8
  142. package/docs/module-report-read-symbol.md +34 -23
  143. package/docs/pi-lens-fixer.md +34 -17
  144. package/docs/pi-lens-investigator.md +3 -0
  145. package/docs/pi-lens-merge-policy.md +34 -17
  146. package/docs/pi-lens-monitor.md +9 -0
  147. package/docs/pi-lens-orchestration.md +4 -1
  148. package/docs/pi-lens-reviewer.md +6 -6
  149. package/docs/pi-lens-subagent.md +19 -3
  150. package/docs/public-api-stability.md +57 -7
  151. package/docs/release-qa-baseline.md +7 -4
  152. package/docs/schema/pi-lens-config-v1.json +21 -2
  153. package/docs/servercapabilities.md +3 -1
  154. package/docs/settings.md +11 -7
  155. package/docs/word-index.md +20 -7
  156. package/package.json +11 -4
  157. package/rules/ast-grep-rules/rule-tests/no-accumulating-spread-js-test.yml +37 -0
  158. package/rules/ast-grep-rules/rule-tests/ts-redundant-filter-map-test.yml +12 -1
  159. package/rules/ast-grep-rules/rule-tests-disabled/filter-then-map-js-test.yml +12 -0
  160. package/rules/ast-grep-rules/rule-tests-disabled/filter-then-map-test.yml +25 -0
  161. package/rules/ast-grep-rules/rules/no-accumulating-spread-js.yml +49 -1
  162. package/rules/ast-grep-rules/rules/no-sql-in-code-execute-js.yml +1 -2
  163. package/rules/ast-grep-rules/rules/no-sql-in-code-execute.yml +1 -2
  164. package/rules/ast-grep-rules/rules/ts-redundant-filter-map.yml +9 -1
  165. package/rules/ast-grep-rules/rules-disabled/filter-then-map-js.yml +17 -0
  166. package/rules/ast-grep-rules/rules-disabled/filter-then-map.yml +36 -0
  167. package/rules/ast-grep-rules/self-scan-baseline.json +1 -1
  168. package/scripts/download-grammars.js +3 -2
  169. package/skills/pi-lens-lsp-navigation/SKILL.md +5 -1
  170. package/dist/chunk-46TNM7XZ.js +0 -88
  171. package/dist/chunk-72OKUXSD.js +0 -31
  172. package/dist/chunk-7GLOLOSH.js +0 -57
  173. package/dist/chunk-AKUUMGD5.js +0 -26
  174. package/dist/chunk-ASUXV767.js +0 -22
  175. package/dist/chunk-CTADOKYM.js +0 -25
  176. package/dist/chunk-GNSIWBAT.js +0 -106
  177. package/dist/chunk-HWDAVBFU.js +0 -49
  178. package/dist/chunk-JJ2RRESP.js +0 -58
  179. package/dist/chunk-KXF5R4UN.js +0 -48
  180. package/dist/chunk-LSC3VADM.js +0 -23
  181. package/dist/chunk-OE5ZBP7F.js +0 -443
  182. package/dist/chunk-SHLDT3OI.js +0 -27
  183. package/dist/chunk-UF7RTZSO.js +0 -27
  184. package/dist/chunk-W4WP2ERB.js +0 -30
  185. package/dist/chunk-YES5CACN.js +0 -73
  186. package/dist/chunk-Z2XAOKHK.js +0 -136
@@ -0,0 +1,31 @@
1
+ # User changelog
2
+
3
+ ## [4.4.9] - 2026-11-05
4
+
5
+ 3 features, 29 fixes, 8 other changes.
6
+
7
+ Full notes: https://github.com/apmantza/pi-lens/releases/tag/v4.4.9
8
+
9
+ ## [4.4.8] - 2026-11-01
10
+
11
+ 1 feature, 28 fixes, 6 other changes.
12
+
13
+ Full notes: https://github.com/apmantza/pi-lens/releases/tag/v4.4.8
14
+
15
+ ## [4.4.7] - 2026-10-29
16
+
17
+ 2 features, 21 fixes.
18
+
19
+ Full notes: https://github.com/apmantza/pi-lens/releases/tag/v4.4.7
20
+
21
+ ## [4.4.6] - 2026-10-27
22
+
23
+ 6 fixes, 2 other changes.
24
+
25
+ Full notes: https://github.com/apmantza/pi-lens/releases/tag/v4.4.6
26
+
27
+ ## [4.4.5] - 2026-10-25
28
+
29
+ 3 features, 67 fixes, 7 other changes.
30
+
31
+ Full notes: https://github.com/apmantza/pi-lens/releases/tag/v4.4.5
package/CHANGELOG.md CHANGED
@@ -16,6 +16,333 @@ All notable changes to pi-lens will be documented in this file.
16
16
 
17
17
  ### Security
18
18
 
19
+ ## [4.4.9] - 2026-11-05
20
+
21
+ ### Added
22
+
23
+ - **Built-in Groovy language server row.** `.groovy`, `.gvy`, `.gy` and `.gsh` files get a `groovy` LSP row for `lens_diagnostics` (`source: "lsp"`) and `lsp_navigation`. groovy-language-server publishes no release, so nothing is downloaded: pi-lens runs a `groovy-language-server` launcher from `PATH`, else `java -jar` on the jar named by `GROOVY_LANGUAGE_SERVER_JAR` (build it with `./gradlew build`), on a JDK 17 or newer found the way the Java server finds one. The server publishes only for files with errors, so a file it stays silent for reads `inconclusive`, never clean; a held empty publish no longer erases an error it just reported. `.gradle` and `Jenkinsfile` stay out unless configured under `lsp.servers`. (#5123)
24
+
25
+ - **Shorter extension update notes** — pi's Extension Updates view now reads the latest five GitHub release summaries, each with a full-notes link.
26
+
27
+ - **Groovy is a file kind (refs #5235)** — `.groovy`, `.gvy`, `.gy` and `.gsh` files, plus `Jenkinsfile`, `build.gradle` and `settings.gradle`, now classify as `groovy`, and the four extensions are selected by `lang:groovy` in `symbol_search`. The `symbol_search` `lang:` filters also accept named files (the three Groovy names, `Dockerfile`, `Makefile`), and the index collects them (#5273). The four extensions announce `groovy` to the language server; the three names have no built-in server, so writing them prints no "analysis unavailable" warning (the language-server lane reports not applicable for any file no server selects). On an adopted analysis root, a write to a file whose every planned runner the root refuses now reads "not analyzed" instead of "clean" (every kind, not only Groovy). Linting, formatting and structure for Groovy are separate slices of #5235.
28
+
29
+ ### Changed
30
+
31
+ - **`lsp_navigation` returns Neovim-style text by default (refs #1449)** — the tool and its MCP mirror `pilens_lsp_navigation` now answer with the text a Neovim LSP user sees: a `path:line:col` location list for definitions, references and call hierarchy, `hover` markdown, an indented `start-end kind name` symbol tree, `path:line:col: severity: message` diagnostic rows, and the rename summary. Pass `view: "json"` for the structured envelope from #261, unchanged; any other value falls through to text.
32
+
33
+ - **`high-complexity` now checks JavaScript files.** `.js`, `.jsx`, `.mjs`,
34
+ and `.cjs` functions, and the `.mts` and `.cts` TypeScript modules, get the
35
+ same cyclomatic and nesting warning as `.ts` and `.tsx`. One per-function
36
+ metrics table per language now feeds the rule, the review graph, and the
37
+ complexity report. Cognitive and nesting scores in `/lens-tdi` and the
38
+ complexity report drop, because a `case` or `match` arm no longer scores on
39
+ its own and a function no longer counts as a nesting level. Stored history
40
+ keeps the old scale until each file is re-measured. A Python lambda now
41
+ counts once, and a Python `except` counts as a decision. A code file with no
42
+ metrics table (Java, Kotlin, C, and others) records one
43
+ `function-metrics-language-unsupported` degradation per language per
44
+ session.
45
+ (closes #5086)
46
+
47
+ - **`module_report` view is now a preset** — `view` names projection ×
48
+ format: `summary-text` (default, metrics off, text), `summary-json`,
49
+ `full-text`, `full-json` (every field, JSON). Applies to `module_report`
50
+ and `pilens_module_report`. The text cell mirrors its JSON payload field by
51
+ field (metrics as `cx:`/`fan:` suffixes, flags per bracket, `used-by:`
52
+ lines, `IMPORTS:` / `CALL GRAPH:` / `BLAST RADIUS:` blocks, `PROVENANCE:`
53
+ footer), with one declared exception: a member's own `exported` flag rides
54
+ on its container's section and has no member-level marker. The stale
55
+ `summary` / `default` / `compact` names fall through to the default, and a
56
+ `maxRefsPerSymbol` argument promotes the projection to `full`. MCP no
57
+ longer wraps the payload in a fenced JSON block.
58
+ (refs #5137)
59
+
60
+ - **`project_report` returns a line-oriented text report by default (refs #5150)** — the tool and its MCP mirror `pilens_project_report` now answer with the compact text cell on every path, warm or cold, so the first tool an agent calls no longer spends a full JSON document on an orientation read. Pass `view: "json"` to get the same engine document as before, byte-for-byte; any other value falls through to text. The MCP warm path also stops appending a fenced JSON copy and reports staleness in its own trailing block.
61
+
62
+ - **Pi 1.5 is supported:** the tested pi range now runs from 0.86.1 up to, but not including, 1.6.0.
63
+
64
+ - **Codemode scripts receive pi-lens notes in the tool text (corrects #3832)** — A codemode script gets each pi-lens tool's joined text, including the notes pi-lens appends to it, such as a blocker note. The #3832 entry said scripts get raw output without those notes. That holds only for a tool that declares an `outputSchema`, and no pi-lens tool declares one, so a script gets text and never `details`.
65
+
66
+ - **Extension update notes show counts, not headlines** — pi's Extension Updates view now lists each new release as its heading, one line counting its features, fixes and other changes, and a full-notes link. (refs #5264)
67
+
68
+ ### Fixed
69
+
70
+ - **A turn worklist owned by a process pi-lens may not signal is no longer handed to the next writer (refs #4907)** — the turn-state owner check read a permission error from `process.kill(pid, 0)` as "owner gone", so a live foreign worklist was reported `available`. It now shares the one pid-liveness check (`clients/pid-liveness.ts`) with the instance registry, the install lock, the bounded pid-file lock and the generation lock, which read that error as alive.
71
+
72
+ - **A partial edit apply now reaches other extensions' pre-write guards (closes #5120)** — When some edits of a batch matched and others did not, pi-lens wrote the matched edits itself from its `tool_call` handler, so an extension loaded after pi-lens never saw those bytes and could not refuse them. pi-lens now narrows the call's `edits` to the matched ones and lets pi's own edit tool write them, so every later `tool_call` handler sees exactly what will be written. The agent still gets the `⚠️ PARTIAL APPLY` message, now on the edit's own result. What changes for sessions with several extensions: a guard loaded after pi-lens is shown the narrowed batch, not the agent's full one, and can refuse it. A guard loaded before pi-lens still sees only the agent's batch, because pi does not re-run earlier handlers. The narrowed batch also goes through pi-lens's own read checks, so an edit to a file the agent never read is refused before anything is written. If the file changed after the check, pi's edit refuses the whole batch and the agent is told nothing was written.
73
+
74
+ - **An unknown id in `lsp.disabledServers` is reported and dropped.** A misspelled server id used to stay in the deny list with no notice and match no server, so a server you meant to turn off kept running. pi-lens now prints one `PILENS_CFG_0005` notice per unknown id, as `dispatch.disabledRunners` already does. Built-in server ids and servers declared under `lsp.servers` stay valid. (refs #5141)
75
+
76
+ - **PowerShell scripts with a UTF-8 BOM no longer get false syntax errors.** PowerShell Editor Services reported them because pi-lens sent the file's leading U+FEFF to the server as document text, which the server parses as a token. It now sends one space in its place, so every column and line ending stays where it is, and the file on disk is not touched. Other language servers receive the text as before. (refs #5151)
77
+
78
+ - **Headless sessions exit after an LSP server stops mid-message.** Disable the unused vscode-jsonrpc partial-message timeout before listening so no pending tick delays teardown. Thanks to SlanyCukr for the analysis. (#5169)
79
+
80
+ - **LSP timeouts now remain visible to navigation consumers instead of appearing as empty results.** Distinguish silent push deadlines from genuine empty answers, disclose partial diagnostics, and persist symbol lookup failures and outer deadlines.
81
+
82
+ - **`PI_LENS_DISABLE_TOOL_INSTALL=1` now stops the lazy installer, govulncheck and `npx` downloads too (#5231)** — with the switch set, `gem install rubocop`, `rustup component add clippy|rustfmt`, govulncheck's `go install` and the `npx @biomejs/biome` probe were still spawned or still downloaded, because only the managed installer read it. The first three now answer "unavailable" without spawning and record one `install-disabled` degradation row per tool per session; `npx` runs offline (`npm_config_offline=true`), so it uses npm's cache or fails. `PI_LENS_DISABLE_LSP_INSTALL` is read through one shared helper as well, with no behaviour change.
83
+
84
+ - **Keep unsupported shell dialects out of the Bash LSP.** Files named `.sh` or `.bash` now use the same shebang and `shellcheck shell=` dialect decision as the CLI runner, so zsh files no longer reach the Bash language server (follow-up to #3969).
85
+
86
+ - **A fixed or deleted file's blocker leaves the session listing and the footer (refs #5020)** — a chart-wide or import-following runner (helm-lint, helm-render, mypy, phpstan, cue-vet) reports a row for a file it was not dispatched for, and the widget store lists it under the file you wrote. The commit gate already retired its copy of that row (#5033); the widget's copy stayed until the written file was next edited. The row now records the file it cites and leaves with the gate's, at the same point. Rows persisted by an older build have no cite and are kept.
87
+
88
+ - **A blocker withheld from a script-written file now reaches the agent when its check runs long (closes #5108)** — when a file the agent wrote through a script was checked by a slow first-run analyzer (a cold Pyright, say), pi-lens stopped waiting after 10 seconds and the finding it had withheld reached nobody. The check now tells the agent at its next turn that it finished late, which file holds blockers, and where to list them, once per file.
89
+
90
+ - **`symbol_search` `ext:` filters now match compound suffixes (closes #5136)** — an `ext:` value matches by path suffix, so `ext:test.ts`, `ext:.ts` and `-ext:test.ts` behave as a reader expects for `.test.ts`, `.spec.ts` and `.d.ts` files.
91
+
92
+ - **Unknown `severity` or `read_symbol` `kind` now fails loudly instead of returning a wrong answer (refs #5138)** — `lens_diagnostics` and `lsp_diagnostics` reject a severity outside `error`, `warning`, `information`, `hint` and `all`, naming the accepted tiers, instead of silently disabling the filter and returning every finding. `read_symbol` rejects a `kind` that matches no candidate, including on a callback handle such as `run.resetLSPService@3`, rather than falling back to a symbol of another kind. An unreadable file or a kind mismatch now answers `Could not inspect <file>: <condition>` on the pi tool and on `pilens_read_symbol`, so neither reads as `Symbol ... not found`.
93
+
94
+ - **Stale-build advisories no longer break `-json` payloads (closes #5159)** — when the warm build went stale, the `warmCodeStale` advisory was appended to the last text block, so every JSON cell (`module_report` `*-json`, `project_report` `view:"json"`, `lsp_navigation`) stopped parsing exactly when an agent most needs to read it. JSON cells now carry the advisory (and any ignored-arguments note) in their own trailing annotation blocks, leaving block 0 parseable. Text cells are byte-identical.
95
+
96
+ - **Cursor's replayed edit cards are no longer refused "Edit without read" (refs #5160)** — pi-cursor-sdk replays Cursor's native work as display-only tool calls (ids prefixed `cursor-replay-`) after the files are already written. pi-lens learned the neutral `cursor` replay tool as a mutating tool and then refused every later one, turning each Cursor edit card red. Calls with that id prefix are now never armed for learning, never classified from a learned name (a `cursor` entry already saved in `observed-mutating-tools.json` is ignored for them) and never checked by the read guard, including replays shown as built-in `edit`. They take no before/after diff of the project either, and a replayed `edit`, `write` or `bash` no longer re-records another writer's change as the agent's own write. Real `edit` and `write` calls, Cursor's real bridged executions (`cursor-pi-bridge-*`) and tools that really mutate are checked as before.
97
+
98
+ - **Late authored findings still block commits.** Checks that finish after the tool-result wait expires now record their blockers and disclose them through the writing session's advisory queue; their findings rows no longer claim inline delivery when either the host's wait or the inner analysis wait discarded the result. (#5165)
99
+
100
+ - **A nearer config no longer re-enables rules you disabled.** `rules.<id>.disable` is now the union of the global, project and nested `.pi-lens.json` lists, so a project or `pkg/.pi-lens.json` that lists one rule keeps the rules the global or root config disabled. A non-string entry in the list is dropped instead of throwing in the rule filter. A global config always reports it with a config notice (#5232).
101
+
102
+ - **Applied `ast_grep_replace` and LSP rename or command edits are now checked like an `edit`.** This covers an `lsp_navigation` rename, `rename_file` and `executeCommand`. The files they write go through dispatch, so a blocker the write introduces reaches the turn-end check and `git commit` under `--lens-guard` refuses it, and a multi-file apply is no longer cut short by the read-only tool-result wall (#5239, #5248).
103
+
104
+ - **An unresolved 🔴 blocker now names itself again at the start of each later prompt (refs #5240)** — the turn-end check reached the model in one request only, and a blocker from a nested write (a codemode script that drops the STOP note) never entered the transcript, so the model saw it once. A duplicate turn end now stages the blockers alone, headed "Still unresolved (already reported on an earlier turn, not new)" and ending with the `lens_diagnostics` call that lists every blocker, and pi takes it at the first request of the next prompt. Requests inside one prompt, resolved blockers, `--no-lens-context` and blockers already retained under `--lens-retain-injections` repeat nothing.
105
+
106
+ - **Structural `ast_grep_replace` rules now work when your project has no `@ast-grep/cli` (closes #5247)** — a replace using `insideKind`, `hasKind`, `hasDescendantKind`, `follows` or `precedes` failed with `npm ERR! canceled` or `unexpected argument '--no'` because its rule scan ignored the ast-grep binary pi-lens had already found or installed. The scan now runs that binary.
107
+
108
+ - **A non-string entry in `rules.<id>.select` no longer throws in the rule filter.** `select` now drops a non-string member, or a value that is not an array, the same way `disable` does, and the valid entries keep their effect. A global config reports each one with a `PILENS_CFG_0005` notice. A project or nested file reports a value that is not an array, or a list whose members are all dropped, with the same notice, and drops a non-string member beside a valid string without one. A blank entry is dropped from `select` and `disable`, so a blank-only `select` no longer hides every rule, and a padded entry such as `" ra "` names its rule (#5250).
109
+
110
+ - **A failing vitest 5 test no longer reads as passing or clears the `--lens-guard` blocker (closes #5257)** — vitest 5 writes its JSON report to a file instead of stdout, so every per-edit test run came back unreadable and was counted as "all tests passed". pi-lens now asks vitest for the report file, treats output it cannot read as a runner error, and clears a test-failure blocker only for a test file that ran and passed at least one test.
111
+
112
+ - **A write no check covered no longer reads `✓ … clean`.** The per-edit line and the footer said clean for a TypeScript file under `--no-lsp`, a `build.gradle`, a generated file and a file whose kind has no analyzer, because the clean line was the default of a missing field. Every producer of a dispatch result now states a required `verdict`, `checked` only from the runners that completed a full read, and an unchecked write names its reason (`⚠ … unconfirmed — <reason>`); a collect-later primary still running reads unconfirmed too, once per file per session. The footer counts only files a check could have covered: a kindless or generated file says so on its write line and never adds to `⚠ N unchecked` (refs #5258).
113
+
114
+ - **A failing test result reaches the model at the next prompt**: a run that finished after the agent did, or a newer run that was still going or finished before the next prompt, used to hold the failure back until the run after (#5259). A run that finishes while the agent is working still waits for that run to end.
115
+
116
+ - **The tree-sitter rule batch is no longer compiled again on the second dispatch.** The first dispatch in a project and every later one gave the batch two identities for the same rules, so each project paid the batch compile twice. On the hot-path sample's large input, the second dispatch drops from about 590-640 ms to 280-330 ms (refs #5260).
117
+
118
+ - **A pytest run with errors beside passes no longer reads as passed (#5270)** — `1 passed, 1 error` (a fixture or collection error) was counted as a clean pass and cleared the `--lens-guard` test-failure blocker. pi-lens now treats pytest's `error` count, and exit 3 (an internal error or `pytest.exit`), as a runner error, and no longer falls back to vitest's stdout when the report file is missing. A passing run that exits 1 for its own threshold (`--cov-fail-under`) still reads as passed.
119
+
120
+ - **`symbol_search` now indexes named files.** A `Jenkinsfile`, `build.gradle`, `settings.gradle`, `Dockerfile`, `Makefile`, `CMakeLists.txt` or `terragrunt.hcl` was never in the word index, because the source walk admitted files by extension only, so `lang:groovy` had nothing to return for a `Jenkinsfile`. The index build and its incremental refresh now keep these names after the usual ignore and generated-file checks. Review graph, project diagnostics, the language profile and the TODO baseline keep their extension-only walk. (#5273)
121
+
122
+ - **An unknown or wrong-typed config key now prints its own code, not `PILENS_CFG_0001`.** A misspelled key such as `lps` prints `PILENS_CFG_0004`, and a value the schema rejects such as `format.mode: "nonsense"` prints `PILENS_CFG_0005`. `PILENS_CFG_0001` now means only that a config file is unreadable, unparsable, or not a JSON object. If you filter on `PILENS_CFG_0001` to hide these notices, filter on `PILENS_CFG_0004` and `PILENS_CFG_0005` as well, because the typo notices move to those codes. (refs #5140)
123
+
124
+ - **LSP navigation now reports request timeouts as errors instead of empty results.** Preserve timeout details when tools reuse a service across module evaluations. A definition timeout still tries the local documentSymbol fallback and discloses the timeout when recovery succeeds.
125
+
126
+ - **Vulture failures show the exception.** Python dead-code scan summaries and degradation reasons retain the last stderr line instead of the traceback header.
127
+
128
+ ### Security
129
+
130
+ - **An untrusted project can no longer set `args` or other launch fields of your LSP servers (#5147)** — a `.pi-lens.json` from a project pi has not marked trusted could set `lsp.servers.<id>.args` for a server declared in your global config, and the flags reached the server's argv. Without trust a project may now set only `name`; if it sets any other field (`args`, `rootMarkers`, `covers`, `extensions`, `env`, `initializationOptions`, `command`, `enabled`, `role`, or a field pi-lens does not recognise) on a server, that server is not started for the project, so a repo cannot start your server on flags it chose or with your own flags stripped. A refused field under `lsp.serverOverrides` drops only the project's fields: your own global override for that built-in still applies, wrapper `command` included, and the built-in stays on. A server entry with no `extensions` list (such as `{"name":"x"}`) is no longer registered, so it cannot make server selection throw `server.extensions is not iterable`. One `lsp-registry-decision` record per field says so. A trusted project and a global-only config behave as before.
131
+
132
+ ### Internal
133
+
134
+ <details>
135
+ <summary>29 internal changes: tests, CI, tooling, and refactors</summary>
136
+
137
+ - The slowest test files run faster: the route-matrix, MCP smoke, pre-push, lane-check and head-move files are split by describe over shared `tests/support` kits, the 4320, 4322 and s7 diagnostics cases wait less, the stryker-diff case spends its budget with a clock offset instead of sleeping, and the guard-bash corpus case spawns its hooks four at a time. No test was dropped; the shard weights for split files are apportioned from local ratios until CI regenerates them. (refs #3801)
138
+
139
+ - Sixty-five scripts decided "am I the entry module?" with a private copy of the gate that compared the module URL with the symlink-preserving `process.argv[1]`, so a script started through a linked path exited 0 without running: `check-changelog-fragments`, `check-pr-body` and `ci-verdict` passed without checking, and the `guard-bash` hook allowed `git stash`. They now call `isMainModule` (the `guard-bash` hook keeps a standalone realpath gate, because the probe loads it from a git ref), and `tests/config/script-entry-portability.test.ts` refuses any new private gate. (refs #4096)
140
+
141
+ - The Stryker nightly no longer launches a sampled range whose verified count alone exceeds the affordable mutant allowance. A retry or a first sample now takes the next-ranked range that fits, and when none fits it reports a zero-mutant outcome without launching Stryker. A failed count pass still launches its range unverified (refs #4171).
142
+
143
+ - PR-time CodeQL runs again on pull requests that leave `formal/` alone. `heavy-gate` reached the skipped `tla-shards` job through `tla-models`, so implicit `success()` skipped the gate and CodeQL. The gate now reads `TLA+ models` from check-runs and needs `Unit tests Windows`. The ten required contexts live in one list, `BRANCH_PROTECTION_CONTEXTS`, and the stale docs and pins that said eight now match. (refs #5002)
144
+
145
+ - A pushed pull request posts four fewer CI check rows with the same coverage: the skipped `Classify failed Unit tests` and `Finalize CI rerun classification` rows are gone, `actionlint` and `markdownlint` are steps of one gating `actionlint & markdownlint` job, and the boundary check moved into the required `Lint & type-check`. Required check names are unchanged. (refs #5002)
146
+
147
+ - A pull request posts fewer CI check rows with the same coverage: vale, jscpd, complexity, strictness, yamllint, typos and taplo are steps of one `Lint (advisory)` job, `PR title` and `Close-keyword syntax` are steps of one gating `PR metadata` job, and OSV scan starts from a `paths:` filter instead of a detect job. Required check names are unchanged. (refs #5002)
148
+
149
+ - The nightly LSP-docs refresh PR and the idle-eviction promotion PR opened with bodies that had none of the PR template's sections (and a flips fence over the 20-line cap), so `PR body (advisory)` was red on every bot push; both composers now write the template sections with docs-only answers, and `tests/scripts/bot-refresh-pr-body-lint.test.ts` runs them through the real body lint. (refs #5062)
150
+
151
+ - Count fake-LSP support routes and AstGrepClient constructions in the interim real-process-spawn census, with explicit non-spawning exemptions and serialized admissions (refs #5100).
152
+
153
+ - The cascade's changed-symbol references calls stay serial (refs #5174). Overlapping them was measured on tsserver and dropped answers under one shared 750 ms window, so the loop keeps one call at a time and a test pins that all three symbols come back.
154
+
155
+ - The read guard's three oldText autopatch span matchers (blank-line, interior-whitespace and Unicode-punctuation tiers) are one `findSignatureInsensitiveCandidate` called with a per-tier line signature, so a safety edit to the unique-match or two-anchor rule reaches every tier; recovered spans are unchanged (refs #4907).
156
+
157
+ - Route Stryker to the root minimatch 11.0.4 dependency, removing its vulnerable nested 10.x copy (#5204).
158
+
159
+ - `npm run check:lockfile` refuses a `libc` field that vanished from a package that stays in the lock, judging what the commit records: the staged blob from Git’s exported commit index (including temporary indexes for `-a` and path commits), the working copy when the index holds no change for it, and the merge base with `origin/master` when the commit records `HEAD`'s bytes unchanged. The refusal names both sides it compared, `package.json`'s `packageManager` pin and the `npx npm@11.18.0 install --package-lock-only --ignore-scripts` regeneration. npm older than the pin writes no `libc` field, so the pre-commit hook catches the drop that a PATH npm 9.2 made all 56 of in #5200; a `git show` failure the gate cannot classify refuses the run instead of reporting `not checked`. (refs #5207)
160
+
161
+ - The PR body lint's `## Summary` refusal now states the counted sentences and which line each one sits on, such as `4 counted sentences (3 in the summary, 1 in the Remaining line)`, and `.github/PULL_REQUEST_TEMPLATE.md`, `docs/pi-lens-fixer.md` and `docs/pi-lens-merge-policy.md` say that counted sentences in the `Refs #NNN`, `Remaining #NNN:` and `Closes #NNN` lines count toward the three-sentence cap. (refs #5208)
162
+
163
+ - The `Lint (advisory)` prose step runs Vale on the Markdown a pull request adds or changes under the prose paths, not on the whole docs tree every PR inherited. A PR with no such change skips the step with a notice. An unreadable diff, a change to a lint config file (`.vale.ini`, `.vale/styles`, the workflow or the selection script) and push or merge-queue runs lint the whole list. Google.DateFormat is off in `.vale.ini`, since pi-lens docs write ISO dates on purpose. (refs #5249)
164
+
165
+ - CI runs less often and opens fewer PRs. CodeQL scans once a day (and on dispatch) instead of on every master push and every pull request, so a new alert surfaces on master up to a day after its change; Dependabot groups minor and patch bumps per dependency type, security updates, and GitHub Actions bumps. (refs #5275)
166
+
167
+ - **Dead exports removed for the knip 6.44.1 bump (refs #5289)** — `summarizeWorklog` and its `WorklogStats` type (`clients/fix-worklog.ts`), `safeSpawnBatch` and the deprecated sync `isCommandAvailable` (`clients/safe-spawn.ts`) had no caller and are deleted with their sweep rows; `clients/lens-engine.ts` drops its unused re-exports of `projectModuleReport`, `renderCompactModuleReport` and four `ModuleReport*` types, which tests import from `clients/module-report.ts` directly. `resetUtf8ConsoleCodePageStateForTests` stays as the review-kept test seam (#1201), marked `@public`.
168
+
169
+ - The #3748 advisory witness ends the sessions each case starts, so the `ast-grep lsp` child its adopted-project `tool_result` spawns no longer outlives the test worker. A per-case census reds any such child the worker still owns (refs #5146).
170
+
171
+ - The #3748 advisory witness census polls, for at most 2 s, for the `ast-grep lsp` children its sessions own to leave, because the fast POSIX shutdown sends SIGTERM and returns before the child exits. A child that never leaves still reds, with the same pid list (refs #5146).
172
+
173
+ - The test files that start sessions on the pi double now end them through one shared `endMockSessions` teardown, so no `ast-grep lsp` child outlives its file and reaches the orphan sweep of a later file. The double reports every session its handlers saw, and a case that ends with one still open reds, whichever route started it (refs #5146).
174
+
175
+ - The nightly test-history download pages the artifact listing at 30 a page and parses it in node. CI printed only `unexpected end of JSON input`, with no status; an orchestrator probe on #5154 (comment 6559081169) saw HTTP 500 on the 100-a-page listing, intermittently, so a listing error now reports gh's HTTP status when gh prints one (refs #5154)
176
+
177
+ - The macOS APFS anchor fixtures now compare kernel-resolved temporary roots, and the advisory floor reds when its JSON report records failed tests (refs #5217).
178
+
179
+ - Keep Vitest's filesystem module cache separate for each worktree.
180
+
181
+ - oxfmt moves from 0.74.0 to 0.75.0, and the seven files it now wraps differently are reformatted in the same change. Formatting only; no code meaning changes. (replaces dependabot #5189)
182
+
183
+ - **Remove the frozen pre-#5150 `project_report` compact renderer (refs #5168)** — `renderCompactProjectReport`, `ProjectReportOptions.view`, `ProjectReport.view` and the engine `view` plumbing are production-dead after #5150 made the default text cell; the pi tool and the MCP mirror never passed `view` to the engine (their `view:"json"` hatch is tool-local). No observable change.
184
+
185
+ - The eight `pi.events` publish functions (`publishFilesTouched`, `publishDiagnostics`, `publishDisposition`, the four format and autofix events, and the lens events) now run one `createBusPublisher` path in `clients/live-bus-emitter.ts` instead of eight hand-copied bodies; the rows, latches and `dbg` lines they write are unchanged, and the bus-row writer is private to that seam (refs #4907). The read-only facade is named `bus-event-rollup.ts`, keeping it outside the NDJSON writer naming population.
186
+
187
+ - SpotBugs' `-output` file, PSScriptAnalyzer's `-File` script and the ast-grep baseline scratch directory now take their parent from `scannerReportParentDir()` instead of a bare `os.tmpdir()`, so a harness-owned scanner root also catches what a killed run strands; production still writes to `os.tmpdir()` (refs #4907).
188
+
189
+ - Five hand-rolled "race a promise against a timer" waits (the runner budget in `runRunner`, `getOpenDocumentSymbols`, the quiet-window heartbeat sample, the session-start sequence read and the analyze CLI's stdin read) now call `withBudget`, and the `hand-rolled-race` scan reads `Promise.race<T>(`, aliased, destructured and computed references instead of only the bare call, which registers the client-wait race in `clients/lsp/index.ts` that it could not see (refs #4907).
190
+
191
+ - The generated-header memo test in `source-filter-async.test.ts` now proves the memo through the verdict a re-read would flip, not a cold/warm wall-clock ratio that a loaded shard could invert (refs #5148, #4909).
192
+
193
+ - Five test cases that could not fail for the defect they name are rewritten or removed (git-fixture-env wrappers and TypeScript twin, a MIN_GH_TIMEOUT_MS constant check, a drift-issue constant check, a PowerShell BOM diagnostics echo); each has a mutation red or a named sibling that reds under the same mutation (refs #4907).
194
+
195
+ </details>
196
+
197
+ ## [4.4.8] - 2026-11-01
198
+
199
+ ### Added
200
+
201
+ - **`dispatch.disabledRunners` turns a dispatch runner off** — list runner ids such as `["dotnet-build"]` in `~/.pi-lens/config.json` or a project `.pi-lens.json` and pi-lens never runs them, so no `dotnet build` (or other tool) is spawned while the language server and every other runner in the group keep working. The list is a denial, resolved like `lsp.disabledServers`: the union of every tier, so a project can add a runner but never re-enable one you denied. A disabled runner is recorded as skipped with the reason `disabled-by-config`, not as a failure, and a fallback group moves on to its next runner. A nested `.pi-lens.json` governs the files under it. When config denied every checker that could not answer, the coverage notice and status line name `dispatch.disabledRunners` once per session; when a sibling also failed, they name the failure and the denial together. An id that names no runner is dropped with a `PILENS_CFG_0005` warning that quotes it (bounded like every config notice) and counted in `effective_config`'s `recordCounts`. `effective_config` shows the runner as `disabled-by-config` with the tier and file that denied it. `dispatch.runnerTimeoutFloorMs` stays global-only and a project file that sets it is now told so. `rules.<id>.disable`, `select` and `ignorePaths` now follow the same owner: each file reads them from the nearest `.pi-lens.json` at or above it, on every surface that filters by them (dispatch, `lens_diagnostics`, `lsp_diagnostics`, the turn-end advisories), and the root's policy still reaches nested files. A nested `ignorePaths` glob is relative to its own file's directory (refs #5010).
202
+
203
+ ### Changed
204
+
205
+ - **`rules.<id>.ignorePaths` now matches like the `ignore` field** — entries follow gitignore rules, relative to the `.pi-lens.json` that declares them: the last matching entry wins, `!` re-includes a path an earlier entry carved out, a leading `/` roots the entry at that file's directory, and a trailing `/` names a directory. Before, every entry was a plain glob, so a `!legacy/keep.ts` entry hid every path its glob did not name, and `/legacy/**` and `legacy/` matched nothing. Entries with a slash keep their meaning; a slashless entry such as `*.gen.ts` now also matches below the root, and a line starting with `#` is a comment. Each config file stays its own scope, so a `!` re-includes only against its own file's entries and never lifts a carve-out another file (or the global config) declared (refs #5029).
206
+
207
+ - **`ast_grep_outline` returns a compact text tree instead of JSON** — one `77-81 export function name` line per symbol, range first like `module_report` compact, with project-relative file headers; the read handles, byte offsets, node kinds and empty signatures are gone, so a file outline is about 5x to 10x smaller. The measured default case, a 60-file directory outline, now fits the delivery bound instead of arriving cut in the middle; the default call is not promised to fit every directory, and `items: "all"` or `view: "expanded"` on a large directory still hit the cut, which keeps a visible marker. Files are sorted by project-relative path before the 50-file cap, and a `... N more files not shown` line says what was left out. Read a listed range with `offset=start`, `limit=end-start+1` (#5071, refs #1449).
208
+
209
+ - **Reducer copy and filter-map warnings change.** `no-accumulating-spread-js` now flags a reduce callback that copies its accumulator through `Object.assign`, `Array.from`, `concat` or `slice`, not only through a spread, and its message names the object case. `ts-redundant-filter-map` now warns only on identity filters (`filter(x => x)`, `filter((x: T) => x)`, `filter(Boolean)`), so a TypeScript `filter().map()` chain that warned before no longer warns. The new `filter-then-map` hint ships disabled. (refs #5093, refs #5094)
210
+
211
+ - **`symbol_search` and `pilens_symbol_search` emit one table, not a table plus the same hits as JSON (refs #5104).** The pi tool appended a compact `JSON.stringify` payload that repeated every hit, and the MCP mirror appended the same hits again as a fenced JSON block; neither carried anything the rows and footer cannot. `renderCompactSymbolSearch` in `clients/lens-engine.ts` now owns the text on both surfaces: a header, one row per hit — ` 1. <path> <line> (score 0.82, 3 hit(s), fanIn 4)` — and a footer with index coverage, the MCP-only staleness note, and one next-step line naming the top-ranked hit (`module_report <path>` on pi, `pilens_module_report <path>` on MCP). Annotations print whenever the cached review graph supplies them, so `fanIn 0` ("no known importers") shows instead of vanishing. Measured on four `clients/` files, one query each, through `finalizeToolResultWithDelivery`: `bytes=3395` before, `bytes=1109` after. `details` keeps `{ available, query, count, coverage }`.
212
+
213
+ - **Twelve hand-rolled containment tests now share one `relativeInside` seam.** A runner diagnostic for the project's parent directory shows its absolute path instead of `..`, and a home directory named `..cfg` under a project directory ends the home-ceiling walk like any other (refs #2556).
214
+
215
+ - **A gitleaks or trivy scan that failed is no longer read as a clean scan.** A CLI that failed to spawn, whose run threw, or that exited non-zero without writing its report now leaves a `security-scan-report-failed` health row and a failed (not cached-clean) result, as opengrep and jscpd already did. Both scanners now share one report-scan body (`SecurityScanClient.runReportScan`), so their outcomes cannot drift apart (refs #4907).
216
+
217
+ ### Fixed
218
+
219
+ - **A bash-only turn no longer labels its fresh turn-end findings historical (refs #4617).** The provenance stamp now speaks for every part the message carries: each file-bound producer registers the files its text reports (the stale-secrets tier, knip, dead-code, trivy's scanned dependency declarations, call-graph impact, the actionable and code-quality warning advisories, the demoted inline blocker, the cascade test suggestions), and a part with no file it could be stale against — a runner crash note, a suppressed-count notice — is stamped current for the turn that produced it. A part carried from an earlier turn, or one that declares neither, still reads "Historical finding; workspace changed since capture", and `tests/config/turn-end-part-provenance-census.test.ts` fails when a new turn-end producer declares nothing.
220
+
221
+ - **A blocker retires when the language server confirms the fix, even if a scanner stayed silent.** A partial language-server run now answers for the servers that answered: the primary's recorded blockers clear, while the unconfirmed auxiliary's own blockers stay pending and still hold the commit gate shut, and the coverage notice still names it. Every edit after the once-only notice keeps naming it too, instead of reading clean. The `🔴 Still unfixed` line also lists a short rule id per line (`L64 ts:6133`) and says how many counted blockers it cannot place — one whose line could not be re-placed in the new bytes, and one with no line in this file — instead of counting lines it no longer lists. (refs #5008)
222
+
223
+ - **A blocker stays recorded when the language server answers for older bytes.** When the server's findings were computed for an earlier version of the file, the edit no longer treats them as a verdict on the new bytes: they are not delivered, a blocker recorded earlier stays pending and keeps the commit gate shut, and the next edit checks again. Before, such findings retired that blocker even though it was still in the file. The turn-end re-check of carried warnings likewise keeps a warning, marked as not re-verified, when the server's answer was for older bytes. (refs #5017)
224
+
225
+ - **An attached session no longer reads another session's stale answer as current.** When a pi-lens session shares a running language server through another session (warm attach), that session's answer now says whether its findings describe the bytes on disk, and the attached session treats findings about older bytes the way a local one does: they are not a verdict, a recorded blocker stays pending, and the tool and sweep results show them as unconfirmed. An answer from a session on an older pi-lens build carries no such statement and is treated as not current until both sessions run this build. (refs #5030)
226
+
227
+ - **A helm chart beside a denied `helm-lint` no longer reads as a failed tool** — with `helm.renderValidation` off, `helm-render` reports a stated `not-enabled` skip, so the coverage notice for a chart file says the runner is disabled in config instead of "a language tool is missing, timed out, or failed to run". The file is still reported unconfirmed (#5042).
228
+
229
+ - **The bundled `minimatch` is updated to 11.x for GHSA-g3hv-75wg-m249.** The published package inlines `minimatch`, so scanners flagged the 10.2.6 copy for a crafted glob that amplifies `globParts` when `optimizationLevel` is 2 or higher. pi-lens never sets `optimizationLevel` (the default is 1), so no pi-lens glob reached the vulnerable path; the dependency is now `^11.0.1`, and the lockfile resolves 11.0.3. One gitignore-style entry changes: a final extglob that can match nothing, such as `dir/!(x)` or `dir/*(x)`, no longer hides the whole `dir/` directory from the walk. 10.2.6 pruned that directory, so this is a fix; 11 hides only the children the extglob matches. (closes #5129)
230
+
231
+ - **The cascade no longer reports neighbour errors computed for other file bytes**: the in-turn cascade showed "Cascade errors in N neighbor file(s)" for findings the language server computed against an earlier version of the file, while the diagnostics check already withheld them; the cascade now withholds those rows too, names the file as unconfirmed instead, and never reads the run as clean (#5051).
232
+
233
+ - **A `pi-lens-ignore` comment or a disposition mark now applies to the file a finding names**: a comment in the edited Helm template no longer hides the blocking `helm-lint` error reported on `Chart.yaml`, on the edit path, in a slow runner's late answer or in the turn-end blocker; a mark on one file's finding no longer hides the same finding on another file; a finding whose file cannot be read or lies outside the project is never suppressed; and a mark made earlier against the template path for a `Chart.yaml` finding stops applying, so that finding shows once until it is marked on `Chart.yaml` (#5044).
234
+
235
+ - **A directory whose name starts with `..` is no longer read as outside its project.** Ten containment tests compared `path.relative` text with `startsWith("..")`, so a file under `<root>/..pkg/` was classed outside the root: its nested `.pi-lens.json` was not read, a hosted LSP client was not reused, a Cargo workspace member kept its own root, a rendered Helm file fell back to Chart.yaml, a mirrored test was not found, a Knip or madge shim was labelled `global`, a stale finding was not retired, and the MCP turn-end route refused the cwd. They now share `isUnderDir`, `isWithinForm`, `isWithinPathForm` and `toProjectRelativePath` from `path-utils.ts` and `file-utils.ts` (refs #2556).
236
+
237
+ - **A `pip install` into a project `.venv` that keeps no lockfile now counts as an install**, so pyright's cached `Import "x" could not be resolved` clears on the next `lsp_diagnostics` call instead of lasting for the server's life. The look stamps each `.venv/<lib|Lib>/…/site-packages` directory beside the lockfile and `node_modules` markers (#4532).
238
+
239
+ - **LSP sees outside disk changes before `lsp_diagnostics` answers; a new subdirectory marker roots it (refs #4532)** — the look that reports a declaration, config or install change walked at most once every `PI_LENS_DECLARATION_LOOK_MS` (2 s), so a `.d.ts`/`.pyi`, a server config or an install made inside that window reached no server before the answer; the diagnostics answer now runs that look itself, with a forced walk (16 ms on a 688-directory repository, 0.12 ms on a small one). Separately, the project-boundary verdict was cached for the client registry's life, negatives included, so a marker created in a subdirectory after the parent's client answered never rooted it (real pyright 1.1.414: stale through 40 calls over 20.25 s); the verdict is now read from the disk on every resolution, and a deleted marker un-roots the directory again.
240
+
241
+ - **A subagent's deferred format runs in its own settle:** with an in-process subagent, a file it wrote through a tool pi-lens observes, `ast_grep_replace`, `lens_diagnostic_mark` or a background change found at settle is now queued under the subagent, and the subagent's own `agent_settled` formats it and its native edits. Before, the parent session formatted such a write as its own, and the subagent's native edits waited for the parent's 10-minute orphan claim. A subagent still never takes the parent's records or runs the actionable-warning quick fixes (refs #4943).
242
+
243
+ - **Upward walks start from the file's real path.** A file reached through a file link now reads its target's Cargo edition, package root, `node_modules` and metrics-history commit, not the link's neighbours; every hand-rolled climb in `clients/` now runs on `walkUpDirs`, and a test runs each walker from a symlink twin (refs #4966).
244
+
245
+ - **A demoted blocker now honours your marks and stops re-serving dead coordinates:** a `[stale — re-run to confirm]` advisory runs the same disposition policy as the live blocker channel, so a `false-positive` or `suppress` mark silences it, and a `self-drift` record the agent fixed by rewriting the file retires after `SELF_DRIFT_MAX_DELIVERIES` deliveries with a "re-run can still confirm" reason. A confirmed-clean verdict that covers only some of a record's sources now retires the source rows it spoke for instead of leaving the whole record, dead coordinates included, to re-serve for the rest of the session (refs #4990).
246
+
247
+ - **A fallback language server no longer confirms a file clean for a primary that never answered.** When the Python checker was refused (an adopted project's local binary), failed to start or was not installed, python-jedi answering with nothing read as "Primary LSP (python): confirmed clean". The file now reads unavailable and names the missing primary, for both server scopes, and says no primary language server answered; the fallback's own findings are still shown, on cascade neighbours too, except an answer computed for older bytes or published before the edit, which is withheld instead of blocking the edit. A neighbour's earlier errors stay listed as not re-checked while only the fallback answers for it (refs #5014).
248
+
249
+ - **A blocker row naming another file retires with that file (refs #5020)** — a helm-lint, helm-render or mypy row recorded against the written file now leaves once the file it names is written clean or deleted, so the commit gate no longer stays shut on a finding nothing can fix.
250
+
251
+ - **`ast_grep_replace` refuses a defaulted working directory at or above `$HOME`** — the mutating tool had the ceiling `ast_grep_search` already enforced, so a dry run from your home directory previewed, and an apply rewrote, files anywhere under it. Both tools now decide through one guard in `tools/shared.ts`, and `#5039`'s refusal names the offending cwd and asks for explicit `paths`. An explicit `paths` entry such as `.` is still honoured, as in search.
252
+
253
+ - **A Java edit now cascades to the files that import it.** The cascade used to skip Java files, so an importer broken by the edit was never reported. It now asks jdtls about each importer, delivers the errors it finds, and names an importer jdtls has not re-checked since the edit as unconfirmed instead of clean (#5040).
254
+
255
+ - **A cascade dependent whose only answer predates the edit no longer reads as clean**: a push-only language server that does not republish a dependent after the file it depends on changed could leave a broken dependent reported as a clean cascade; the run now names it unconfirmed instead.
256
+
257
+ - **An edit whose dependents the graph cannot place no longer reads as a leaf.** When a caller references a changed symbol by name alone and another definition shares the name, the cascade dropped the caller and reported no neighbours, the same verdict as a file nothing uses. It now reports the run as indeterminate and says a clean cascade result does not cover those files (#5055).
258
+
259
+ - **A blocker on a file a script wrote is no longer reported as clean**: when a bash heredoc (python, node) writes a file pi-lens cannot prove you authored, the tool result now names the file and the number of blocking findings it withheld instead of `✓ clean`, and when the host's 500 ms read-only bound abandons the check, the same disclosure reaches you at the next context call with the abandonment stated. The STOP block, autofix and the commit gate stay off for those bytes (#5108).
260
+
261
+ - **A diagnostics pass no longer rewrites your file under a project fix setting**: `ruff check` now runs with `--no-fix --no-fix-only` (a project `fix = true` or `fix-only = true` used to delete unused imports on save, even with pi-lens format and autofix off) and `golangci-lint run` with `--fix=false` (`issues.fix: true`) (#5119).
262
+
263
+ - **A markdownlint diagnostics pass no longer rewrites your file under `"fix": true`**: pi-lens now lints through `markdownlint-cli2`'s exported `main` with `fix` forced off, run in a small child process under the same 15 s budget, found beside the resolved command (project `node_modules/.bin`, the managed tool dir, or a PATH install), so a project `.markdownlint-cli2.jsonc` with `"fix": true` no longer deletes trailing spaces on save even with autofix off; config discovery, `extends`, `ignores` and `overrides` stay cli2's own, an edited `.cjs` config is read fresh, the autofix stage still fixes, and when no package sits beside the command the CLI is spawned as before and one `markdownlint-api-unavailable` row is recorded (a project `"fix": true` can still write on that path) (#5119).
264
+
265
+ - **`lsp.servers.<id>.command` accepts the argv array the docs show**: `"command": ["my-lsp-server", "--stdio"]` now launches (the first element is the program, the rest come before `args`, and no default `--stdio` is added) instead of failing with `The "path" argument must be of type string`, and `effective_config` shows such a server's command and argument count (#5127).
266
+
267
+ - **A custom server that recompiles on pi-lens's own file notice can no longer wipe a real error**: when a version-less `lsp.servers` server (groovy-language-server) published an error for a freshly opened file and then an empty set right after the `workspace/didChangeWatchedFiles` pi-lens sends for that file, the file read clean; that one empty publish is now held and the error stays, and a later edit still earns its own clean. Built-in servers are unchanged (#5131).
268
+
269
+ - **A second session's commit no longer writes the first session's blockers into its own record**: with `--lens-guard`, a commit by a concurrent session in another repository that picked up the first session's settled collect-later blocker recorded it in its own tree's commit-gate record under the first session's id, so every later commit there was refused `session_mismatch` for a file it did not own. The gate now persists only the committing session's own blockers in the committed repository, and a commit in one repository is no longer refused for a blocker in another, whoever wrote it. The other session's blocker still gates its own tree (#5048).
270
+
271
+ - **A custom language server that publishes late is no longer stuck as unsupported**: a custom push-only server that had not published by the end of the first-contact wait was latched diagnostics-unsupported for the whole session, so it never reported findings and one report could list a finding beside `unsupported=1`. A publish at any time now clears the mark, and a server that has not published reads as unconfirmed (`inconclusive`), not unsupported (#5128, #5123).
272
+
273
+ - **`path` is the one single-file parameter, and `paths` behaves the same on every tool**: `pilens_module_report {path}`, `pilens_diagnostics {file}` and `pilens_analyze {path}` now run instead of being refused or silently answering for the whole default scope, `effective_config` and `lens_diagnostic_mark` accept `path` while keeping their older `file`/`filePath` spellings, a non-string, blank or empty (`[]`) `paths` list, or one over 100 entries (`ast_grep_search` took 200 before), is refused with one message on every tool instead of being dropped, and `symbol_search` now scopes `src`, `./src` and the absolute directory to the same hits and clamps `limit` to `max(1, floor)` (#5041, #5038).
274
+
275
+ ### Internal
276
+
277
+ <details>
278
+ <summary>32 internal changes: tests, CI, tooling, and refactors</summary>
279
+
280
+ - `node scripts/probe-save-verdict.mjs` measures, per server, whether a language server publishes its findings without a `textDocument/didSave` or only after one, through the real client on the tool-smoke fixtures. The nightly `tool-smoke` workflow runs it with `--install` and it regenerates the three measurement columns of `docs/lsp-capability-matrix.md`'s save-verdict table, merge-guarded so a runner that cannot install a server keeps that row, and an unmeasured row names the installer's own cause beside the reason no arm could measure it, while a tool the installer does not manage (its binary on the runner's PATH) is still measured. `tests/config/lsp-save-verdict-census.test.ts` pins the population, the verdict vocabulary and the rule that a verdict without provenance is refused. (refs #3405)
281
+
282
+ - A governance ast-grep suite (`scripts/governance-rules/`, `npm run astgrep:governance`, also run by `npm run astgrep:self-scan`) flags a test loop that waits by counting turns or polls and then checks a condition (defect shape 86), and a `*ForTests` hook in `clients/` that does the same. A real-clock deadline (`waitFor`) is the admitted form; 46 existing members sit in a reasoned, content-keyed baseline, and eight one-line members moved to `waitFor`. An `ast-grep-ignore` must name its rule and a reason. The LSP facade import sweep moved to oxlint's `no-restricted-imports`. (refs #4865)
283
+
284
+ - The tree-walk timeout census (`tests/config/tree-census-timeout.test.ts`) now scans every test under `tests/`, not only `tests/config`, so a tree walk without a timeout budget reds wherever it sits. The 87 refused members that predate the widening are admitted by name in `tests/config/tree-census-timeout.baseline.json`, each with a reason. (refs #4967)
285
+
286
+ - The session-state owner-key check now covers the file-level exemptions, the declared session stores, reset-less module containers, class fields bound to a container and containers held as members of a module-level object, so state the #4965 bugs sat in is no longer outside it. (refs #5027)
287
+
288
+ - `tests/clients/installer/managed-tool-refresh-strategies.test.ts` clears `GH_TOKEN`, `GITHUB_TOKEN`, `ZIZMOR_GITHUB_TOKEN` and `ZIZMOR_OFFLINE` for every case through `withEnv` and restores the caller's values afterwards, so a token exported in the environment no longer reds nine github cells. (#5073)
289
+
290
+ - `Targeted tests (advisory)` is gone from PR CI: its selection caught the failing file on 26.7% of real Unit reds (#3215), so the full Unit suite stays the only test gate. The changed-test shuffle (#4397) is now its own advisory job, `Changed tests shuffled (advisory)`, with only the setup it needs (refs #3215).
291
+
292
+ - `Hot-path latency (advisory)` now starts on every pull request and passes with "no hot-path files changed" when the diff touches none of `HOT_PATH_PATHS` (`scripts/ci-changed-files.mjs`), so it can become a required check without leaving docs-only pull requests at "Expected"; a hot-path diff still runs the full timing job, and a master push keeps its `paths:` filter (#4363).
293
+
294
+ - **Nightly refresh PRs start the required CI**: the job that opens the LSP-docs refresh and idle-eviction promotion PRs now dispatches `ci.yml` and `lint.yml` on the bot branch, because a PR opened with `GITHUB_TOKEN` starts no `pull_request` run and sat BLOCKED with every check absent, and `ci-verdict` now gates the non-advisory checks of a dispatch run on a bot-opened PR like a `pull_request` run (#5062).
295
+
296
+ - **CI frees runner slots, rebalances the Unit shards and keeps one npm cache**: the four `TLA+ models` shard jobs no longer start on a pull request that leaves `formal/` and its checker alone (the required `TLA+ models` aggregate still reports), the Unit shard weights are regenerated from five master runs (215 test files had no recorded duration), the Unit shards restore `~/.npm` once instead of twice, and `cache-prune.yml` also prunes when the CodeQL workflow completes on master so the overlay databases stay bounded (#5082).
297
+
298
+ - The PR-body lint prints sentence-length and filler findings as warnings and no longer fails on them. Structural rules and title-case headings still fail (#5110).
299
+
300
+ - The three required `Install test (<os>)` legs now install only when a pull request touches `INSTALL_PATHS` (`scripts/ci-changed-files.mjs`: the manifests, the lifecycle scripts, the scripts the job runs, `bin/`, the two install workflows) and otherwise pass in seconds with "no install files changed"; `Strict install (cold npm cache)`, the lint `strictness` job and the install-smoke `smoke` job (outside install paths) no longer start on a pull request, the `greeting` job starts only for a first-time author, and master pushes and dispatches keep every step (#5112).
301
+
302
+ - The nightly live cascade lane gains a typescript-go rename phase: it restores the exporter, moves it through `LSPService.renameFile` and requires each importer to reach the verdict its file calls for (refs #1712).
303
+
304
+ - The local PR-body lint sends every git read through the injected git, and the Observability record scan skips the family token of a `TLA+ unaffected:` line, so the TLA+ coverage lint cases no longer spawn real git or lex the runtime tree and stop timing out at 5 s on a loaded runner (closes #3902, refs #4909).
305
+
306
+ - **Stryker nightly bounds its range sample by mutants, not ranges (refs #4171)** — the sampler kept `ranges x allowance / mutants` ranges, which assumes every range holds the same number of mutants; run 40847865852 kept 3 ranges holding 55 mutants against ~24 affordable and exited 1 at the budget. The sample is now counted with a no-test Stryker pass and shrunk, deterministically, until it fits the allowance.
307
+
308
+ - **LSP sweeps, warm-ups, batches and project scans no longer leave an abort listener per file (refs #4907).** Five private races of a promise against the caller's `AbortSignal` added a listener and never removed it (the warm-up and its retry backoff, the per-file pre-open of a sweep, the analyzer race of a project scan, and each file of an `lsp_diagnostics` batch), so a signal that outlives one call kept a dead closure for every file it served. All seven races now go through one `untilAborted` in `clients/deadline-utils.ts`, which releases its listener when the race settles, and `tests/clients/abort-listener-release-sweep.test.ts` refuses any abort listener site it does not admit, including a computed method name or a non-literal event (an aliased import and a method fetched by `Reflect.get` stay an accepted gap).
309
+
310
+ - The lockfile-completeness npm-9 rewrite case runs real npm on rolldown's closure from the repo lock instead of all ~450 packages, and its budgets follow the lane's test-timeout scale with the gate's kill below the case budget, so a slow cold-cache runner no longer times it out (closes #4936).
311
+
312
+ - A lockfile-completeness gate that hits its npm timeout now stays inconclusive with the reason `timed out after <budget>ms` instead of `npm pin unavailable`, and the CLI line prints that reason; an acquisition outage still reads `npm pin unavailable` (#4995).
313
+
314
+ - **PR body lint: a re-spelled failure token is not a new failure path (#5019)** — the Observability failure-path scan credits a hunk's removed `catch`, `throw`, `return null` or `recordDegradationOnce` against that hunk's additions of the same kind, compares per token kind and per hunk (never per file), and lexes the reconstructed pre-image so a token inside a removed comment or string credits nothing. A body that only re-spells the condition in front of an existing `return null` now passes `pr-body.sh`, and an addition with no removed counterpart still refuses.
315
+
316
+ - The nightly save-verdict refresh keeps a settled `no`/`yes` and its evidence when a night measures `inconclusive` or `cannot measure`, and logs the held night instead of overwriting the row (#5060).
317
+
318
+ - `guard-bash` now admits the read-only `git stash list` and `git stash show` (every writing stash form and any spelling it cannot classify stays denied), and every worktree-remove refusal names the new `scripts/worktree-remove.mjs <path>`, which unlinks a `node_modules` symlink, refuses a real `node_modules` directory, then runs `git worktree remove` (#5111).
319
+
320
+ - PR bodies now have four sections (`Summary`, `Notes for the reviewer`, `Change outline`, and `Proof and checks`), and the body lint counts the parsed markdown: visible text is capped at 5000 characters, each code block at 20 lines and 400 columns (100 lines in all), the summary at three sentences and 600 characters, and reviewer notes at one list of five bullets. `Class sweep` carries an `Alignment:` line naming the families of `docs/alignment-families.md` it touches. `Why` folds into `Summary`, `Test assessment`, `Type of change`, `Area`, and `Checklist` are gone, and `Blast radius` is conditional (#5003). A table row whose cell count differs from its header (an unescaped `|` in a backticked cell splits it on GitHub) is refused.
321
+
322
+ - The ast-grep snippet directories of `dumpAst`, `validatePattern` and `validateRule`, and the helm render scratch directory, now take their parent from `scannerReportParentDir()` like every other `mkdtempSync` scanner directory, so a harness-owned scanner root also catches a directory a killed child strands (refs #4907).
323
+
324
+ - Every spawn of a System32 executable (`taskkill`, `cmd`, `chcp`, `tar`, `powershell`) in `safe-spawn`, the LSP teardowns and the installer now takes its path from `windowsExe` instead of a hand-built `%SystemRoot%` string, and `windowsExe` builds a Windows path whatever host runs it (refs #4907).
325
+
326
+ - 38 production sites that hand-rolled the backslash-to-slash fold (`.replace(/\\/g, "/")`, `.replaceAll("\\", "/")` and `.split("\\").join("/")`) now call `toPosix` from `clients/path-utils.ts`, and one fold that was a no-op (`detectFileRole`'s second fold) is deleted. Behaviour is unchanged; `tests/clients/to-posix-fold-sites.test.ts` drives 12 of the former sites through their exported callers. (refs #4907)
327
+
328
+ - Adds a nightly live cascade lane to the tool-smoke workflow: for typescript-go, rust-analyzer, gopls and jdtls it edits an exporter, calls the production cascade, and reds when an importer does not reach a conclusive verdict with the server's own finding (refs #1712). The first measured time-to-conclusive per server is committed in `tests/fixtures/lsp-cascade/measurements.json`.
329
+
330
+ - **The tmp-fixture census asserts on the Windows lane again, and a red names its producer**: the `win32` quarantine around the four census assertions is removed, each sweep now persists what it found at every registered root, and the census failure message states per leaked entry whether the registry held it at sweep time, how its birth, modification and change times sit against the last sweep, and its first-level children (#4591).
331
+
332
+ - Moves the stale-context stub out of the pi double and five pi-mock cases onto the real pi session, and retires two admit rows (refs #4937).
333
+
334
+ - Moves both NDJSON shutdown-drain cases off the pi double onto the real pi session (inline-factory mode), drops the file's census row and relabels the `handler-verdict-helper` row (refs #4937).
335
+
336
+ - Joins the loaded extension copy's deferred snapshot and probe-cache writes (and its NDJSON rows) before the tier-2 test helper removes its fixture root, so a late write no longer re-creates the root and reds the tmp-fixture hygiene census (refs #4937).
337
+
338
+ - Plants the yamllint shim of the smoke-tools cwd case outside the checkout, so it passes on a host with its own yamllint (closes #4996).
339
+
340
+ - `tests/index-lsp-config-root-eviction.test.ts` now joins the background-write drain registry before it removes its `PI_LENS_HOME` fixture, so a late project-snapshot worker write no longer re-creates the directory after a settled teardown and reds the tmp-fixture hygiene owner. The instance-registry mutation tail is left to the environment restore and the worker's own teardown (refs #5024).
341
+
342
+ - `tests/support/pi-session-commit-gate.ts` now owns one `warmGuardedSession` warm-up that pays a guarded session's cold first-session cost in a `beforeAll`, so `tests/index-4689-path-identity-witness.test.ts` no longer times out on its first case under `--sequence.seed=424`; `tests/index-4632-s4-tool-call-verdict.test.ts` calls it instead of carrying its own copy (closes #5061, refs #5023 #4909).
343
+
344
+ </details>
345
+
19
346
  ## [4.4.7] - 2026-10-29
20
347
 
21
348
  ### Added
package/README.md CHANGED
@@ -4,6 +4,8 @@
4
4
 
5
5
  # pi-lens
6
6
 
7
+ [![omp status](https://omppackages.com/badge/pi-lens.svg)](https://omppackages.com/packages/pi-lens)
8
+
7
9
  pi-lens gives AI coding agents fast, language-aware feedback while they write/edit.
8
10
 
9
11
  > **Working in this project as an AI agent?** Read the [agent guide](docs/agent-guide.md)
@@ -530,9 +532,9 @@ Thanks goes to these wonderful people:
530
532
  <td align="center" valign="top" width="14.28%"><a href="https://github.com/Nyarlathoteppppp"><img src="https://avatars.githubusercontent.com/u/126082256?v=4" width="100px;" alt=""/><br /><sub><b>bowen xu</b></sub></a><br /><a href="#code-Nyarlathoteppppp" title="Code">💻</a> <a href="https://github.com/apmantza/pi-lens/commits?author=Nyarlathoteppppp" title="Tests">⚠️</a></td>
531
533
  </tr>
532
534
  <tr>
533
- <td align="center" valign="top" width="14.28%"><a href="https://github.com/dmae97"><img src="https://avatars.githubusercontent.com/u/146327957?v=4" width="100px;" alt=""/><br /><sub><b>dmae97</b></sub></a><br /><a href="#code-dmae97" title="Code">💻</a></td>
535
+ <td align="center" valign="top" width="14.28%"><a href="https://github.com/dmae97"><img src="https://avatars.githubusercontent.com/u/146327957?v=4" width="100px;" alt=""/><br /><sub><b>dmae97</b></sub></a><br /><a href="#code-dmae97" title="Code">💻</a> <a href="#bug-dmae97" title="Bug reports">🐛</a></td>
534
536
  <td align="center" valign="top" width="14.28%"><a href="https://github.com/Battlelamb"><img src="https://avatars.githubusercontent.com/u/12995996?v=4" width="100px;" alt=""/><br /><sub><b>Battlelamb</b></sub></a><br /><a href="#code-Battlelamb" title="Code">💻</a></td>
535
- <td align="center" valign="top" width="14.28%"><a href="http://wayneh.tw/"><img src="https://avatars.githubusercontent.com/u/5166321?v=4" width="100px;" alt=""/><br /><sub><b>WeiHung</b></sub></a><br /><a href="#code-wayne930242" title="Code">💻</a></td>
537
+ <td align="center" valign="top" width="14.28%"><a href="http://wayneh.tw/"><img src="https://avatars.githubusercontent.com/u/5166321?v=4" width="100px;" alt=""/><br /><sub><b>WeiHung</b></sub></a><br /><a href="#code-wayne930242" title="Code">💻</a> <a href="#ideas-wayne930242" title="Ideas & Planning">🤔</a></td>
536
538
  <td align="center" valign="top" width="14.28%"><a href="https://github.com/wertyMSD"><img src="https://avatars.githubusercontent.com/u/130595241?v=4" width="100px;" alt=""/><br /><sub><b>wertyMSD</b></sub></a><br /><a href="#bug-wertyMSD" title="Bug reports">🐛</a></td>
537
539
  <td align="center" valign="top" width="14.28%"><a href="https://github.com/rcdailey"><img src="https://avatars.githubusercontent.com/u/1768054?v=4" width="100px;" alt=""/><br /><sub><b>Robert Dailey</b></sub></a><br /><a href="#bug-rcdailey" title="Bug reports">🐛</a></td>
538
540
  <td align="center" valign="top" width="14.28%"><a href="https://twitter.com/letwir"><img src="https://avatars.githubusercontent.com/u/16576177?v=4" width="100px;" alt=""/><br /><sub><b>letwir</b></sub></a><br /><a href="#doc-letwir" title="Documentation">📖</a></td>
@@ -541,6 +543,15 @@ Thanks goes to these wonderful people:
541
543
  <tr>
542
544
  <td align="center" valign="top" width="14.28%"><a href="https://github.com/Silvio-Re"><img src="https://avatars.githubusercontent.com/u/5860449?v=4" width="100px;" alt=""/><br /><sub><b>Silvio</b></sub></a><br /><a href="#bug-Silvio-Re" title="Bug reports">🐛</a></td>
543
545
  <td align="center" valign="top" width="14.28%"><a href="https://github.com/forge18"><img src="https://avatars.githubusercontent.com/u/31629847?v=4" width="100px;" alt=""/><br /><sub><b>forge18</b></sub></a><br /><a href="#ideas-forge18" title="Ideas & Planning">🤔</a></td>
546
+ <td align="center" valign="top" width="14.28%"><a href="https://github.com/paymog"><img src="https://avatars.githubusercontent.com/u/1986950?v=4" width="100px;" alt=""/><br /><sub><b>Paymahn Moghadasian</b></sub></a><br /><a href="#doc-paymog" title="Documentation">📖</a></td>
547
+ <td align="center" valign="top" width="14.28%"><a href="https://github.com/vjda"><img src="https://avatars.githubusercontent.com/u/20127271?v=4" width="100px;" alt=""/><br /><sub><b>Victor J. Diaz Ayuste</b></sub></a><br /><a href="#ideas-vjda" title="Ideas & Planning">🤔</a></td>
548
+ <td align="center" valign="top" width="14.28%"><a href="https://github.com/GlitchOverride"><img src="https://avatars.githubusercontent.com/u/112761176?v=4" width="100px;" alt=""/><br /><sub><b>GlitchOverride</b></sub></a><br /><a href="#bug-GlitchOverride" title="Bug reports">🐛</a></td>
549
+ <td align="center" valign="top" width="14.28%"><a href="https://github.com/sbscan"><img src="https://avatars.githubusercontent.com/u/18386839?v=4" width="100px;" alt=""/><br /><sub><b>Can Gürcan</b></sub></a><br /><a href="#ideas-sbscan" title="Ideas & Planning">🤔</a> <a href="#bug-sbscan" title="Bug reports">🐛</a></td>
550
+ <td align="center" valign="top" width="14.28%"><a href="https://github.com/zackchiutw"><img src="https://avatars.githubusercontent.com/u/107488700?v=4" width="100px;" alt=""/><br /><sub><b>Zachary Chiu</b></sub></a><br /><a href="#bug-zackchiutw" title="Bug reports">🐛</a></td>
551
+ </tr>
552
+ <tr>
553
+ <td align="center" valign="top" width="14.28%"><a href="https://github.com/yxlimo"><img src="https://avatars.githubusercontent.com/u/13878887?v=4" width="100px;" alt=""/><br /><sub><b>ShayLu</b></sub></a><br /><a href="#bug-yxlimo" title="Bug reports">🐛</a></td>
554
+ <td align="center" valign="top" width="14.28%"><a href="https://github.com/aprudkin"><img src="https://avatars.githubusercontent.com/u/126267327?v=4" width="100px;" alt=""/><br /><sub><b>aprudkin</b></sub></a><br /><a href="#bug-aprudkin" title="Bug reports">🐛</a></td>
544
555
  </tr>
545
556
  </tbody>
546
557
  </table>
@@ -6,7 +6,7 @@
6
6
  "./clients/bounded-cache.js",
7
7
  "./clients/bounded-telemetry.js",
8
8
  "./clients/build-identity.js",
9
- "./clients/bus-events-logger.js",
9
+ "./clients/bus-event-rollup.js",
10
10
  "./clients/bus-publish.js",
11
11
  "./clients/cache-manager.js",
12
12
  "./clients/cache-observability.js",
@@ -0,0 +1,36 @@
1
+ // Child entry for the markdownlint runner (#5119): runs markdownlint-cli2's
2
+ // exported `main` with `fix` forced off. cli2 has no CLI switch that turns a
3
+ // project's `"fix": true` off, and a directory config beats `--config`, so the
4
+ // runner spawns this file instead of the cli2 bin. It is a child so the
5
+ // 15 s spawn budget can kill it, so a rule's late throw cannot reach the host,
6
+ // and so an edited .cjs/.mjs config or custom rule is imported fresh.
7
+ //
8
+ // argv: <cli2 entry module> <directory> <cli2 argv...>
9
+ // Output and exit codes follow the cli2 bin: findings on stdout/stderr, exit
10
+ // 0/1 from `main`, exit 2 for anything that went wrong before or inside it.
11
+ import { pathToFileURL } from "node:url";
12
+
13
+ const [entry, directory, ...argv] = process.argv.slice(2);
14
+
15
+ function fail(thrown) {
16
+ process.stderr.write(
17
+ `${thrown instanceof Error ? (thrown.stack ?? thrown.message) : String(thrown)}\n`,
18
+ () => process.exit(2),
19
+ );
20
+ }
21
+
22
+ process.on("uncaughtException", fail);
23
+
24
+ try {
25
+ const { main } = await import(pathToFileURL(entry).href);
26
+ if (typeof main !== "function") fail(new Error(`${entry} exports no main`));
27
+ process.exitCode = await main({
28
+ directory,
29
+ argv,
30
+ optionsOverride: { fix: false },
31
+ logMessage: (message) => process.stdout.write(`${message}\n`),
32
+ logError: (message) => process.stderr.write(`${message}\n`),
33
+ });
34
+ } catch (thrown) {
35
+ fail(thrown);
36
+ }
@@ -1,10 +1,10 @@
1
1
  import { createRequire as __pilensCreateRequire } from "node:module"; const require = __pilensCreateRequire(import.meta.url);
2
2
  import {
3
3
  createToolchainAvailability
4
- } from "./chunk-CB4WHS4H.js";
4
+ } from "./chunk-L4Y3ROKQ.js";
5
5
  import {
6
6
  createSubsystemLogger
7
- } from "./chunk-KXF5R4UN.js";
7
+ } from "./chunk-W5E72HJA.js";
8
8
 
9
9
  // dist/clients/go-client.js
10
10
  import * as path from "node:path";
@@ -1,14 +1,14 @@
1
1
  import { createRequire as __pilensCreateRequire } from "node:module"; const require = __pilensCreateRequire(import.meta.url);
2
2
  import {
3
3
  getSourceFiles
4
- } from "./chunk-ABPKUVA4.js";
4
+ } from "./chunk-CDFJF5YD.js";
5
5
  import {
6
6
  readDirEntriesSafe,
7
7
  shouldRecurseIntoDir
8
- } from "./chunk-ZGSJDWQU.js";
8
+ } from "./chunk-ZCQBNPRH.js";
9
9
  import {
10
10
  getProjectIgnoreMatcher
11
- } from "./chunk-YVHBNSME.js";
11
+ } from "./chunk-TMNUTMT5.js";
12
12
  import {
13
13
  CODE_KINDS,
14
14
  DOTNET_CSHARP_ROOT_MARKERS,
@@ -17,18 +17,18 @@ import {
17
17
  LEAN_ROOT_MARKERS,
18
18
  TERRAGRUNT_FILENAMES,
19
19
  detectFileKind
20
- } from "./chunk-RZOXUSPC.js";
20
+ } from "./chunk-CZCAZVTD.js";
21
21
  import {
22
22
  findNearestDirWithAnyBasename,
23
23
  registerWorkspaceTopologyReset
24
- } from "./chunk-J6JP25XU.js";
24
+ } from "./chunk-NL5LSKVD.js";
25
25
  import {
26
26
  BoundedLruCache,
27
27
  direntsHaveMarkerGlobMatch,
28
28
  isUnderDir,
29
29
  normalizeMapKey,
30
30
  realpathOrResolve
31
- } from "./chunk-PQJFG24Z.js";
31
+ } from "./chunk-CB7PEVOJ.js";
32
32
 
33
33
  // dist/clients/language-profile.js
34
34
  import * as fs from "node:fs";
@@ -94,6 +94,7 @@ var LANGUAGE_POLICY = {
94
94
  lua: { lspCapable: true },
95
95
  zig: { lspCapable: true },
96
96
  haskell: { lspCapable: true },
97
+ groovy: { lspCapable: true },
97
98
  "helm-template": { lspCapable: false },
98
99
  elixir: { lspCapable: true },
99
100
  gleam: { lspCapable: true },
@@ -221,6 +222,7 @@ var PRIMARY_DISPATCH_GROUPS = {
221
222
  lua: { mode: "fallback", runnerIds: ["lsp"], filterKinds: ["lua"] },
222
223
  zig: { mode: "all", runnerIds: ["lsp", "zig-check"], filterKinds: ["zig"] },
223
224
  haskell: { mode: "fallback", runnerIds: ["lsp"], filterKinds: ["haskell"] },
225
+ groovy: { mode: "fallback", runnerIds: ["lsp"], filterKinds: ["groovy"] },
224
226
  "helm-template": {
225
227
  mode: "all",
226
228
  // helm-render is opt-in (`helm.renderValidation.enabled`) and skips itself