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.
Files changed (148) hide show
  1. package/CHANGELOG-USER.md +12 -12
  2. package/CHANGELOG.md +253 -0
  3. package/README.md +11 -2
  4. package/config/dependency-cruiser-eager-allowlist.json +1 -0
  5. package/dist/{chunk-ZULZS2I6.js → chunk-2ERVW2UF.js} +1115 -423
  6. package/dist/{chunk-BBSDJTOV.js → chunk-2K7BUOKS.js} +13 -13
  7. package/dist/{chunk-I2FYOZNW.js → chunk-3JJ4OAJI.js} +10 -10
  8. package/dist/{chunk-5JB4WENL.js → chunk-3UHGSUVL.js} +1 -1
  9. package/dist/{chunk-W26QZ3OM.js → chunk-463WN3VP.js} +10 -10
  10. package/dist/{chunk-4IZZEN63.js → chunk-4X3ML2UQ.js} +31 -34
  11. package/dist/{chunk-I3NZVAMN.js → chunk-5BI5YP57.js} +10 -10
  12. package/dist/{chunk-7U36VQL6.js → chunk-5Z4XLUFF.js} +3 -3
  13. package/dist/{chunk-DCA2MXVQ.js → chunk-62AJH3IN.js} +51 -29
  14. package/dist/{chunk-37IDWT6O.js → chunk-6F34GMP7.js} +16 -14
  15. package/dist/{chunk-VSQT6IHZ.js → chunk-6LIUVGOR.js} +28 -4
  16. package/dist/{chunk-27JQHK7Y.js → chunk-6REF4GCO.js} +1 -1
  17. package/dist/{chunk-INBK3HIT.js → chunk-7KRR24GO.js} +3 -3
  18. package/dist/{chunk-OZQQ3AIR.js → chunk-7OMOMBEQ.js} +9 -9
  19. package/dist/{chunk-ARTYCUGF.js → chunk-7ZFXICNN.js} +123 -20
  20. package/dist/{chunk-K4Z7MK6T.js → chunk-ABKRQVOY.js} +28 -52
  21. package/dist/{chunk-C5PLBTNR.js → chunk-ANSLRJBG.js} +1 -1
  22. package/dist/{chunk-HRLF35WL.js → chunk-AWMFBPGJ.js} +9 -9
  23. package/dist/{chunk-CXQYK4YT.js → chunk-BG7KHGNX.js} +2 -2
  24. package/dist/{chunk-ZI7YHV6I.js → chunk-BK2R2223.js} +10 -8
  25. package/dist/chunk-BXXC6KRR.js +107 -0
  26. package/dist/{chunk-QMWKSYWB.js → chunk-CKJS2AUI.js} +4 -4
  27. package/dist/{chunk-PPQHMSPH.js → chunk-COGU5KQJ.js} +15 -15
  28. package/dist/{chunk-NHA5K226.js → chunk-CQNXALZJ.js} +27 -6
  29. package/dist/{chunk-KZ732ZVW.js → chunk-CSZESDPP.js} +1 -1
  30. package/dist/chunk-CZ5TCJPB.js +98 -0
  31. package/dist/{chunk-LOEJFTF2.js → chunk-D2LFEA5U.js} +9 -2
  32. package/dist/chunk-D3KLF5CD.js +50 -0
  33. package/dist/{chunk-4DAHGU3V.js → chunk-ENJ2M76Y.js} +31 -29
  34. package/dist/{chunk-ZQSSO7LO.js → chunk-EQKF6BAK.js} +3 -3
  35. package/dist/{chunk-PFJLYRO3.js → chunk-F2SAP2FM.js} +40 -47
  36. package/dist/{chunk-ADYQRETD.js → chunk-F6QAJXQV.js} +2 -2
  37. package/dist/chunk-GR2QDWH5.js +25 -0
  38. package/dist/{chunk-LVLPA32Q.js → chunk-GVE5VZYQ.js} +48 -11
  39. package/dist/{chunk-AZG5UJYY.js → chunk-GWZZOJD2.js} +1 -1
  40. package/dist/chunk-GZS6VPIE.js +27 -0
  41. package/dist/chunk-H4B4SC7I.js +71 -0
  42. package/dist/{chunk-YCR6ZYTE.js → chunk-HA6TUJOE.js} +1 -1
  43. package/dist/{chunk-DI4AZZNY.js → chunk-HKPJTI47.js} +2 -2
  44. package/dist/{chunk-O6LCSHHI.js → chunk-HPKC55MA.js} +1 -1
  45. package/dist/{chunk-LQQNFCQJ.js → chunk-I65CQLCG.js} +1 -1
  46. package/dist/{chunk-P5MSLVUW.js → chunk-IDKLWVKY.js} +11 -11
  47. package/dist/chunk-IUM2Q7NF.js +25 -0
  48. package/dist/{chunk-L6BDRYUK.js → chunk-J24IS3KZ.js} +5 -5
  49. package/dist/{chunk-KNSOA43J.js → chunk-J2DAHH4T.js} +2 -2
  50. package/dist/{chunk-7ZVTFLCC.js → chunk-JBDZVOFL.js} +11 -11
  51. package/dist/{chunk-HIJ4CHFF.js → chunk-JC6NFC57.js} +3 -3
  52. package/dist/{chunk-K7O6AHSJ.js → chunk-JTHEUTW7.js} +11 -11
  53. package/dist/{chunk-KXGTLAUW.js → chunk-JWW3ODBN.js} +2 -2
  54. package/dist/{chunk-HIRBC72R.js → chunk-K3ZIYLHT.js} +4 -4
  55. package/dist/{chunk-6GLMMGCX.js → chunk-KDPZA2UE.js} +2 -3
  56. package/dist/{chunk-AXAR5ZW2.js → chunk-KMY2OU4T.js} +553 -434
  57. package/dist/{chunk-DFKOA74L.js → chunk-KQF7VT26.js} +10 -10
  58. package/dist/{chunk-S6MCMD27.js → chunk-KVGA7X76.js} +3 -3
  59. package/dist/{chunk-74AMPWNC.js → chunk-KW7O72AK.js} +2 -2
  60. package/dist/{chunk-UN72ZAJ5.js → chunk-LEQTVRSV.js} +9 -9
  61. package/dist/{chunk-B42AIWPJ.js → chunk-LKPSBM6S.js} +3 -3
  62. package/dist/{chunk-R4L7KZ7R.js → chunk-LKW2HFSZ.js} +9 -9
  63. package/dist/{chunk-3PO4YYOX.js → chunk-LURFD4HD.js} +4240 -3734
  64. package/dist/{chunk-PQXUZYTQ.js → chunk-M6ELTECW.js} +4 -4
  65. package/dist/{chunk-3QXFUP6T.js → chunk-MGVVYYKW.js} +12 -12
  66. package/dist/{chunk-CZJGAOKL.js → chunk-MQBKGRSB.js} +7 -7
  67. package/dist/{chunk-NNEQOC3U.js → chunk-MVG2ZEAO.js} +9 -7
  68. package/dist/{chunk-VWEBZ2JV.js → chunk-MY4XNNTX.js} +39 -41
  69. package/dist/{chunk-RIH3UBK4.js → chunk-N4AJVFRF.js} +11 -11
  70. package/dist/{chunk-TKOFTLGB.js → chunk-OFKKMXWM.js} +31 -36
  71. package/dist/{chunk-3PAS2ERX.js → chunk-OFZE4ANN.js} +8 -8
  72. package/dist/chunk-OLXBUTJR.js +61 -0
  73. package/dist/{chunk-6CFSDLHE.js → chunk-OZGEHOSG.js} +38 -17
  74. package/dist/{chunk-3TSMQZG6.js → chunk-PKGOROPQ.js} +40 -2
  75. package/dist/{chunk-OLWGYBYT.js → chunk-Q6D5QKRG.js} +17 -17
  76. package/dist/{chunk-QE7BJQ6K.js → chunk-QECLJFHI.js} +12 -17
  77. package/dist/{chunk-RJ3APNIP.js → chunk-QJA33VD5.js} +4 -4
  78. package/dist/{chunk-MOAVEPC4.js → chunk-R5XVJ6AN.js} +11 -11
  79. package/dist/{chunk-ZRQMENT4.js → chunk-REZL4OM4.js} +1 -1
  80. package/dist/{chunk-PKWEBMCA.js → chunk-RK5RBREN.js} +251 -201
  81. package/dist/chunk-RP5ZQTHO.js +86 -0
  82. package/dist/{chunk-J2ZB5MDS.js → chunk-RURPX2YV.js} +23 -23
  83. package/dist/chunk-TB5MGZLS.js +53 -0
  84. package/dist/chunk-TC63XRYP.js +27 -0
  85. package/dist/chunk-TJOYHAXJ.js +69 -0
  86. package/dist/{chunk-Q7J3JYJ2.js → chunk-TRXKDCBP.js} +13 -13
  87. package/dist/{chunk-6E5QLMWI.js → chunk-TTK37D7R.js} +22 -23
  88. package/dist/{chunk-XDNWR7SG.js → chunk-UH3QHLR5.js} +2 -2
  89. package/dist/{chunk-SCU62JLX.js → chunk-UNTJJ7GN.js} +7 -7
  90. package/dist/{chunk-O2MHF7QM.js → chunk-UPAFSETJ.js} +58 -63
  91. package/dist/{chunk-PQF6YGYB.js → chunk-UX75PTQW.js} +50 -31
  92. package/dist/{chunk-TWEOJE3D.js → chunk-V353PYMK.js} +1233 -576
  93. package/dist/{chunk-CQY2HEH7.js → chunk-V4TFQY5G.js} +2 -2
  94. package/dist/{chunk-B2OXE4AH.js → chunk-VC3W54G3.js} +446 -293
  95. package/dist/{chunk-JGUDT5KD.js → chunk-VSBCJVPC.js} +5 -5
  96. package/dist/{chunk-5HBQL7DH.js → chunk-WAQQGXVV.js} +3 -3
  97. package/dist/{chunk-7DPXUPRF.js → chunk-WLEVWR7Y.js} +2 -2
  98. package/dist/{chunk-QE5DJ7MX.js → chunk-WPMPVP5I.js} +4 -4
  99. package/dist/{chunk-KNJH6WJQ.js → chunk-WXNLFOC2.js} +7 -7
  100. package/dist/{chunk-XSC3BCN3.js → chunk-Y3ZNOZZS.js} +6 -6
  101. package/dist/{chunk-VGRGW4UL.js → chunk-YL6JQTWC.js} +29 -32
  102. package/dist/{chunk-7CLWC2UH.js → chunk-YVE5Q2UU.js} +86 -217
  103. package/dist/{chunk-LGH2HHZG.js → chunk-YZNARDMM.js} +42 -28
  104. package/dist/{chunk-NGNBJIUO.js → chunk-ZDWNFZJ2.js} +8 -8
  105. package/dist/{chunk-X33QECRJ.js → chunk-ZEUF7BIN.js} +2 -2
  106. package/dist/{chunk-2H5GHZKC.js → chunk-ZIF4WLWR.js} +45 -25
  107. package/dist/{chunk-WLD6BGON.js → chunk-ZSPVF7KI.js} +231 -24
  108. package/dist/{chunk-SDYLT45T.js → chunk-ZX6OKBVO.js} +2 -2
  109. package/dist/index.js +10566 -6819
  110. package/dist/mcp/analyze-cli.js +8 -8
  111. package/dist/mcp/cli.js +39 -41
  112. package/dist/mcp/server.js +1083 -685
  113. package/dist/mcp/worker.js +68 -59
  114. package/dist/probes/installer.js +21 -22
  115. package/docs/ci-bot-pr-checks.md +18 -9
  116. package/docs/ci.md +7 -0
  117. package/docs/configuration.md +24 -10
  118. package/docs/defect-shapes.md +61 -30
  119. package/docs/environment-variables.md +18 -9
  120. package/docs/globalconfig.md +17 -0
  121. package/docs/invariants/dispatch-runners.md +22 -0
  122. package/docs/invariants/lsp-trust-exec.md +33 -3
  123. package/docs/lsp-capability-matrix.md +23 -10
  124. package/docs/lsp-idle-eviction.md +7 -1
  125. package/docs/module-report-read-symbol.md +6 -2
  126. package/docs/pi-lens-merge-policy.md +3 -2
  127. package/docs/pi-lens-orchestration.md +2 -1
  128. package/docs/pi-lens-subagent.md +2 -1
  129. package/docs/release-qa-baseline.md +22 -17
  130. package/docs/servercapabilities.md +1 -1
  131. package/docs/settings.md +10 -2
  132. package/docs/tools.md +1 -1
  133. package/docs/usage.md +1 -0
  134. package/package.json +3 -3
  135. package/dist/chunk-2H7NFZ4Q.js +0 -25
  136. package/dist/chunk-5YJXF2IS.js +0 -56
  137. package/dist/chunk-7WKVCZI4.js +0 -69
  138. package/dist/chunk-BKWFDWYM.js +0 -46
  139. package/dist/chunk-G53LBDNU.js +0 -255
  140. package/dist/chunk-GCSDF5IE.js +0 -27
  141. package/dist/chunk-H5API74E.js +0 -67
  142. package/dist/chunk-HBX55MWO.js +0 -27
  143. package/dist/chunk-JOIKBUQN.js +0 -88
  144. package/dist/chunk-M2YMBT5G.js +0 -73
  145. package/dist/chunk-MJRGPEQ5.js +0 -25
  146. package/dist/chunk-QV3JPCMK.js +0 -17
  147. package/dist/chunk-TFKN5EIR.js +0 -27
  148. package/dist/chunk-UNP6Y4JV.js +0 -38
