pi-lens 4.4.8 → 4.4.10
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.
- package/CHANGELOG-USER.md +31 -0
- package/CHANGELOG.md +258 -0
- package/README.md +4 -1
- package/config/dependency-cruiser-eager-allowlist.json +1 -1
- package/dist/{chunk-6YUNI7B5.js → chunk-2ADRLTM2.js} +14 -60
- package/dist/{chunk-4B2YFN4U.js → chunk-2LVJQU3I.js} +46 -33
- package/dist/{chunk-2453RRJ2.js → chunk-3FRI5H4T.js} +72 -23
- package/dist/{chunk-7MAD5ZAY.js → chunk-3HM4BUHR.js} +14 -16
- package/dist/chunk-3QWVOBZJ.js +73 -0
- package/dist/{chunk-PIQQM32Y.js → chunk-46TQJSUE.js} +4 -2
- package/dist/{chunk-RZG472YW.js → chunk-4ITEFRDH.js} +84 -46
- package/dist/{chunk-6FIRFP6A.js → chunk-4NCDHTFI.js} +10 -12
- package/dist/{chunk-7CGIDRIK.js → chunk-6I44EDNQ.js} +14 -16
- package/dist/{chunk-2BKUFQKR.js → chunk-6MDM5MQT.js} +554 -217
- package/dist/{chunk-BBET6HD6.js → chunk-7JX3RNG4.js} +1 -1
- package/dist/{chunk-JE6HKLC7.js → chunk-7WJ55KBN.js} +2 -4
- package/dist/{chunk-4BKU7PV3.js → chunk-A5TEJZGJ.js} +2 -1
- package/dist/{chunk-7ANZ7XDD.js → chunk-ACRJ2GZ5.js} +2 -2
- package/dist/{chunk-2ZE3AUJQ.js → chunk-ALIZWXHZ.js} +13 -15
- package/dist/{chunk-BQG2QFVO.js → chunk-AON2QIJF.js} +43 -55
- package/dist/chunk-B2YUE6YD.js +23 -0
- package/dist/{chunk-L4NEVZ4T.js → chunk-B6HXETWY.js} +25 -27
- package/dist/chunk-BDR5MEZY.js +25 -0
- package/dist/{chunk-HXFUTMX2.js → chunk-BGLS5SDN.js} +2 -2
- package/dist/{chunk-ZZDIOAAJ.js → chunk-BRESRQBE.js} +6 -6
- package/dist/{chunk-WXUDRAG6.js → chunk-C6AODRNU.js} +10 -12
- package/dist/{chunk-GMROJJRN.js → chunk-CB7PEVOJ.js} +9 -1
- package/dist/{chunk-BHWW6FAX.js → chunk-CTB5BAJI.js} +53 -22
- package/dist/{chunk-VN3L2JWZ.js → chunk-CYUJB552.js} +5 -5
- package/dist/{chunk-6GMGEKQN.js → chunk-CZAWWXP6.js} +39 -12
- package/dist/{chunk-G5GV2Q7K.js → chunk-CZCAZVTD.js} +16 -2
- package/dist/chunk-DBS736MA.js +57 -0
- package/dist/{chunk-OWTG6UMO.js → chunk-DOUAWKLO.js} +75 -22
- package/dist/{chunk-BOPDQ7AZ.js → chunk-DVRJBQOJ.js} +19 -21
- package/dist/{chunk-UHHLR2VY.js → chunk-E4VXKTBR.js} +38 -41
- package/dist/{chunk-X66YJ2SS.js → chunk-F6FT6BVQ.js} +33 -34
- package/dist/{chunk-GIRBSBGL.js → chunk-FCQSZQAT.js} +3 -3
- package/dist/{chunk-X35S7HSB.js → chunk-FOEPIX76.js} +41 -30
- package/dist/{chunk-MC6VB2E5.js → chunk-GMC4ZGYR.js} +17 -5
- package/dist/{chunk-7TNILKGY.js → chunk-GTTMQ6XB.js} +1 -1
- package/dist/{chunk-HHR7WGCI.js → chunk-GUGKKGG7.js} +3 -3
- package/dist/{chunk-OZWXLJMX.js → chunk-GVWIU7M7.js} +2 -2
- package/dist/{chunk-WMDUT4KH.js → chunk-H65TYP6V.js} +94 -90
- package/dist/{chunk-5F3XF3SX.js → chunk-HILZE4BQ.js} +9 -8
- package/dist/{chunk-PKSUMEPT.js → chunk-HSYFLOZY.js} +3 -3
- package/dist/{chunk-4QG55RRC.js → chunk-I32RSMH6.js} +10 -12
- package/dist/chunk-I74RQGKA.js +88 -0
- package/dist/{chunk-G6JKM4O7.js → chunk-IDCTDKIA.js} +10 -10
- package/dist/chunk-IK4YS3KC.js +25 -0
- package/dist/{chunk-O2ARHQKF.js → chunk-IL6PIV33.js} +2 -2
- package/dist/{chunk-L3CLUGDY.js → chunk-J6BR5XN2.js} +3 -3
- package/dist/chunk-JKOZ2Z4U.js +20 -0
- package/dist/{chunk-SP4TFY5F.js → chunk-JZQGRARR.js} +11 -13
- package/dist/{chunk-CUDD35TW.js → chunk-K6WIBVMK.js} +6 -5
- package/dist/{chunk-DIWK3LBC.js → chunk-KDCIG23C.js} +8 -10
- package/dist/{chunk-4NBWFYWW.js → chunk-KFRDFAOE.js} +8 -33
- package/dist/{chunk-I22THIHI.js → chunk-KJ3AHOCK.js} +10 -12
- package/dist/{chunk-VOP4PJKA.js → chunk-KSTQ4VXT.js} +7 -9
- package/dist/{chunk-RGGH6M34.js → chunk-LT62P654.js} +1 -1
- package/dist/chunk-MAD4QJTP.js +198 -0
- package/dist/{chunk-CM73PPGD.js → chunk-MN635QYA.js} +3 -4
- package/dist/{chunk-HUAM7QG3.js → chunk-NBM7PNBP.js} +25 -23
- package/dist/{chunk-DYRZGUMA.js → chunk-NE4EFHJX.js} +2 -2
- package/dist/{chunk-SQC7K3SP.js → chunk-NL5LSKVD.js} +2 -2
- package/dist/{chunk-JZRP4DGP.js → chunk-NPNFGYLV.js} +4 -2
- package/dist/{chunk-NM2NWH55.js → chunk-NUSXS6YB.js} +6 -5
- package/dist/{chunk-ZKLTNLAW.js → chunk-OPFNQBS5.js} +6 -6
- package/dist/{chunk-PPKECBPP.js → chunk-OTSTS7L2.js} +19 -1
- package/dist/{chunk-SFLHSL5R.js → chunk-PTSA6QKL.js} +18 -7
- package/dist/{chunk-OY7WZI7Q.js → chunk-Q2VCKC3X.js} +6 -6
- package/dist/{chunk-HKIL6DCL.js → chunk-QGITU23N.js} +1 -1
- package/dist/{chunk-3O5EII3W.js → chunk-QHOTTC4A.js} +2 -2
- package/dist/{chunk-35WKJWO5.js → chunk-QL37SGTS.js} +112 -20
- package/dist/{chunk-OC7VWJBZ.js → chunk-QMV2APEH.js} +35 -37
- package/dist/{chunk-BUZIQDFS.js → chunk-QSCZAP24.js} +3 -3
- package/dist/{chunk-O4N5BQ3T.js → chunk-QUPYLQA4.js} +8 -10
- package/dist/{chunk-A5GRLYPZ.js → chunk-QUQY3IME.js} +7 -13
- package/dist/{chunk-R2QQC33W.js → chunk-QWTHFFU6.js} +12 -14
- package/dist/{chunk-TV6RXRYH.js → chunk-RQRKIRFY.js} +8 -10
- package/dist/{chunk-ZFORSIED.js → chunk-S3WFVG5P.js} +15 -42
- package/dist/{chunk-5RNB4HVK.js → chunk-SG2JQ2YP.js} +1 -1
- package/dist/{chunk-KZ4ALBCH.js → chunk-SJQUWQR6.js} +2 -2
- package/dist/{chunk-T2S3FNNJ.js → chunk-SKVNHCT5.js} +41 -42
- package/dist/{chunk-SDFKOLSF.js → chunk-TJQSYX3J.js} +8 -6
- package/dist/{chunk-IYVYZQRL.js → chunk-TLWFZ66Y.js} +5 -7
- package/dist/{chunk-5T5A6YAJ.js → chunk-TN5CWX5D.js} +33 -34
- package/dist/chunk-TQHOKMVZ.js +28 -0
- package/dist/{chunk-XOMGO63G.js → chunk-TYHOEX4V.js} +19 -21
- package/dist/{chunk-6LJOJ6EO.js → chunk-UNBRHPHJ.js} +14 -16
- package/dist/{chunk-4LL2VRNY.js → chunk-UOO4D2TK.js} +16 -18
- package/dist/{chunk-AGGUWKRK.js → chunk-UY745U35.js} +1 -1
- package/dist/{chunk-LSFXZLPW.js → chunk-V7F7JHS5.js} +218 -253
- package/dist/{chunk-VLQ7UKZH.js → chunk-VCRVNLE7.js} +135 -2
- package/dist/{chunk-JPRDTY5S.js → chunk-VGTBLTPN.js} +8 -10
- package/dist/{chunk-JBP7KESM.js → chunk-VPFRU5IG.js} +1 -1
- package/dist/chunk-VS2L7QDI.js +25 -0
- package/dist/{chunk-4W52ZKZX.js → chunk-W4CUK5G6.js} +2 -2
- package/dist/{chunk-VPLBLWFO.js → chunk-W7TY6HYX.js} +1 -1
- package/dist/{chunk-JYLOYTZD.js → chunk-WAA63ZJV.js} +5 -1
- package/dist/{chunk-WC6WRNQT.js → chunk-WS3UFJOU.js} +2 -2
- package/dist/chunk-XAFZJEXY.js +50 -0
- package/dist/{chunk-XYLC35E4.js → chunk-XPGH5O74.js} +555 -336
- package/dist/{chunk-VOXTCULR.js → chunk-XVB3Q2PG.js} +2 -4
- package/dist/{chunk-FRLAUP2B.js → chunk-Y3EHLUPL.js} +4 -4
- package/dist/{chunk-CZL44WFN.js → chunk-YF4G5NN5.js} +2 -2
- package/dist/{chunk-XWIME22V.js → chunk-YQA34KAF.js} +11 -13
- package/dist/{chunk-FHEV6T4L.js → chunk-YT2VR4SL.js} +8 -10
- package/dist/chunk-ZD4KVFXI.js +234 -0
- package/dist/{chunk-NSPVR3FN.js → chunk-ZOPXB2KK.js} +17 -19
- package/dist/chunk-ZPFLHB3R.js +28 -0
- package/dist/{chunk-R4QWJQ2H.js → chunk-ZZDVGCGG.js} +9 -11
- package/dist/index.js +5398 -4438
- package/dist/mcp/analyze-cli.js +12 -17
- package/dist/mcp/cli.js +41 -42
- package/dist/mcp/server.js +1466 -663
- package/dist/mcp/worker.js +59 -60
- package/dist/probes/installer.js +17 -19
- package/docs/agent-guide.md +2 -1
- package/docs/agent-tools.md +53 -10
- package/docs/analysisall.md +1 -1
- package/docs/ci-bot-pr-checks.md +7 -5
- package/docs/configuration.md +60 -13
- package/docs/defect-shapes.md +67 -4
- package/docs/environment-variables.md +18 -1
- package/docs/features.md +23 -6
- package/docs/globalconfig.md +24 -3
- package/docs/invariants/language-config.md +9 -1
- package/docs/invariants/lsp-trust-exec.md +9 -2
- package/docs/invariants/session-telemetry.md +2 -2
- package/docs/language-coverage.md +67 -0
- package/docs/lsp-capability-matrix.md +121 -53
- package/docs/lsp-idle-eviction.md +20 -13
- package/docs/merge-queue-rollout.md +10 -8
- package/docs/module-report-read-symbol.md +34 -23
- package/docs/pi-lens-fixer.md +19 -7
- package/docs/pi-lens-investigator.md +3 -0
- package/docs/pi-lens-merge-policy.md +20 -8
- package/docs/pi-lens-release.md +3 -2
- package/docs/pi-lens-reviewer.md +53 -12
- package/docs/pi-lens-subagent.md +13 -0
- package/docs/public-api-stability.md +39 -5
- package/docs/release-qa-baseline.md +7 -4
- package/docs/schema/pi-lens-config-v1.json +11 -2
- package/docs/servercapabilities.md +3 -1
- package/docs/settings.md +9 -6
- package/docs/usage.md +1 -0
- package/docs/word-index.md +3 -2
- package/package.json +9 -4
- package/rules/ast-grep-rules/rules/no-sql-in-code-execute-js.yml +1 -2
- package/rules/ast-grep-rules/rules/no-sql-in-code-execute.yml +1 -2
- package/scripts/download-grammars.js +13 -2
- package/scripts/grammars.lock.json +7 -0
- package/skills/pi-lens-lsp-navigation/SKILL.md +5 -1
- package/vendor/grammars/tree-sitter-groovy.wasm +0 -0
- package/dist/chunk-2TS4GLOJ.js +0 -31
- package/dist/chunk-3JAHQBSY.js +0 -27
- package/dist/chunk-447YZL4S.js +0 -25
- package/dist/chunk-565VRUP4.js +0 -136
- package/dist/chunk-57X2CDRX.js +0 -49
- package/dist/chunk-GGYOZWHW.js +0 -27
- package/dist/chunk-IE5D3RA5.js +0 -58
- package/dist/chunk-LPYTPNOJ.js +0 -22
- package/dist/chunk-OFNMHPBT.js +0 -89
- package/dist/chunk-U3AS2FR6.js +0 -106
- package/dist/chunk-W3BGKBBK.js +0 -27
- package/dist/chunk-WQV6BI4Q.js +0 -48
- package/dist/chunk-YHGYAEFH.js +0 -443
- package/dist/chunk-ZONZ6YY3.js +0 -74
- package/dist/chunk-ZSM35JF4.js +0 -30
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
# User changelog
|
|
2
|
+
|
|
3
|
+
## [4.4.10] - 2026-11-06
|
|
4
|
+
|
|
5
|
+
2 features, 7 fixes, 1 other change.
|
|
6
|
+
|
|
7
|
+
Full notes: https://github.com/apmantza/pi-lens/releases/tag/v4.4.10
|
|
8
|
+
|
|
9
|
+
## [4.4.9] - 2026-11-05
|
|
10
|
+
|
|
11
|
+
3 features, 29 fixes, 8 other changes.
|
|
12
|
+
|
|
13
|
+
Full notes: https://github.com/apmantza/pi-lens/releases/tag/v4.4.9
|
|
14
|
+
|
|
15
|
+
## [4.4.8] - 2026-11-01
|
|
16
|
+
|
|
17
|
+
1 feature, 28 fixes, 6 other changes.
|
|
18
|
+
|
|
19
|
+
Full notes: https://github.com/apmantza/pi-lens/releases/tag/v4.4.8
|
|
20
|
+
|
|
21
|
+
## [4.4.7] - 2026-10-29
|
|
22
|
+
|
|
23
|
+
2 features, 21 fixes.
|
|
24
|
+
|
|
25
|
+
Full notes: https://github.com/apmantza/pi-lens/releases/tag/v4.4.7
|
|
26
|
+
|
|
27
|
+
## [4.4.6] - 2026-10-27
|
|
28
|
+
|
|
29
|
+
6 fixes, 2 other changes.
|
|
30
|
+
|
|
31
|
+
Full notes: https://github.com/apmantza/pi-lens/releases/tag/v4.4.6
|
package/CHANGELOG.md
CHANGED
|
@@ -16,6 +16,264 @@ All notable changes to pi-lens will be documented in this file.
|
|
|
16
16
|
|
|
17
17
|
### Security
|
|
18
18
|
|
|
19
|
+
## [4.4.10] - 2026-11-06
|
|
20
|
+
|
|
21
|
+
### Added
|
|
22
|
+
|
|
23
|
+
#### Tools and reports
|
|
24
|
+
|
|
25
|
+
- **`module_report` and `read_symbol` now list Groovy classes and methods.** Symbol search, imports and read expansion work for them too, and traits, interfaces, enums and constructors are listed. `.groovy`, `.gvy`, `.gy` and `.gsh` files, plus `Jenkinsfile`, `build.gradle` and `settings.gradle`, parse with a vendored tree-sitter grammar. The grammar is partial: 70% of 1,353 real files parse with no error node. Types nested in a class, command calls with named arguments and the diamond `<>` do not parse, and `module_report` shows its syntax-error warning on a partial parse. Lint and format for Groovy are not part of this change. (refs #5235)
|
|
26
|
+
|
|
27
|
+
#### Configuration and flags
|
|
28
|
+
|
|
29
|
+
- **Read widening can now be turned off without losing the read-before-edit guard.** Pass `--no-read-expansion` or set the global `readGuard.expandReads=false` to keep the requested read ranges while the guard stays active. Read widening stays on by default. (refs #5303)
|
|
30
|
+
|
|
31
|
+
### Changed
|
|
32
|
+
|
|
33
|
+
#### Language servers
|
|
34
|
+
|
|
35
|
+
- **A large file can now be checked with `lens_diagnostics source=lsp` on one path.** The new user-level key `lsp.queryMaxFileLines` (5000 to 40000, suggested 20000) raises the line limit of that single-file query only; per-edit, dispatch and batch checks keep 5000 lines and 2 MiB. A project `.pi-lens.json` cannot set it, and an out-of-range value is ignored with a warning. An explicit `waitMs` now waits past the server's own wait, up to 30000 ms. A file over the limit or a wait that runs out reads as too large or timed out, never as clean, and a language server whose wait ran out now reads as timed out even while a slower scanner is still running. (refs #5306)
|
|
36
|
+
|
|
37
|
+
### Fixed
|
|
38
|
+
|
|
39
|
+
#### Language servers
|
|
40
|
+
|
|
41
|
+
- **On Windows, a missing project-local server `.cmd` no longer blocks the PATH server or install.** When a project had no `node_modules/.bin/pyright-langserver.cmd` (or the `.cmd` for the YAML, Bash, Docker, HTML, CSS, PHP, Prisma, Vue, Svelte or Fish server), pi-lens treated the absent file as an installed server and failed with a runtime error. The Python server never reached its PATH server, and the Node-based servers never reached their managed install. An absent local `.cmd` is now skipped like any other missing candidate. Thanks to ProphetOfDoom-PoD for the report and reproduction. (refs #5305)
|
|
42
|
+
|
|
43
|
+
- **An explicit `~/.pi/agent/tsconfig.json` now roots extensions that have no project of their own.** A TypeScript extension under `~/.pi/agent/extensions/` with neither a `package.json` nor a `tsconfig.json` used to get its own directory as the language-server root even when the agent directory carried a `tsconfig.json`; the server now roots at the agent directory so that config's `types` and `paths` apply. An extension-local project still wins, an agent `package.json` alone keeps the per-file root, and only the agent directory itself is read. (refs #5335)
|
|
44
|
+
|
|
45
|
+
#### Rules
|
|
46
|
+
|
|
47
|
+
- **`.mts` and `.cts` files now get the same checks as `.ts`.** Twelve fact rules (`error-swallowing`, `cors-wildcard`, `no-commented-credentials`, `placeholder-comments` and eight more), the comment and try/catch fact providers, the JS/TS autofix and linter policy, and the project scan each left out `.mts` and `.cts`, so those files read as unchecked with no notice. They now share one TypeScript-family check. (refs #4907)
|
|
48
|
+
|
|
49
|
+
- **A nested package's `rules.<id>.threshold` now applies to its own files.** `rules.high-complexity.threshold` and `rules.high-fan-out.threshold` follow the edited file's nearest `.pi-lens.json`, field by field, like `rules.<id>.disable`: with `40` at the workspace root and `5` in `pkg/.pi-lens.json`, a function in `pkg/` is judged by `5`. A threshold in `~/.pi-lens/config.json` now applies to every file no project `.pi-lens.json` sets one for, and a project or nested file still wins over it. (refs #5292)
|
|
50
|
+
|
|
51
|
+
#### Tools and reports
|
|
52
|
+
|
|
53
|
+
- **Read notes now name Kotlin and Swift symbols.** A widened read named the enclosing Kotlin or Swift symbol by its node type (`function_declaration`, `class_declaration`); it now shows the real name (`greet`, `Greeter`) in the note, the read-widening record and the retry hint. Java read notes are unchanged. (refs #5320)
|
|
54
|
+
|
|
55
|
+
#### Install and updates
|
|
56
|
+
|
|
57
|
+
- **The first edit of a session no longer waits on an `npm config get prefix` spawn.** The lookup of the package managers' global bin dirs now starts at session start, so the first dispatch joins it instead of paying about 0.3 s for `which npm` and `npm config get prefix`. `session_start` itself costs no more than before. A tool process that exits before its first resource sample no longer records a false `resource-sampler-query-failed` record. (refs #5261)
|
|
58
|
+
|
|
59
|
+
#### Hosts and integrations
|
|
60
|
+
|
|
61
|
+
- **A resumed session now publishes its restored diagnostics on `pilens:diagnostics`.** An extension that listens on the bus sees the same findings as the widget, instead of nothing until the next write. (refs #5301)
|
|
62
|
+
|
|
63
|
+
### Internal
|
|
64
|
+
|
|
65
|
+
<details>
|
|
66
|
+
<summary>14 internal changes: tests, CI, tooling, and refactors</summary>
|
|
67
|
+
|
|
68
|
+
- Tier-2 pi sessions start with the orphan-backstop cooldown armed, so a long test file's 30 s sweep cannot SIGKILL a stale host process and red the #2042 kill guard (refs #4909).
|
|
69
|
+
|
|
70
|
+
- Fixed nightly LSP drift notification setup, idle-eviction provisioning, and capability-matrix row coverage (refs #5323).
|
|
71
|
+
|
|
72
|
+
- The type-aware lint lane enables `typescript/switch-exhaustiveness-check`, so a union switch whose `default:` would absorb a new member is flagged; the 11 runtime sites are listed explicitly or carry a reasoned disable (#5331).
|
|
73
|
+
|
|
74
|
+
- The module-level ast-grep availability sweep in `clients/dispatch/runners/utils/runner-helpers.ts` (`isSgAvailableAsync`, `getSgCommand`, the `sg` export and their helpers) is deleted: it had no production caller, carried the B1 cross-session latch write, and production ast-grep runs through `SgRunner` (closes #5345).
|
|
75
|
+
|
|
76
|
+
- The nightly clean-signal probe no longer credits a fixture's row to a different launch: a `typescript7` row that ran the classic server now reads `unknown` instead of `mode=push-only`, the probe rewrites the tracked LSP capability matrix only with `--write-matrix`, and the comments and matrix prose no longer say native TS7 is silent on clean (it is a pull server) (refs #5348).
|
|
77
|
+
|
|
78
|
+
- The nightly `silentOnClean` drift check no longer files `silent-not-marked` for an auxiliary server (fallow, ast-grep, opengrep, zizmor, typos), and the comments and matrix prose no longer say native TS7 publishes on clean (refs #5348). The native TS7 marker stays `false`.
|
|
79
|
+
|
|
80
|
+
- Changelog fragments now carry an `area:` and one fixed headline-and-body shape that `rollup-changelog.mjs --check` enforces, and the release rollup groups each section's entries by area (refs #5351).
|
|
81
|
+
|
|
82
|
+
- **PR body Refs checks now match land-time requirements.** A referenced open issue must have a line-start `Remaining #N:` line, unless GitHub identifies it as a tracking or umbrella issue.
|
|
83
|
+
|
|
84
|
+
- **Fact-store bound test fills the session-fact cap directly** — the large-batch case no longer dispatches 4296 real files to fill the cap, so it stops running at its timeout on CI. The test also pins the dispatcher's own baseline write (refs #5307).
|
|
85
|
+
|
|
86
|
+
- The installer's npm global-bin and pip user-base rungs now verify their candidates through one `firstVerifiedBinary` loop instead of two byte-identical copies of the access, project-trust and verification steps; resolution results are unchanged (refs #4907).
|
|
87
|
+
|
|
88
|
+
- Five hand-written `key === root || key.startsWith(`${root}/`)` containment tests (LSP client-root overlap in two places, the blocker sweep's root test, `findModuleForPath`, the `lens_diagnostics` directory scope) now ask `isWithinForm`, the path owner (refs #4907).
|
|
89
|
+
|
|
90
|
+
- **The dispatcher's code-like diagnostic path check folds backslashes through `toPosix` (refs #4907)** — `looksLikeDiagnosticCodePath` hand-rolled `.replace(/\\/g, "/")`; it now calls the shared seam, and the `path-key-fold-sweep` pin for `clients/dispatch/dispatcher.ts` is gone. Behaviour is unchanged.
|
|
91
|
+
|
|
92
|
+
- Pin five behaviours that survived hand mutation: the single-tag token precedence in `check-action-pins`, the sentence splitter and list-marker strip in `check-prose`, the libc drift predicate in `package-lock-sync`, and the exact root entries in `lint-prose-files` (refs #4907).
|
|
93
|
+
|
|
94
|
+
- Governance now requires every module-level state-helper use to appear in the
|
|
95
|
+
TLA+ coverage map (refs #5330).
|
|
96
|
+
|
|
97
|
+
</details>
|
|
98
|
+
|
|
99
|
+
## [4.4.9] - 2026-11-05
|
|
100
|
+
|
|
101
|
+
### Added
|
|
102
|
+
|
|
103
|
+
- **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)
|
|
104
|
+
|
|
105
|
+
- **Shorter extension update notes** — pi's Extension Updates view now reads the latest five GitHub release summaries, each with a full-notes link.
|
|
106
|
+
|
|
107
|
+
- **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.
|
|
108
|
+
|
|
109
|
+
### Changed
|
|
110
|
+
|
|
111
|
+
- **`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.
|
|
112
|
+
|
|
113
|
+
- **`high-complexity` now checks JavaScript files.** `.js`, `.jsx`, `.mjs`,
|
|
114
|
+
and `.cjs` functions, and the `.mts` and `.cts` TypeScript modules, get the
|
|
115
|
+
same cyclomatic and nesting warning as `.ts` and `.tsx`. One per-function
|
|
116
|
+
metrics table per language now feeds the rule, the review graph, and the
|
|
117
|
+
complexity report. Cognitive and nesting scores in `/lens-tdi` and the
|
|
118
|
+
complexity report drop, because a `case` or `match` arm no longer scores on
|
|
119
|
+
its own and a function no longer counts as a nesting level. Stored history
|
|
120
|
+
keeps the old scale until each file is re-measured. A Python lambda now
|
|
121
|
+
counts once, and a Python `except` counts as a decision. A code file with no
|
|
122
|
+
metrics table (Java, Kotlin, C, and others) records one
|
|
123
|
+
`function-metrics-language-unsupported` degradation per language per
|
|
124
|
+
session.
|
|
125
|
+
(closes #5086)
|
|
126
|
+
|
|
127
|
+
- **`module_report` view is now a preset** — `view` names projection ×
|
|
128
|
+
format: `summary-text` (default, metrics off, text), `summary-json`,
|
|
129
|
+
`full-text`, `full-json` (every field, JSON). Applies to `module_report`
|
|
130
|
+
and `pilens_module_report`. The text cell mirrors its JSON payload field by
|
|
131
|
+
field (metrics as `cx:`/`fan:` suffixes, flags per bracket, `used-by:`
|
|
132
|
+
lines, `IMPORTS:` / `CALL GRAPH:` / `BLAST RADIUS:` blocks, `PROVENANCE:`
|
|
133
|
+
footer), with one declared exception: a member's own `exported` flag rides
|
|
134
|
+
on its container's section and has no member-level marker. The stale
|
|
135
|
+
`summary` / `default` / `compact` names fall through to the default, and a
|
|
136
|
+
`maxRefsPerSymbol` argument promotes the projection to `full`. MCP no
|
|
137
|
+
longer wraps the payload in a fenced JSON block.
|
|
138
|
+
(refs #5137)
|
|
139
|
+
|
|
140
|
+
- **`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.
|
|
141
|
+
|
|
142
|
+
- **Pi 1.5 is supported:** the tested pi range now runs from 0.86.1 up to, but not including, 1.6.0.
|
|
143
|
+
|
|
144
|
+
- **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`.
|
|
145
|
+
|
|
146
|
+
- **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)
|
|
147
|
+
|
|
148
|
+
### Fixed
|
|
149
|
+
|
|
150
|
+
- **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.
|
|
151
|
+
|
|
152
|
+
- **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.
|
|
153
|
+
|
|
154
|
+
- **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)
|
|
155
|
+
|
|
156
|
+
- **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)
|
|
157
|
+
|
|
158
|
+
- **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)
|
|
159
|
+
|
|
160
|
+
- **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.
|
|
161
|
+
|
|
162
|
+
- **`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.
|
|
163
|
+
|
|
164
|
+
- **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).
|
|
165
|
+
|
|
166
|
+
- **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.
|
|
167
|
+
|
|
168
|
+
- **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.
|
|
169
|
+
|
|
170
|
+
- **`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.
|
|
171
|
+
|
|
172
|
+
- **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`.
|
|
173
|
+
|
|
174
|
+
- **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.
|
|
175
|
+
|
|
176
|
+
- **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.
|
|
177
|
+
|
|
178
|
+
- **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)
|
|
179
|
+
|
|
180
|
+
- **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).
|
|
181
|
+
|
|
182
|
+
- **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).
|
|
183
|
+
|
|
184
|
+
- **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.
|
|
185
|
+
|
|
186
|
+
- **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.
|
|
187
|
+
|
|
188
|
+
- **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).
|
|
189
|
+
|
|
190
|
+
- **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.
|
|
191
|
+
|
|
192
|
+
- **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).
|
|
193
|
+
|
|
194
|
+
- **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.
|
|
195
|
+
|
|
196
|
+
- **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).
|
|
197
|
+
|
|
198
|
+
- **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.
|
|
199
|
+
|
|
200
|
+
- **`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)
|
|
201
|
+
|
|
202
|
+
- **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)
|
|
203
|
+
|
|
204
|
+
- **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.
|
|
205
|
+
|
|
206
|
+
- **Vulture failures show the exception.** Python dead-code scan summaries and degradation reasons retain the last stderr line instead of the traceback header.
|
|
207
|
+
|
|
208
|
+
### Security
|
|
209
|
+
|
|
210
|
+
- **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.
|
|
211
|
+
|
|
212
|
+
### Internal
|
|
213
|
+
|
|
214
|
+
<details>
|
|
215
|
+
<summary>29 internal changes: tests, CI, tooling, and refactors</summary>
|
|
216
|
+
|
|
217
|
+
- 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)
|
|
218
|
+
|
|
219
|
+
- 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)
|
|
220
|
+
|
|
221
|
+
- 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).
|
|
222
|
+
|
|
223
|
+
- 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)
|
|
224
|
+
|
|
225
|
+
- 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)
|
|
226
|
+
|
|
227
|
+
- 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)
|
|
228
|
+
|
|
229
|
+
- 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)
|
|
230
|
+
|
|
231
|
+
- 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).
|
|
232
|
+
|
|
233
|
+
- 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.
|
|
234
|
+
|
|
235
|
+
- 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).
|
|
236
|
+
|
|
237
|
+
- Route Stryker to the root minimatch 11.0.4 dependency, removing its vulnerable nested 10.x copy (#5204).
|
|
238
|
+
|
|
239
|
+
- `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)
|
|
240
|
+
|
|
241
|
+
- 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)
|
|
242
|
+
|
|
243
|
+
- 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)
|
|
244
|
+
|
|
245
|
+
- 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)
|
|
246
|
+
|
|
247
|
+
- **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`.
|
|
248
|
+
|
|
249
|
+
- 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).
|
|
250
|
+
|
|
251
|
+
- 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).
|
|
252
|
+
|
|
253
|
+
- 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).
|
|
254
|
+
|
|
255
|
+
- 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)
|
|
256
|
+
|
|
257
|
+
- 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).
|
|
258
|
+
|
|
259
|
+
- Keep Vitest's filesystem module cache separate for each worktree.
|
|
260
|
+
|
|
261
|
+
- 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)
|
|
262
|
+
|
|
263
|
+
- **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.
|
|
264
|
+
|
|
265
|
+
- 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.
|
|
266
|
+
|
|
267
|
+
- 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).
|
|
268
|
+
|
|
269
|
+
- 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).
|
|
270
|
+
|
|
271
|
+
- 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).
|
|
272
|
+
|
|
273
|
+
- 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).
|
|
274
|
+
|
|
275
|
+
</details>
|
|
276
|
+
|
|
19
277
|
## [4.4.8] - 2026-11-01
|
|
20
278
|
|
|
21
279
|
### Added
|
package/README.md
CHANGED
|
@@ -546,11 +546,14 @@ Thanks goes to these wonderful people:
|
|
|
546
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
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
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></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
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
551
|
</tr>
|
|
552
552
|
<tr>
|
|
553
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>
|
|
555
|
+
<td align="center" valign="top" width="14.28%"><a href="https://github.com/ProphetOfDoom-PoD"><img src="https://avatars.githubusercontent.com/u/260035065?v=4" width="100px;" alt=""/><br /><sub><b>Prophet Of Doom</b></sub></a><br /><a href="#ideas-ProphetOfDoom-PoD" title="Ideas & Planning">🤔</a></td>
|
|
556
|
+
<td align="center" valign="top" width="14.28%"><a href="http://www.apostolapostolov.com/"><img src="https://avatars.githubusercontent.com/u/4083812?v=4" width="100px;" alt=""/><br /><sub><b>Apostol Apostolov</b></sub></a><br /><a href="#bug-apoapostolov" title="Bug reports">🐛</a></td>
|
|
554
557
|
</tr>
|
|
555
558
|
</tbody>
|
|
556
559
|
</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-
|
|
9
|
+
"./clients/bus-event-rollup.js",
|
|
10
10
|
"./clients/bus-publish.js",
|
|
11
11
|
"./clients/cache-manager.js",
|
|
12
12
|
"./clients/cache-observability.js",
|
|
@@ -1,17 +1,20 @@
|
|
|
1
1
|
import { createRequire as __pilensCreateRequire } from "node:module"; const require = __pilensCreateRequire(import.meta.url);
|
|
2
|
+
import {
|
|
3
|
+
measureFunction
|
|
4
|
+
} from "./chunk-ZD4KVFXI.js";
|
|
2
5
|
import {
|
|
3
6
|
extractFactsFromTree
|
|
4
|
-
} from "./chunk-
|
|
7
|
+
} from "./chunk-GTTMQ6XB.js";
|
|
5
8
|
import {
|
|
6
9
|
findOwnerName
|
|
7
10
|
} from "./chunk-5W3R6LFT.js";
|
|
8
11
|
import {
|
|
9
12
|
firstChildOfType,
|
|
10
13
|
walk
|
|
11
|
-
} from "./chunk-
|
|
14
|
+
} from "./chunk-CTB5BAJI.js";
|
|
12
15
|
import {
|
|
13
16
|
isJstsFactFile
|
|
14
|
-
} from "./chunk-
|
|
17
|
+
} from "./chunk-CZCAZVTD.js";
|
|
15
18
|
|
|
16
19
|
// dist/clients/dispatch/facts/function-facts.js
|
|
17
20
|
var BOUNDARY_PREFIXES = [
|
|
@@ -30,28 +33,6 @@ var FUNCTION_TYPES = /* @__PURE__ */ new Set([
|
|
|
30
33
|
"function_expression",
|
|
31
34
|
"arrow_function"
|
|
32
35
|
]);
|
|
33
|
-
var COMPLEXITY_TYPES = /* @__PURE__ */ new Set([
|
|
34
|
-
"if_statement",
|
|
35
|
-
"for_statement",
|
|
36
|
-
"for_in_statement",
|
|
37
|
-
// for…of and for…in both parse to for_in_statement
|
|
38
|
-
"while_statement",
|
|
39
|
-
"do_statement",
|
|
40
|
-
"switch_case",
|
|
41
|
-
// `case` only — `default` (switch_default) is not counted
|
|
42
|
-
"catch_clause",
|
|
43
|
-
"ternary_expression"
|
|
44
|
-
]);
|
|
45
|
-
var NESTING_TYPES = /* @__PURE__ */ new Set([
|
|
46
|
-
"if_statement",
|
|
47
|
-
"for_statement",
|
|
48
|
-
"for_in_statement",
|
|
49
|
-
"while_statement",
|
|
50
|
-
"do_statement",
|
|
51
|
-
"switch_statement",
|
|
52
|
-
"try_statement"
|
|
53
|
-
]);
|
|
54
|
-
var LOGICAL_OPERATORS = /* @__PURE__ */ new Set(["&&", "||", "??"]);
|
|
55
36
|
function namedChildren(node) {
|
|
56
37
|
return (node.children ?? []).filter((c) => c && c.isNamed && c.type !== "comment");
|
|
57
38
|
}
|
|
@@ -123,19 +104,6 @@ function isCallPassThrough(stmt, paramNames) {
|
|
|
123
104
|
}
|
|
124
105
|
return { pass: true, target: (expr.children ?? [])[0]?.text };
|
|
125
106
|
}
|
|
126
|
-
function isDecisionPoint(type, children) {
|
|
127
|
-
if (COMPLEXITY_TYPES.has(type))
|
|
128
|
-
return true;
|
|
129
|
-
return type === "binary_expression" && children.some((c) => LOGICAL_OPERATORS.has(c?.type));
|
|
130
|
-
}
|
|
131
|
-
function calcCyclomaticComplexity(body) {
|
|
132
|
-
let cc = 1;
|
|
133
|
-
walk(body, (node) => {
|
|
134
|
-
if (isDecisionPoint(node.type, node.children ?? []))
|
|
135
|
-
cc++;
|
|
136
|
-
});
|
|
137
|
-
return cc;
|
|
138
|
-
}
|
|
139
107
|
function memberCallSite(callee) {
|
|
140
108
|
if (callee?.type !== "member_expression")
|
|
141
109
|
return void 0;
|
|
@@ -177,21 +145,13 @@ function addNewReceiverType(children, receiverTypes) {
|
|
|
177
145
|
if (id && ctor?.type === "identifier")
|
|
178
146
|
receiverTypes[id.text] = ctor.text;
|
|
179
147
|
}
|
|
180
|
-
function summarizeBody(
|
|
148
|
+
function summarizeBody(fn, params) {
|
|
181
149
|
let hasAwait = false;
|
|
182
150
|
let hasReturnAwaitCall = false;
|
|
183
|
-
let cyclomaticComplexity = 1;
|
|
184
|
-
let maxNestingDepth = 0;
|
|
185
151
|
const calls = /* @__PURE__ */ new Set();
|
|
186
152
|
const memberCallSites = [];
|
|
187
153
|
const receiverTypes = parameterReceiverTypes(params);
|
|
188
|
-
const
|
|
189
|
-
const type = node.type;
|
|
190
|
-
const children = node.children ?? [];
|
|
191
|
-
if (depth > maxNestingDepth)
|
|
192
|
-
maxNestingDepth = depth;
|
|
193
|
-
if (isDecisionPoint(type, children))
|
|
194
|
-
cyclomaticComplexity++;
|
|
154
|
+
const metrics = measureFunction(fn, "typescript", (node, type, children) => {
|
|
195
155
|
if (type === "await_expression") {
|
|
196
156
|
hasAwait = true;
|
|
197
157
|
} else if (type === "return_statement") {
|
|
@@ -202,18 +162,13 @@ function summarizeBody(body, params) {
|
|
|
202
162
|
} else if (type === "variable_declarator") {
|
|
203
163
|
addNewReceiverType(children, receiverTypes);
|
|
204
164
|
}
|
|
205
|
-
|
|
206
|
-
for (const child of children) {
|
|
207
|
-
if (child)
|
|
208
|
-
visit(child, next);
|
|
209
|
-
}
|
|
210
|
-
};
|
|
211
|
-
visit(body, 0);
|
|
165
|
+
});
|
|
212
166
|
return {
|
|
213
167
|
hasAwait,
|
|
214
168
|
hasReturnAwaitCall,
|
|
215
|
-
cyclomaticComplexity,
|
|
216
|
-
maxNestingDepth,
|
|
169
|
+
cyclomaticComplexity: metrics.cyclomatic,
|
|
170
|
+
maxNestingDepth: metrics.nesting,
|
|
171
|
+
parameterCount: metrics.parameters,
|
|
217
172
|
outgoingCalls: [...calls],
|
|
218
173
|
memberCallSites,
|
|
219
174
|
receiverTypes
|
|
@@ -248,7 +203,7 @@ var functionFactProvider = {
|
|
|
248
203
|
const target = passThrough.target ?? "";
|
|
249
204
|
const lowerTarget = target.toLowerCase();
|
|
250
205
|
const isBoundaryWrapper = BOUNDARY_PREFIXES.some((prefix) => lowerTarget.startsWith(prefix));
|
|
251
|
-
const bodySummary = summarizeBody(
|
|
206
|
+
const bodySummary = summarizeBody(node, params);
|
|
252
207
|
summaries.push({
|
|
253
208
|
name: getFunctionName(node),
|
|
254
209
|
line: node.startPosition.row + 1,
|
|
@@ -258,7 +213,7 @@ var functionFactProvider = {
|
|
|
258
213
|
hasAwait: bodySummary.hasAwait,
|
|
259
214
|
hasReturnAwaitCall: bodySummary.hasReturnAwaitCall,
|
|
260
215
|
statementCount,
|
|
261
|
-
parameterCount:
|
|
216
|
+
parameterCount: bodySummary.parameterCount,
|
|
262
217
|
isPassThroughWrapper: passThrough.pass,
|
|
263
218
|
passThroughTarget: passThrough.target,
|
|
264
219
|
isBoundaryWrapper,
|
|
@@ -296,6 +251,5 @@ var functionFactProvider = {
|
|
|
296
251
|
};
|
|
297
252
|
|
|
298
253
|
export {
|
|
299
|
-
calcCyclomaticComplexity,
|
|
300
254
|
functionFactProvider
|
|
301
255
|
};
|