pi-lens 4.4.7 → 4.4.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (167) hide show
  1. package/CHANGELOG.md +149 -0
  2. package/README.md +12 -2
  3. package/config/markdownlint/run-no-fix.mjs +36 -0
  4. package/dist/{chunk-WME2OQST.js → chunk-2453RRJ2.js} +11 -6
  5. package/dist/{chunk-FZKFVUEC.js → chunk-2BKUFQKR.js} +276 -208
  6. package/dist/chunk-2TS4GLOJ.js +31 -0
  7. package/dist/{chunk-QHSNL7B2.js → chunk-2ZE3AUJQ.js} +12 -14
  8. package/dist/{chunk-MPKRJBPK.js → chunk-35WKJWO5.js} +28 -30
  9. package/dist/chunk-3JAHQBSY.js +27 -0
  10. package/dist/{chunk-4LM3VAZH.js → chunk-3O5EII3W.js} +2 -2
  11. package/dist/chunk-447YZL4S.js +25 -0
  12. package/dist/{chunk-H7OR7DFZ.js → chunk-4B2YFN4U.js} +25 -21
  13. package/dist/{chunk-OSTKYB55.js → chunk-4BKU7PV3.js} +1 -1
  14. package/dist/{chunk-RRV3FNNM.js → chunk-4LL2VRNY.js} +27 -28
  15. package/dist/{chunk-BZARLRJW.js → chunk-4NBWFYWW.js} +9 -9
  16. package/dist/{chunk-KKCK636N.js → chunk-4QG55RRC.js} +12 -12
  17. package/dist/{chunk-RQS4QQSD.js → chunk-4W52ZKZX.js} +2 -2
  18. package/dist/{chunk-Z2XAOKHK.js → chunk-565VRUP4.js} +2 -2
  19. package/dist/{chunk-HWDAVBFU.js → chunk-57X2CDRX.js} +23 -23
  20. package/dist/{chunk-MB6PXBUA.js → chunk-5F3XF3SX.js} +7 -15
  21. package/dist/{chunk-O4BJFESU.js → chunk-5RNB4HVK.js} +1 -1
  22. package/dist/{chunk-ZMAUPOMG.js → chunk-5T5A6YAJ.js} +35 -34
  23. package/dist/{chunk-4ZYJHQMB.js → chunk-6FIRFP6A.js} +12 -12
  24. package/dist/{chunk-4YHYPW2G.js → chunk-6GMGEKQN.js} +9 -5
  25. package/dist/{chunk-4LOE5R5P.js → chunk-6LJOJ6EO.js} +20 -15
  26. package/dist/{chunk-3YY7IXIL.js → chunk-6YUNI7B5.js} +3 -3
  27. package/dist/{chunk-PKES3ISE.js → chunk-7ANZ7XDD.js} +2 -2
  28. package/dist/{chunk-FB5SCCPT.js → chunk-7CGIDRIK.js} +16 -15
  29. package/dist/{chunk-L3CMBQMH.js → chunk-7MAD5ZAY.js} +16 -17
  30. package/dist/{chunk-WDBICWH3.js → chunk-7TNILKGY.js} +1 -1
  31. package/dist/{chunk-RORGS5II.js → chunk-A5GRLYPZ.js} +9 -9
  32. package/dist/{chunk-MNJIXFX4.js → chunk-AGGUWKRK.js} +1 -1
  33. package/dist/{chunk-ABPKUVA4.js → chunk-BBET6HD6.js} +1 -1
  34. package/dist/{chunk-L5JYIU47.js → chunk-BHWW6FAX.js} +14 -13
  35. package/dist/{chunk-URCQWAQ4.js → chunk-BOPDQ7AZ.js} +23 -21
  36. package/dist/{chunk-KDX35VXP.js → chunk-BQG2QFVO.js} +158 -133
  37. package/dist/{chunk-CB4WHS4H.js → chunk-BUZIQDFS.js} +3 -3
  38. package/dist/{chunk-2PHMIAKO.js → chunk-CM73PPGD.js} +4 -4
  39. package/dist/{chunk-DH5JPM3K.js → chunk-CUDD35TW.js} +10 -9
  40. package/dist/{chunk-AWDSEDER.js → chunk-CZL44WFN.js} +2 -2
  41. package/dist/{chunk-N5WSK2K7.js → chunk-DIWK3LBC.js} +12 -15
  42. package/dist/{chunk-24BILSZW.js → chunk-DYRZGUMA.js} +2 -2
  43. package/dist/{chunk-PR6PO3ES.js → chunk-FHEV6T4L.js} +22 -18
  44. package/dist/{chunk-DQZFQSR5.js → chunk-FRLAUP2B.js} +4 -4
  45. package/dist/{chunk-RZOXUSPC.js → chunk-G5GV2Q7K.js} +2 -2
  46. package/dist/{chunk-EKWX4WD3.js → chunk-G6JKM4O7.js} +7 -7
  47. package/dist/chunk-GGYOZWHW.js +27 -0
  48. package/dist/{chunk-XT2HTCJ5.js → chunk-GIRBSBGL.js} +6 -5
  49. package/dist/{chunk-PQJFG24Z.js → chunk-GMROJJRN.js} +1292 -946
  50. package/dist/{chunk-U6VN4NVL.js → chunk-HHR7WGCI.js} +3 -3
  51. package/dist/{chunk-TIQJPRDD.js → chunk-HKIL6DCL.js} +3 -2
  52. package/dist/{chunk-SNDXCFRS.js → chunk-HUAM7QG3.js} +11 -11
  53. package/dist/{chunk-QOE342SU.js → chunk-HXFUTMX2.js} +2 -2
  54. package/dist/{chunk-U7BD2QL7.js → chunk-I22THIHI.js} +12 -12
  55. package/dist/chunk-IE5D3RA5.js +58 -0
  56. package/dist/{chunk-DPGEAHZT.js → chunk-IYVYZQRL.js} +10 -16
  57. package/dist/{chunk-3F6BMY53.js → chunk-JBP7KESM.js} +1 -1
  58. package/dist/{chunk-U5HPROLA.js → chunk-JE6HKLC7.js} +2 -2
  59. package/dist/{chunk-ZE3KXHS7.js → chunk-JPRDTY5S.js} +85 -3
  60. package/dist/{chunk-HO6LWE2E.js → chunk-JYLOYTZD.js} +17 -1
  61. package/dist/{chunk-KW5JQPO5.js → chunk-JZRP4DGP.js} +2 -2
  62. package/dist/{chunk-CPSR3AVL.js → chunk-KZ4ALBCH.js} +2 -2
  63. package/dist/{chunk-6IR3ZYIB.js → chunk-L3CLUGDY.js} +3 -3
  64. package/dist/{chunk-LV4UMYVH.js → chunk-L4NEVZ4T.js} +28 -27
  65. package/dist/chunk-LPYTPNOJ.js +22 -0
  66. package/dist/{chunk-WGRJOXED.js → chunk-LSFXZLPW.js} +1016 -636
  67. package/dist/{chunk-LBLBAFG3.js → chunk-MC6VB2E5.js} +4 -4
  68. package/dist/{chunk-U2SDMG7C.js → chunk-NM2NWH55.js} +5 -5
  69. package/dist/{chunk-T7A2HK2B.js → chunk-NSPVR3FN.js} +19 -18
  70. package/dist/{chunk-ZGSJDWQU.js → chunk-O2ARHQKF.js} +2 -2
  71. package/dist/{chunk-OXOI55RU.js → chunk-O4N5BQ3T.js} +10 -10
  72. package/dist/{chunk-3FRLWYBG.js → chunk-OC7VWJBZ.js} +39 -40
  73. package/dist/chunk-OFNMHPBT.js +89 -0
  74. package/dist/{chunk-HR3OJ3TH.js → chunk-OWTG6UMO.js} +21 -21
  75. package/dist/{chunk-75GAYVNO.js → chunk-OY7WZI7Q.js} +6 -6
  76. package/dist/{chunk-ZJTT47IG.js → chunk-OZWXLJMX.js} +2 -2
  77. package/dist/{chunk-F6X3YJWD.js → chunk-PIQQM32Y.js} +2 -2
  78. package/dist/chunk-PKLB2XJL.js +8 -0
  79. package/dist/{chunk-EAOK7MIZ.js → chunk-PKSUMEPT.js} +17 -4
  80. package/dist/{chunk-YISME6ON.js → chunk-PPKECBPP.js} +1 -1
  81. package/dist/{chunk-4L36HG27.js → chunk-R2QQC33W.js} +14 -14
  82. package/dist/{chunk-LUBPZN36.js → chunk-R4QWJQ2H.js} +11 -11
  83. package/dist/{chunk-V63BC55Q.js → chunk-RGGH6M34.js} +1 -1
  84. package/dist/{chunk-Y7F7IEE3.js → chunk-RZG472YW.js} +65 -7
  85. package/dist/{chunk-PUZ3E2J4.js → chunk-SDFKOLSF.js} +6 -6
  86. package/dist/{chunk-YHC2O2WO.js → chunk-SFLHSL5R.js} +9 -9
  87. package/dist/{chunk-CCV2EU7T.js → chunk-SP4TFY5F.js} +14 -13
  88. package/dist/{chunk-J6JP25XU.js → chunk-SQC7K3SP.js} +4 -3
  89. package/dist/{chunk-3K2F6UDZ.js → chunk-T2S3FNNJ.js} +44 -42
  90. package/dist/{chunk-2TF6RXWB.js → chunk-TV6RXRYH.js} +10 -10
  91. package/dist/{chunk-GNSIWBAT.js → chunk-U3AS2FR6.js} +3 -3
  92. package/dist/{chunk-F7K5IBZG.js → chunk-UHHLR2VY.js} +40 -40
  93. package/dist/chunk-UYXV5NIS.js +20 -0
  94. package/dist/{chunk-VSFLRN5Y.js → chunk-VLQ7UKZH.js} +1 -1
  95. package/dist/{chunk-VUZWQ7UG.js → chunk-VN3L2JWZ.js} +46 -72
  96. package/dist/{chunk-NA7SEXHE.js → chunk-VOP4PJKA.js} +7 -7
  97. package/dist/{chunk-F5Z6URKM.js → chunk-VOXTCULR.js} +2 -2
  98. package/dist/{chunk-LLS45EWB.js → chunk-VPLBLWFO.js} +6 -8
  99. package/dist/chunk-W3BGKBBK.js +27 -0
  100. package/dist/{chunk-ZKXQKGWZ.js → chunk-WC6WRNQT.js} +4 -3
  101. package/dist/{chunk-YVHBNSME.js → chunk-WMDUT4KH.js} +1148 -1132
  102. package/dist/{chunk-KXF5R4UN.js → chunk-WQV6BI4Q.js} +1 -1
  103. package/dist/chunk-WXUDRAG6.js +24 -0
  104. package/dist/{chunk-KPPJTH44.js → chunk-X35S7HSB.js} +28 -10
  105. package/dist/{chunk-JMEKXFOL.js → chunk-X66YJ2SS.js} +40 -34
  106. package/dist/{chunk-CE6VMBCB.js → chunk-XOMGO63G.js} +22 -21
  107. package/dist/{chunk-LS3QJRUB.js → chunk-XWIME22V.js} +13 -13
  108. package/dist/{chunk-R5MOQM2H.js → chunk-XYLC35E4.js} +119 -87
  109. package/dist/{chunk-OE5ZBP7F.js → chunk-YHGYAEFH.js} +18 -18
  110. package/dist/{chunk-7E2563GA.js → chunk-ZFORSIED.js} +13 -13
  111. package/dist/{chunk-E7HJ56Y7.js → chunk-ZKLTNLAW.js} +64 -73
  112. package/dist/chunk-ZONZ6YY3.js +74 -0
  113. package/dist/chunk-ZSM35JF4.js +30 -0
  114. package/dist/{chunk-RC2Z6K47.js → chunk-ZZDIOAAJ.js} +15 -6
  115. package/dist/index.js +6993 -5396
  116. package/dist/mcp/analyze-cli.js +10 -10
  117. package/dist/mcp/cli.js +44 -42
  118. package/dist/mcp/server.js +1627 -504
  119. package/dist/mcp/worker.js +62 -61
  120. package/dist/probes/installer.js +20 -19
  121. package/docs/adr/0003-git-guard-latch-writer.md +11 -6
  122. package/docs/agent-tools.md +18 -8
  123. package/docs/alignment-families.md +29 -0
  124. package/docs/ast-grep_rules_catalog.md +6 -4
  125. package/docs/ci-bot-pr-checks.md +126 -0
  126. package/docs/configuration.md +99 -3
  127. package/docs/defect-shapes.md +55 -12
  128. package/docs/engineering-principles.md +27 -2
  129. package/docs/features.md +2 -2
  130. package/docs/invariants/git-guard-host.md +7 -3
  131. package/docs/invariants/language-config.md +15 -4
  132. package/docs/invariants/lsp-trust-exec.md +16 -2
  133. package/docs/invariants/paths-os.md +4 -2
  134. package/docs/lsp-capability-matrix.md +119 -39
  135. package/docs/merge-queue-rollout.md +1 -1
  136. package/docs/pi-lens-fixer.md +24 -17
  137. package/docs/pi-lens-merge-policy.md +20 -11
  138. package/docs/pi-lens-monitor.md +9 -0
  139. package/docs/pi-lens-orchestration.md +4 -1
  140. package/docs/pi-lens-reviewer.md +5 -5
  141. package/docs/pi-lens-subagent.md +6 -3
  142. package/docs/public-api-stability.md +18 -2
  143. package/docs/schema/pi-lens-config-v1.json +10 -0
  144. package/docs/settings.md +10 -6
  145. package/docs/word-index.md +17 -5
  146. package/package.json +5 -3
  147. package/rules/ast-grep-rules/rule-tests/no-accumulating-spread-js-test.yml +37 -0
  148. package/rules/ast-grep-rules/rule-tests/ts-redundant-filter-map-test.yml +12 -1
  149. package/rules/ast-grep-rules/rule-tests-disabled/filter-then-map-js-test.yml +12 -0
  150. package/rules/ast-grep-rules/rule-tests-disabled/filter-then-map-test.yml +25 -0
  151. package/rules/ast-grep-rules/rules/no-accumulating-spread-js.yml +49 -1
  152. package/rules/ast-grep-rules/rules/ts-redundant-filter-map.yml +9 -1
  153. package/rules/ast-grep-rules/rules-disabled/filter-then-map-js.yml +17 -0
  154. package/rules/ast-grep-rules/rules-disabled/filter-then-map.yml +36 -0
  155. package/rules/ast-grep-rules/self-scan-baseline.json +1 -1
  156. package/dist/chunk-46TNM7XZ.js +0 -88
  157. package/dist/chunk-72OKUXSD.js +0 -31
  158. package/dist/chunk-7GLOLOSH.js +0 -57
  159. package/dist/chunk-AKUUMGD5.js +0 -26
  160. package/dist/chunk-ASUXV767.js +0 -22
  161. package/dist/chunk-CTADOKYM.js +0 -25
  162. package/dist/chunk-JJ2RRESP.js +0 -58
  163. package/dist/chunk-LSC3VADM.js +0 -23
  164. package/dist/chunk-SHLDT3OI.js +0 -27
  165. package/dist/chunk-UF7RTZSO.js +0 -27
  166. package/dist/chunk-W4WP2ERB.js +0 -30
  167. package/dist/chunk-YES5CACN.js +0 -73