@@ -2,83 +2,83 @@
2
2
  import { createRequire as __pilensCreateRequire } from "node:module"; const require = __pilensCreateRequire(import.meta.url);
3
3
  import {
4
4
  analyzeFile
5
- } from "../chunk-ZULZS2I6.js";
6
- import "../chunk-G53LBDNU.js";
7
- import "../chunk-YCR6ZYTE.js";
8
- import "../chunk-HIJ4CHFF.js";
9
- import "../chunk-7DPXUPRF.js";
10
- import "../chunk-CZJGAOKL.js";
11
- import "../chunk-S6MCMD27.js";
12
- import "../chunk-ZI7YHV6I.js";
13
- import "../chunk-INBK3HIT.js";
14
- import "../chunk-SDYLT45T.js";
15
- import "../chunk-XDNWR7SG.js";
16
- import "../chunk-QMWKSYWB.js";
17
- import "../chunk-QE7BJQ6K.js";
18
- import "../chunk-PKWEBMCA.js";
19
- import "../chunk-HIRBC72R.js";
20
- import "../chunk-PQXUZYTQ.js";
21
- import "../chunk-C5PLBTNR.js";
22
- import "../chunk-KZ732ZVW.js";
23
- import "../chunk-4DAHGU3V.js";
5
+ } from "../chunk-2ERVW2UF.js";
6
+ import "../chunk-CZ5TCJPB.js";
7
+ import "../chunk-HA6TUJOE.js";
8
+ import "../chunk-JC6NFC57.js";
9
+ import "../chunk-WLEVWR7Y.js";
10
+ import "../chunk-MQBKGRSB.js";
11
+ import "../chunk-KVGA7X76.js";
12
+ import "../chunk-BK2R2223.js";
13
+ import "../chunk-7KRR24GO.js";
14
+ import "../chunk-ZX6OKBVO.js";
15
+ import "../chunk-UH3QHLR5.js";
16
+ import "../chunk-CKJS2AUI.js";
17
+ import "../chunk-QECLJFHI.js";
18
+ import "../chunk-RK5RBREN.js";
19
+ import "../chunk-K3ZIYLHT.js";
20
+ import "../chunk-M6ELTECW.js";
21
+ import "../chunk-ANSLRJBG.js";
22
+ import "../chunk-CSZESDPP.js";
23
+ import "../chunk-ENJ2M76Y.js";
24
24
  import "../chunk-3MED75HT.js";
