pi-lens 4.5.0 → 4.5.2
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 +12 -12
- package/CHANGELOG.md +253 -0
- package/README.md +11 -2
- package/config/dependency-cruiser-eager-allowlist.json +1 -0
- package/dist/{chunk-ZULZS2I6.js → chunk-2ERVW2UF.js} +1115 -423
- package/dist/{chunk-BBSDJTOV.js → chunk-2K7BUOKS.js} +13 -13
- package/dist/{chunk-I2FYOZNW.js → chunk-3JJ4OAJI.js} +10 -10
- package/dist/{chunk-5JB4WENL.js → chunk-3UHGSUVL.js} +1 -1
- package/dist/{chunk-W26QZ3OM.js → chunk-463WN3VP.js} +10 -10
- package/dist/{chunk-4IZZEN63.js → chunk-4X3ML2UQ.js} +31 -34
- package/dist/{chunk-I3NZVAMN.js → chunk-5BI5YP57.js} +10 -10
- package/dist/{chunk-7U36VQL6.js → chunk-5Z4XLUFF.js} +3 -3
- package/dist/{chunk-DCA2MXVQ.js → chunk-62AJH3IN.js} +51 -29
- package/dist/{chunk-37IDWT6O.js → chunk-6F34GMP7.js} +16 -14
- package/dist/{chunk-VSQT6IHZ.js → chunk-6LIUVGOR.js} +28 -4
- package/dist/{chunk-27JQHK7Y.js → chunk-6REF4GCO.js} +1 -1
- package/dist/{chunk-INBK3HIT.js → chunk-7KRR24GO.js} +3 -3
- package/dist/{chunk-OZQQ3AIR.js → chunk-7OMOMBEQ.js} +9 -9
- package/dist/{chunk-ARTYCUGF.js → chunk-7ZFXICNN.js} +123 -20
- package/dist/{chunk-K4Z7MK6T.js → chunk-ABKRQVOY.js} +28 -52
- package/dist/{chunk-C5PLBTNR.js → chunk-ANSLRJBG.js} +1 -1
- package/dist/{chunk-HRLF35WL.js → chunk-AWMFBPGJ.js} +9 -9
- package/dist/{chunk-CXQYK4YT.js → chunk-BG7KHGNX.js} +2 -2
- package/dist/{chunk-ZI7YHV6I.js → chunk-BK2R2223.js} +10 -8
- package/dist/chunk-BXXC6KRR.js +107 -0
- package/dist/{chunk-QMWKSYWB.js → chunk-CKJS2AUI.js} +4 -4
- package/dist/{chunk-PPQHMSPH.js → chunk-COGU5KQJ.js} +15 -15
- package/dist/{chunk-NHA5K226.js → chunk-CQNXALZJ.js} +27 -6
- package/dist/{chunk-KZ732ZVW.js → chunk-CSZESDPP.js} +1 -1
- package/dist/chunk-CZ5TCJPB.js +98 -0
- package/dist/{chunk-LOEJFTF2.js → chunk-D2LFEA5U.js} +9 -2
- package/dist/chunk-D3KLF5CD.js +50 -0
- package/dist/{chunk-4DAHGU3V.js → chunk-ENJ2M76Y.js} +31 -29
- package/dist/{chunk-ZQSSO7LO.js → chunk-EQKF6BAK.js} +3 -3
- package/dist/{chunk-PFJLYRO3.js → chunk-F2SAP2FM.js} +40 -47
- package/dist/{chunk-ADYQRETD.js → chunk-F6QAJXQV.js} +2 -2
- package/dist/chunk-GR2QDWH5.js +25 -0
- package/dist/{chunk-LVLPA32Q.js → chunk-GVE5VZYQ.js} +48 -11
- package/dist/{chunk-AZG5UJYY.js → chunk-GWZZOJD2.js} +1 -1
- package/dist/chunk-GZS6VPIE.js +27 -0
- package/dist/chunk-H4B4SC7I.js +71 -0
- package/dist/{chunk-YCR6ZYTE.js → chunk-HA6TUJOE.js} +1 -1
- package/dist/{chunk-DI4AZZNY.js → chunk-HKPJTI47.js} +2 -2
- package/dist/{chunk-O6LCSHHI.js → chunk-HPKC55MA.js} +1 -1
- package/dist/{chunk-LQQNFCQJ.js → chunk-I65CQLCG.js} +1 -1
- package/dist/{chunk-P5MSLVUW.js → chunk-IDKLWVKY.js} +11 -11
- package/dist/chunk-IUM2Q7NF.js +25 -0
- package/dist/{chunk-L6BDRYUK.js → chunk-J24IS3KZ.js} +5 -5
- package/dist/{chunk-KNSOA43J.js → chunk-J2DAHH4T.js} +2 -2
- package/dist/{chunk-7ZVTFLCC.js → chunk-JBDZVOFL.js} +11 -11
- package/dist/{chunk-HIJ4CHFF.js → chunk-JC6NFC57.js} +3 -3
- package/dist/{chunk-K7O6AHSJ.js → chunk-JTHEUTW7.js} +11 -11
- package/dist/{chunk-KXGTLAUW.js → chunk-JWW3ODBN.js} +2 -2
- package/dist/{chunk-HIRBC72R.js → chunk-K3ZIYLHT.js} +4 -4
- package/dist/{chunk-6GLMMGCX.js → chunk-KDPZA2UE.js} +2 -3
- package/dist/{chunk-AXAR5ZW2.js → chunk-KMY2OU4T.js} +553 -434
- package/dist/{chunk-DFKOA74L.js → chunk-KQF7VT26.js} +10 -10
- package/dist/{chunk-S6MCMD27.js → chunk-KVGA7X76.js} +3 -3
- package/dist/{chunk-74AMPWNC.js → chunk-KW7O72AK.js} +2 -2
- package/dist/{chunk-UN72ZAJ5.js → chunk-LEQTVRSV.js} +9 -9
- package/dist/{chunk-B42AIWPJ.js → chunk-LKPSBM6S.js} +3 -3
- package/dist/{chunk-R4L7KZ7R.js → chunk-LKW2HFSZ.js} +9 -9
- package/dist/{chunk-3PO4YYOX.js → chunk-LURFD4HD.js} +4240 -3734
- package/dist/{chunk-PQXUZYTQ.js → chunk-M6ELTECW.js} +4 -4
- package/dist/{chunk-3QXFUP6T.js → chunk-MGVVYYKW.js} +12 -12
- package/dist/{chunk-CZJGAOKL.js → chunk-MQBKGRSB.js} +7 -7
- package/dist/{chunk-NNEQOC3U.js → chunk-MVG2ZEAO.js} +9 -7
- package/dist/{chunk-VWEBZ2JV.js → chunk-MY4XNNTX.js} +39 -41
- package/dist/{chunk-RIH3UBK4.js → chunk-N4AJVFRF.js} +11 -11
- package/dist/{chunk-TKOFTLGB.js → chunk-OFKKMXWM.js} +31 -36
- package/dist/{chunk-3PAS2ERX.js → chunk-OFZE4ANN.js} +8 -8
- package/dist/chunk-OLXBUTJR.js +61 -0
- package/dist/{chunk-6CFSDLHE.js → chunk-OZGEHOSG.js} +38 -17
- package/dist/{chunk-3TSMQZG6.js → chunk-PKGOROPQ.js} +40 -2
- package/dist/{chunk-OLWGYBYT.js → chunk-Q6D5QKRG.js} +17 -17
- package/dist/{chunk-QE7BJQ6K.js → chunk-QECLJFHI.js} +12 -17
- package/dist/{chunk-RJ3APNIP.js → chunk-QJA33VD5.js} +4 -4
- package/dist/{chunk-MOAVEPC4.js → chunk-R5XVJ6AN.js} +11 -11
- package/dist/{chunk-ZRQMENT4.js → chunk-REZL4OM4.js} +1 -1
- package/dist/{chunk-PKWEBMCA.js → chunk-RK5RBREN.js} +251 -201
- package/dist/chunk-RP5ZQTHO.js +86 -0
- package/dist/{chunk-J2ZB5MDS.js → chunk-RURPX2YV.js} +23 -23
- package/dist/chunk-TB5MGZLS.js +53 -0
- package/dist/chunk-TC63XRYP.js +27 -0
- package/dist/chunk-TJOYHAXJ.js +69 -0
- package/dist/{chunk-Q7J3JYJ2.js → chunk-TRXKDCBP.js} +13 -13
- package/dist/{chunk-6E5QLMWI.js → chunk-TTK37D7R.js} +22 -23
- package/dist/{chunk-XDNWR7SG.js → chunk-UH3QHLR5.js} +2 -2
- package/dist/{chunk-SCU62JLX.js → chunk-UNTJJ7GN.js} +7 -7
- package/dist/{chunk-O2MHF7QM.js → chunk-UPAFSETJ.js} +58 -63
- package/dist/{chunk-PQF6YGYB.js → chunk-UX75PTQW.js} +50 -31
- package/dist/{chunk-TWEOJE3D.js → chunk-V353PYMK.js} +1233 -576
- package/dist/{chunk-CQY2HEH7.js → chunk-V4TFQY5G.js} +2 -2
- package/dist/{chunk-B2OXE4AH.js → chunk-VC3W54G3.js} +446 -293
- package/dist/{chunk-JGUDT5KD.js → chunk-VSBCJVPC.js} +5 -5
- package/dist/{chunk-5HBQL7DH.js → chunk-WAQQGXVV.js} +3 -3
- package/dist/{chunk-7DPXUPRF.js → chunk-WLEVWR7Y.js} +2 -2
- package/dist/{chunk-QE5DJ7MX.js → chunk-WPMPVP5I.js} +4 -4
- package/dist/{chunk-KNJH6WJQ.js → chunk-WXNLFOC2.js} +7 -7
- package/dist/{chunk-XSC3BCN3.js → chunk-Y3ZNOZZS.js} +6 -6
- package/dist/{chunk-VGRGW4UL.js → chunk-YL6JQTWC.js} +29 -32
- package/dist/{chunk-7CLWC2UH.js → chunk-YVE5Q2UU.js} +86 -217
- package/dist/{chunk-LGH2HHZG.js → chunk-YZNARDMM.js} +42 -28
- package/dist/{chunk-NGNBJIUO.js → chunk-ZDWNFZJ2.js} +8 -8
- package/dist/{chunk-X33QECRJ.js → chunk-ZEUF7BIN.js} +2 -2
- package/dist/{chunk-2H5GHZKC.js → chunk-ZIF4WLWR.js} +45 -25
- package/dist/{chunk-WLD6BGON.js → chunk-ZSPVF7KI.js} +231 -24
- package/dist/{chunk-SDYLT45T.js → chunk-ZX6OKBVO.js} +2 -2
- package/dist/index.js +10566 -6819
- package/dist/mcp/analyze-cli.js +8 -8
- package/dist/mcp/cli.js +39 -41
- package/dist/mcp/server.js +1083 -685
- package/dist/mcp/worker.js +68 -59
- package/dist/probes/installer.js +21 -22
- package/docs/ci-bot-pr-checks.md +18 -9
- package/docs/ci.md +7 -0
- package/docs/configuration.md +24 -10
- package/docs/defect-shapes.md +61 -30
- package/docs/environment-variables.md +18 -9
- package/docs/globalconfig.md +17 -0
- package/docs/invariants/dispatch-runners.md +22 -0
- package/docs/invariants/lsp-trust-exec.md +33 -3
- package/docs/lsp-capability-matrix.md +23 -10
- package/docs/lsp-idle-eviction.md +7 -1
- package/docs/module-report-read-symbol.md +6 -2
- package/docs/pi-lens-merge-policy.md +3 -2
- package/docs/pi-lens-orchestration.md +2 -1
- package/docs/pi-lens-subagent.md +2 -1
- package/docs/release-qa-baseline.md +22 -17
- package/docs/servercapabilities.md +1 -1
- package/docs/settings.md +10 -2
- package/docs/tools.md +1 -1
- package/docs/usage.md +1 -0
- package/package.json +3 -3
- package/dist/chunk-2H7NFZ4Q.js +0 -25
- package/dist/chunk-5YJXF2IS.js +0 -56
- package/dist/chunk-7WKVCZI4.js +0 -69
- package/dist/chunk-BKWFDWYM.js +0 -46
- package/dist/chunk-G53LBDNU.js +0 -255
- package/dist/chunk-GCSDF5IE.js +0 -27
- package/dist/chunk-H5API74E.js +0 -67
- package/dist/chunk-HBX55MWO.js +0 -27
- package/dist/chunk-JOIKBUQN.js +0 -88
- package/dist/chunk-M2YMBT5G.js +0 -73
- package/dist/chunk-MJRGPEQ5.js +0 -25
- package/dist/chunk-QV3JPCMK.js +0 -17
- package/dist/chunk-TFKN5EIR.js +0 -27
- package/dist/chunk-UNP6Y4JV.js +0 -38
package/CHANGELOG-USER.md
CHANGED
|
@@ -1,5 +1,17 @@
|
|
|
1
1
|
# User changelog
|
|
2
2
|
|
|
3
|
+
## [4.5.2] - 2026-11-22
|
|
4
|
+
|
|
5
|
+
1 feature, 23 fixes, 2 other changes.
|
|
6
|
+
|
|
7
|
+
Full notes: https://github.com/apmantza/pi-lens/releases/tag/v4.5.2
|
|
8
|
+
|
|
9
|
+
## [4.5.1] - 2026-11-16
|
|
10
|
+
|
|
11
|
+
1 feature, 26 fixes, 1 other change.
|
|
12
|
+
|
|
13
|
+
Full notes: https://github.com/apmantza/pi-lens/releases/tag/v4.5.1
|
|
14
|
+
|
|
3
15
|
## [4.5.0] - 2026-11-14
|
|
4
16
|
|
|
5
17
|
31 fixes, 2 other changes.
|
|
@@ -17,15 +29,3 @@ Full notes: https://github.com/apmantza/pi-lens/releases/tag/v4.4.12
|
|
|
17
29
|
32 fixes, 2 other changes.
|
|
18
30
|
|
|
19
31
|
Full notes: https://github.com/apmantza/pi-lens/releases/tag/v4.4.11
|
|
20
|
-
|
|
21
|
-
## [4.4.10] - 2026-11-06
|
|
22
|
-
|
|
23
|
-
2 features, 7 fixes, 1 other change.
|
|
24
|
-
|
|
25
|
-
Full notes: https://github.com/apmantza/pi-lens/releases/tag/v4.4.10
|
|
26
|
-
|
|
27
|
-
## [4.4.9] - 2026-11-05
|
|
28
|
-
|
|
29
|
-
3 features, 29 fixes, 8 other changes.
|
|
30
|
-
|
|
31
|
-
Full notes: https://github.com/apmantza/pi-lens/releases/tag/v4.4.9
|
package/CHANGELOG.md
CHANGED
|
@@ -16,6 +16,259 @@ All notable changes to pi-lens will be documented in this file.
|
|
|
16
16
|
|
|
17
17
|
### Security
|
|
18
18
|
|
|
19
|
+
## [4.5.2] - 2026-11-22
|
|
20
|
+
|
|
21
|
+
### Added
|
|
22
|
+
|
|
23
|
+
#### Configuration and flags
|
|
24
|
+
|
|
25
|
+
- **The diagnostics widget can now move above the editor or hide when clean.** Set `widget.position` to `"aboveEditor"` or `"belowEditor"` (the default), and set `widget.hideWhenClean` to `true` to hide the widget 5 seconds after it first shows `✓ clean`. With the hide on, the widget also draws nothing until a first check gives it something to show. It returns on any finding, unchecked file, suppressed finding, failed formatter or starting server. Both keys are global-only and have no CLI flag. (refs #5724)
|
|
26
|
+
|
|
27
|
+
### Changed
|
|
28
|
+
|
|
29
|
+
#### Install and updates
|
|
30
|
+
|
|
31
|
+
- **The jscpd installer pins 5.4.3, and pi 1.5.2 is the tested host.** New installs get jscpd 5.4.3 in place of 5.4.2. (refs #5670)
|
|
32
|
+
|
|
33
|
+
- **pi-lens no longer installs rubocop, rustfmt or rust-clippy without asking.** Their installs (`gem install`, `rustup component add`) change your whole gem root or toolchain. The three still run when present. When they are absent, the rubocop runner reports `not-installed`, the rust-clippy runner reports `probe-rejected`, and the rustfmt and rubocop formatters skip silently. (refs #5410)
|
|
34
|
+
|
|
35
|
+
### Fixed
|
|
36
|
+
|
|
37
|
+
#### Language servers
|
|
38
|
+
|
|
39
|
+
- **Esc now cancels a project-wide diagnostics pull and a TypeScript project probe.** A `lens_diagnostics` full scan and the `projectInfo` request sent when a TypeScript file opens used to keep waiting on the language server after you aborted. Both now send a cancel and return at once. (refs #5097)
|
|
40
|
+
|
|
41
|
+
- **A language-server edit keeps the line ending of the edited line.** In a file with mixed line endings, new lines inserted by a rename or code action took the file's first line ending, so a CRLF line in an LF-first file got a bare LF (and the reverse). Files with one line-ending style are unchanged. (refs #5670)
|
|
42
|
+
|
|
43
|
+
- **Python servers reach global fallbacks, and PATH never runs unadmitted project files.** Python servers now reach global fallbacks for adopted projects: absent project candidates are reported as missing before trust is considered, while existing refused candidates no longer end a launch stage when installation is disabled. For an adopted project, or one pi has not trusted, a PATH entry inside the project (relative entries such as `bin` or `.` included) is skipped when a language server is looked up, and a PATH link into the project is refused. When PATH reaches such a project, managed lookups read only the pi-lens tool store, so the TypeScript and Jedi fallbacks and the Go, Ruby and .NET runtime installs no longer probe or run its `tsc`, `python` or `go`. (refs #5674)
|
|
44
|
+
|
|
45
|
+
- **The cascade now re-asks a push-only server about dependents it answered before your edit.** A server such as jdtls republishes a dependent when its own model changes, not when asked, so importers of an edited Java file stayed unconfirmed every time. For a server declared to re-check unchanged bytes (jdtls, TypeScript, Python) the cascade re-sends the dependent once per run and reads the answer; other servers are left as they were. A server that stays silent still leaves the dependent unconfirmed, never clean. (refs #5675)
|
|
46
|
+
|
|
47
|
+
- **LSP timeout notices now name the server and cause.** An unconfirmed document no longer reports only the generic unavailable message; the dispatch record carries the same reason for later inspection. (refs #5692)
|
|
48
|
+
|
|
49
|
+
- **On Windows, more language servers now end when pi ends.** A server whose path held a space, such as PowerShell 7 under `C:\Program Files`, or one installed as an npm 9 or later `.cmd` shim, ran behind `cmd.exe`, so pi's exit ended only the wrapper and the server kept running. pi-lens now starts these servers as its own direct child, so Windows ends them with pi even when pi is killed. A server started through another wrapper, such as a pnpm shim or a shim that passes Node flags, still runs behind `cmd.exe` and can outlive pi; pi-lens records each one as `lsp-server-uncontained`. (refs #5694)
|
|
50
|
+
|
|
51
|
+
- **Language servers now end with the pi or MCP process that started them.** On Linux and macOS, a server that ignored stdin EOF and SIGTERM outlived a pi quit, an MCP client disconnect, a SIGTERM to the MCP host and every `fresh` analysis worker. pi-lens now sends each held server's process group SIGKILL when its host exits. A host killed before that keeps its `instances.json` row, and the next pi or MCP start reaps the server. A server's child that ignores SIGTERM after the server exits is killed too, and `fresh` analysis now reads `lsp.json`. (refs #5699)
|
|
52
|
+
|
|
53
|
+
- **Language servers close old files and stop when a session goes idle.** Each client keeps at most 256 documents open (`PI_LENS_LSP_OPEN_DOCUMENT_CAP`) and closes the least recently sent one with `didClose`. A closed file's last findings stay readable, marked `closed: true` in the `lsp_navigation` workspace snapshot, and the next touch opens it again. Every server not declared `resident` is now released after the idle window on the pi host and the MCP host. Before, 32 servers, including every server a project declares, were never released. Only five project indexers (expert, kotlin, powershell, rust, svelte) stay resident. The pi host's session idle reset now restarts after a turn that edited files; before, such a turn cancelled it and nothing armed it again. (refs #5700)
|
|
54
|
+
|
|
55
|
+
- **Deno projects now use the Deno language server for TypeScript files.** TypeScript no longer claims files governed by `deno.json` or `deno.jsonc`, allowing the configured Deno fallback to start. (refs #5720)
|
|
56
|
+
|
|
57
|
+
- **An uncaught host error now runs exit cleanup for held language servers.** The LSP crash guard prints the stack and exits non-zero through Node's normal exit path, so pi RPC/print mode and the MCP host no longer leave a server behind. The stack report writes at most 16 KiB and waits at most 1 s for a full stderr pipe, so it cannot hold a crashing host. (refs #5744)
|
|
58
|
+
|
|
59
|
+
- **A checkout or rebase in a sibling worktree now refreshes the language server.**
|
|
60
|
+
A bash command that moved HEAD in another linked worktree it named, or
|
|
61
|
+
discarded edits there, left the server holding the old files with no record,
|
|
62
|
+
so it reported errors against code that no longer existed. (refs #5718)
|
|
63
|
+
|
|
64
|
+
#### Blockers and sessions
|
|
65
|
+
|
|
66
|
+
- **A file reached through a symlink no longer blocks its own export.** The duplicate-export STOP, the cached-export refresh and the deferred runner blocker each compared two spellings of one file as two files, so an edit through the real path left a removed export cached, the next write that declared it was refused, and a deferred blocker lost its line text. All three now compare by path identity. (refs #2556)
|
|
67
|
+
|
|
68
|
+
- **A fixed ast-grep blocker no longer stays "Still unfixed" while the language server is silent.** When a file's language server did not answer or could not start, pi-lens kept every blocker it had recorded for the file, including ast-grep ones that the ast-grep server had just checked clean. The fix then read as unfixed, stayed in `lens_diagnostics`, was listed again at turn end, and kept the commit gate shut. A recorded blocker is now judged by its own server's answer; blockers of a server that did not answer still stay. (refs #5727)
|
|
69
|
+
|
|
70
|
+
- **A STOP block now names the file a cross-file blocker belongs to.** The mypy
|
|
71
|
+
runner reports errors in the modules an edit imports, and those rows used to read as
|
|
72
|
+
lines of the edited file, with that file's line shown as their snippet. An
|
|
73
|
+
agent then marked them against the wrong file, where the mark never applied. (refs #5710)
|
|
74
|
+
|
|
75
|
+
- **A false-positive mark made from a STOP block now hides that finding.** Marking
|
|
76
|
+
what the block shows (the `[rule]` bracket as the rule, the rest as the message,
|
|
77
|
+
no tool) used to anchor on an identity the finding never had, so the same
|
|
78
|
+
finding came back on every edit. (refs #5709)
|
|
79
|
+
|
|
80
|
+
#### Runners and scanners
|
|
81
|
+
|
|
82
|
+
- **Prisma and Vite+ project edits no longer start an extra process per save.** The prisma and oxlint runners probed `prisma --version` and `vp --version` on PATH and kept no answer, so a tool that was slow to start or failed its probe cost every edit again. Both now read the shared per-project verdict like every other runner. (refs #5410)
|
|
83
|
+
|
|
84
|
+
- **A project that ships its own jscpd is no longer reported as missing.** The duplicate-code, circular-dependency, unused-code and secret scans now check their binary the way the linters do, so a managed gitleaks or opengrep that fails its version check falls back to the one on PATH instead of triggering an install. (refs #5410)
|
|
85
|
+
|
|
86
|
+
#### Tools and reports
|
|
87
|
+
|
|
88
|
+
- **Suppressing a diagnostic no longer rewrites a CRLF file's line endings.** The inline `pi-lens-ignore` comment takes the ending of the line it is inserted above, every existing line ending is kept, and a whitespace-only CRLF line no longer lends its bare `\r` to the inserted comment's indentation. (refs #5686)
|
|
89
|
+
|
|
90
|
+
#### Configuration and flags
|
|
91
|
+
|
|
92
|
+
- **Config readers now agree on `ignorePaths`, `effective_config` tools and legacy files.** A rule's `ignorePaths` match from the folder of the config file that declares them, so `/gen/**` in `repo/.pi-lens.json` skips `repo/gen` wherever you start pi. `effective_config` reports the tool switches your session uses, from the repository's own `.pi-lens.json` and your global config. Once a `.pi-lens.json` sits in the chain from your working directory up to the git root, a legacy `pi-lens.json` is ignored everywhere except the language-server settings. (refs #5738, #5739, #5740)
|
|
93
|
+
|
|
94
|
+
#### Install and updates
|
|
95
|
+
|
|
96
|
+
- **Installer downloads are streamed into bounded temporary files.** Release assets no longer collect the full download and decompressed binary in memory before installation. Downloads are capped, timed out, cleaned on failure, and only then moved into the managed install. (refs #5701)
|
|
97
|
+
|
|
98
|
+
#### Hosts and integrations
|
|
99
|
+
|
|
100
|
+
- **pi-lens now reaps its leftover logs, state and sockets at session start.** Oversized tool-result spill logs, saved session state, endpoint sockets whose owner process is gone, and project data directories whose project no longer exists used to accumulate forever; a disk audit measured 431 MB of project directories, 16 spill files from September, and 36 stale sockets on one machine. The session-start sweep now reaps each of these past its retention window. A project data directory goes only after 30 days, only when no path on disk can still be the project it was named for, and never on Windows; anything the sweep cannot judge stays. (refs #5702)
|
|
101
|
+
|
|
102
|
+
#### Security
|
|
103
|
+
|
|
104
|
+
- **A directory named with a backslash no longer counts as inside the project.** On Linux and macOS, a sibling directory such as `proj\evil` next to the session root `proj` was treated as part of it, so edits there got session treatment. (refs #2556)
|
|
105
|
+
|
|
106
|
+
- **On Windows, an untrusted project's gopls or rust-analyzer no longer runs through a sibling file.** When `$GOPATH\bin` or `$CARGO_HOME\bin` sat inside the repository and pi did not trust it, pi-lens refused the project's `<tool>.exe` but still offered the extensionless name, which Windows completes to any `.cmd`, `.bat` or `.com` beside it. The extensionless name is now withheld from an untrusted project directory, and refusing a sibling file that exists there is recorded as `trust-refusal`. (refs #5715)
|
|
107
|
+
|
|
108
|
+
### Internal
|
|
109
|
+
|
|
110
|
+
<details>
|
|
111
|
+
<summary>10 internal changes: tests, CI, tooling, and refactors</summary>
|
|
112
|
+
|
|
113
|
+
- A settled `publishes after save only` cell in the LSP capability matrix now changes only after two nights agree, as `clean-behavior` does. One night's silent no-save arm had flipped powershell from `no` to `yes (saved write)` on 2026-11-15. (refs #3405)
|
|
114
|
+
|
|
115
|
+
- The idle-eviction doc's `result`, `reason`, `respawn` and `coverage` cells now change only after two nights agree, a night that could not spawn a server leaves its row alone, and the nightly seed step restores the doc with the matrix, so one night's reading no longer flips a row (opengrep on 2026-11-14) and a move between `unavailable` and `eligible` (csharp, dart, fsharp, go and ruby on 2026-11-06) waits for its second agreeing night. A census names the hold or the reason for every generated measured column. (refs #5667)
|
|
116
|
+
|
|
117
|
+
- The `--no-lens` control case in `tests/index-4913-cli-flag-timing.test.ts` and the mark-only turn case in `tests/index-4698-mark-only-turn-gate.test.ts` no longer carry the process's one-time cold start inside their 5 s cap, so both keep their headroom on a slow CI runner, and their stale timeout-headroom baseline rows are gone. (refs #5731)
|
|
118
|
+
|
|
119
|
+
- The whole-module `vi.mock` export ratchet now reds on a baseline count above the live count, as the flake-shape and LSP-double ratchets do. (refs #4907)
|
|
120
|
+
|
|
121
|
+
- The PR-gating `host range · newest-in-range` lane now installs the newest stable pi (the npm dist-tag `latest`) with no hand-kept ceiling, so a new pi release is exercised by a gating lane at once; a registry failure resolving `latest` fails the lane closed. The `PI_HOST_SUPPORTED_RANGE` ceiling is gone and the floor stays 0.86.1. (refs #5749)
|
|
122
|
+
|
|
123
|
+
- The nightly LSP census tracker files its drift issue only when a census output is not success. A job failure outside the census no longer files an issue with an empty census section (refs #5676).
|
|
124
|
+
|
|
125
|
+
- The `forgetTurnSession` FileTime test now passes on macOS. It looked up FileTime
|
|
126
|
+
under the temp directory's linked spelling, while the read guard stamps a
|
|
127
|
+
file's resolved path, so it failed whenever `TMPDIR` was a link. (refs #5716)
|
|
128
|
+
|
|
129
|
+
- Test workers no longer inherit the shell's active Python environment. An
|
|
130
|
+
exported `VIRTUAL_ENV`, `CONDA_PREFIX` or `UV_PROJECT_ENVIRONMENT`, and the bin
|
|
131
|
+
directory activation put on PATH, gave every test that environment's tools.
|
|
132
|
+
A developer with a global venv active saw tests read its pyright and pytest. (refs #5712)
|
|
133
|
+
|
|
134
|
+
- The Qodo review bot is retired: its trial ended and its billing notice read as unanswered findings at the land gate. `.pr_agent.toml` is deleted; CodeRabbit and Greptile keep their configs. (refs #4685)
|
|
135
|
+
|
|
136
|
+
- Four process-wide slots (the spawn-timeout cooldown, the opaque baseline store, the probe-home memo and safe-spawn's lifetime registry) now live behind `getProcessSingleton`, and a new sweep (`tests/config/process-slot-sweep.test.ts`) reds a hand-rolled `globalThis`, `Symbol.for` or `process` slot outside it. (refs #4907)
|
|
137
|
+
|
|
138
|
+
</details>
|
|
139
|
+
|
|
140
|
+
## [4.5.1] - 2026-11-16
|
|
141
|
+
|
|
142
|
+
### Added
|
|
143
|
+
|
|
144
|
+
#### Hosts and integrations
|
|
145
|
+
|
|
146
|
+
- **An opt-in `pi-lens-issues` footer status shows diagnostics counts.** `--lens-issues-status` (or
|
|
147
|
+
`ui.issuesStatus: true`) publishes `●<N>E`, `!<N>W`, both side by side,
|
|
148
|
+
`⚠ <N> unchecked`, or `✓ clean`, drawn from the widget header's own tallies so
|
|
149
|
+
the footer and the widget cannot disagree. Off by default; the footer is
|
|
150
|
+
unchanged when the flag is unset. The text is plain, with no terminal color
|
|
151
|
+
escapes, so a status-rendering host or bridge reads it as written. (refs #5588)
|
|
152
|
+
|
|
153
|
+
### Changed
|
|
154
|
+
|
|
155
|
+
#### Blockers and sessions
|
|
156
|
+
|
|
157
|
+
- **A `lens_diagnostic_mark` suppress now dispatches the file it wrote.** The files a call wrote through the mutation bridge, such as an `ast_grep_replace` or an `lsp_navigation` rename, reach the dispatcher and the commit gate whatever the tool is named, and under any host call id, including OpenAI Responses ids that contain a pipe or pass 64 characters. (refs #5551)
|
|
158
|
+
|
|
159
|
+
### Fixed
|
|
160
|
+
|
|
161
|
+
#### Language servers
|
|
162
|
+
|
|
163
|
+
- **Esc now returns an `lsp_navigation` call on a silent language server at once.** A request that times out or is aborted is cancelled on the wire and no longer keeps the server marked busy, so a wedged server is evicted when idle instead of piling up liveness pings. (refs #5097)
|
|
164
|
+
|
|
165
|
+
- **Esc now cancels the diagnostic pull and the clean-confirm ping a cut-off check had started.** A turn-end re-verify or an enrichment pass that hit its bound used to leave `textDocument/diagnostic` running on the language server; it now sends `$/cancelRequest`. A warm-up that Esc cut is no longer remembered as a cold server. (refs #5097)
|
|
166
|
+
|
|
167
|
+
- **A dead or cancelled language server no longer retires a carried code-action warning as clean.** A code-action request that died, was cancelled or came back malformed keeps the warning. A failed capability lookup, a defensive path no real lookup reaches today, now reports the file as unconfirmed. (refs #5258)
|
|
168
|
+
|
|
169
|
+
- **A manifest fixed before pi's first look at a project now reaches its running server.** An MCP hover that started rust-analyzer, then a fixed `Cargo.toml`, used to leave `pilens_diagnostics` reading `workspace failed to load`. The session root and the MCP working directory now forward a manifest fixed after the server started, and still restart no server for an install on that first look. (refs #5501)
|
|
170
|
+
|
|
171
|
+
- **A member crate's `Cargo.toml` or a nested `go.mod` fixed outside pi now reaches the running server.** Both servers read it without a restart. A manifest fixed after a server started, and before pi's first look at a client root other than the session root, now reaches that server. (refs #5501)
|
|
172
|
+
|
|
173
|
+
#### Blockers and sessions
|
|
174
|
+
|
|
175
|
+
- **A Go module CVE is no longer labelled historical on a turn that wrote no file.** The advisory for a vulnerability pinned by a module, with no call site to name, now cites `go.mod` and `go.sum`, so it reads current unless a module file changed after the turn end. (refs #4617)
|
|
176
|
+
|
|
177
|
+
- **The commit gate now refuses a blocker the staged lines add, whoever wrote them.** Under `--lens-guard`, a `debugger;` that a script, a tool that names no path or an external editor adds no longer commits unchecked. The gate dry-runs the command's commit with `git`, after the usual steps before it (`git add`, `git rm`, `git mv`, `cd`, `export`, `make`, `npm test`). It runs the linters, ast-grep and tree-sitter over the committed bytes, not LSP or type checks. It refuses only on a line the commit adds. A linter with no answer, a read past its time, or a step it cannot replay refuses (a script or `git reset` before the commit): run that first, then commit. (refs #5553)
|
|
178
|
+
|
|
179
|
+
- **A commit is no longer refused over a blocker that was already in the file.** `ast_grep_replace`, `sed -i`, an unclassified tool and an LSP rename now take the same pre-edit baseline as a host `edit`, so an unrelated change through them to a file that holds a committed `debugger;` commits. A blocker the writer adds is still refused. (refs #5553)
|
|
180
|
+
|
|
181
|
+
- **A file your script wrote now gets its blockers like an edit does.** When a bash command such as `python3 fix.py` changes a file that was clean before it, and nothing else pi-lens saw wrote that file meanwhile, the blockers show as a STOP and the commit gate holds them. Blockers the file already held at the last commit stay quiet, as they do for an edit, and pi-lens does not reformat or autofix that file. When pi-lens cannot tell (the file was already modified, another write touched it, or the command failed), the line it shows now names each blocker's line and rule, says the file changed during the command, and asks you to fix them if your command wrote it. (refs #5616)
|
|
182
|
+
|
|
183
|
+
- **A seed copy no longer reaches `git add -A`.** For a Python file the earlier bytes reach ruff through its standard input, so no copy exists. Where a linter reads the disk, such as biome on TypeScript, the one-run copy is still written, and its name is first added to the repository's local `.git/info/exclude` (never a tracked `.gitignore`). (refs #5621)
|
|
184
|
+
|
|
185
|
+
- **The commit gate now sees commits that bash runs after escapes or Unicode spaces.** The gate read a no-break space or an escaped quote differently from bash, so a `git commit` written after one went unseen. It now splits words on a space, a tab and a newline only, as bash does. (refs #5649)
|
|
186
|
+
|
|
187
|
+
- **The commit gate now judges the staged bytes of a file rewritten as it was staged.** The gate reads a copy of the index, and the copy's new timestamp hid that git had not yet told such a file apart from its staged blob, so the gate linted the working bytes and could pass a commit that carried other bytes. The copy now keeps the index's timestamp. (refs #5650)
|
|
188
|
+
|
|
189
|
+
- **The commit gate now sees a commit run through a substitution inside `bash -c` or `eval`.** The gate read a `bash -c` or `eval` string as words and never scanned it for `$(...)` or backticks, and it read `#` after a substitution's closing `)` as a comment. A `git commit` written either way went unseen, and so did one nested more than three command strings deep or run through `bash -ce`. (refs #5652)
|
|
190
|
+
|
|
191
|
+
#### Runners and scanners
|
|
192
|
+
|
|
193
|
+
- **A pyright that fails its version check is now skipped, not run.** The runner used to fall back to the first `pyright` on PATH without checking it, so a broken install reported a failed run with a parse error. It now reads the one version check like every other runner and skips with the cause stated. It also finds a `pyright` in the project's own `node_modules/.bin`. On Windows, each project bin dir now supplies its own launcher extension (`.exe` in a venv, `.cmd` in `node_modules/.bin`) to every registry tool. (refs #5410)
|
|
194
|
+
|
|
195
|
+
- **Projects without a Python environment now run tests with the pytest on PATH.** Before, pi-lens ran a bare `python -m pytest`, which failed where `python` is missing or lacks pytest. A project with its own environment still runs that interpreter's `-m pytest`. (refs #5410)
|
|
196
|
+
|
|
197
|
+
- **A project's own `shellcheck` in `node_modules/.bin` is now found.** The shellcheck, shfmt, tflint, terragrunt, cue-vet and spellcheck runners each kept a private tool check. Each looked in the project's venv and nowhere else. They now use the one lookup every other runner uses. In a trusted project, a `node_modules/.bin` copy now wins over PATH. On Windows, `.cmd` and `.exe` resolve per directory. Which tools pi-lens installs on its own does not change. (refs #5410)
|
|
198
|
+
|
|
199
|
+
- **Rubocop runs without bundler, and jdtls starts past a macOS `java` stub.** A Gemfile that names rubocop no longer skips the runner while a working rubocop is on PATH, and a `java` on PATH that cannot run (the macOS stub with no JDK behind it) no longer hides the JDK pi-lens found, so jdtls starts. KtFmt autofix and SpotBugs also find a binary in a project's `node_modules/.bin` now. (refs #5410)
|
|
200
|
+
|
|
201
|
+
- **Vale now reads the `.vale.ini` sections that name your project's files.** The runner handed Vale the absolute path, so a section such as `[docs/*.md]` never matched, and a section naming an ancestor directory (`[**/.claude/**]` in a Claude Code worktree) matched the project's own files and silenced them. Vale now gets the project-relative path, with a `./` prefix for a name that starts like an option. (refs #5556)
|
|
202
|
+
|
|
203
|
+
- **detekt, phpstan and credo no longer read a project under a `.claude/worktrees` checkout as clean.** A project config that ignores `**/.claude/**` matched the checkout's own ancestors, so the tool saw no file and the runner reported none. The runner now gives the tool the project's own config plus a generated overlay in which each ignore entry is anchored at the project root, with the same meaning it had in any other checkout. An entry whose meaning it cannot keep runs as written, and a clean result from that run is reported as inconclusive. (refs #5594)
|
|
204
|
+
|
|
205
|
+
- **Credo findings from every category are now reported.** Credo's 1–127 category bitmask statuses are treated as completed analyses, while 128+ invocation errors remain rejected. (refs #5608)
|
|
206
|
+
|
|
207
|
+
- **oxlint and ESLint now find a root config for files inside a nested package.** The earlier fix did not take effect for an edit in a package, because the config search stopped at the package. It now stops at the project root, so a root config with a cwd-relative path, such as the `better-tailwindcss` `entryPoint`, no longer reports false findings. (refs #5631)
|
|
208
|
+
|
|
209
|
+
#### Tools and reports
|
|
210
|
+
|
|
211
|
+
- **The review graph now marks public Rust, Go, Java, Kotlin and C# symbols as exported.** Editing a `pub fn` now raises the exported symbol changed risk flag, and Rust structs, enums, traits, constants, type aliases and modules now reach the graph. A language whose visibility cannot be read from the declaration, such as Python, reports unknown instead of not exported, and `module_report` lists its symbols under `SYMBOLS (visibility unknown)` with no export count instead of "0 exported". `module_report` now splits Rust files into API and INTERNAL, `mod tests` nests as a class, `read_enclosing` answers struct, enum and mod lines, and on a line shared by an interface and a function the interface now wins. The review graph rebuilds once after upgrade. (refs #5599)
|
|
212
|
+
|
|
213
|
+
#### Install and updates
|
|
214
|
+
|
|
215
|
+
- **Helm now installs on a machine that does not have it.** The helm release on GitHub holds only signature files, so the installer found no archive on any platform and never installed it. It now downloads the archive from get.helm.sh on Linux, macOS and Windows, for x64 and arm64. (refs #5643)
|
|
216
|
+
|
|
217
|
+
- **Opengrep, Hadolint, Vale, shfmt and tflint install again from their current releases.** Opengrep 2.0.0 renamed its release files and ships Windows as a zip with its DLLs, so the managed install found nothing to download. Hadolint's Linux file names and Vale's pinned 3.14.2 had also drifted from the latest releases, and shfmt and tflint looked for Windows arm64 builds that do not exist, so Windows arm64 now gets the x64 build. (refs #5624)
|
|
218
|
+
|
|
219
|
+
- **Global bin lookups no longer write into your project.** For a trusted project, pi-lens asked pnpm, npm and yarn for their global bin folder from the project itself. A relative `PNPM_HOME` then created a `${HOME}` folder in the repository, and a project `.npmrc` could change the answer. The lookup now runs from your home folder whatever the trust. (refs #5632)
|
|
220
|
+
|
|
221
|
+
#### Hosts and integrations
|
|
222
|
+
|
|
223
|
+
- **Bash `rsync -a`, `tar x` and `mv` into a directory are now seen.** When the file keeps an old modification time, a move or copy into a directory names `src/a.ts`, and an `rsync` into a tree or a `tar x` is credited by content in the directory it fills, so the changed file reaches dispatch, the change log and the commit gate like a `cp` does. In a checkout with 512 or more files already modified, none of this applies, because a file the command wrote cannot be told from one you had edited, and the older time rule stays. (refs #5552)
|
|
224
|
+
|
|
225
|
+
### Internal
|
|
226
|
+
|
|
227
|
+
<details>
|
|
228
|
+
<summary>20 internal changes: tests, CI, tooling, and refactors</summary>
|
|
229
|
+
|
|
230
|
+
- **The Unit tests shard weights come from fifteen master runs.** The old snapshot held one regressed file at 302 s after its fix. The slowest shard ran 62 s p50 over the mean (measured). The refresh models 16 s over the mean with no run noise, and about 32 s p50 with run noise (modelled). The shard count stays at five. The model alone gives the 3, 4 and 6 comparisons; no run measured them. (refs #3801)
|
|
231
|
+
|
|
232
|
+
- Record the rust-analyzer measurement at the neighbour cascade's references loop. Overlapping the calls saves 5 ms warm, 16 ms after a body edit and an unstable 21-77 ms after a structural edit on clap, short of a stable 50 ms, so the loop stays serial. (closes #5174)
|
|
233
|
+
|
|
234
|
+
- **CI flags the tests that already spent most of their timeout.** `scripts/check-test-timeout-headroom.mjs` reads each shard's `vitest-results.json`, folds the effective per-test budget out of the source (the `it`/`test` value, an options object's `timeout`, the enclosing `describe` or `test.each` tail options, a module-scope `vi.setConfig`, `scaledTestTimeout`, or Vitest's default), and annotates every assertion that ran past 60% of it. A cap the fold cannot settle — a `vi.setConfig` inside a hook or test body, an options name re-bound with `=`, an options object with a spread after `timeout`, or options written after the handler, a signature half vitest refuses to collect — is counted in the summary as unresolved and measured against the smallest budget the file declares, so it is visible rather than measured against a default it does not run under. The step is advisory (`continue-on-error`) and a run that could not measure at all emits a `::warning` rather than reddening the shard, `scripts/test-timeout-headroom-baseline.json` carries the current offenders, so the annotation surface is the new ones. (`--fail-on-new` makes the same check block.) A baseline row whose test has been renamed or deleted is printed as `stale` so the ledger cannot quietly stop measuring. The LSP explicit-query test file `tests/tools/lsp-diagnostics-explicit-query-limit-5306.test.ts` now calls `vi.setConfig` at module scope, where vitest reads it, so its real budget widens from 5000 ms to 30000 ms (90000 ms at CI scale 3); the old `beforeAll` call never applied, and its longest test runs 339 ms. (refs #5311)
|
|
235
|
+
|
|
236
|
+
- Let `bounded()` take its work as a thunk, `bounded((signal) => work, opts)`, run inside `spawnAbortScope` so a bound that fires aborts the scope its work runs in: the spawns and the requests that read `getAmbientAbortSignal()` (document symbols, code actions, and since #5097 the diagnostic pull and clean-confirm ping under `touchFile` and `getDiagnostics`) are cancelled instead of abandoned. Eight hook awaits that left work running now use it or carry a named reason in the `work` column of `BOUNDED_CALL_SITES`, and a new `bounded(` without that column reds. (refs #5550)
|
|
237
|
+
|
|
238
|
+
- Remove `withTimeout` and `withinRemaining` from `clients/deadline-utils.ts`. Both only preset `withDeadline`'s options, and none of their 11 callers is a hook await, so each now names the options on `withDeadline`; behaviour is unchanged. Two cases prove that a `bounded()` deadline, not only the turn's abort, cancels the real diagnostic pull under the persistent re-verify touch and the enrichment's `getDiagnostics`. (refs #5550)
|
|
239
|
+
|
|
240
|
+
- Make `scripts/ci-verdict.mjs` print green for a PR only when the PR's own `statusCheckRollup` (the view GitHub's merge gate reads) also carries a concluded success for every required name (each judged by its newest rollup entry, so a superseded cancelled run does not red): a PR whose required rows came from `workflow_dispatch` runs alone, as #5623's did, reads pending with the close/reopen advice instead of exit 0 over a BLOCKED merge, and an unreadable rollup is pending, never green. (refs #5629)
|
|
241
|
+
|
|
242
|
+
- Stopped two required-lane test flakes: the tool-cwd language-root cell now runs under the lane-scaled timeout, and the `lsp_diagnostics` abort cell asserts the abort (not the per-file deadline) released the in-flight file from the outcome's reason instead of a 500 ms elapsed margin. (refs #5645)
|
|
243
|
+
|
|
244
|
+
- Settle the installer's probe-cache writer before the fallow archive test removes its home: the teardown now joins `updateProbeCache` calls that have not marked their change yet, then drains the probe-cache flush, so `probe-cache.json` and its lock no longer re-create the removed root and red the tmp-fixture hygiene owner. (closes #5657)
|
|
245
|
+
|
|
246
|
+
- The shard 5 dead-owner census lists a managed process whose owner tag it could not read and that nothing owns any more, and a real-process witness shows it finds a managed child under a reaped owner (refs #5528).
|
|
247
|
+
|
|
248
|
+
- **A broader shape-86 governance rule ships disabled.** `awaited-loop-wait` admits an awaited test loop only when a real-clock deadline bounds it or it awaits nothing but `waitFor`, and it reports the 29 of the #5618 review's 35 planted equivalents that the active `turn-count-wait` rule misses. On the tree it reports 669 loops, of which at least 17, among the members read, are real-I/O waits, so it sits in `scripts/governance-rules/rules-disabled/`. Its rule tests run through `sgconfig-disabled.yml`. The active rule and its baseline are unchanged. (refs #4865)
|
|
249
|
+
|
|
250
|
+
- **The real-I/O members of the shape-86 census end their waits on the clock.** Thirteen test files and the two test-hook poll loops in `clients/` bounded a wait by an iteration count, so one descheduled sleep shortened the wall clock the wait was giving its producer: the two persist waits in `waitForProjectSnapshotPersistsForTests` and `waitForReviewGraphPersistsForTests`, the rename-echo grace windows, the file-landed and file-removed helpers, the degradation-ledger and session-sidecar pumps, and the two installer negative windows. Each now carries a `Date.now()` ceiling — `waitFor` where the read is synchronous, the same pump under a deadline where it is not — and `warm-attach-socket-error`'s negative case takes the event its 50 turns stood in for: the accepted socket's own `close`. The governance baseline drops the 14 `turn-count-wait` rows these fixes removed, and the flake-shape baseline drops two vanished `raw-timer-wait` rows and tightens two counts. (refs #4865)
|
|
251
|
+
|
|
252
|
+
- Delete the sync `findCommand` from `clients/safe-spawn.ts` and the `isOnPath` wrapper from `clients/lsp/server.ts`. The LSP runtime gate calls `isCommandAvailableAsync` directly, so it asks the same PATH question as before. No observable change. (refs #5410)
|
|
253
|
+
|
|
254
|
+
- The DEFERRED auxiliary-resync drift case no longer shrinks the notify budget: the 50ms value armed a 250ms wedge timer, and a loaded runner that outlived it demoted the auxiliary mid-case and left the sweep with nothing to heal. The case now parks and releases the blocking write itself, and the `never-settling-wait` baseline row for the file is gone. (refs #5555)
|
|
255
|
+
|
|
256
|
+
- **The local PR-body lint self-check keeps its time budget on a loaded runner.** The case that runs the preflight command in five argv forms launched its five `node` children one after another, so a loaded runner pushed it past the 5000 ms test timeout (941 ms idle, 8970 ms on a loaded CI shard). The five forms now run together, so the case costs its slowest single child, and each refusal is pinned by the rule text the child prints, not only by a non-zero exit. (refs #5597)
|
|
257
|
+
|
|
258
|
+
- Pin the slow-filesystem kill switch (`PI_LENS_ALLOW_SLOW_FS_SCAN=1`) for every pi-session test case, so its notification assertions no longer depend on the runner's disk latency. A forced-slow case guards the pin, and the restore runs in `afterAll`. (refs #5602)
|
|
259
|
+
|
|
260
|
+
- Make the Java trust-flip probe case in `session-repository-trust-4530.test.ts` warm its own lazy probe helpers, so it no longer passes only after a sibling case loaded them; it was red under the nightly shuffle seeds 202 and 424. (refs #5607)
|
|
261
|
+
|
|
262
|
+
- The pre-push hook puts this checkout's `node_modules/.bin` first as an absolute path, so a test spawn from another directory finds `ast-grep` instead of failing `ENOENT` (refs #5630).
|
|
263
|
+
|
|
264
|
+
- **The Unit tests shard weights come from the newest ten green master runs.** The old 15-run snapshot priced 10 live test files at the median; the refresh from the shard reports of ten green `ci.yml` push runs prices all 1,882 live files. (refs #3753)
|
|
265
|
+
|
|
266
|
+
- The agent_end drain's format and autofix writes record through the mutation bridge's one body, `recordMutationOutcome`, as a `drain` writer, so its two hand-copied recorders are gone; the direct LSP branch names its change-log row through the same `source` option. (refs #5551)
|
|
267
|
+
|
|
268
|
+
- Add the writer table (`clients/writers.ts`): every route that changes a file, against the consumers each one reaches, with the probe behind each cell. A census test fails on a new file-writing site with no registry row. The LSP edit bookkeeping now records through `recordMutationOutcome`, the one recorder the mutation bridge uses, instead of a hand copy. (refs #5551)
|
|
269
|
+
|
|
270
|
+
</details>
|
|
271
|
+
|
|
19
272
|
## [4.5.0] - 2026-11-14
|
|
20
273
|
|
|
21
274
|
### Changed
|
package/README.md
CHANGED
|
@@ -77,7 +77,7 @@ Project-local binaries, such as `node_modules/.bin/eslint` or `.venv/bin/ruff`,
|
|
|
77
77
|
| Command | What it does |
|
|
78
78
|
|---|---|
|
|
79
79
|
| `/lens-health` | Show runtime health, latency, and degradation counts |
|
|
80
|
-
| `/lens-widget-toggle` | Show or hide the diagnostics widget
|
|
80
|
+
| `/lens-widget-toggle` | Show or hide the diagnostics widget |
|
|
81
81
|
| `/lens-toggle` | Turn pi-lens on or off for the session |
|
|
82
82
|
| `/lens-map` | Build an interactive HTML dependency map of the project |
|
|
83
83
|
| `/lens-allow-edit <path>` | Override the read-before-edit guard for one edit |
|
|
@@ -296,7 +296,7 @@ Thanks goes to these wonderful people:
|
|
|
296
296
|
</tr>
|
|
297
297
|
<tr>
|
|
298
298
|
<td align="center" valign="top" width="14.28%"><a href="https://github.com/kevinkirkup"><img src="https://avatars.githubusercontent.com/u/38406?v=4" width="100px;" alt=""/><br /><sub><b>Kevin S Kirkup</b></sub></a><br /><a href="#bug-kevinkirkup" title="Bug reports">🐛</a></td>
|
|
299
|
-
<td align="center" valign="top" width="14.28%"><a href="https://github.com/georgeharker"><img src="https://avatars.githubusercontent.com/u/2169888?v=4" width="100px;" alt=""/><br /><sub><b>George Harker</b></sub></a><br /><a href="#code-georgeharker" title="Code">💻</a> <a href="#bug-georgeharker" title="Bug reports">🐛</a> <a href="#ideas-georgeharker" title="Ideas & Planning">🤔</a></td>
|
|
299
|
+
<td align="center" valign="top" width="14.28%"><a href="https://github.com/georgeharker"><img src="https://avatars.githubusercontent.com/u/2169888?v=4" width="100px;" alt=""/><br /><sub><b>George Harker</b></sub></a><br /><a href="#code-georgeharker" title="Code">💻</a> <a href="#bug-georgeharker" title="Bug reports">🐛</a> <a href="#ideas-georgeharker" title="Ideas & Planning">🤔</a> <a href="#doc-georgeharker" title="Documentation">📖</a> <a href="https://github.com/apmantza/pi-lens/commits?author=georgeharker" title="Tests">⚠️</a></td>
|
|
300
300
|
<td align="center" valign="top" width="14.28%"><a href="https://zuey.me"><img src="https://avatars.githubusercontent.com/u/6857382?v=4" width="100px;" alt=""/><br /><sub><b>Duy /zuey/</b></sub></a><br /><a href="#ideas-mrgoonie" title="Ideas & Planning">🤔</a> <a href="#code-mrgoonie" title="Code">💻</a></td>
|
|
301
301
|
<td align="center" valign="top" width="14.28%"><a href="https://github.com/luw2007"><img src="https://avatars.githubusercontent.com/u/1415541?v=4" width="100px;" alt=""/><br /><sub><b>luw2007</b></sub></a><br /><a href="#bug-luw2007" title="Bug reports">🐛</a></td>
|
|
302
302
|
<td align="center" valign="top" width="14.28%"><a href="https://github.com/WrongWorry"><img src="https://avatars.githubusercontent.com/u/188037855?v=4" width="100px;" alt=""/><br /><sub><b>WrongWorry</b></sub></a><br /><a href="#bug-WrongWorry" title="Bug reports">🐛</a></td>
|
|
@@ -441,6 +441,15 @@ Thanks goes to these wonderful people:
|
|
|
441
441
|
<tr>
|
|
442
442
|
<td align="center" valign="top" width="14.28%"><a href="https://github.com/HyeokjaeLee"><img src="https://avatars.githubusercontent.com/u/71566740?v=4" width="100px;" alt=""/><br /><sub><b>HyeokjaeLee</b></sub></a><br /><a href="#code-HyeokjaeLee" title="Code">💻</a> <a href="#bug-HyeokjaeLee" title="Bug reports">🐛</a></td>
|
|
443
443
|
<td align="center" valign="top" width="14.28%"><a href="https://github.com/dmarchevsky"><img src="https://avatars.githubusercontent.com/u/32597866?v=4" width="100px;" alt=""/><br /><sub><b>Dima Marchevskyi</b></sub></a><br /><a href="#bug-dmarchevsky" title="Bug reports">🐛</a></td>
|
|
444
|
+
<td align="center" valign="top" width="14.28%"><a href="https://jennyleidig.straw.page/"><img src="https://avatars.githubusercontent.com/u/131712584?v=4" width="100px;" alt=""/><br /><sub><b>Jenny Leidig</b></sub></a><br /><a href="#code-jennymaeleidig" title="Code">💻</a> <a href="#ideas-jennymaeleidig" title="Ideas & Planning">🤔</a></td>
|
|
445
|
+
<td align="center" valign="top" width="14.28%"><a href="https://github.com/yorch"><img src="https://avatars.githubusercontent.com/u/60499?v=4" width="100px;" alt=""/><br /><sub><b>Jorge Barnaby</b></sub></a><br /><a href="#bug-yorch" title="Bug reports">🐛</a></td>
|
|
446
|
+
<td align="center" valign="top" width="14.28%"><a href="https://github.com/aloneangel45"><img src="https://avatars.githubusercontent.com/u/63845775?v=4" width="100px;" alt=""/><br /><sub><b>Aloneangel20</b></sub></a><br /><a href="#code-aloneangel45" title="Code">💻</a></td>
|
|
447
|
+
<td align="center" valign="top" width="14.28%"><a href="https://github.com/ody"><img src="https://avatars.githubusercontent.com/u/193064?v=4" width="100px;" alt=""/><br /><sub><b>Cody Herriges</b></sub></a><br /><a href="#code-ody" title="Code">💻</a> <a href="#ideas-ody" title="Ideas & Planning">🤔</a></td>
|
|
448
|
+
<td align="center" valign="top" width="14.28%"><a href="https://github.com/slacktracer"><img src="https://avatars.githubusercontent.com/u/1865407?v=4" width="100px;" alt=""/><br /><sub><b>Thiago F</b></sub></a><br /><a href="#bug-slacktracer" title="Bug reports">🐛</a></td>
|
|
449
|
+
</tr>
|
|
450
|
+
<tr>
|
|
451
|
+
<td align="center" valign="top" width="14.28%"><a href="https://etcherfx.dev/"><img src="https://avatars.githubusercontent.com/u/96310503?v=4" width="100px;" alt=""/><br /><sub><b>EtcherFX </b></sub></a><br /><a href="#bug-etcherfx" title="Bug reports">🐛</a></td>
|
|
452
|
+
<td align="center" valign="top" width="14.28%"><a href="https://github.com/carhartl"><img src="https://avatars.githubusercontent.com/u/21918?v=4" width="100px;" alt=""/><br /><sub><b>Klaus Hartl</b></sub></a><br /><a href="#ideas-carhartl" title="Ideas & Planning">🤔</a></td>
|
|
444
453
|
</tr>
|
|
445
454
|
</tbody>
|
|
446
455
|
</table>
|