@herbertgao/pi-extensions 2026.9.2 → 2026.9.4

package/node_modules/pi-lens/docs/pi-lens-fixer.md

@@ -23,3 +23,74 @@ redesigned before the fix is complete.
 Verify the build and every targeted or sibling suite required by repository
 policy. Follow the shared contract's Git authority. Report what ran, what was
 skipped, and why. Use active, plain prose.
+
+## Standard mechanics (apply unless the brief overrides)
+
+A fix on `clients/lsp/`, the read guard, tool registration, or session lifecycle adds or updates a real-harness scenario when the defect is only observable through the host; the scenario is the red-first proof where a unit seam cannot show it.
+
+- Every language pi-lens supports (`LANGUAGES` in `clients/language-registry.ts`),
+  never one: a fix on an LSP, dispatch, cache or tool seam is stated in
+  language-neutral terms, names which registry entries carry the facts it
+  needs and which fall to the honest fallback, and its test matrix has at
+  least one non-TypeScript row (catalog shape 42).
+- `npm run build` before any test run; rebuild between mutations. Tests run as
+  `PI_LENS_HOME=$PWD/.probe-home node_modules/.bin/vitest run <files> --configLoader runner`
+  (sweeps get `30_000`). A CI-only red is reproduced in the job's shape first
+  (`npm test` PATH prefix, pinned `HOME`, no `PI_LENS_HOME`).
+- When a task regenerates `package-lock.json`, use the exact npm version in
+  `package.json`'s `packageManager` field, which is also the CI production-install pin.
+- Required test set = the named files + every test that mocks (`vi.mock`) or
+  deep-equals a module or record you touched + `tests/config/` when you add a
+  real-spawn test or a fixture + the flake-shape ratchet when you touch waits.
+- Never `vi.waitFor` with real timers; never a `// flake-shape` admission for
+  a test you wrote; never `git stash`; never edit `CHANGELOG.md` (one fragment
+  under `.changelog/`, exactly one top-level entry).
+- Every test id, probe id or fixture name you write into a PR-body table
+  (state-space, writers-by-axis, population) must exist as a grep-able `it(`
+  title or file name in the tree at handoff. The orchestrator greps each id
+  before accepting the round; a table whose ids do not exist is a fabricated
+  claim and fails the round (2026-09-10: #2877 r3 and #2868 r3 each shipped a
+  48- to 72-cell table with zero real ids).
+- A claim about the HOST or the ENVIRONMENT is a transcript, not a sentence.
+  "pi does not re-run the factory on resume", "this failure is pre-existing on
+  master", "the harness cannot fire that event" — each carries the command and
+  output that measured it in the same environment (a probe extension against
+  real pi in rpc mode; the same test file run on origin/master in the same
+  tree). 2026-09-10: three rounds on #2866 and #2878 were built on unmeasured
+  host claims the verify overturned, and "pre-existing analyze-cli red" was
+  reported by four workers whose sandbox differed from CI and master.
+- When a fix is a RULE (a scanner's scope rule, a lifecycle rule, a
+  classification), derive it from the source of truth and enumerate from
+  there — the tree-sitter grammar table, pi's pinned event types measured
+  live, the client's real return sites — never from a hand-written list of
+  the cases the reviewer named. Seven rounds on #2877 each closed the named
+  launderer and left the next scope kind open until round 4 generated the
+  scope table from the grammar.
+- A change to a release-QA row (`docs/release-qa-baseline.md` +
+  `scripts/release-qa.mjs`) runs `node scripts/release-qa.mjs` end to end
+  once on the pushed head and quotes the verdict line in the body; the
+  row↔probe tie test cannot see a row that never passes (#2893).
+- Before handoff, run `npm run preflight` last and paste its table in
+  `PR_BODY.md` — a handoff without it is incomplete.
+- One set of template headings per PR. A fix round APPENDS `## Round N` and
+  edits the existing `## Observability` / `## Tests` sections in place; it
+  never adds a second `## Observability` (the lint reads the first one, and a
+  stale first section was the most common `PR body` red on 2026-09-10). Lint
+  the FULL body you will publish (`gh pr view <n> --json body -q .body` plus
+  your round), against the real `origin/master...HEAD` diff (fetch first),
+  not a hand-shaped diff.
+- `PR_BODY.md` passes `node scripts/check-pr-body.mjs --lint-local PR_BODY.md`
+  before handoff. The gate requires the headings `## Summary`, `## Tests`,
+  `## Blast radius`, `## Class sweep`, `## Observability`, and
+  `## Test assessment` whenever the diff touches `tests/`; Observability
+  names a record literal that appears in the runtime diff, and may say
+  exactly "No new failure path; no record added." only when the diff adds no
+  failure path (no new catch, fallback or degradation branch). Record: on
+  2026-09-10 most open PRs failed the PR-body check on one of these two rules.
+- No Git authority unless granted: leave changes uncommitted; hand off
+  `PR_BODY.md` (template headings, every red and mutation quoted in ≤5 lines)
+  plus two optional one-liners the reviewer reads first: `Operating rule:`
+  (the one sentence the change enforces) and `Kept:` (what was deliberately
+  not changed, so a reviewer does not re-litigate it);
+  and `COMMIT_MSG.txt` at the worktree root. Final message: verdict line, files
+  changed, test totals, what could not be verified.

package/node_modules/pi-lens/docs/pi-lens-investigator.md

@@ -1,5 +1,8 @@
 # Investigator contract
 
+Grep the `turnId` first when correlating rows across telemetry sinks.
+Premise-first reproductions of dogfood reports go through the harness with a fixture built from the reporter's shape, before any seam is named.
+
 Root-cause runtime behavior from reproducible and durable evidence.
 
 Define the symptom as a question that evidence can answer. Name the time window,
@@ -13,6 +16,18 @@ and against each hypothesis and the observation that would settle it. Sweep the
 tree for the root-cause pattern and every member of the affected population.
 State the blast radius and any missing or unbounded observability.
 
+For a reported defect, the first deliverable is the reporter's symptom
+reproduced through the production entry point (the tool handler or host
+command the reporter used), red on the current code; a seam named before
+that reproduction is a hypothesis and is labelled as one. Write the report
+to a file at the worktree root AND, when the delegation grants issue
+access, post it on the tracking issue: a file left in a worktree is not a
+durable deliverable until it is posted or committed.
+When the symptom involves a language server, runner or formatter, say which
+registry entries (`clients/language-registry.ts`) the diagnosis covers and
+whether the reporter's language is special or merely the one observed; the
+fix lane inherits that scope (catalog shape 42).
+
 Deliver a proven diagnosis and a concrete next step. If the task expands to an
 implementation, stop and return it to the orchestrator for a fixer delegation.
 Use concise, active, plain prose.

package/node_modules/pi-lens/docs/pi-lens-monitor.md

@@ -0,0 +1,88 @@
+# pi-lens monitor — role contract
+
+Read a LIVE pi-lens session's logs and report what the numbers say, so the
+maintainer does not have to. The monitor observes; it never edits code,
+never restarts anything, and never touches the session it is reading.
+
+Read first: `AGENTS.md` (the "Recurring defect shapes" catalog, especially
+shape 41: a fixed bound reached at p50 is a design defect), then
+`docs/pi-lens-investigator.md` for the forensics conventions this role
+inherits. This contract adds the standing readout.
+
+## Inputs
+
+- `~/.pi-lens/latency.log` and `~/.pi-lens/extension.log` (JSON lines; every
+  row carries `pid` and `ts`). The session is the `pid` the brief names, or the
+  newest pid with rows in the last hour when the brief says "live".
+- The previous readout for the same project when one exists (an issue comment
+  the brief links, or a file under the scratch directory). Every number is
+  reported as a delta against it when available.
+
+## The readout (fixed shape, one comment or file, never stdout to the session)
+
+1. **Session line**: pid, project root, first/last row timestamps, row count,
+   pi-lens version if a session-start row carries it.
+2. **Phase table**: for every `type:"phase"` value, `n | p50 | p95 | max |
+   total_ms`, sorted by total, top 15. Durations in ms, from `durationMs`.
+3. **Bounds reached at p50** (shape 41): every phase whose p50 is within 10%
+   of a declared budget or timeout in its metadata (`budgetMs`, `timeoutMs`,
+   `elapsedMs` ≈ budget). Name the constant when it is known
+   (`PI_LENS_AUX_GRACE_MS`, `TOUCH_DEBOUNCE_MS`, drift batch) and the awaited
+   path it sits on (tool_result, agent_end, background).
+4. **Per-server auxiliary outcomes**: from `lsp_aux_wait_outcome.metadata.outcomes[]`,
+   one row per `serverId | outcome | publishedThisContent`, with n and p50/p95
+   `elapsedMs` versus `budgetMs`.
+5. **Degradation and error lines**: counts by `kind` from the degradation
+   records and by `message` from `extension.log` at `level:"error"`; any
+   message that repeats per file or per occurrence is flagged as catalog
+   shape 10 with the emit site if it can be found by grep.
+   Also report `Situational dead weight` from the `tools` extension-log row,
+   including its bounded `metadata.tools` list; `[]` means every situational
+   tool was activated or called in the conversation. A shutdown with
+   `targetSessionFile` emits the ending conversation's row before a new set
+   opens for new, resume, or fork. Reload re-runs the extension factory but
+   keeps the same session file, so it preserves one conversation row. Caveat: resuming into the session you are already in still carries `targetSessionFile`, so one conversation is split into two rows and a tool activated before the resume is listed as dead weight in the second (pi exposes no current-session-file accessor; not fixed). A process restart (`pi --continue`) recovers
+   nothing — the restore deactivates every situational tool — so the first row
+   after one legitimately lists all five, and shrinks only as the model
+   re-activates and uses them. MCP remains connection-scoped and owns the
+   terminal latch.
+6. **Backlogs**: `lsp_document_drift` rows by disposition, files affected,
+   `driftAgeMs` p50/p95/max; `agent_end_deferred_mutation_drain` durations and
+   coalesced path counts; `deferred_format_file` runs with `changed:true`
+   versus total.
+7. **Timeouts**: `lsp_diagnostics_timeout`, `lsp_nav_request_timeout`,
+   `lsp_client_wait_timeout` counts with `serverIds`/`source`.
+8. **Delta**: for each of the above, the change since the previous readout,
+   one line each, only where the number moved by more than 20% or a new
+   kind appeared.
+9. **Injected context**: report injected bytes per source per turn
+   (`sessionGuidance`, `turnFindings`, `testFindings`, `agentNudge`,
+   `turnEndAdvisory`, `other`) at p50/p95, plus the repeated-findings ratio
+   (`injectedFindingsRepeated` divided by injected finding observations).
+10. **Findings**: at most five, each with the number that proves it, the seam
+   (file:line when found), and one of: `already filed #N` (search open issues
+   first: `gh issue list --search "<phase or kind>"`), `new`, or
+   `expected` (with the rule that makes it expected). A finding without a
+   number is not a finding.
+
+## Rules
+
+- Premise first: before naming a constant or a seam, read the code that owns
+  it (`clients/lsp/index.ts`, `clients/pipeline.ts`, `clients/runtime-agent-end.ts`,
+  `clients/lsp/document-drift.ts`). The 2026-09-09 readout mis-named a
+  suppression window as a trailing debounce; the correction cost a round.
+- Bounded output: the readout is one comment or one file. Never one line per
+  row of the log. Quote at most three raw rows, each cut at 300 characters.
+- No repo edits, no Git commands, no restarts, no writes under `~/.pi-lens`.
+  Scratch files go under the working tree's `.probe-home/` or the scratch
+  directory the brief names.
+- File nothing yourself unless the brief grants `gh`; then one comment on the
+  issue the brief names, never a new issue: the orchestrator decides what
+  becomes a lane.
+- A worker that finds the logs empty or the pid absent reports exactly that
+  with the `ls -la` of the two files and stops.
+
+## Deliverable
+
+`MONITOR.md` at the worktree root with the readout, and when `gh` is granted,
+the same text as a comment on the issue the brief names (today: #2809).

package/node_modules/pi-lens/docs/pi-lens-reviewer.md

@@ -1,5 +1,7 @@
 # Reviewer contract
 
+Reviewers run the relevant scenario as a probe and may add a throwaway scenario directory to reproduce a finding through the real host; quote the RPC event or tool result.
+
 Adversarially verify a change before merge and report proven findings.
 
 Assume the implementation's claims are incomplete. Read the issue, full diff,
@@ -31,3 +33,36 @@ Check that each regression test reaches the real seam and observes an independen
 effect. Remove or mutate the claimed guard and require the test to fail for the
 intended reason. Flag tests that restate the implementation, assert setup data,
 or swap a real in-process store, sink, coordinator, or registry for a fake.
+
+## Language coverage is a standing attack
+
+For any diff on an LSP, dispatch, cache, runner or tool seam, ask whether the
+rule holds for every entry in `clients/language-registry.ts` or only for the
+language the fixer tested. A rule keyed on `.ts`/tsserver where rust-analyzer,
+pyright or gopls behave the same is a finding (catalog shape 42); probe it
+with one non-TypeScript fixture through the same seam and quote the result.
+
+## Finding shape and disposition
+
+Every finding is written in four moves, in this order: the smallest concrete
+instance (the probe command and its output, or the failing scenario) with the
+expected value beside it; one plain-language sentence saying what is wrong;
+the cause and its cost in prose; the remedy, with options labelled A/B when
+more than one is defensible. Symbols and `file:line` anchor the prose and
+never replace it. Severity is earned by the instance: a CRITICAL or HIGH
+without a reproduced failure scenario is a MEDIUM at most.
+
+The verdict line comes first. After the findings, two fixed sections:
+"Could not verify" (what was blocked and why, never implied green) and
+"Named output" (the structural insight the probes could not close). A Named
+output entry may carry an advisory strength — Strong, Worth exploring, or
+Speculative — judged by the deletion test alone (would removing the shared
+module concentrate complexity back into callers, or merely relocate it); it is
+a triage aid for the orchestrator, never a severity, and never substitutes for
+a reproduced instance on a finding. A verify
+round ends with a disposition table for the previous round's findings —
+`fixed | not fixed | new defect | withdrawn` per finding id — so the
+orchestrator reads outcomes, not prose. Safe deltas (a body sentence, a
+comment, a literal, a doc line) are reported as such and never counted as
+actionable rounds. Borrowed shape: p3bot/library `tasks/review/pre-commit`
+(finding IDs, per-item template, remediation summary), 2026-09-09.

package/node_modules/pi-lens/docs/pi-lens-subagent.md

@@ -16,7 +16,10 @@ and every member of any enumerable population. Record both sweeps.
 
 State the blast radius, including callers, durable shapes, strict parsers, and
 tool surfaces. Add bounded observability for every new failure path. Include the
-required changelog fragment for a code change. Report verification honestly.
+required changelog fragment for a code change: ONE file under `.changelog/`;
+never edit `CHANGELOG.md` itself (it is generated at release; two fixers
+hand-edited it on 2026-09-09 and the orchestrator had to revert both).
+Report verification honestly.
 Write active, direct prose with short sentences and consistent terms.
 
 ## Tautological tests considered harmful
@@ -26,6 +29,7 @@ or feed the expected answer in through setup. Keep the red-first failure tied to
 the defect, and mutate the guard or filter to prove the test can detect its loss.
 Mocks belong only at true process or host boundaries. When a test can use the
 real store, sink, coordinator, or registry, use it and assert the durable result.
+For a whole-module mock, prefer `vi.mock("./module.js", async (importOriginal) => ({ ...(await importOriginal()), override }))` so new exports pass through by default; annotate dynamic imports as `typeof import(spec)` when needed.
 
 Git authority is separate from the role. Commit, push, or open a PR only when
 the delegation explicitly grants that authority after worktree verification.
@@ -34,11 +38,15 @@ directory, leave every change uncommitted, and write two handoff files at the
 worktree root: `PR_BODY.md` (the full PR body, transcripts pasted) and
 `COMMIT_MSG.txt` (subject, body, issue ref, trailers). Name any path inside the
 worktree that must not be committed. The orchestrator commits from those files;
-they are never committed themselves. Never merge.
+they are never committed themselves. Never merge. Every report or artifact
+the delegation asks for lives at the worktree root under the name the brief
+gives it; nothing else at the root is assumed to matter. When the brief
+names findings by id, the handoff answers each id with one of
+`fixed | not fixed | withdrawn (why)` before any prose.
 
 A sandboxed worker may find the shared `.git` and the linked `node_modules`
-read-only and the network absent (the codex `workspace-write` sandbox does
-this; see plegma#311). Run Vitest as
+read-only and the network absent (a write-confined sandbox does this; the
+runner's own notes say which mode lifts it). Run Vitest as
 `node_modules/.bin/vitest run <files> --configLoader runner`, and if the
 tree-sitter grammar prefetch hangs offline, verify through direct probes of the
 built code and say so; the orchestrator re-runs the files outside the sandbox.

package/node_modules/pi-lens/docs/public-api-stability.md

@@ -107,6 +107,7 @@ this policy explicitly reserves the right to change.
 | `PILENS_CFG_0006` | A config key that would modify an object's prototype (`__proto__`, `constructor`, `prototype`) was refused. | Both halves of the config core, through the shared policy in `clients/config-core/safe-object.ts`. |
 | `PILENS_CFG_0007` | Further config notices were suppressed by a bound, and this one carries the count — the WHOLE count, including anything an earlier bound in the same pipeline dropped. Nothing about the config is wrong; the notice list was truncated. | `MigrationRecordCollector.finalize` (`clients/config-core/records.ts`) — the ONE producer, reached through `finalizeRecords` by every record list: the shared resolution, the global loader's unknown-key scan, the project loader's unknown-key scan, and its legacy-document enumeration. Rendered with neutral prose and recorded under the `config-notice-suppressed` degradation kind, never `config-ignored`. |
 | `PILENS_CFG_0008` | Resolving a config failed internally, so the WHOLE file was ignored and pi-lens ran on defaults. | The two guards under the pipeline: `resolveConfig` (`clients/config-core/resolve.ts`) and the global loader's post-parse catch (`clients/lens-config.ts`). Carries the error class only, never its message. |
+| `PILENS_CFG_0009` | A tool config key is unknown or names a required, non-disableable tool. | The shared model-facing tool registry (`clients/tool-config.ts`) and both pi/MCP registration surfaces. |
 
 A reserved code is registered and referenced by the deprecation registry, but
 nothing emits it today. That is deliberate: the number must be pinned before the

package/node_modules/pi-lens/docs/real-harness.md

@@ -0,0 +1,46 @@
+# Real pi harness
+
+The real-harness lane runs the built extension inside a real `pi --mode rpc`
+process. Use it when a host event, provider turn, or tool handler crosses a
+process boundary that an in-process test cannot observe.
+
+## Five-minute scenario recipe
+
+1. Add `tests/fixtures/real-harness/<name>/project/` and a `script.json`.
+2. Use `withRealPi({ fixture: "<name>", script: "script.json" }, ...)`.
+3. Call `awaitAssistantTurn()` after each prompt.
+4. Call `awaitToolResult("<tool>")` for every expected tool result.
+5. Add the test to `realHarnessInclude` and the real-process-spawn ratchet.
+
+Scripts contain turns. Each turn contains text or typed tool-call actions.
+Malformed scripts fail validation before the child starts.
+
+## Run one file
+
+Build first, then run one serialized file with the pinned probe home:
+
+`PI_LENS_HOME=$PWD/.probe-home npm run test:real-harness -- tests/real-harness/scenario-1.test.ts`
+
+The lane has a 60-second wall budget and one worker. Do not use it for tests
+that can assert the same behavior through an in-process seam.
+
+## Hermetic home contents
+
+The harness pins `HOME`, `PI_LENS_HOME`, and the provider observation log to a
+claimed scratch directory. It copies only the scenario project fixture. The
+scratch seam records an owner PID, sweeps dead entries when a run starts, and
+removes the project and home in `finally`. A killed run is therefore cleaned
+by the next run before it claims new directories.
+
+## Wall budget
+
+Real provider startup, RPC traffic, tool execution, and teardown share the
+60-second test budget. Keep assertions on events and durable sink rows. Avoid
+elapsed-time assertions inside scenarios; scheduler-sensitive timing belongs
+in the serialized wall-clock lane.
+
+## Live mode
+
+Live-provider mode remains a placeholder for #2826. The scripted provider is
+hermetic and is the only supported provider for this lane until that issue
+defines credentials, redaction, and replay rules.

package/node_modules/pi-lens/docs/release-qa-baseline.md

@@ -17,7 +17,9 @@ first six runs — which pinned the pi-lens home but passed no environment to
 `npm` at all — put 41 records into the maintainer's real
 `~/.pi-lens/install.log` (#2619 review F1). The pack runs in a
 `git archive HEAD` export, never the live checkout, because `npm pack` fires our
-own `prepack` (rewrites `package.json` + `package-lock.json`) and `prepare`
+own `prepack` (rewrites `package.json` + `package-lock.json`) and `prepare`.
+When regenerating the lockfile, use the exact npm version in `package.json`'s
+`packageManager` field (`npm@11.18.0`), matching the production-install CI job.
 (rebuilds `dist/`, downloads grammars, reinstalls git hooks).
 
 Why it exists: #2587. The four shipped skills were suspected of never
@@ -84,6 +86,7 @@ PR's packed tarball (#2700, the check #2587 was missing). `attw`
 | config-provenance | a project config is LOADED and its provenance is reportable | mcp-stdio | `tools/call` `pilens_effective_config` with the fixture file | result names the fixture's `.pi-lens.json` as a contributing document | tool result text | new — `tests/config/pi-lens-config-schema.test.ts` covers the schema, not the packaged load | — |
 | degradation-visible | a silently-ignored input is RECORDED as a degradation instead of vanishing | mcp-stdio | `tools/call` `pilens_health` with the fixture's project-tier `lsp.enabled` (a global-only setting) loaded | health text carries a `config-ignored` degradation line naming the fixture's `.pi-lens.json` | health tool result text | `clients/degradation-ledger.ts` is the reused machinery; no smoke asserts it end to end | #1605 lane 2 (availability-lifecycle): the degradation-recorded half; #1605 additionally asserts RECOVERY, which this row does not |
 | git-install-loads | a `git:` install of a pushed ref builds and loads in a real pi | git-install | `pi install git:github.com/apmantza/pi-lens@<ref>` then `get_commands` | at least 1 `lens-*` command and at least 4 skills | get_commands response JSON | `scripts/rpc-load-check.mjs` assertion, re-run against the git layout | — |
+| tool-smoke-install | every npm/pip entry in the installer registry resolves on a real install | npm-install | `node <export>/scripts/smoke-tools.mjs --install --install-registry --installer-root=<installed>/` (registry `<installed>/dist/clients/installer/index.js`; about 1m 29s cold on this box for 33 entries; harness from export root) | the report shows every npm/pip entry resolved or a named legitimate skip (toolchain absent, declined), and no genuine install failure; a registry-unreachable classification leaves the lane UNMEASURED; requires network access to the npm and pip registries | install-registry JSON report | `classifyInstallOutcome` from the #2661 fixture lanes — this lane sweeps the whole npm/pip registry, where fixture lanes exercise only the entries their fixtures name | — |
 
 ## Why `skills-registered` pins the registrar
 
@@ -150,6 +153,7 @@ Ship line, from the outcomes:
 | pi did not boot with NO candidate installed | BLOCKED — no verdict | 3 | 0 |
 | pi booted, the candidate would not install or activate | do not ship, cause named on the verdict | 1 | 0 |
 | any row FAILED | do not ship | 1 | N |
+| any row classified registry-unreachable (its lane UNMEASURED) | INCONCLUSIVE — no verdict, the skips are not green | 3 | N |
 | pi booted but zero rows PASSED | INCONCLUSIVE — no verdict | 3 | N |
 | any UNTESTED or SKIPPED, at least one PASS | ship with caveats, each named | 2 | N |
 | all PASS | ship | 0 | N |

package/node_modules/pi-lens/docs/servercapabilities.md

@@ -6,7 +6,7 @@ server's `initialize` handshake. Generated by `node scripts/server-capabilities.
 absent on the generating host are listed under *Unavailable* — run in a
 provisioned environment (the nightly) to capture those rows.
 
-_Last generated: 2026-09-08 on linux; 30 servers captured, 18 unavailable._
+_Last generated: 2026-09-09 on linux; 31 servers captured, 13 unavailable._
 
 ## Diagnostic mode + navigation/edit operations
 
@@ -109,7 +109,6 @@ Toolchain/binary not installed here, so capabilities weren't captured
 (many are the toolchain-gated family tracked in #241):
 
 - @prisma/language-server
-- @vue/language-server
 - PowerShell Editor Services (pwsh Start-EditorServices.ps1 -Stdio)
 - clangd
 - cmake-language-server
@@ -122,7 +121,3 @@ Toolchain/binary not installed here, so capabilities weren't captured
 - ocamllsp
 - rust-analyzer
 - sourcekit-lsp
-- typescript native (clean file)
-- typescript native (tsc --lsp --stdio, TS7+)
-- typescript-language-server
-- typescript-language-server (clean file)

package/node_modules/pi-lens/docs/settings.md

@@ -9,6 +9,19 @@ flags in context, see [Usage](./usage.md).
 pi-lens ships with sensible defaults, so **zero configuration is needed** — it
 works out of the box. Everything below is optional tuning.
 
+Tool root resolution is recorded in the pi-lens extension log as one bounded
+line per session key: `cwd <kind> <tool> cwd=<path>
+reason=<dispatch-root|marker:<name>|git-root|file-dir-fallback|home-cap>`.
+Fallbacks also create one `tool-cwd-resolution` degradation record per tool and
+session, so repeated files do not create unbounded health or log rows.
+
+Complete MCP tool results use `COMPLETE_MCP_RESULT_INPUT_BUDGET_BYTES` (8 MiB) as
+their input budget. Results above this budget
+write a bounded head, an `[incomplete: N bytes omitted, budget M]` marker, and a
+tail to the session log, and record one `mcp-complete-result-budget-exceeded`
+degradation per session. Results at or below the budget keep the complete-log
+contract.
+
 ## The three ways to configure pi-lens
 
 1. **Environment variables** (`PI_LENS_*`) — read at process start; set them in
@@ -60,7 +73,7 @@ column is the effective behavior when nothing is set.
 | `--no-tests` | `tests.enabled` | global | test runner **on** |
 | `--no-delta` | `delta.enabled` | global | delta mode **on** (new diagnostics only) |
 | `--lens-guard` | `guard.enabled` | global | **off** |
-
+| `--lens-checkout-guard` | `guard.sharedCheckout` | global | **off** |
 | `--no-opengrep` | `opengrep.enabled` | global | Opengrep scanner **on** |
 | `--no-read-guard` | `readGuard.enabled` | global | read-before-edit monitor **on** |
 | `--no-lens-context` | `contextInjection.enabled` | global | context injection **on** |
@@ -70,14 +83,36 @@ column is the effective behavior when nothing is set.
 | `--lens-actionable-warning-autofix` | `actionableWarnings.autoFix.enabled` | project | **off** |
 | `--lens-actionable-warning-all` | `actionableWarnings.deltaOnly` (`false`) | global | `deltaOnly` **on** (report this turn only) |
 | `--lens-compact-tool-line` | `ui.compactToolLine` | global | **off** (two-row tool rendering) |
-| `--no-lazy-tools` | `tools.lazy` | global | lazy tools **on** (six situational tools start inactive) |
+| `--no-lazy-tools` | `tools.lazy` | global | lazy tools **on** (five situational tools start inactive) |
+| `--no-tool=<name>` | `tools.<name>.enabled` | project | every lens tool **on** |
 | `--lens-turn-end-madge` | `turnEnd.madge.enabled` | global | **off** (madge runs at session start, not per turn) |
+| `--no-knip` | `knip.enabled` | project | knip analyzer **on** |
+| `--no-jscpd` | `jscpd.enabled` | project | jscpd analyzer **on** |
+| `--no-madge` | `madge.enabled` | project | madge analyzer **on** |
+| `--no-gitleaks` | `gitleaks.enabled` | project | gitleaks analyzer **on** |
+| `--no-govulncheck` | `govulncheck.enabled` | project | govulncheck analyzer **on** |
+| `--no-dead-code` | `deadCode.enabled` | project | dead-code analyzer **on** |
+| `--no-complexity` | `complexity.enabled` | project | complexity analyzer **on** |
 
 `--no-lazy-tools` keeps every pi-lens tool active for the whole session, so the
 advertised tool list never changes. The `pi_lens_activate_tools` loader stays
 registered and keeps its usual description; under this flag the tools it names
 are already active, so calling it is a no-op.
 
+The `tools.<name>.enabled` population covers every model-facing pi and MCP
+tool. The loader `pi_lens_activate_tools` and MCP lifecycle tools
+`pilens_session_start`, `pilens_turn_end`, and `pilens_session_end` are
+required by their host protocols and cannot be disabled. Unknown or
+non-disableable names emit `PILENS_CFG_0009`.
+
+Valid names for `tools.<name>.enabled` include `ast_grep_search`,
+`ast_grep_replace`, `ast_grep_outline`, `lsp_navigation`,
+`lens_diagnostics`, `lens_diagnostic_mark`, `symbol_search`,
+`module_report`, `project_report`, `read_symbol`, `read_enclosing`,
+`effective_config`, `analyze`, `health`, `latency`, `project_scan`, and
+`rebuild`. The activation loader and MCP lifecycle tools `session_start`,
+`turn_end`, and `session_end` cannot be disabled.
+
 `--lens-guard` is **EXPERIMENTAL and strictly opt-in**. When enabled, actual
 `git commit`/`git push` commands are blocked only for current, structured
 blocking findings (including blocking test failures); advisory/no-action-required

package/node_modules/pi-lens/docs/tools_improvement2.md

@@ -276,7 +276,7 @@ These categories are language-agnostic at the tool UX level even if implementati
 - Keep `items: "exports"` prominent in the docs; it is much more usable than `items: "all"` on configuration-heavy modules.
 - Include a clear `syntaxOnly: true` and “does not satisfy read guard” note in the main text, not only details.
 
-## `ast_grep_dump` / `ast_dump`
+## `ast_grep_search` dump mode
 
 ### What works well
 
@@ -322,12 +322,12 @@ These categories are language-agnostic at the tool UX level even if implementati
 - For `codeAction`, include whether diagnostics were present at the requested range; an empty result is more useful if it says “no diagnostic at range” vs “server has no quickfix.”
 - For rename previews, the current summary is useful; consider adding a `filesTouched` / `editsCount` top-level summary for easier scanning.
 
-## `lsp_diagnostics` and `lens_diagnostics`
+## `lens_diagnostics` (`source=session` / `source=lsp`)
 
 ### What works well
 
-- `lsp_diagnostics` is good for file-scoped type/error checks before builds.
-- `lens_diagnostics` is valuable because it includes non-LSP runners.
+- `source=lsp` is good for file-scoped type/error checks before builds.
+- `source=session` is valuable because it includes non-LSP runners.
 
 ### Proposed improvements
 

package/node_modules/pi-lens/docs/tree-sitter_rules_catalog.md

@@ -218,7 +218,7 @@ Rule source: `rules/tree-sitter-queries/<language>/`.
 | `no-eval` | error | security | eval() detected — security risk, never use eval |
 | `no-jump-in-finally` | warning | bug | return/break/continue/throw in finally overrides the try/catch result and silently swallows exceptions |
 | `self-assignment` | error | reliability | '{{VAR}}' is assigned to itself |
-| `sql-injection` | error | security | SQL injection risk — use parameterized queries, never interpolate into SQL |
+| `sql-injection` | warning | security | SQL injection risk — use parameterized queries, never interpolate into SQL |
 | `switch-case-termination` | error | reliability | Switch case should end with break, return, throw, or continue |
 | `switch-non-case-labels-ts` | error | reliability | switch statements should not contain non-case labels |
 | `ts-command-injection` | error | security | Potential command injection sink — avoid child_process command execution with untrusted input |

package/node_modules/pi-lens/docs/usage.md

@@ -50,9 +50,11 @@ for the consumer-facing version of this routing.
 
 pi-lens exposes these high-value tools to agents:
 
-- `lens_diagnostics` — cached diagnostic state; use `mode=all` before declaring
-  work complete, and `mode=full` for an expensive project-wide LSP scan.
-- `lsp_navigation` / `lsp_diagnostics` — IDE-style navigation and diagnostics.
+- `lens_diagnostics` — `source=session` (default) reports cached findings; an
+  empty cache is not proof of a clean file. If changed files have no cached
+  diagnostics or stale findings, use `source=lsp scope=paths` for targeted
+  active verification (or `scope=workspace` to sweep a whole directory/project).
+- `lsp_navigation` — IDE-style code navigation (definition/references/etc.).
 - `ast_grep_search` / `ast_grep_replace` — AST-aware structural search/replace.
 - `module_report` / `read_symbol` — navigable outline and targeted symbol-body
   reads; prefer these before broad full-file reads.
@@ -105,12 +107,20 @@ pi --no-autofix          # Skip auto-fix (Biome, Ruff, ESLint, stylelint, sqlflu
 pi --no-tests            # Skip test runner
 pi --no-delta            # Disable delta mode (show all diagnostics, not just new ones)
 pi --lens-guard          # Block git commit/push when unresolved blockers exist (experimental)
+pi --lens-checkout-guard # Decline git commands that rewrite the working tree while another live pi-lens session shares this dirty checkout (experimental)
 pi --no-opengrep         # Disable the Opengrep security scanner (default-on auxiliary LSP)
 pi --no-read-guard       # Disable the read-before-edit behavior monitor
 pi --lens-turn-summary   # Persist a per-turn summary of diagnostics, autofixes, and autoformats
 pi --lens-compact-tool-line   # Render tool results as one compact, theme-aware line (closes #1327)
 pi --no-lazy-tools       # Keep every pi-lens tool active instead of activating the situational ones on demand
 pi --lens-turn-end-madge # Run the madge circular-dependency check at every turn end, not just at session start
+pi --no-knip             # Disable the knip session-start analyzer
+pi --no-jscpd            # Disable the jscpd session-start analyzer
+pi --no-madge            # Disable the madge session-start analyzer
+pi --no-gitleaks         # Disable the gitleaks session-start analyzer
+pi --no-govulncheck      # Disable the govulncheck session-start analyzer
+pi --no-dead-code        # Disable the dead-code session-start analyzer
+pi --no-complexity       # Disable the complexity session-start analyzer
 
 # Actionable warnings (all default off)
 pi --lens-actionable-warnings          # Report fixable warnings at turn end

package/node_modules/pi-lens/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "pi-lens",
-	"version": "4.1.5",
+	"version": "4.1.6",
 	"type": "module",
 	"description": "Real-time code feedback for pi — LSP, linters, formatters, type-checking, structural analysis & booboo",
 	"repository": {
@@ -33,10 +33,13 @@
 		"test:integration": "node scripts/with-test-lock.mjs -- vitest run tests/index-integration.test.ts tests/clients/lsp/integration.test.ts",
 		"test:targeted": "node scripts/with-test-lock.mjs --shared -- vitest run",
 		"test:watch": "vitest",
+		"test:real-harness": "node scripts/with-test-lock.mjs --shared -- vitest run",
+		"mutation:diff": "node scripts/stryker-diff.mjs --base origin/master --max-files 6",
 		"hygiene": "node scripts/prune-agent-worktrees.mjs",
 		"check": "node scripts/check-extensions.mjs",
 		"selftest:install": "node scripts/install-selftest.mjs",
 		"check:lockfile": "node scripts/check-lockfile-sync.mjs",
+		"preflight": "node scripts/pr-preflight.mjs",
 		"knip": "node scripts/run-knip.mjs",
 		"check:grammars": "node scripts/check-grammar-provenance.mjs",
 		"check:grammar-load": "node scripts/check-grammar-load.mjs",
@@ -49,7 +52,9 @@
 		"bench:cascade-budget": "node scripts/bench-cascade-budget.mjs",
 		"bench:word-index-replacement": "node scripts/bench-word-index-replacement.mjs",
 		"logs:smells": "node scripts/analyze-pi-lens-logs.mjs",
+		"complexity": "node scripts/complexity-report.mjs",
 		"changelog:check": "node scripts/rollup-changelog.mjs --check",
+		"test:regen": "node scripts/regen-test-baseline.mjs",
 		"changelog:release": "node scripts/changelog-release.mjs",
 		"changelog:extract": "node scripts/changelog-extract.mjs",
 		"release:backfill-notes": "node scripts/backfill-github-releases.mjs",
@@ -83,6 +88,7 @@
 	"engines": {
 		"node": ">=22.19.0"
 	},
+	"packageManager": "npm@11.18.0",
 	"files": [
 		"dist/",
 		"docs/",
@@ -145,5 +151,8 @@
 		"@ast-grep/cli@0.45.3": true,
 		"@google/genai@1.52.0": true,
 		"protobufjs@7.6.5": true
+	},
+	"overrides": {
+		"qs": "^6.15.4"
 	}
 }

package/node_modules/pi-lens/rules/tree-sitter-queries/typescript/sql-injection.yml

@@ -1,11 +1,15 @@
 # SQL Injection Detection
-# Detects unsafe interpolation in SQL-like template literals
+# Detects unsafe interpolation in SQL-like template literals.
+# Demoted from error/blocking to warning on 2026-09-10 (maintainer): the
+# query keys on the callee NAME only (query|execute|exec|run), so any
+# `run(`…${x}…`)` / `exec(`…`)` in non-SQL code fires — too many false
+# positives to block on. A real SQL sink needs a receiver/type signal.
 id: sql-injection
 name: SQL Injection Risk
-severity: error
+severity: warning
 category: security
 defect_class: injection
-inline_tier: blocking
+inline_tier: warning
 language: typescript
 
 message: "SQL injection risk — use parameterized queries, never interpolate into SQL"