25
25
  import "../chunk-PKLB2XJL.js";
26
- import "../chunk-TWEOJE3D.js";
27
- import "../chunk-VSQT6IHZ.js";
26
+ import "../chunk-V353PYMK.js";
27
+ import "../chunk-6LIUVGOR.js";
28
28
  import "../chunk-XIMYZ3JA.js";
29
- import "../chunk-AXAR5ZW2.js";
30
- import "../chunk-7WKVCZI4.js";
31
- import "../chunk-2H5GHZKC.js";
32
- import "../chunk-QV3JPCMK.js";
33
- import "../chunk-NNEQOC3U.js";
34
- import "../chunk-LQQNFCQJ.js";
29
+ import {
30
+ initLSPConfig
31
+ } from "../chunk-KMY2OU4T.js";
32
+ import "../chunk-ZIF4WLWR.js";
33
+ import "../chunk-I65CQLCG.js";
35
34
  import "../chunk-5W3R6LFT.js";
36
- import "../chunk-ARTYCUGF.js";
37
- import "../chunk-JGUDT5KD.js";
38
- import "../chunk-CXQYK4YT.js";
39
- import "../chunk-37IDWT6O.js";
35
+ import "../chunk-7ZFXICNN.js";
36
+ import "../chunk-VSBCJVPC.js";
37
+ import "../chunk-BG7KHGNX.js";
38
+ import "../chunk-6F34GMP7.js";
40
39
  import "../chunk-Z54ZSOBZ.js";
41
- import "../chunk-ZQSSO7LO.js";
40
+ import "../chunk-EQKF6BAK.js";
42
41
  import "../chunk-6HWVI6MI.js";
43
- import "../chunk-AZG5UJYY.js";
44
- import "../chunk-P5MSLVUW.js";
45
- import "../chunk-ADYQRETD.js";
46
- import "../chunk-DI4AZZNY.js";
47
- import "../chunk-3TSMQZG6.js";
42
+ import "../chunk-GWZZOJD2.js";
43
+ import "../chunk-MVG2ZEAO.js";
44
+ import "../chunk-IDKLWVKY.js";
45
+ import "../chunk-F6QAJXQV.js";
46
+ import "../chunk-HKPJTI47.js";
47
+ import "../chunk-PKGOROPQ.js";
48
48
  import "../chunk-2APSZHHI.js";
49
- import "../chunk-ZRQMENT4.js";
49
+ import "../chunk-REZL4OM4.js";
50
+ import "../chunk-CIA7X2PZ.js";
50
51
  import "../chunk-2BEMIWEW.js";
51
52
  import "../chunk-IJYGIDF4.js";
52
- import "../chunk-B2OXE4AH.js";
53
- import "../chunk-LVLPA32Q.js";
54
- import "../chunk-LGH2HHZG.js";
55
- import "../chunk-KXGTLAUW.js";
53
+ import "../chunk-VC3W54G3.js";
54
+ import "../chunk-GVE5VZYQ.js";
55
+ import "../chunk-YZNARDMM.js";
56
+ import "../chunk-JWW3ODBN.js";
57
+ import "../chunk-J2DAHH4T.js";
58
+ import "../chunk-KDPZA2UE.js";
59
+ import "../chunk-Y3ZNOZZS.js";
60
+ import "../chunk-6REF4GCO.js";
61
+ import "../chunk-LKW2HFSZ.js";
62
+ import "../chunk-KW7O72AK.js";
56
63
  import "../chunk-TQWRH25U.js";