package/CHANGELOG.md CHANGED
@@ -16,6 +16,155 @@ All notable changes to pi-lens will be documented in this file.
16
16
 
17
17
  ### Security
18
18
 
19
+ ## [4.4.8] - 2026-11-01
20
+
21
+ ### Added
22
+
23
+ - **`dispatch.disabledRunners` turns a dispatch runner off** — list runner ids such as `["dotnet-build"]` in `~/.pi-lens/config.json` or a project `.pi-lens.json` and pi-lens never runs them, so no `dotnet build` (or other tool) is spawned while the language server and every other runner in the group keep working. The list is a denial, resolved like `lsp.disabledServers`: the union of every tier, so a project can add a runner but never re-enable one you denied. A disabled runner is recorded as skipped with the reason `disabled-by-config`, not as a failure, and a fallback group moves on to its next runner. A nested `.pi-lens.json` governs the files under it. When config denied every checker that could not answer, the coverage notice and status line name `dispatch.disabledRunners` once per session; when a sibling also failed, they name the failure and the denial together. An id that names no runner is dropped with a `PILENS_CFG_0005` warning that quotes it (bounded like every config notice) and counted in `effective_config`'s `recordCounts`. `effective_config` shows the runner as `disabled-by-config` with the tier and file that denied it. `dispatch.runnerTimeoutFloorMs` stays global-only and a project file that sets it is now told so. `rules.<id>.disable`, `select` and `ignorePaths` now follow the same owner: each file reads them from the nearest `.pi-lens.json` at or above it, on every surface that filters by them (dispatch, `lens_diagnostics`, `lsp_diagnostics`, the turn-end advisories), and the root's policy still reaches nested files. A nested `ignorePaths` glob is relative to its own file's directory (refs #5010).
24
+
25
+ ### Changed
26
+
27
+ - **`rules.<id>.ignorePaths` now matches like the `ignore` field** — entries follow gitignore rules, relative to the `.pi-lens.json` that declares them: the last matching entry wins, `!` re-includes a path an earlier entry carved out, a leading `/` roots the entry at that file's directory, and a trailing `/` names a directory. Before, every entry was a plain glob, so a `!legacy/keep.ts` entry hid every path its glob did not name, and `/legacy/**` and `legacy/` matched nothing. Entries with a slash keep their meaning; a slashless entry such as `*.gen.ts` now also matches below the root, and a line starting with `#` is a comment. Each config file stays its own scope, so a `!` re-includes only against its own file's entries and never lifts a carve-out another file (or the global config) declared (refs #5029).
28
+
29
+ - **`ast_grep_outline` returns a compact text tree instead of JSON** — one `77-81 export function name` line per symbol, range first like `module_report` compact, with project-relative file headers; the read handles, byte offsets, node kinds and empty signatures are gone, so a file outline is about 5x to 10x smaller. The measured default case, a 60-file directory outline, now fits the delivery bound instead of arriving cut in the middle; the default call is not promised to fit every directory, and `items: "all"` or `view: "expanded"` on a large directory still hit the cut, which keeps a visible marker. Files are sorted by project-relative path before the 50-file cap, and a `... N more files not shown` line says what was left out. Read a listed range with `offset=start`, `limit=end-start+1` (#5071, refs #1449).
30
+
31
+ - **Reducer copy and filter-map warnings change.** `no-accumulating-spread-js` now flags a reduce callback that copies its accumulator through `Object.assign`, `Array.from`, `concat` or `slice`, not only through a spread, and its message names the object case. `ts-redundant-filter-map` now warns only on identity filters (`filter(x => x)`, `filter((x: T) => x)`, `filter(Boolean)`), so a TypeScript `filter().map()` chain that warned before no longer warns. The new `filter-then-map` hint ships disabled. (refs #5093, refs #5094)
32
+
33
+ - **`symbol_search` and `pilens_symbol_search` emit one table, not a table plus the same hits as JSON (refs #5104).** The pi tool appended a compact `JSON.stringify` payload that repeated every hit, and the MCP mirror appended the same hits again as a fenced JSON block; neither carried anything the rows and footer cannot. `renderCompactSymbolSearch` in `clients/lens-engine.ts` now owns the text on both surfaces: a header, one row per hit — ` 1. <path> <line> (score 0.82, 3 hit(s), fanIn 4)` — and a footer with index coverage, the MCP-only staleness note, and one next-step line naming the top-ranked hit (`module_report <path>` on pi, `pilens_module_report <path>` on MCP). Annotations print whenever the cached review graph supplies them, so `fanIn 0` ("no known importers") shows instead of vanishing. Measured on four `clients/` files, one query each, through `finalizeToolResultWithDelivery`: `bytes=3395` before, `bytes=1109` after. `details` keeps `{ available, query, count, coverage }`.
34
+
35
+ - **Twelve hand-rolled containment tests now share one `relativeInside` seam.** A runner diagnostic for the project's parent directory shows its absolute path instead of `..`, and a home directory named `..cfg` under a project directory ends the home-ceiling walk like any other (refs #2556).
36
+
37
+ - **A gitleaks or trivy scan that failed is no longer read as a clean scan.** A CLI that failed to spawn, whose run threw, or that exited non-zero without writing its report now leaves a `security-scan-report-failed` health row and a failed (not cached-clean) result, as opengrep and jscpd already did. Both scanners now share one report-scan body (`SecurityScanClient.runReportScan`), so their outcomes cannot drift apart (refs #4907).
38
+
39
+ ### Fixed
40
+
41
+ - **A bash-only turn no longer labels its fresh turn-end findings historical (refs #4617).** The provenance stamp now speaks for every part the message carries: each file-bound producer registers the files its text reports (the stale-secrets tier, knip, dead-code, trivy's scanned dependency declarations, call-graph impact, the actionable and code-quality warning advisories, the demoted inline blocker, the cascade test suggestions), and a part with no file it could be stale against — a runner crash note, a suppressed-count notice — is stamped current for the turn that produced it. A part carried from an earlier turn, or one that declares neither, still reads "Historical finding; workspace changed since capture", and `tests/config/turn-end-part-provenance-census.test.ts` fails when a new turn-end producer declares nothing.
42
+
43
+ - **A blocker retires when the language server confirms the fix, even if a scanner stayed silent.** A partial language-server run now answers for the servers that answered: the primary's recorded blockers clear, while the unconfirmed auxiliary's own blockers stay pending and still hold the commit gate shut, and the coverage notice still names it. Every edit after the once-only notice keeps naming it too, instead of reading clean. The `🔴 Still unfixed` line also lists a short rule id per line (`L64 ts:6133`) and says how many counted blockers it cannot place — one whose line could not be re-placed in the new bytes, and one with no line in this file — instead of counting lines it no longer lists. (refs #5008)
44
+
45
+ - **A blocker stays recorded when the language server answers for older bytes.** When the server's findings were computed for an earlier version of the file, the edit no longer treats them as a verdict on the new bytes: they are not delivered, a blocker recorded earlier stays pending and keeps the commit gate shut, and the next edit checks again. Before, such findings retired that blocker even though it was still in the file. The turn-end re-check of carried warnings likewise keeps a warning, marked as not re-verified, when the server's answer was for older bytes. (refs #5017)
46
+
47
+ - **An attached session no longer reads another session's stale answer as current.** When a pi-lens session shares a running language server through another session (warm attach), that session's answer now says whether its findings describe the bytes on disk, and the attached session treats findings about older bytes the way a local one does: they are not a verdict, a recorded blocker stays pending, and the tool and sweep results show them as unconfirmed. An answer from a session on an older pi-lens build carries no such statement and is treated as not current until both sessions run this build. (refs #5030)
48
+
49
+ - **A helm chart beside a denied `helm-lint` no longer reads as a failed tool** — with `helm.renderValidation` off, `helm-render` reports a stated `not-enabled` skip, so the coverage notice for a chart file says the runner is disabled in config instead of "a language tool is missing, timed out, or failed to run". The file is still reported unconfirmed (#5042).
50
+
51
+ - **The bundled `minimatch` is updated to 11.x for GHSA-g3hv-75wg-m249.** The published package inlines `minimatch`, so scanners flagged the 10.2.6 copy for a crafted glob that amplifies `globParts` when `optimizationLevel` is 2 or higher. pi-lens never sets `optimizationLevel` (the default is 1), so no pi-lens glob reached the vulnerable path; the dependency is now `^11.0.1`, and the lockfile resolves 11.0.3. One gitignore-style entry changes: a final extglob that can match nothing, such as `dir/!(x)` or `dir/*(x)`, no longer hides the whole `dir/` directory from the walk. 10.2.6 pruned that directory, so this is a fix; 11 hides only the children the extglob matches. (closes #5129)
52
+
53
+ - **The cascade no longer reports neighbour errors computed for other file bytes**: the in-turn cascade showed "Cascade errors in N neighbor file(s)" for findings the language server computed against an earlier version of the file, while the diagnostics check already withheld them; the cascade now withholds those rows too, names the file as unconfirmed instead, and never reads the run as clean (#5051).
54
+
55
+ - **A `pi-lens-ignore` comment or a disposition mark now applies to the file a finding names**: a comment in the edited Helm template no longer hides the blocking `helm-lint` error reported on `Chart.yaml`, on the edit path, in a slow runner's late answer or in the turn-end blocker; a mark on one file's finding no longer hides the same finding on another file; a finding whose file cannot be read or lies outside the project is never suppressed; and a mark made earlier against the template path for a `Chart.yaml` finding stops applying, so that finding shows once until it is marked on `Chart.yaml` (#5044).
56
+
57
+ - **A directory whose name starts with `..` is no longer read as outside its project.** Ten containment tests compared `path.relative` text with `startsWith("..")`, so a file under `<root>/..pkg/` was classed outside the root: its nested `.pi-lens.json` was not read, a hosted LSP client was not reused, a Cargo workspace member kept its own root, a rendered Helm file fell back to Chart.yaml, a mirrored test was not found, a Knip or madge shim was labelled `global`, a stale finding was not retired, and the MCP turn-end route refused the cwd. They now share `isUnderDir`, `isWithinForm`, `isWithinPathForm` and `toProjectRelativePath` from `path-utils.ts` and `file-utils.ts` (refs #2556).
58
+
59
+ - **A `pip install` into a project `.venv` that keeps no lockfile now counts as an install**, so pyright's cached `Import "x" could not be resolved` clears on the next `lsp_diagnostics` call instead of lasting for the server's life. The look stamps each `.venv/<lib|Lib>/…/site-packages` directory beside the lockfile and `node_modules` markers (#4532).
60
+
61
+ - **LSP sees outside disk changes before `lsp_diagnostics` answers; a new subdirectory marker roots it (refs #4532)** — the look that reports a declaration, config or install change walked at most once every `PI_LENS_DECLARATION_LOOK_MS` (2 s), so a `.d.ts`/`.pyi`, a server config or an install made inside that window reached no server before the answer; the diagnostics answer now runs that look itself, with a forced walk (16 ms on a 688-directory repository, 0.12 ms on a small one). Separately, the project-boundary verdict was cached for the client registry's life, negatives included, so a marker created in a subdirectory after the parent's client answered never rooted it (real pyright 1.1.414: stale through 40 calls over 20.25 s); the verdict is now read from the disk on every resolution, and a deleted marker un-roots the directory again.
62
+
63
+ - **A subagent's deferred format runs in its own settle:** with an in-process subagent, a file it wrote through a tool pi-lens observes, `ast_grep_replace`, `lens_diagnostic_mark` or a background change found at settle is now queued under the subagent, and the subagent's own `agent_settled` formats it and its native edits. Before, the parent session formatted such a write as its own, and the subagent's native edits waited for the parent's 10-minute orphan claim. A subagent still never takes the parent's records or runs the actionable-warning quick fixes (refs #4943).
64
+
65
+ - **Upward walks start from the file's real path.** A file reached through a file link now reads its target's Cargo edition, package root, `node_modules` and metrics-history commit, not the link's neighbours; every hand-rolled climb in `clients/` now runs on `walkUpDirs`, and a test runs each walker from a symlink twin (refs #4966).
66
+
67
+ - **A demoted blocker now honours your marks and stops re-serving dead coordinates:** a `[stale — re-run to confirm]` advisory runs the same disposition policy as the live blocker channel, so a `false-positive` or `suppress` mark silences it, and a `self-drift` record the agent fixed by rewriting the file retires after `SELF_DRIFT_MAX_DELIVERIES` deliveries with a "re-run can still confirm" reason. A confirmed-clean verdict that covers only some of a record's sources now retires the source rows it spoke for instead of leaving the whole record, dead coordinates included, to re-serve for the rest of the session (refs #4990).
68
+
69
+ - **A fallback language server no longer confirms a file clean for a primary that never answered.** When the Python checker was refused (an adopted project's local binary), failed to start or was not installed, python-jedi answering with nothing read as "Primary LSP (python): confirmed clean". The file now reads unavailable and names the missing primary, for both server scopes, and says no primary language server answered; the fallback's own findings are still shown, on cascade neighbours too, except an answer computed for older bytes or published before the edit, which is withheld instead of blocking the edit. A neighbour's earlier errors stay listed as not re-checked while only the fallback answers for it (refs #5014).
70
+
71
+ - **A blocker row naming another file retires with that file (refs #5020)** — a helm-lint, helm-render or mypy row recorded against the written file now leaves once the file it names is written clean or deleted, so the commit gate no longer stays shut on a finding nothing can fix.
72
+
73
+ - **`ast_grep_replace` refuses a defaulted working directory at or above `$HOME`** — the mutating tool had the ceiling `ast_grep_search` already enforced, so a dry run from your home directory previewed, and an apply rewrote, files anywhere under it. Both tools now decide through one guard in `tools/shared.ts`, and `#5039`'s refusal names the offending cwd and asks for explicit `paths`. An explicit `paths` entry such as `.` is still honoured, as in search.
74
+
75
+ - **A Java edit now cascades to the files that import it.** The cascade used to skip Java files, so an importer broken by the edit was never reported. It now asks jdtls about each importer, delivers the errors it finds, and names an importer jdtls has not re-checked since the edit as unconfirmed instead of clean (#5040).
76
+
77
+ - **A cascade dependent whose only answer predates the edit no longer reads as clean**: a push-only language server that does not republish a dependent after the file it depends on changed could leave a broken dependent reported as a clean cascade; the run now names it unconfirmed instead.
78
+
79
+ - **An edit whose dependents the graph cannot place no longer reads as a leaf.** When a caller references a changed symbol by name alone and another definition shares the name, the cascade dropped the caller and reported no neighbours, the same verdict as a file nothing uses. It now reports the run as indeterminate and says a clean cascade result does not cover those files (#5055).
80
+
81
+ - **A blocker on a file a script wrote is no longer reported as clean**: when a bash heredoc (python, node) writes a file pi-lens cannot prove you authored, the tool result now names the file and the number of blocking findings it withheld instead of `✓ clean`, and when the host's 500 ms read-only bound abandons the check, the same disclosure reaches you at the next context call with the abandonment stated. The STOP block, autofix and the commit gate stay off for those bytes (#5108).
82
+
83
+ - **A diagnostics pass no longer rewrites your file under a project fix setting**: `ruff check` now runs with `--no-fix --no-fix-only` (a project `fix = true` or `fix-only = true` used to delete unused imports on save, even with pi-lens format and autofix off) and `golangci-lint run` with `--fix=false` (`issues.fix: true`) (#5119).
84
+
85
+ - **A markdownlint diagnostics pass no longer rewrites your file under `"fix": true`**: pi-lens now lints through `markdownlint-cli2`'s exported `main` with `fix` forced off, run in a small child process under the same 15 s budget, found beside the resolved command (project `node_modules/.bin`, the managed tool dir, or a PATH install), so a project `.markdownlint-cli2.jsonc` with `"fix": true` no longer deletes trailing spaces on save even with autofix off; config discovery, `extends`, `ignores` and `overrides` stay cli2's own, an edited `.cjs` config is read fresh, the autofix stage still fixes, and when no package sits beside the command the CLI is spawned as before and one `markdownlint-api-unavailable` row is recorded (a project `"fix": true` can still write on that path) (#5119).
86
+
87
+ - **`lsp.servers.<id>.command` accepts the argv array the docs show**: `"command": ["my-lsp-server", "--stdio"]` now launches (the first element is the program, the rest come before `args`, and no default `--stdio` is added) instead of failing with `The "path" argument must be of type string`, and `effective_config` shows such a server's command and argument count (#5127).
88
+
89
+ - **A custom server that recompiles on pi-lens's own file notice can no longer wipe a real error**: when a version-less `lsp.servers` server (groovy-language-server) published an error for a freshly opened file and then an empty set right after the `workspace/didChangeWatchedFiles` pi-lens sends for that file, the file read clean; that one empty publish is now held and the error stays, and a later edit still earns its own clean. Built-in servers are unchanged (#5131).
90
+
91
+ - **A second session's commit no longer writes the first session's blockers into its own record**: with `--lens-guard`, a commit by a concurrent session in another repository that picked up the first session's settled collect-later blocker recorded it in its own tree's commit-gate record under the first session's id, so every later commit there was refused `session_mismatch` for a file it did not own. The gate now persists only the committing session's own blockers in the committed repository, and a commit in one repository is no longer refused for a blocker in another, whoever wrote it. The other session's blocker still gates its own tree (#5048).
92
+
93
+ - **A custom language server that publishes late is no longer stuck as unsupported**: a custom push-only server that had not published by the end of the first-contact wait was latched diagnostics-unsupported for the whole session, so it never reported findings and one report could list a finding beside `unsupported=1`. A publish at any time now clears the mark, and a server that has not published reads as unconfirmed (`inconclusive`), not unsupported (#5128, #5123).
94
+
95
+ - **`path` is the one single-file parameter, and `paths` behaves the same on every tool**: `pilens_module_report {path}`, `pilens_diagnostics {file}` and `pilens_analyze {path}` now run instead of being refused or silently answering for the whole default scope, `effective_config` and `lens_diagnostic_mark` accept `path` while keeping their older `file`/`filePath` spellings, a non-string, blank or empty (`[]`) `paths` list, or one over 100 entries (`ast_grep_search` took 200 before), is refused with one message on every tool instead of being dropped, and `symbol_search` now scopes `src`, `./src` and the absolute directory to the same hits and clamps `limit` to `max(1, floor)` (#5041, #5038).
96
+
97
+ ### Internal
98
+
99
+ <details>
100
+ <summary>32 internal changes: tests, CI, tooling, and refactors</summary>
101
+
102
+ - `node scripts/probe-save-verdict.mjs` measures, per server, whether a language server publishes its findings without a `textDocument/didSave` or only after one, through the real client on the tool-smoke fixtures. The nightly `tool-smoke` workflow runs it with `--install` and it regenerates the three measurement columns of `docs/lsp-capability-matrix.md`'s save-verdict table, merge-guarded so a runner that cannot install a server keeps that row, and an unmeasured row names the installer's own cause beside the reason no arm could measure it, while a tool the installer does not manage (its binary on the runner's PATH) is still measured. `tests/config/lsp-save-verdict-census.test.ts` pins the population, the verdict vocabulary and the rule that a verdict without provenance is refused. (refs #3405)
103
+
104
+ - A governance ast-grep suite (`scripts/governance-rules/`, `npm run astgrep:governance`, also run by `npm run astgrep:self-scan`) flags a test loop that waits by counting turns or polls and then checks a condition (defect shape 86), and a `*ForTests` hook in `clients/` that does the same. A real-clock deadline (`waitFor`) is the admitted form; 46 existing members sit in a reasoned, content-keyed baseline, and eight one-line members moved to `waitFor`. An `ast-grep-ignore` must name its rule and a reason. The LSP facade import sweep moved to oxlint's `no-restricted-imports`. (refs #4865)
105
+
106
+ - The tree-walk timeout census (`tests/config/tree-census-timeout.test.ts`) now scans every test under `tests/`, not only `tests/config`, so a tree walk without a timeout budget reds wherever it sits. The 87 refused members that predate the widening are admitted by name in `tests/config/tree-census-timeout.baseline.json`, each with a reason. (refs #4967)
107
+
108
+ - The session-state owner-key check now covers the file-level exemptions, the declared session stores, reset-less module containers, class fields bound to a container and containers held as members of a module-level object, so state the #4965 bugs sat in is no longer outside it. (refs #5027)
109
+
110
+ - `tests/clients/installer/managed-tool-refresh-strategies.test.ts` clears `GH_TOKEN`, `GITHUB_TOKEN`, `ZIZMOR_GITHUB_TOKEN` and `ZIZMOR_OFFLINE` for every case through `withEnv` and restores the caller's values afterwards, so a token exported in the environment no longer reds nine github cells. (#5073)
111
+
112
+ - `Targeted tests (advisory)` is gone from PR CI: its selection caught the failing file on 26.7% of real Unit reds (#3215), so the full Unit suite stays the only test gate. The changed-test shuffle (#4397) is now its own advisory job, `Changed tests shuffled (advisory)`, with only the setup it needs (refs #3215).
113
+
114
+ - `Hot-path latency (advisory)` now starts on every pull request and passes with "no hot-path files changed" when the diff touches none of `HOT_PATH_PATHS` (`scripts/ci-changed-files.mjs`), so it can become a required check without leaving docs-only pull requests at "Expected"; a hot-path diff still runs the full timing job, and a master push keeps its `paths:` filter (#4363).
115
+
116
+ - **Nightly refresh PRs start the required CI**: the job that opens the LSP-docs refresh and idle-eviction promotion PRs now dispatches `ci.yml` and `lint.yml` on the bot branch, because a PR opened with `GITHUB_TOKEN` starts no `pull_request` run and sat BLOCKED with every check absent, and `ci-verdict` now gates the non-advisory checks of a dispatch run on a bot-opened PR like a `pull_request` run (#5062).
117
+
118
+ - **CI frees runner slots, rebalances the Unit shards and keeps one npm cache**: the four `TLA+ models` shard jobs no longer start on a pull request that leaves `formal/` and its checker alone (the required `TLA+ models` aggregate still reports), the Unit shard weights are regenerated from five master runs (215 test files had no recorded duration), the Unit shards restore `~/.npm` once instead of twice, and `cache-prune.yml` also prunes when the CodeQL workflow completes on master so the overlay databases stay bounded (#5082).
119
+
120
+ - The PR-body lint prints sentence-length and filler findings as warnings and no longer fails on them. Structural rules and title-case headings still fail (#5110).
121
+
122
+ - The three required `Install test (<os>)` legs now install only when a pull request touches `INSTALL_PATHS` (`scripts/ci-changed-files.mjs`: the manifests, the lifecycle scripts, the scripts the job runs, `bin/`, the two install workflows) and otherwise pass in seconds with "no install files changed"; `Strict install (cold npm cache)`, the lint `strictness` job and the install-smoke `smoke` job (outside install paths) no longer start on a pull request, the `greeting` job starts only for a first-time author, and master pushes and dispatches keep every step (#5112).
123
+
124
+ - The nightly live cascade lane gains a typescript-go rename phase: it restores the exporter, moves it through `LSPService.renameFile` and requires each importer to reach the verdict its file calls for (refs #1712).
125
+
126
+ - The local PR-body lint sends every git read through the injected git, and the Observability record scan skips the family token of a `TLA+ unaffected:` line, so the TLA+ coverage lint cases no longer spawn real git or lex the runtime tree and stop timing out at 5 s on a loaded runner (closes #3902, refs #4909).
127
+
128
+ - **Stryker nightly bounds its range sample by mutants, not ranges (refs #4171)** — the sampler kept `ranges x allowance / mutants` ranges, which assumes every range holds the same number of mutants; run 40847865852 kept 3 ranges holding 55 mutants against ~24 affordable and exited 1 at the budget. The sample is now counted with a no-test Stryker pass and shrunk, deterministically, until it fits the allowance.
129
+
130
+ - **LSP sweeps, warm-ups, batches and project scans no longer leave an abort listener per file (refs #4907).** Five private races of a promise against the caller's `AbortSignal` added a listener and never removed it (the warm-up and its retry backoff, the per-file pre-open of a sweep, the analyzer race of a project scan, and each file of an `lsp_diagnostics` batch), so a signal that outlives one call kept a dead closure for every file it served. All seven races now go through one `untilAborted` in `clients/deadline-utils.ts`, which releases its listener when the race settles, and `tests/clients/abort-listener-release-sweep.test.ts` refuses any abort listener site it does not admit, including a computed method name or a non-literal event (an aliased import and a method fetched by `Reflect.get` stay an accepted gap).
131
+
132
+ - The lockfile-completeness npm-9 rewrite case runs real npm on rolldown's closure from the repo lock instead of all ~450 packages, and its budgets follow the lane's test-timeout scale with the gate's kill below the case budget, so a slow cold-cache runner no longer times it out (closes #4936).
133
+
134
+ - A lockfile-completeness gate that hits its npm timeout now stays inconclusive with the reason `timed out after <budget>ms` instead of `npm pin unavailable`, and the CLI line prints that reason; an acquisition outage still reads `npm pin unavailable` (#4995).
135
+
136
+ - **PR body lint: a re-spelled failure token is not a new failure path (#5019)** — the Observability failure-path scan credits a hunk's removed `catch`, `throw`, `return null` or `recordDegradationOnce` against that hunk's additions of the same kind, compares per token kind and per hunk (never per file), and lexes the reconstructed pre-image so a token inside a removed comment or string credits nothing. A body that only re-spells the condition in front of an existing `return null` now passes `pr-body.sh`, and an addition with no removed counterpart still refuses.
137
+
138
+ - The nightly save-verdict refresh keeps a settled `no`/`yes` and its evidence when a night measures `inconclusive` or `cannot measure`, and logs the held night instead of overwriting the row (#5060).
139
+
140
+ - `guard-bash` now admits the read-only `git stash list` and `git stash show` (every writing stash form and any spelling it cannot classify stays denied), and every worktree-remove refusal names the new `scripts/worktree-remove.mjs <path>`, which unlinks a `node_modules` symlink, refuses a real `node_modules` directory, then runs `git worktree remove` (#5111).
141
+
142
+ - PR bodies now have four sections (`Summary`, `Notes for the reviewer`, `Change outline`, and `Proof and checks`), and the body lint counts the parsed markdown: visible text is capped at 5000 characters, each code block at 20 lines and 400 columns (100 lines in all), the summary at three sentences and 600 characters, and reviewer notes at one list of five bullets. `Class sweep` carries an `Alignment:` line naming the families of `docs/alignment-families.md` it touches. `Why` folds into `Summary`, `Test assessment`, `Type of change`, `Area`, and `Checklist` are gone, and `Blast radius` is conditional (#5003). A table row whose cell count differs from its header (an unescaped `|` in a backticked cell splits it on GitHub) is refused.
143
+
144
+ - The ast-grep snippet directories of `dumpAst`, `validatePattern` and `validateRule`, and the helm render scratch directory, now take their parent from `scannerReportParentDir()` like every other `mkdtempSync` scanner directory, so a harness-owned scanner root also catches a directory a killed child strands (refs #4907).
145
+
146
+ - Every spawn of a System32 executable (`taskkill`, `cmd`, `chcp`, `tar`, `powershell`) in `safe-spawn`, the LSP teardowns and the installer now takes its path from `windowsExe` instead of a hand-built `%SystemRoot%` string, and `windowsExe` builds a Windows path whatever host runs it (refs #4907).
147
+
148
+ - 38 production sites that hand-rolled the backslash-to-slash fold (`.replace(/\\/g, "/")`, `.replaceAll("\\", "/")` and `.split("\\").join("/")`) now call `toPosix` from `clients/path-utils.ts`, and one fold that was a no-op (`detectFileRole`'s second fold) is deleted. Behaviour is unchanged; `tests/clients/to-posix-fold-sites.test.ts` drives 12 of the former sites through their exported callers. (refs #4907)
149
+
150
+ - Adds a nightly live cascade lane to the tool-smoke workflow: for typescript-go, rust-analyzer, gopls and jdtls it edits an exporter, calls the production cascade, and reds when an importer does not reach a conclusive verdict with the server's own finding (refs #1712). The first measured time-to-conclusive per server is committed in `tests/fixtures/lsp-cascade/measurements.json`.
151
+
152
+ - **The tmp-fixture census asserts on the Windows lane again, and a red names its producer**: the `win32` quarantine around the four census assertions is removed, each sweep now persists what it found at every registered root, and the census failure message states per leaked entry whether the registry held it at sweep time, how its birth, modification and change times sit against the last sweep, and its first-level children (#4591).
153
+
154
+ - Moves the stale-context stub out of the pi double and five pi-mock cases onto the real pi session, and retires two admit rows (refs #4937).
155
+
156
+ - Moves both NDJSON shutdown-drain cases off the pi double onto the real pi session (inline-factory mode), drops the file's census row and relabels the `handler-verdict-helper` row (refs #4937).
157
+
158
+ - Joins the loaded extension copy's deferred snapshot and probe-cache writes (and its NDJSON rows) before the tier-2 test helper removes its fixture root, so a late write no longer re-creates the root and reds the tmp-fixture hygiene census (refs #4937).
159
+
160
+ - Plants the yamllint shim of the smoke-tools cwd case outside the checkout, so it passes on a host with its own yamllint (closes #4996).
161
+
162
+ - `tests/index-lsp-config-root-eviction.test.ts` now joins the background-write drain registry before it removes its `PI_LENS_HOME` fixture, so a late project-snapshot worker write no longer re-creates the directory after a settled teardown and reds the tmp-fixture hygiene owner. The instance-registry mutation tail is left to the environment restore and the worker's own teardown (refs #5024).
163
+
164
+ - `tests/support/pi-session-commit-gate.ts` now owns one `warmGuardedSession` warm-up that pays a guarded session's cold first-session cost in a `beforeAll`, so `tests/index-4689-path-identity-witness.test.ts` no longer times out on its first case under `--sequence.seed=424`; `tests/index-4632-s4-tool-call-verdict.test.ts` calls it instead of carrying its own copy (closes #5061, refs #5023 #4909).
165
+
166
+ </details>
167
+
19
168
  ## [4.4.7] - 2026-10-29
20
169
 
21
170
  ### Added
package/README.md CHANGED
@@ -4,6 +4,8 @@
4
4
 
5
5
  # pi-lens
6
6
 
7
+ [![omp status](https://omppackages.com/badge/pi-lens.svg)](https://omppackages.com/packages/pi-lens)
8
+
7
9
  pi-lens gives AI coding agents fast, language-aware feedback while they write/edit.
8
10
 
9
11
  > **Working in this project as an AI agent?** Read the [agent guide](docs/agent-guide.md)
@@ -530,9 +532,9 @@ Thanks goes to these wonderful people:
530
532
  <td align="center" valign="top" width="14.28%"><a href="https://github.com/Nyarlathoteppppp"><img src="https://avatars.githubusercontent.com/u/126082256?v=4" width="100px;" alt=""/><br /><sub><b>bowen xu</b></sub></a><br /><a href="#code-Nyarlathoteppppp" title="Code">💻</a> <a href="https://github.com/apmantza/pi-lens/commits?author=Nyarlathoteppppp" title="Tests">⚠️</a></td>
531
533
  </tr>
532
534
  <tr>
533
- <td align="center" valign="top" width="14.28%"><a href="https://github.com/dmae97"><img src="https://avatars.githubusercontent.com/u/146327957?v=4" width="100px;" alt=""/><br /><sub><b>dmae97</b></sub></a><br /><a href="#code-dmae97" title="Code">💻</a></td>
535
+ <td align="center" valign="top" width="14.28%"><a href="https://github.com/dmae97"><img src="https://avatars.githubusercontent.com/u/146327957?v=4" width="100px;" alt=""/><br /><sub><b>dmae97</b></sub></a><br /><a href="#code-dmae97" title="Code">💻</a> <a href="#bug-dmae97" title="Bug reports">🐛</a></td>
534
536
  <td align="center" valign="top" width="14.28%"><a href="https://github.com/Battlelamb"><img src="https://avatars.githubusercontent.com/u/12995996?v=4" width="100px;" alt=""/><br /><sub><b>Battlelamb</b></sub></a><br /><a href="#code-Battlelamb" title="Code">💻</a></td>
535
- <td align="center" valign="top" width="14.28%"><a href="http://wayneh.tw/"><img src="https://avatars.githubusercontent.com/u/5166321?v=4" width="100px;" alt=""/><br /><sub><b>WeiHung</b></sub></a><br /><a href="#code-wayne930242" title="Code">💻</a></td>
537
+ <td align="center" valign="top" width="14.28%"><a href="http://wayneh.tw/"><img src="https://avatars.githubusercontent.com/u/5166321?v=4" width="100px;" alt=""/><br /><sub><b>WeiHung</b></sub></a><br /><a href="#code-wayne930242" title="Code">💻</a> <a href="#ideas-wayne930242" title="Ideas & Planning">🤔</a></td>
536
538
  <td align="center" valign="top" width="14.28%"><a href="https://github.com/wertyMSD"><img src="https://avatars.githubusercontent.com/u/130595241?v=4" width="100px;" alt=""/><br /><sub><b>wertyMSD</b></sub></a><br /><a href="#bug-wertyMSD" title="Bug reports">🐛</a></td>
537
539
  <td align="center" valign="top" width="14.28%"><a href="https://github.com/rcdailey"><img src="https://avatars.githubusercontent.com/u/1768054?v=4" width="100px;" alt=""/><br /><sub><b>Robert Dailey</b></sub></a><br /><a href="#bug-rcdailey" title="Bug reports">🐛</a></td>
538
540
  <td align="center" valign="top" width="14.28%"><a href="https://twitter.com/letwir"><img src="https://avatars.githubusercontent.com/u/16576177?v=4" width="100px;" alt=""/><br /><sub><b>letwir</b></sub></a><br /><a href="#doc-letwir" title="Documentation">📖</a></td>
@@ -541,6 +543,14 @@ Thanks goes to these wonderful people:
541
543
  <tr>
542
544
  <td align="center" valign="top" width="14.28%"><a href="https://github.com/Silvio-Re"><img src="https://avatars.githubusercontent.com/u/5860449?v=4" width="100px;" alt=""/><br /><sub><b>Silvio</b></sub></a><br /><a href="#bug-Silvio-Re" title="Bug reports">🐛</a></td>
543
545
  <td align="center" valign="top" width="14.28%"><a href="https://github.com/forge18"><img src="https://avatars.githubusercontent.com/u/31629847?v=4" width="100px;" alt=""/><br /><sub><b>forge18</b></sub></a><br /><a href="#ideas-forge18" title="Ideas & Planning">🤔</a></td>
546
+ <td align="center" valign="top" width="14.28%"><a href="https://github.com/paymog"><img src="https://avatars.githubusercontent.com/u/1986950?v=4" width="100px;" alt=""/><br /><sub><b>Paymahn Moghadasian</b></sub></a><br /><a href="#doc-paymog" title="Documentation">📖</a></td>
547
+ <td align="center" valign="top" width="14.28%"><a href="https://github.com/vjda"><img src="https://avatars.githubusercontent.com/u/20127271?v=4" width="100px;" alt=""/><br /><sub><b>Victor J. Diaz Ayuste</b></sub></a><br /><a href="#ideas-vjda" title="Ideas & Planning">🤔</a></td>
548
+ <td align="center" valign="top" width="14.28%"><a href="https://github.com/GlitchOverride"><img src="https://avatars.githubusercontent.com/u/112761176?v=4" width="100px;" alt=""/><br /><sub><b>GlitchOverride</b></sub></a><br /><a href="#bug-GlitchOverride" title="Bug reports">🐛</a></td>
549
+ <td align="center" valign="top" width="14.28%"><a href="https://github.com/sbscan"><img src="https://avatars.githubusercontent.com/u/18386839?v=4" width="100px;" alt=""/><br /><sub><b>Can Gürcan</b></sub></a><br /><a href="#ideas-sbscan" title="Ideas & Planning">🤔</a></td>
550
+ <td align="center" valign="top" width="14.28%"><a href="https://github.com/zackchiutw"><img src="https://avatars.githubusercontent.com/u/107488700?v=4" width="100px;" alt=""/><br /><sub><b>Zachary Chiu</b></sub></a><br /><a href="#bug-zackchiutw" title="Bug reports">🐛</a></td>
551
+ </tr>
552
+ <tr>
553
+ <td align="center" valign="top" width="14.28%"><a href="https://github.com/yxlimo"><img src="https://avatars.githubusercontent.com/u/13878887?v=4" width="100px;" alt=""/><br /><sub><b>ShayLu</b></sub></a><br /><a href="#bug-yxlimo" title="Bug reports">🐛</a></td>
544
554
  </tr>
545
555
  </tbody>
546
556
  </table>
@@ -0,0 +1,36 @@
1
+ // Child entry for the markdownlint runner (#5119): runs markdownlint-cli2's
2
+ // exported `main` with `fix` forced off. cli2 has no CLI switch that turns a
3
+ // project's `"fix": true` off, and a directory config beats `--config`, so the
4
+ // runner spawns this file instead of the cli2 bin. It is a child so the
5
+ // 15 s spawn budget can kill it, so a rule's late throw cannot reach the host,
6
+ // and so an edited .cjs/.mjs config or custom rule is imported fresh.
7
+ //
8
+ // argv: <cli2 entry module> <directory> <cli2 argv...>
9
+ // Output and exit codes follow the cli2 bin: findings on stdout/stderr, exit
10
+ // 0/1 from `main`, exit 2 for anything that went wrong before or inside it.
11
+ import { pathToFileURL } from "node:url";
12
+
13
+ const [entry, directory, ...argv] = process.argv.slice(2);
14
+
15
+ function fail(thrown) {
16
+ process.stderr.write(
17
+ `${thrown instanceof Error ? (thrown.stack ?? thrown.message) : String(thrown)}\n`,
18
+ () => process.exit(2),
19
+ );
20
+ }
21
+
22
+ process.on("uncaughtException", fail);
23
+
24
+ try {
25
+ const { main } = await import(pathToFileURL(entry).href);
26
+ if (typeof main !== "function") fail(new Error(`${entry} exports no main`));
27
+ process.exitCode = await main({
28
+ directory,
29
+ argv,
30
+ optionsOverride: { fix: false },
31
+ logMessage: (message) => process.stdout.write(`${message}\n`),
32
+ logError: (message) => process.stderr.write(`${message}\n`),
33
+ });
34
+ } catch (thrown) {
35
+ fail(thrown);
36
+ }
@@ -1,13 +1,13 @@
1
1
  import { createRequire as __pilensCreateRequire } from "node:module"; const require = __pilensCreateRequire(import.meta.url);
2
2
  import {
3
3
  logExtension
4
- } from "./chunk-KXF5R4UN.js";
4
+ } from "./chunk-WQV6BI4Q.js";
5
5
  import {
6
6
  DEPRECATED_CONFIG_SURFACES
7
7
  } from "./chunk-S26LC76R.js";
8
8
  import {
9
9
  logLatency
10
- } from "./chunk-Z2XAOKHK.js";
10
+ } from "./chunk-565VRUP4.js";
11
11
  import {
12
12
  PROCESS_SINGLETON_RESET_KIND,
13
13
  getProbeHomeRedirectEvent,
@@ -18,11 +18,11 @@ import {
18
18
  getSinkWriteFailures,
19
19
  resetSinkRotations,
20
20
  resetSinkWriteFailures
21
- } from "./chunk-VSFLRN5Y.js";
21
+ } from "./chunk-VLQ7UKZH.js";
22
22
  import {
23
23
  getPathIdentityFallbacks,
24
24
  resetPathIdentityFallbacks
25
- } from "./chunk-PQJFG24Z.js";
25
+ } from "./chunk-GMROJJRN.js";
26
26
 
27
27
  // dist/clients/ledger-bounds.js
28
28
  var LEDGER_FIELD_MAX = 200;
@@ -632,7 +632,8 @@ var GLOBAL_NON_FLAG_CONFIG_SECTIONS = [
632
632
  "$schema"
633
633
  ];
634
634
  var GLOBAL_ONLY_NON_FLAG_KEYS = [
635
- "actionableWarnings.autoFix.maxFixes"
635
+ "actionableWarnings.autoFix.maxFixes",
636
+ "dispatch.runnerTimeoutFloorMs"
636
637
  ];
637
638
  var PROJECT_NON_FLAG_CONFIG_SECTIONS = [
638
639
  "ignore",
@@ -659,6 +660,7 @@ var PROJECT_NON_FLAG_CONFIG_SECTIONS = [
659
660
  var LSP_PROJECT_HONORED_KEYS = DEPRECATED_CONFIG_SURFACES.filter((row) => row.kind === "key").map((row) => row.surface);
660
661
  var PROJECT_FOREIGN_CONFIG_NAMESPACES = [
661
662
  "lsp",
663
+ "dispatch",
662
664
  // DERIVED, not restated: the four legacy root keys are exactly the
663
665
  // `kind: "key"` rows of the deprecation registry, and a hand-copied second
664
666
  // list of them would be a place for the accepted set and the removal
@@ -667,7 +669,10 @@ var PROJECT_FOREIGN_CONFIG_NAMESPACES = [
667
669
  ...LSP_PROJECT_HONORED_KEYS,
668
670
  "$schema"
669
671
  ];
670
- var PROJECT_FOREIGN_NAMESPACE_HONORED_KEYS = /* @__PURE__ */ new Map([["lsp", LSP_PROJECT_HONORED_KEYS]]);
672
+ var PROJECT_FOREIGN_NAMESPACE_HONORED_KEYS = /* @__PURE__ */ new Map([
673
+ ["lsp", LSP_PROJECT_HONORED_KEYS],
674
+ ["dispatch", ["disabledRunners"]]
675
+ ]);
671
676
  function flagConfigSectionKeys(flags) {
672
677
  return [...new Set(flags.map((spec) => spec.configKey.split(".")[0]))];
673
678
  }