57
64
  import "../chunk-UYXV5NIS.js";
58
- import "../chunk-KNSOA43J.js";
59
- import "../chunk-6GLMMGCX.js";
60
- import "../chunk-XSC3BCN3.js";
61
- import "../chunk-27JQHK7Y.js";
62
- import "../chunk-R4L7KZ7R.js";
63
- import "../chunk-74AMPWNC.js";
64
- import "../chunk-3PO4YYOX.js";
65
- import "../chunk-5JB4WENL.js";
65
+ import "../chunk-LURFD4HD.js";
66
+ import "../chunk-3UHGSUVL.js";
66
67
  import "../chunk-QYF5S6P6.js";
67
- import "../chunk-CQY2HEH7.js";
68
- import "../chunk-PQF6YGYB.js";
69
- import "../chunk-LOEJFTF2.js";
70
- import "../chunk-CIA7X2PZ.js";
68
+ import "../chunk-UX75PTQW.js";
69
+ import "../chunk-V4TFQY5G.js";
70
+ import "../chunk-D2LFEA5U.js";
71
71
  import {
72
72
  setProjectTrustState
73
- } from "../chunk-W26QZ3OM.js";
73
+ } from "../chunk-463WN3VP.js";
74
74
  import {
75
75
  logExtension
76
- } from "../chunk-NHA5K226.js";
76
+ } from "../chunk-CQNXALZJ.js";
77
77
  import "../chunk-S26LC76R.js";
78
- import "../chunk-7CLWC2UH.js";
78
+ import "../chunk-YVE5Q2UU.js";
79
79
  import "../chunk-LJDODBBZ.js";
80
- import "../chunk-O6LCSHHI.js";
81
- import "../chunk-WLD6BGON.js";
80
+ import "../chunk-HPKC55MA.js";
81
+ import "../chunk-ZSPVF7KI.js";
82
82
  import "../chunk-NXL4FFQQ.js";
83
83
 
84
84
  // dist/mcp/worker.js
@@ -110,6 +110,15 @@ async function main() {
110
110
  process.exit(2);
111
111
  }
112
112
  }
113
+ try {
114
+ await initLSPConfig(cwd);
115
+ } catch (err) {
116
+ logExtension({
117
+ subsystem: "lsp-config",
118
+ level: "warn",
119
+ message: `mcp-worker: initLSPConfig failed for ${cwd}: ${String(err)}`
120
+ });
121
+ }
113
122
  const result = await analyzeFile(file, cwd, { flags });
114
123
  process.stdout.write(JSON.stringify(result), () => process.exit(0));
115
124
  }
@@ -40,7 +40,7 @@ import {
40
40
  resetResolvedPathCache,
41
41
  resolveArchiveKind,
42
42
  resolveArchiveUrl,
43
- resolveDerivedHashiCorpReleaseAsset,
43
+ resolveDerivedReleaseAsset,
44
44
  resolveGitHubArchiveBinaryCandidates,
45
45
  resolveGitHubAsset,
46
46
  resolveGitHubAssetLauncher,
@@ -53,31 +53,30 @@ import {
53
53
  verifyNpmPackageEntry,
54
54
  verifyToolBinary,
55
55
  wasLastResolveTransient
56
- } from "../chunk-B2OXE4AH.js";
57
- import "../chunk-LVLPA32Q.js";
58
- import "../chunk-LGH2HHZG.js";
59
- import "../chunk-KXGTLAUW.js";
56
+ } from "../chunk-VC3W54G3.js";
57
+ import "../chunk-GVE5VZYQ.js";
58
+ import "../chunk-YZNARDMM.js";
59
+ import "../chunk-JWW3ODBN.js";
60
+ import "../chunk-J2DAHH4T.js";
61
+ import "../chunk-KDPZA2UE.js";
62
+ import "../chunk-Y3ZNOZZS.js";
63
+ import "../chunk-6REF4GCO.js";
64
+ import "../chunk-LKW2HFSZ.js";
65
+ import "../chunk-KW7O72AK.js";
60
66
  import "../chunk-TQWRH25U.js";
61
67
  import "../chunk-UYXV5NIS.js";
62
- import "../chunk-KNSOA43J.js";
63
- import "../chunk-6GLMMGCX.js";
64
- import "../chunk-XSC3BCN3.js";
65
- import "../chunk-27JQHK7Y.js";
66
- import "../chunk-R4L7KZ7R.js";
67
- import "../chunk-74AMPWNC.js";
68
- import "../chunk-3PO4YYOX.js";
69
- import "../chunk-5JB4WENL.js";
68
+ import "../chunk-LURFD4HD.js";
69
+ import "../chunk-3UHGSUVL.js";
70
70
  import "../chunk-QYF5S6P6.js";
71
- import "../chunk-CQY2HEH7.js";
72
- import "../chunk-PQF6YGYB.js";
73
- import "../chunk-LOEJFTF2.js";
74
- import "../chunk-CIA7X2PZ.js";
75
- import "../chunk-W26QZ3OM.js";
76
- import "../chunk-NHA5K226.js";
71
+ import "../chunk-UX75PTQW.js";
72
+ import "../chunk-V4TFQY5G.js";
73
+ import "../chunk-D2LFEA5U.js";
74
+ import "../chunk-463WN3VP.js";
75
+ import "../chunk-CQNXALZJ.js";
77
76
  import "../chunk-S26LC76R.js";
78
- import "../chunk-7CLWC2UH.js";
77
+ import "../chunk-YVE5Q2UU.js";
79
78
  import "../chunk-LJDODBBZ.js";
80
- import "../chunk-WLD6BGON.js";
79
+ import "../chunk-ZSPVF7KI.js";
81
80
  import "../chunk-NXL4FFQQ.js";
82
81
  export {
83
82
  GITHUB_TOOLS,
@@ -120,7 +119,7 @@ export {
120
119
  resetResolvedPathCache,
121
120
  resolveArchiveKind,
122
121
  resolveArchiveUrl,
123
- resolveDerivedHashiCorpReleaseAsset,
122
+ resolveDerivedReleaseAsset,
124
123
  resolveGitHubArchiveBinaryCandidates,
125
124
  resolveGitHubAsset,
126
125
  resolveGitHubAssetLauncher,
@@ -2,15 +2,19 @@
2
2
 
3
3
  A pull request that a workflow opens or updates with the repository
4
4
  `GITHUB_TOKEN` starts no `pull_request` run: GitHub does not let a token-pushed
5
- commit trigger other workflows. Every required check then stays absent and the
6
- PR is BLOCKED until a maintainer closes and reopens it. PR #4945 sat that way
7
- from 2026-10-28 (#5062; #4338 and #2801 before it).
5
+ commit trigger other workflows. Every required check then stays absent from the
6
+ PR and it is BLOCKED until a maintainer closes and reopens it. PR #4945 sat that
7
+ way from 2026-10-28 (#5062; #4338 and #2801 before it). The dispatch described
8
+ below does not change that: its rows land on the head commit, not in the PR's
9
+ `statusCheckRollup` that branch protection reads (#5623, #5629), so close and
10
+ reopen is the re-arm.
8
11
 
9
12
  ## The mechanism
10
13
 
11
14
  `workflow_dispatch` and `repository_dispatch` are the two events a
12
15
  `GITHUB_TOKEN` can start. The job that opens the PR dispatches every workflow
13
- that produces a required check on the branch it just pushed:
16
+ that produces a required check on the branch it just pushed. This tests the
17
+ branch head; it does not satisfy the PR's required checks (see below):
14
18
 
15
19
  ```
16
20
  gh workflow run ci.yml --ref <bot branch>
@@ -29,13 +33,18 @@ head, and post the required check names (`Lint & type-check`, `Unit tests`,
29
33
  `Hot-path latency (advisory)` (#4363) and always reports on the head. A manual
30
34
  run reads as `hotpath=true`, so it times the head against `HEAD^1`, the
31
35
  previous commit on the bot branch.
32
- Branch protection matches a required check by name and app, not by event, and
33
36
  `scripts/ci-verdict.mjs` gates a branch-protection name whatever event its run
34
- came from (#4090), so those rows count.
37
+ came from (#4090), and those rows land on the commit. They are not enough for a
38
+ PR. On #5623 (2026-11-15) the dispatch rows held every required name, green,
39
+ while the PR's `statusCheckRollup` listed only CodeRabbit and SonarCloud and the
40
+ merge stayed BLOCKED (#5629). A PR verdict is therefore green only when its
41
+ rollup also carries a concluded success for every required name. A PR with
42
+ dispatch rows alone reads pending, and the remedy is to close and reopen it so
43
+ its `pull_request` runs start.
35
44
 
36
- On a bot-opened PR the dispatch runs are the PR's whole CI, so `ci-verdict`
37
- also gates every non-`(advisory)` check from a `workflow_dispatch` run on its
38
- head, such as `actionlint & markdownlint` and `Production install build`, exactly
45
+ On a bot-opened PR the dispatch runs are the CI the PR has until its
46
+ `pull_request` runs start, so `ci-verdict` also gates every non-`(advisory)`
47
+ check from a `workflow_dispatch` run on its head, such as `actionlint & markdownlint` and `Production install build`, exactly
39
48
  as it gates a `pull_request` run. It reads the PR author (the `gh` `is_bot`
40
49
  flag, an `app/` or `[bot]` login; the REST user type `Bot`). #4090's advisory
41
50
  rule stays for dispatch runs on a human PR, for a bare-SHA target (no author to
package/docs/ci.md CHANGED
@@ -80,6 +80,13 @@ files unknown, with `node scripts/gen-test-shard-weights.mjs` from either the
80
80
  shards' uploaded `vitest-results.json` (`--run <dir>`) or the nightly journal
81
81
  (`--journal <file> [--days 5]`, no GitHub API: `git fetch <remote>
82
82
  data/test-history`, then `git show FETCH_HEAD:history/test-daily.ndjson`).
83
+ Prefer `--run` over the journal, on the newest 10 or more green master pushes.
84
+ The journal's five-day median held a regressed file (`tool-state-matrix`, 302 s
85
+ against 60 s once fixed) for days after its fix. With the previous weights,
86
+ shard max-minus-mean was 62 s p50 over 15 runs of 2026-11-13 (measured, #3801).
87
+ The refreshed weights model 16 s with no run noise. With run noise added, the
88
+ model gives about 32 s p50 and 68 s p90, so the #3801 bar of a gap under 30 s
89
+ is probably not met (modelled).
83
90
 
84
91
  ## Actions cache
85
92
 
@@ -380,7 +380,9 @@ does. A `select` that is not an array is ignored, and the farther list stands.
380
380
  `ignorePaths` entries follow the same gitignore rules as the `ignore` field. Each entry is
381
381
  relative to the directory of the file that declares it: a global entry, and an entry in the
382
382
  workspace root's own file, match against the workspace root, and an entry in `pkg/.pi-lens.json`
383
- matches under `pkg/`:
383
+ matches under `pkg/`. An entry in a file above the workspace root matches under that file's own
384
+ directory, so `/gen/**` in `repo/.pi-lens.json` skips `repo/gen` whether you start pi in `repo` or in
385
+ `repo/pkg` (#5738):
384
386
 
385
387
  ```jsonc
386
388
  // pkg/.pi-lens.json — carves out pkg/legacy/** except pkg/legacy/keep.ts; nothing at the root
@@ -434,12 +436,17 @@ these dates instantiate.
434
436
  A `.pi-lens.json` that mixes both spellings is fine while you migrate: the
435
437
  canonical key wins, and the keys you have not moved yet keep working.
436
438
 
437
- For project settings the same rule reaches across directories (#5291): a legacy
438
- `pi-lens.json` still supplies its values whole while it is the only config
439
- file in the chain from your working directory upward, and once a canonical
440
- `.pi-lens.json` sits anywhere in that chain the legacy file only produces its
441
- migration notices — its fields are not merged in, and the canonical files
442
- layer per field as above. Move the settings; the notices name the file.
439
+ For project settings the same rule reaches across directories (#5291, #5740): a
440
+ legacy `pi-lens.json` still supplies its values whole while it is the only config
441
+ file in the chain from your working directory up to the git root, and once a
442
+ canonical `.pi-lens.json` sits anywhere in that chain the legacy file only
443
+ produces its migration notices — its fields are not merged in, and the
444
+ canonical files layer per field as above. Every reader follows it: the project
445
+ settings, the rule policy (`rules`, `dispatch.disabledRunners`), the per-folder
446
+ `autofix` and `format` switches, the nested `ignore` lists and
447
+ `effective_config`. The one exception is the language-server section, which
448
+ keeps reading legacy `lsp` values until the deprecation window closes. Move the
449
+ settings; the notices name the file.
443
450
 
444
451
  Only keys pi-lens actually recognizes get "move it to …" advice. A key in a
445
452
  legacy file that is not a pi-lens setting at all — a typo, or a leftover from
@@ -493,9 +500,16 @@ dispatch. That is the answer to "why is this running" and to "why is this *not*
493
500
  running", without reading a log.
494
501
 
495
502
  Naming a file (the `path` argument) resolves the configuration **at that file's own directory**,
496
- which is where the runtime decides from — so a nested `repo/sub/.pi-lens.json`
497
- layer contributes to the answer, appears in the reported document list, and is
498
- named as the file behind any decision it made. The walk runs upward and is
503
+ which is where the runtime decides the language-server and rule-policy answers
504
+ from — so a nested `repo/sub/.pi-lens.json` layer contributes to those answers,
505
+ appears in the reported document list, and is named as the file behind any
506
+ decision it made. The `tools` list is the exception: the runtime registers tools
507
+ once per session, from the repository's own `.pi-lens.json` files at your `cwd`
508
+ and the global config, so that list does not change with `path` and does not
509
+ read a legacy file beside a canonical one or a nested package's file (#5739).
510
+ It reads a file above the git root only when the repository has no
511
+ `.pi-lens.json` of its own: the git-root limit applies to layered reads, not to
512
+ the single-file fallback described under the config tiers. The walk runs upward and is
499
513
  **confined to `cwd`**: a `path` that resolves outside `cwd` — including a
500
514
  sibling package in the same monorepo — is rejected rather than answered from
501
515
  its own unrelated tree, because the per-file answer is only ever correct when
@@ -60,23 +60,24 @@ fixes its members says so instead of quoting a before and after.
60
60
  or generated by pi-lens is an identity and is never re-resolved.
61
61
 
62
62
  64. **Named path vs written set:** a guard keyed on the path a tool NAMES must
63
- hold for every path the tool WRITES; enumerate the written set (a rename's
64
- importers, an `ast_grep_replace` folder or its project default, a
65
- server-initiated `workspace/applyEdit` with no call at all) and key the
66
- permission per call, never per path. The screen: for each writer, table
67
- named-at-call against actually-written, and ask which rule answers for a
68
- path in the second column only.
69
- A first credit from a bridge is range-scoped to the bytes it reports, and
70
- settled-sweep drift never creates authorship; screen the next positional
71
- edit both inside and outside the reported range. This is the
72
- bridge/LSP/native-edit rule only: recognized bash, pipeline sibling files,
73
- and agent_end are pinned whole-file exceptions.
63
+ hold for every path the tool WRITES, and its permission is per call, never
64
+ per path. The writer table (`clients/writers.ts`) states each route's
65
+ named set (`names`) against its written set (`writes`), and its census
66
+ (`tests/clients/writers-census-5551.test.ts`) reds a file-writing site no
67
+ row admits. Screen: which rule answers for a path in a route's `writes`
68
+ and not in its `names`? A first credit from a bridge is range-scoped to
69
+ the bytes it reports (screen the next edit inside and outside that
70
+ range), and settled-sweep drift never creates authorship; the table's
71
+ `authorship` column marks the whole-file exceptions (recognized bash,
72
+ pipeline sibling files, agent_end).
74
73
 
75
74
  65. **Unknown authorship range:** a producer that cannot recover a truthful
76
75
  range must carry UNKNOWN to `ReadGuard.creditAuthorship`; UNKNOWN
77
- creates no authorship. A scope after a credit is what the credit holds
78
- plus what it may keep, so no credit widens an empty or range scope past
79
- the lines it produced: not a drain, a bash write or a pipeline credit.
76
+ creates no authorship. The range each writer route can state is the
77
+ writer table's `authorship` column (`clients/writers.ts`). A scope after
78
+ a credit is what the credit holds plus what it may keep, so no credit
79
+ widens an empty or range scope past the lines it produced: not a drain,
80
+ a bash write or a pipeline credit.
80
81
  A native write's creation read vouches for the whole file instead.
81
82
  UNKNOWN keeps a scope only under the writer rule
82
83
  (`mayAdvanceAuthorship`) and while a read that names a tool call bounds
@@ -128,7 +129,8 @@ fixes its members says so instead of quoting a before and after.
128
129
  promotion of values served during cooldown.
129
130
 
130
131
  24. **Second writer without discriminator:** enumerate all writers and add a
131
- reason/kind field before composing branches.
132
+ reason/kind field before composing branches. For file writes the writer
133
+ table (`clients/writers.ts`) is that enumeration.
132
134
 
133
135
  28. **Cold-path work on warm path:** compute expensive record fields only inside
134
136
  the failure or timeout branch, and measure any hot-path cost.
@@ -351,7 +353,14 @@ file-scoped worklist and receives no project-wide scanner output.
351
353
  project-relative path, `./`-prefixed unless it starts with a letter, digit,
352
354
  `_` or `.`, because a bare `-D.ts` is an option and `--fix` then rewrites
353
355
  files nobody dispatched. The absolute dispatched path stays for attribution
354
- and for files outside that cwd.
356
+ and for files outside that cwd. Probe a new runner's argv before it lands.
357
+ Enforcer: none: a per-runner census of argv verdicts would be prose the
358
+ test cannot observe. Tools that absolutize their own
359
+ config glob or regex before matching (detekt `excludes`, phpstan
360
+ `excludePaths`, credo `files.excluded`) stay silent under a relative
361
+ argument too: no argv fix exists, so the verdict is `residual`. Most tools
362
+ never apply an ignore to an explicit file (mypy, shfmt, typos, swiftlint,
363
+ trivy, dart), so their verdict is `cleared`.
355
364
  Screen: does the runner hand the tool the absolute dispatched path while
356
365
  the tool matches its ignore globs against the argument string (probe the
357
366
  same file under `<root>/.claude/worktrees/<lane>` and a neutral ancestor,
@@ -503,18 +512,20 @@ file-scoped worklist and receives no project-wide scanner output.
503
512
  unbuilt script cannot import clients/string-utils.js).
504
513
 
505
514
  88. **Learned attribution keyed on a name alone:** tier 4 of
506
- `classifyMutatingTool` admits any tool name that was once seen with a disk
507
- change in its call window and a `path` field, then classifies every later
508
- call of that name as an edit. A tool that never wrote (one operation of a
509
- mixed tool, #4139) and a call whose work already ran (a provider's
510
- display-only replay, #5160) both reach it on name plus path alone. Tier 4 is
515
+ `classifyMutatingTool` learns a tool name from a disk change in its call
516
+ window plus a `path` field, then classifies every later call of that name
517
+ as an edit, so a tool that never wrote and a call whose work already ran
518
+ both reach it on name plus path alone. The writer table's `attribution`
519
+ column (`clients/writers.ts`) names how each route is attributed; its
520
+ `observed-window` rows are the ones tier 4 learns. Tier 4 is
511
521
  admit-by-default with enumerated exemptions (the registry names, the
512
- `cursor-replay-` id prefix); a third carve-out is the trigger to redesign it
513
- fail-closed, learning only when the call, not the window, owns the change.
514
- Screen: can a call whose work already ran, or a tool that never wrote, reach
515
- the learned lookup or the arm gate on name plus path alone? Census: not
516
- countable. Enforcer: none: judgment-only, the exempt population is whatever
517
- other providers replay or mix. Instances and dates: `HISTORY.md`.
522
+ `cursor-replay-` id prefix); a third carve-out is the trigger to redesign
523
+ it fail-closed, learning only when the call, not the window, owns the
524
+ change. Screen: can a call whose work already ran, or a tool that never
525
+ wrote, reach the learned lookup or the arm gate on name plus path alone?
526
+ Census: not countable. Enforcer: none: judgment-only, the exempt
527
+ population is whatever other providers replay or mix. Instances and
528
+ dates: `HISTORY.md`.
518
529
 
519
530
  91. **Failure kind checked after the generic error branch:** a timeout or abort
520
531
  result also carries `error`, so an `if (result.error)` placed
@@ -764,7 +775,11 @@ file-scoped worklist and receives no project-wide scanner output.
764
775
  count (a pure `for (N) await yield` flush), a wait spelled as recursion, a
765
776
  count written as iteration over a generated range
766
777
  (`for (const _ of Array.from({ length: N }))`), or a loop that compares a
767
- clock value for some other purpose.
778
+ clock value for some other purpose. The broader `awaited-loop-wait` rule,
779
+ which admits an awaited loop only on a real-clock deadline or a lone
780
+ `waitFor`, sees all of these but ships disabled
781
+ (`scripts/governance-rules/rules-disabled/`, #4865): at least 17 of its 669
782
+ members on the tree, among the members read, were real-I/O waits.
768
783
  Instances and dates: `HISTORY.md`.
769
784
 
770
785
  92. **Test double with a result shape the real producer never returns:** a
@@ -818,8 +833,24 @@ file-scoped worklist and receives no project-wide scanner output.
818
833
  25. **Module-scope uniqueness assumption:** process evaluation can create
819
834
  multiple copies; process-wide registries and latches use `getProcessSingleton`.
820
835
  Enforced by `tests/config/module-instance-coverage.test.ts` (partial: the
821
- test-side duplicate-instance half; module-level registries without
822
- `getProcessSingleton` are not censused).
836
+ test-side duplicate-instance half) and by
837
+ `tests/config/process-slot-sweep.test.ts` (every `globalThis`, `Symbol.for`,
838
+ `process` member write or `console` patch in `clients/`, `tools/`, `mcp/` and
839
+ `index.ts` outside the seam is a reasoned baseline row; shrink-only; partial:
840
+ a `process.env.<name>` write is admitted, and a module-level `let` latch
841
+ that guards a per-evaluation exit hook is not a slot). Census:
842
+ `PI_LENS_PRINT_PINS=1 npx vitest run tests/config/process-slot-sweep.test.ts`
843
+ prints one `ROW` per site (27 on master after the fold).
844
+ Consolidation verdict: folded onto `getProcessSingleton` for the four
845
+ hand-rolled slots that adopted any value under their key (spawn-timeout
846
+ cooldown, opaque baseline store, probe-home memo, safe-spawn lifetime
847
+ registry), which now share the seam's family version and its one bounded
848
+ reset record. The rest stay distributed, each with its reason in the sweep:
849
+ the cross-build bridges (the key is the API), the NDJSON logger (its own
850
+ legacy-adopting protocol), the background-write-drain registry (a test reset
851
+ must not drop a loaded copy's registration), class brands, platform reads and
852
+ console patches. The `__piLens*` flags in `handleSessionStart` are the one
853
+ live member left, sequenced behind the change that edits that file.
823
854
 
824
855
  30. **Load-time platform constant:** use a live platform read or an isolated
825
856
  fresh import for every platform branch test.
@@ -196,12 +196,11 @@ Set to `1` to skip auto-installing language servers. Off by default.
196
196
  ### `PI_LENS_DISABLE_TOOL_INSTALL`
197
197
 
198
198
  Set to `1` to skip auto-installing managed tools (formatters, linters,
199
- scanners). Off by default. It stops four things: the managed installer, the
200
- lazy installer (`gem install rubocop`, `rustup component add clippy|rustfmt`),
199
+ scanners). Off by default. It stops three things: the managed installer,
201
200
  govulncheck's `go install`, and any `npx` package-runner spawn, which runs
202
201
  offline (`npm_config_offline=true`): it uses npm's cache or fails, and never
203
- downloads. A refused lazy or govulncheck install records one `install-disabled`
204
- degradation row per tool per session. It does not cover `bunx` (which ignores
202
+ downloads. A refused govulncheck install records one `install-disabled`
203
+ degradation row per session. It does not cover `bunx` (which ignores
205
204
  that variable; pi-lens never spawns it) or language-server installs (see
206
205
  `PI_LENS_DISABLE_LSP_INSTALL`).
207
206
 
@@ -353,15 +352,25 @@ complete field definitions are in
353
352
 
354
353
  ### `PI_LENS_LSP_IDLE_EVICT_MS`
355
354
 
356
- Shared idle window (ms) after which every language-service client whose registry
357
- `idleEviction` is `transparent` releases its hydrated program and shuts down,
358
- rebuilding transparently on the next request. Servers declared `resident` or
359
- `unmeasured` are never evicted. Which servers are declared which way, and the
360
- nightly measurement behind each declaration, is in
355
+ Shared idle window (ms) after which every language-service client releases its
356
+ hydrated program and shuts down, rebuilding on the next request, on the pi host
357
+ and the MCP host alike. Only servers declared `resident` stay (#5700): today
358
+ the five project indexers held by #3952 (expert, kotlin, powershell, rust,
359
+ svelte). Which servers are declared which way, and the nightly measurement
360
+ behind each declaration, is in
361
361
  [`lsp-idle-eviction.md`](lsp-idle-eviction.md).
362
362
  When unset or invalid, `PI_LENS_TS_IDLE_EVICT_MS` (below) is read.
363
363
  **Default:** 20 minutes (`1200000`).
364
364
 
365
+ ### `PI_LENS_LSP_OPEN_DOCUMENT_CAP`
366
+
367
+ How many documents one language-server client keeps open (#5700). Past it the
368
+ client closes its least recently sent document with `didClose`, so the server
369
+ drops its text and syntax tree. The closed file's last findings stay readable,
370
+ marked `closed: true` in the `lsp_navigation` workspace snapshot, and the next
371
+ touch opens the file again.
372
+ **Default:** `256`.
373
+
365
374
  ### `PI_LENS_EPHEMERAL_LSP_IDLE_EVICT_MS`
366
375
 
367
376
  Idle window (ms) for language-service clients whose workspace is inside a
@@ -40,6 +40,7 @@ Each runtime toggle is settable from the CLI *and* from `config.json`. The two a
40
40
  | `--lens-compact-lsp-status` | `ui.compactLspStatus` | `false` |
41
41
  | `--lens-hide-lsp-status` | `ui.hideLspStatus` | `false` |
42
42
  | `--lens-compact-widget` | `ui.compactWidget` | `false` |
43
+ | `--lens-issues-status` | `ui.issuesStatus` | `false` |
43
44
  | `--no-lazy-tools` | `tools.lazy` | `true` |
44
45
  | `--lens-turn-end-madge` | `turnEnd.madge.enabled` | `false` |
45
46
  | `--lens-fallow` | `fallow.enabled` | `false` |
@@ -141,6 +142,22 @@ Hide the diagnostics widget by default, run formatting immediately after write/e
141
142
 
142
143
  `format.mode` can be `"deferred"` (default) or `"immediate"`. Set `format.enabled` to `false` to match `--no-autoformat`. `/lens-widget-toggle` still works as a session-only override.
143
144
 
145
+ ### Widget position and hiding
146
+
147
+ `widget.position` (default `"belowEditor"`) sets where the diagnostics widget draws relative to the input editor. Use `"aboveEditor"` or `"belowEditor"`.
148
+
149
+ `widget.hideWhenClean` (default `false`) hides the widget while the project is clean. The widget hides 5 seconds after it first shows `✓ clean`.
150
+
151
+ Clean means no error, warning, or unchecked file, at least one completed check, no analysis running, no suppressed findings, and no language server still starting.
152
+
153
+ The widget also stays hidden from session start until a first edit gives it something to show. A language server that is up, or a file no check can cover, does not draw a bare header.
154
+
155
+ The widget returns on any finding, unchecked file, or starting server. It also returns on an edit whose analysis is running, so each edit shows the widget briefly. This feedback is by design.
156
+
157
+ `/lens-widget-toggle` does not override the hide. A widget toggled visible can draw nothing while the project is clean. A resumed session whose restored state is clean shows `✓ clean` for 5 seconds, then hides.
158
+
159
+ Both keys are global-only. Neither has a CLI flag, and a project `.pi-lens.json` cannot set them. The delay is not configurable.
160
+
144
161
  `autofix.enabled` (default `true`) is the global-config counterpart to the project `.pi-lens.json` `autofix.enabled` below — set it to `false` to match `--no-autofix` for every project that doesn't set its own `autofix.enabled`. As with `format.enabled` and `actionableWarnings.autoFix.enabled`, a project's own `.pi-lens.json` value overrides this global default in either direction (see "Mutation controls" below).
145
162
 
146
163
  `contextInjection.enabled` (default `true`) controls whether pi-lens prepends automatic findings — session-start guidance, turn-end findings, and test findings — into the next model turn. Set it to `false` (or use `--no-lens-context` / `PI_LENS_NO_CONTEXT_INJECTION=1` / `/lens-context-toggle`) to keep tools, LSP, read-guard, and formatting running while avoiding the prompt-cache invalidation that injected messages cause in long, cache-sensitive sessions. Findings are still cached, so `lens_diagnostics` and `/lens-health` keep working.
@@ -80,6 +80,13 @@
80
80
  root), so the two never share an answer (#5410). A present tool that fails its
81
81
  version check and has no later rung is a failed formatter outcome carrying the
82
82
  probe's stderr, not "executable not found".
83
+ The clients ask the same ladder (`resolveToolCommandWithInstallFallback`,
84
+ `toolBinaryVerdict`) rather than build a checker: jscpd, madge, knip and the
85
+ security scanners' managed-binary lookup (#5410). Every client-owned lookup
86
+ helper, installer ask or version probe that stays is a row of
87
+ `CLIENT_LADDER_ADMISSIONS` in `tests/config/client-ladder-census.test.ts`
88
+ with its reason; a new one reds until it is folded or admitted there. A
89
+ probe made with `safeSpawn*` that never asks the installer is not seen.
83
90
  - Windows LSP startup exit-code-1 failures are repairable only when the shared
84
91
  command resolver finds no command or an npm shim target is absent; present
85
92
  binaries that exit 1 remain runtime failures (#4263, #1199). The launch and
@@ -161,6 +168,21 @@
161
168
  seeded (maintainer scope, 2026-10-15). Collect-later linters and the MCP
162
169
  route have no seed. Proven by
163
170
  `tests/index-4483-first-write-seed-witness.test.ts`.
171
+ - Every writer that names the files it will change takes the same seed before
172
+ it writes (#5553), through `captureWriterSeeds` in `clients/runtime-tool-call.ts`:
173
+ a bash command's written paths, an applied `ast_grep_replace`'s `paths`, an
174
+ applied LSP rename's file, an unclassified tool's one path while the
175
+ observational net still arms for it, and a tool learned from one observation.
176
+ These give the dispatch no edit span, so the two edit-gated lanes (ast-grep,
177
+ tree-sitter) read the whole file; their seed joins the linters'
178
+ (`PRE_EDIT_SEED_SPANLESS_RUNNER_IDS`, tied to the edit-scope census). Those
179
+ two lanes' entries classify only a dispatch that read the whole file: a
180
+ dispatch with an edit span (a host `edit`) reports the lines it touched, so it
181
+ neither classifies by them nor keeps them, and an identical blocker the edit
182
+ adds elsewhere blocks (`classifyPreExisting`, #5583 review F1). A
183
+ writer's written set wider than its named one (a rename's importers, a replace
184
+ over a folder, a rename_file's new path) is not seeded. Proven by
185
+ `tests/index-5553-writer-baselines.test.ts`.
164
186
  - `clients/dispatch/runners/runner-spawn-cwd-sweep.test.ts` is the population
165
187
  guard for child cwd derivation. Add a reasoned migration row instead of a
166
188
  pin-only update.