@herbertgao/pi-extensions 2026.10.0 → 2026.10.2

package/node_modules/pi-lens/dist/clients/finding-delivery-gate.js

@@ -1,494 +0,0 @@
-/**
- * Single documentation home for the finding-delivery gate stack (#1634).
- *
- * Every store that renders findings to the AGENT — the turn-end blocker/
- * advisory tiers, `lens_diagnostics` mode=full/all/delta, the widget/footer
- * tally, agent nudges, and the persisted project-diagnostics snapshot —
- * invented its own freshness and retirement rules across
- * #1461/#1561/#1622/#1631, so the stores drifted from each other and each new
- * store re-created the class. #1622/#1625/#1627/#1633 converged on two gates;
- * this module names them ONE time so every other file points here instead of
- * re-explaining the contract. `mode=delta` — the tool's DEFAULT mode — was
- * the review round's live catch: it re-served the actionable/quality-warnings
- * caches verbatim, unfixed by the earlier per-store passes because it sits
- * one layer up from any single scanner.
- *
- * ── Freshness (mtime vs scannedAt, onMissing policy) ──────────────────────
- * `gateFindingsByPathFreshness` (advisory-provenance.ts) partitions a cached
- * store's findings by what the cited path looks like NOW versus the scan
- * timestamp (`scannedAt`) the store was captured at:
- *   - missing  → `onMissing: "drop"` (default) removes the finding outright —
- *     right when the finding IS the file's content (a secret in a deleted
- *     file cannot be rotated). `onMissing: "demote"` keeps it — right when the
- *     cited path is only EVIDENCE for a finding pinned elsewhere (a
- *     govulncheck CVE is pinned by go.mod, not by the traced call site).
- *   - stale (mtime > scannedAt + MTIME_DRIFT_TOLERANCE_MS,
- *     `blocker-freshness.ts`) → DEMOTE, never drop. The finding survives,
- *     the now-untrustworthy line number does not.
- *   - live  → deliver unchanged, full authority.
- *   - unknown (unparseable/absent `scannedAt`, unreadable path) → fail OPEN,
- *     deliver unchanged. A missed demotion is noise; a wrong drop can hide a
- *     live credential or CVE.
- * The turn-end secrets (gitleaks/trivy-secrets) and govulncheck advisory both
- * route through this gate in `clients/runtime-turn.ts`, in ONE shared call
- * (#3264) whose arms the secrets LANE (`clients/turn-end/lanes/secrets.ts`,
- * #1892) renders. A lane declares its sources and never gates itself: the
- * pass, its stat budget and its bounded records are per DELIVERY, not per
- * lane.
- *
- * The SAME freshness family, one level up, covers cross-file drift: a cached
- * inline blocker is a verdict about its file *and everything that file
- * imports* — `clients/blocker-freshness.ts` (`sweepInlineBlockerFreshness`,
- * the widget-store counterpart `reconcileStaleWidgetDependencyBlockers`
- * paired with `reconcileStaleWidgetFiles`) stats the file and its forward
- * imports against the verdict's `recordedAtMs` baseline (#1631/#1633). A
- * drifted entry is demoted with the SAME `[stale — re-run to confirm]`
- * marker (`STALE_LINE_MARKER`, `clients/stale-marker.ts` — its own leaf
- * module so `widget-state.ts` can use it without a circular import back
- * through the turn orchestrator, #1631 review V2) and `isBlocking`
- * answers false for it — the one predicate both the footer tally and
- * `mode=all`'s blocking count consult, which is what keeps `mode=all` from
- * contradicting a same-minute `mode=full` sweep on the same paths (#1631
- * criterion 3 / #1634 criterion 4).
- *
- * Two INDEPENDENT gates share this `stale` field, distinguished by
- * `WidgetDiagnostic.staleReason`: `"dependency-drift"` (#1631, above) and
- * `"past-eof"` (#1641 — a cited line beyond the file's current on-disk length,
- * a stale in-memory LSP document diverged from disk). Each gate only HEALS
- * demotions it made itself (`staleReason` defaults to `"past-eof"` for
- * backward compatibility with pre-#1641 records) — composed, not merged into
- * one undifferentiated flag, so a fix for one hazard can never silently clear
- * the other's verdict.
- *
- * ── Dispositions (strict-only for blocking) ───────────────────────────────
- * `applyDispositions` (diagnostic-dispositions.ts) filters false-positive/
- * suppress/defer/flagged judgments the agent or user already recorded for a
- * finding. Anchoring is STRICT (line-content-hashed) only for false-positive
- * — a judgment about one exact piece of code that must NOT survive a rewrite
- * of that line — and WEAK (no line hash) for defer/flagged/suppress, which
- * are intent-level judgments that must survive incidental nearby edits.
- * `formatFullMode` (tools/lens-diagnostics.ts) applies this on every
- * mode=full pass; the per-edit dispatch path applies the identical filter
- * before writing into widget-state, so mode=all and the footer inherit
- * disposition state for any file that has gone through a live edit this
- * session WITHOUT re-computing it (kept cache-only and instant, #1634
- * criterion 5's documented exception — see "Explicit lag labels" below).
- *
- * ── Demotion rendering (#1419) ─────────────────────────────────────────────
- * A demoted finding is never silently dropped and never re-asserted at full
- * authority: it renders with `STALE_LINE_MARKER` (or the widget's `[stale]`
- * tag) in place of the coordinate the drift invalidated. This is the one
- * rendering convention every gated surface reuses — a store must not invent
- * its own "stale" wording.
- *
- * #1944 completes the rule: demotion must change the BODY, not only the
- * channel and the coordinate. A demoted body carries no STOP banner and no
- * "must be fixed" imperative, and a cited line the file no longer has renders
- * as `L<n> (line no longer exists)`. `clients/demoted-finding-render.ts`
- * (`degradeDemotedFindingBody`) is the one implementation for surfaces that
- * deliver a RENDERED BODY — the turn-end advisory tier. Per-row surfaces
- * (`clients/widget-state.ts`, `tools/lens-diagnostics.ts`) have no body to
- * degrade; they satisfy the same rule by dropping the authority marker
- * alongside the coordinate.
- *
- * ── Retirement (#1944, #1950, #2275) ──────────────────────────────────────
- * Demote-not-drop assumes the agent CAN re-run to confirm. Retirement is what
- * happens when re-serving a demotion forever stops being honest. Every kind
- * of retirement records itself in the degradation ledger under
- * `demoted-finding-retired`, whose subject keeps the store and the file
- * (`inline-blocker:` / `widget-blocker:`), so an empty section can only mean
- * "nothing to say". There are three, and they differ in WHY and in HOW MUCH
- * they remove:
- *
- * 1. Past-EOF, unrecoverable (#1944). The file shrank past the cited lines,
- *    so no re-run can ever speak to them. Delivered ONCE, degraded, then the
- *    record is DROPPED (`RuntimeCoordinator.retireDemotedPastEofBlocker`).
- *
- * 2. Dependency-drift, inline-blocker channel (#1950). The coordinates are
- *    still in bounds and a re-run COULD confirm them, so this is a delivery
- *    cap, not a verdict: after `DEPENDENCY_DRIFT_MAX_DELIVERIES` turn-end
- *    deliveries with no re-run the record is dropped from
- *    `_pendingInlineBlockers`, and the LAST delivery carries a note saying it
- *    will not be shown again and can still be confirmed
- *    (`formatDeliveryCapNote`). Counting is deferred until the turn's content
- *    is known not to be suppressed, so the count is deliveries the agent
- *    actually received (#1950 fix round F1).
- *
- * 3. Dependency-drift, widget footer (#2275). The same cap number over the
- *    widget store, which unlike the inline-blocker map backs MORE THAN ONE
- *    surface — `lens_diagnostics mode=all` and `lens_diagnostic_mark` read
- *    the same `allDiagnostics` list the footer draws from. So this retirement
- *    HIDES rather than drops: the entry keeps its demotion and its place in
- *    the error tally, gains `WidgetDiagnostic.footerRetired`, and only the
- *    footer stops rendering it; mode=all carries the "capped, no longer shown
- *    in the footer, re-run can still confirm" note in place of the inline
- *    channel's last-delivery note. Its count is RENDERS, not turn ends — the
- *    footer serves one record per pass, so `renderWidget` marks what it drew
- *    and the turn-end step drains those marks. Dropping the record instead
- *    would have made an unconfirmed LSP error read as CLEAN on mode=all.
- *
- * The rule the three share: a retirement may remove a finding from the
- * surface that has re-served it, never from every surface at once, unless no
- * re-run could ever confirm it (case 1).
- *
- * ── Explicit lag labels (the non-gated escape hatch) ──────────────────────
- * A store that cannot afford the freshness/disposition stack — because it
- * has no cited per-file path to stat (a package-pinned finding like a trivy
- * CRITICAL CVE or a license-risk row), or because re-computing dispositions
- * would cost the "instant" cache-only render mode=all/the footer promise —
- * MUST say so explicitly, with the finding's age, rather than presenting as
- * if it were current. `formatCacheAgeLabel` below is the one implementation;
- * every labeled surface in `DELIVERY_SURFACES` calls it instead of hand-
- * rolling an age string. This is the "(b)" arm of #1634's contract: every
- * agent-facing surface is EITHER gated OR explicitly labeled — never neither.
- */
-const MS_PER_MINUTE = 60_000;
-/** Mark retained findings whose replacement result could not be reconciled. */
-export function markUnreconciledFindings(findings) {
-    return findings.map((finding) => ({ ...finding, stale: true }));
-}
-/**
- * Render a short, honest age suffix for a store that cannot be freshness-
- * gated per-path (see module doc). `undefined`/unparseable `scannedAt`
- * degrades to a neutral "scan age unknown" label — fail open on WORDING the
- * same way the freshness gate fails open on VERDICT: an unlabeled finding is
- * worse than a vague one, but never fabricate a number from a bad timestamp.
- */
-export function formatCacheAgeLabel(scannedAt, nowMs = Date.now()) {
-    if (scannedAt === undefined || scannedAt === null || scannedAt === "") {
-        return "scan age unknown";
-    }
-    const scannedAtMs = typeof scannedAt === "number" ? scannedAt : Date.parse(scannedAt);
-    if (!Number.isFinite(scannedAtMs))
-        return "scan age unknown";
-    const ageMs = Math.max(0, nowMs - scannedAtMs);
-    const ageMinutes = Math.round(ageMs / MS_PER_MINUTE);
-    if (ageMinutes < 1)
-        return "scanned <1m ago";
-    if (ageMinutes < 60)
-        return `scanned ${ageMinutes}m ago`;
-    // Floor the hour, keep the remainder minutes explicit — a naive
-    // `Math.round(ageMinutes / 60)` reported "1h" at 89 minutes (F5), rounding
-    // a finding's age UP is the wrong direction to err for a staleness label.
-    const ageHours = Math.floor(ageMinutes / 60);
-    const remMinutes = ageMinutes % 60;
-    return remMinutes === 0
-        ? `scanned ${ageHours}h ago`
-        : `scanned ${ageHours}h ${remMinutes}m ago`;
-}
-/**
- * The enumeration (#1634 criterion 1): every surface that renders findings to
- * the agent. Two DIFFERENT seam shapes, each derived structurally rather than
- * hand-listed (#1634 review round F2):
- *
- *   - `clients/runtime-turn.ts`: every `blockerParts.push`/`advisoryParts.push`/
- *     `staleSecretParts.push` call site carries an `@delivery-surface: <id>`
- *     comment naming its entry here. `tests/clients/finding-delivery-gate.test.ts`
- *     scans the file for every such push call (comments/strings stripped, so a
- *     commented-out or string-embedded false match can't hide a REAL untagged
- *     seam) and fails if one has no tag, or a tag names an id not in this
- *     registry — a brand-new ungated `advisoryParts.push` cannot pass silently.
- *   - `tools/lens-diagnostics.ts`: each `mode=` report is its own function
- *     (`formatFullMode`/`formatAllMode`/`formatDeltaMode`), tagged the same way
- *     immediately above its `function` line.
- *   - `clients/widget-state.ts` (the footer) and `clients/agent-nudge.ts` are
- *     hand-registered below — one surface each, not a push-site pattern the
- *     scan can derive structurally, so a coverage test asserts these two
- *     files are not silently untouched by other tests in the same run.
- *
- * Single source of truth: adding a new render seam without adding/tagging an
- * entry here fails the coverage test, not a human re-reading a hand list.
- */
-/**
- * Factory for a `gated` entry. #1634 review round (SonarCloud): 20+ entries
- * written as multi-line object literals put the SAME `mode`/`file` key
- * sequence on the same relative lines over and over — the TS/JS duplication
- * detector normalizes string literals to a placeholder token, so those
- * literally-different-content blocks still read as duplicate TOKEN STREAMS.
- * Collapsing each entry to one factory call removes the repeating shape
- * instead of the (irreducible) per-entry data.
- */
-function gated(file, description, gates, evidence, extra = {}) {
-    return { mode: "gated", file, description, gates, evidence, ...extra };
-}
-/** Factory for a `labeled` entry — see {@link gated}'s doc for why this exists. */
-function labeled(file, description, reason, ageSource, evidence = [], extra = {}) {
-    return {
-        mode: "labeled",
-        file,
-        description,
-        reason,
-        ageSource,
-        evidence,
-        ...extra,
-    };
-}
-const RUNTIME_TURN_FILE = "clients/runtime-turn.ts";
-const LENS_DIAGNOSTICS_FILE = "tools/lens-diagnostics.ts";
-export const DELIVERY_SURFACES = {
-    // #1892 (lane extraction): both secrets tiers are rendered by the secrets
-    // LANE (`clients/turn-end/lanes/secrets.ts`), so `clients/runtime-turn.ts`
-    // no longer reads `.live`/`.stale` itself — the arm it can still be pinned
-    // to is the whole gated store object it hands the lane. That is WEAKER than
-    // the previous `gitleaksGate.live,` pin (it no longer says which partition
-    // feeds which tier) and the loss is deliberate: the live/stale split is a
-    // lane rule now, pinned behaviourally instead, by
-    // `tests/clients/runtime-turn-finding-freshness.test.ts` ("keeps an
-    // unmodified file's finding as a full-severity blocker" / "DEMOTES a
-    // finding whose file was edited after the scan — kept, no line") and the
-    // committed witness goldens under `tests/fixtures/witness/`. What the pin
-    // still proves is what this registry exists for: the rows the tier renders
-    // came out of a real `gateFindingsByPathFreshness` call and not out of a
-    // hand-built object (the R2 binding chain in
-    // `tests/clients/finding-delivery-gate.test.ts` walks
-    // `gitleaksGate` → `scannerGates` → the call).
-    "runtime-turn:secrets-gitleaks": gated(RUNTIME_TURN_FILE, "Turn-end 🔴 secrets blocker, gitleaks cache.", ["gateFindingsByPathFreshness"], ["gitleaksGate,"]),
-    "runtime-turn:secrets-trivy": gated(RUNTIME_TURN_FILE, "Turn-end 🔴 secrets blocker, trivy secrets cache.", ["gateFindingsByPathFreshness"], ["trivySecretsGate,"]),
-    "runtime-turn:govulncheck-advisory": gated(RUNTIME_TURN_FILE, "Turn-end 🛡️ Go CVE advisory (call-site line only).", ["gateFindingsByPathFreshness"], ["scannerGates.govulncheck"]),
-    // Two tagged seams (the stale and live render branches below the same
-    // `sweepInlineBlockerFreshness` call) legitimately share one evidence
-    // occurrence — evidenceMin: 2 tells the exclusive-assignment check both
-    // are expected claimants, not a rogue seam contesting the real one.
-    "runtime-turn:unresolved-inline-blocker": gated(RUNTIME_TURN_FILE, "Turn-end re-surfaced unresolved inline blockers.", ["sweepInlineBlockerFreshness"], 
-    // #1790: the call now passes `additionalEntries` (widget-store rows) as a
-    // third argument, so the literal is the call's opening rather than the
-    // whole single-line invocation.
-    ["sweepInlineBlockerFreshness(runtime, cwd, {"], { evidenceMin: 2 }),
-    // The same shared gate call and the same two stores as the live secrets
-    // tier — one lane renders both tiers, so this surface has no gate call and
-    // no arm read of its own; see the note above the live tier for what the pin
-    // does and does not prove.
-    "runtime-turn:stale-secrets-tier": gated(RUNTIME_TURN_FILE, "Turn-end 🔑 demoted-secrets tier (drifted since scan).", ["gateFindingsByPathFreshness"], ["gitleaksGate,", "trivySecretsGate,"]),
-    // The evidence below is the literal header FRAGMENT including the
-    // interpolation — proves the label is actually rendered, not merely
-    // computed and discarded (review round F1's "deleted the age
-    // interpolations" attack).
-    "runtime-turn:trivy-critical-blocker": labeled(RUNTIME_TURN_FILE, "Turn-end 🔴 CRITICAL dependency CVE blocker (trivy).", "Package-pinned finding with no cited file:line to stat — freshness has " +
-        "nothing to check drift against. The session_start cache can be " +
-        "arbitrarily old, so its age is stated instead. Also routes through " +
-        "`filterFindingsByDisposition` (#1625) first — a suppressed/false-" +
-        "positive finding never reaches this render, so the age label and the " +
-        "disposition filter compose rather than substitute for each other.", "TrivyResult.scannedAt", ["CRITICAL dependency CVEs (trivy, ${trivyAgeLabel}"]),
-    "runtime-turn:trivy-cve-advisory": labeled(RUNTIME_TURN_FILE, "Turn-end 🛡️ non-critical dependency CVE advisory (trivy).", "Same package-pinned shape and #1625 disposition composition as the " +
-        "CRITICAL blocker above.", "TrivyResult.scannedAt", ["Dependency CVEs (trivy, ${trivyAgeLabel}"]),
-    "runtime-turn:trivy-license-advisory": labeled(RUNTIME_TURN_FILE, "Turn-end 📜 dependency license-risk advisory (trivy).", "Same package-pinned shape as the CRITICAL blocker above.", "TrivyResult.scannedAt", ["Dependency license risk (trivy, ${trivyAgeLabel}"]),
-    "runtime-turn:dead-code-advisory": labeled(RUNTIME_TURN_FILE, "Turn-end dead-code delta advisory (knip/vulture/etc).", "The delta shown is computed from THIS turn's own analyze() call, " +
-        "diffed against the previous cache — never a replay of a stale cache.", "live"),
-    "runtime-turn:knip-blocker": labeled(RUNTIME_TURN_FILE, "Turn-end 🔴 Knip unresolved-imports/deps blocker.", "Same shape as the dead-code advisory: `await knipClient.analyze(cwd, " +
-        "...)` runs fresh THIS turn, diffed against the previous cache and " +
-        "filtered to files edited this turn — never a replay of a stale cache.", "live"),
-    "runtime-turn:knip-advisory": labeled(RUNTIME_TURN_FILE, "Turn-end ⚠️ Knip newly-unused-exports advisory.", "Same live-this-turn shape as the Knip blocker above.", "live"),
-    "runtime-turn:actionable-warnings-advisory": labeled(RUNTIME_TURN_FILE, "Turn-end actionable-warnings advisory (ast-grep etc).", "`peekActionableWarnings` reads `_actionableWarningsThisTurn` — recorded " +
-        "fresh from this turn's own dispatch, never a cross-turn cache.", "live"),
-    "runtime-turn:code-quality-warnings-advisory": labeled(RUNTIME_TURN_FILE, "Turn-end code-quality-warnings advisory.", "`peekCodeQualityWarnings` reads `_codeQualityWarningsThisTurn` — the " +
-        "same per-turn accumulator shape as actionable-warnings above.", "live"),
-    "runtime-turn:disposition-suppressed-notice": labeled(RUNTIME_TURN_FILE, "Turn-end running disposition-suppressed-count notice (#1616).", "A live running total accumulated from this turn's own gate/disposition " +
-        "calls above (`dispositionSuppressedTotal`) — telemetry ABOUT the other " +
-        "gated surfaces, not a cache of its own.", "live"),
-    // #2001/#2002 collect-later: findings an auxiliary LSP published AFTER its
-    // aux-grace window expired, probed from the client cache at the next
-    // turn_end. Gated on the mark timestamp: a cited file deleted or edited
-    // since the mark drops its findings (never delivered before, and the
-    // drifting edit already re-touched the file — a fresh pending pair
-    // supersedes this one), with both drop arms counted in the
-    // `late_auxiliary_findings` latency record rather than silenced.
-    //
-    // #3102: freshness is only half the gate. The survivors also take the shared
-    // `clients/dispatch/finding-policy.ts` stack (inline `pi-lens-ignore` →
-    // stored dispositions → `.pi-lens.json` rule policy) the per-edit dispatcher,
-    // `mode=full` and the `source=lsp` probe lane apply — without it a finding
-    // the agent marked `false-positive` re-reported on every drain. Per #3088
-    // round-2 F4, the evidence is the CALL TEXT of that filter, which exists
-    // nowhere else in this file: a bare `applyFindingPolicy` would also be
-    // satisfied by an import line or an unrelated caller.
-    "runtime-turn:late-auxiliary-findings": gated(RUNTIME_TURN_FILE, "Turn-end late-auxiliary LSP findings (collect-later probe of aux " +
-        "client caches whose grace window expired).", 
-    // #3248: the open-coded `applyFindingPolicy(...)` here and the identical
-    // one the late-RUNNER lane needed are now one `applyPushedFindingPolicy`
-    // call, so the gate and the evidence name that call. Same stack, same
-    // identities — only the spelling moved.
-    ["gateFindingsByPathFreshness", "applyPushedFindingPolicy"], ['"late-auxiliary-findings": {', "applyPushedFindingPolicy(gate.live, {"]),
-    "runtime-turn:late-runner-findings": gated(RUNTIME_TURN_FILE, "Turn-end CLI runner findings collected after the post-write path.", 
-    // #3248: this lane was the last push surface with no disposition stage;
-    // it now routes through the same shared policy call as its
-    // late-auxiliary twin, which is what this gate pins.
-    ["gateFindingsByPathFreshness", "applyPushedFindingPolicy"], ['"late-runner-findings"'], { evidenceMin: 2 }),
-    "runtime-turn:cascade-blocker": labeled(RUNTIME_TURN_FILE, "Turn-end 🧪 cascade neighbor blocker.", "Cascade results settle synchronously this turn where possible " +
-        "(`settleCascadeRuns`), but an unsettled compute can carry over to a " +
-        "later turn (bounded by a carry cap) — a carried-over result renders " +
-        "with an explicit `(carried N turns · scanned Xm ago)` label (#3167, " +
-        "#3168 F3), so the agent can tell it from a fresh observation.", "live", ["cascadeCarrySuffix("], { evidenceMin: 1 }),
-    "runtime-turn:cascade-coverage-advisory": labeled(RUNTIME_TURN_FILE, "Turn-end cascade-coverage-gap advisories (graph/binding/budget).", "Explains what the cascade check could NOT confirm this turn — not a " +
-        "finding with a cited path, an absence-of-coverage disclosure computed " +
-        "from this turn's own indeterminate-run list. An advisory computed from " +
-        "a carried indeterminate run is labeled `(carried N turns · <age>)` " +
-        "(#3167, #3168 F4 — dropped on mixed carried/fresh buckets). The age " +
-        "half reads `scan age unknown` on this surface today: no indeterminate-" +
-        "run producer stamps `observedAt` (only the resolved-found plumb does, " +
-        "`clients/cascade-format.ts`), and one unstamped carried run collapses " +
-        "the whole bucket's age rather than claiming the stamped runs' (#3168 " +
-        "F13). The carry COUNT is always real.", "live", ["withCarryLabel("], { evidenceMin: 3 }),
-    // #3102: the cold-neighbour cascade run is BUILT here, in the quiet-window
-    // reconcile (`onResolvedFound` in index.ts), a turn earlier than the
-    // `runtime-turn:cascade-blocker` render that finally carries it — so it is
-    // its own delivery lane, and it was the one that rendered raw LSP findings
-    // with no policy filter at all. The evidence is the CALL TEXT of the shared
-    // filter (#3088 round-2 F4): a bare `applyFindingPolicy` would also be
-    // satisfied by the import line.
-    "cascade-format:resolved-found-run": gated("clients/cascade-format.ts", "Cold-neighbour ERROR diagnostics formatted into the turn-end cascade " +
-        "run by `buildResolvedFoundCascadeRun` (quiet-window reconcile of a " +
-        "cascade touch that skipped its in-lane wait).", ["applyFindingPolicy"], ["applyFindingPolicy(retained, {"]),
-    // #3157: the IN-LANE cascade — a different delivery lane from the
-    // quiet-window run above, and the one #3102's sweep cleared WRONGLY. Its four
-    // display sites (passive cold snapshot, fresh touch, touch-error fallback,
-    // degraded fallback) assemble `CascadeNeighborResult.diagnostics` and reach
-    // the agent through `formatCascadeNeighborDiagnostics` without ever entering
-    // the dispatcher's `applyOutputFilters` pipeline: the sweep's file-level
-    // verdict ("the per-edit dispatch path, which already filters in
-    // dispatcher.ts") was true only of the per-edit RUNNER output in
-    // `runners/lsp.ts`, which is a different call site in a different file.
-    //
-    // Evidence is the CALL TEXT (#3088 round-2 F4), counted: `cascadeDisplay(` is
-    // the one seam all four sites route through, so `evidenceMin: 4` is the count
-    // of display sites in the file and dropping ANY of them back to a raw
-    // `convertLspDiagnostics` reds this suite. Identity-stubbing the callee
-    // instead is caught behaviourally — it reds twelve cases in
-    // `tests/clients/inlane-cascade-finding-policy.test.ts`, which is a stronger
-    // signal than the R2 proximity heuristic. Residual, stated: a FIFTH display
-    // site that open-codes the conversion keeps the count at 4 and is caught by
-    // review, not by this row.
-    "dispatch-integration:in-lane-cascade": gated("clients/dispatch/integration.ts", "In-lane per-edit cascade neighbour ERROR diagnostics, rendered into the " +
-        "turn-end cascade block by `computeCascadeForFile`.", ["applyCascadeDisplayPolicy"], ["cascadeDisplay("], { evidenceMin: 4 }),
-    "runtime-turn:call-graph-advisory": labeled(RUNTIME_TURN_FILE, "Turn-end 📊 call-graph impact advisory.", "`runtime.callGraph` is a session-lifetime in-memory structure; this " +
-        "round does not verify or gate ITS OWN freshness policy (how/when it " +
-        "incorporates edits made earlier in the session).", "live", [], {
-        status: "partial",
-        partialReason: "call-graph freshness/invalidation policy is out of this PR's scope — " +
-            "tracked as a follow-up, not silently assumed fresh.",
-    }),
-    // #3088 round 2 F4: this row used to name `applyDispositions`/`applyRulePolicy`
-    // with whole-file evidence literals. Once #3088 folded mode=full's stack onto
-    // `applyFindingPolicy`, those two literals survived only in UNRELATED
-    // mode=delta helpers in the same file, so deleting the entire policy stack out
-    // of `applyInlineSuppressionsToSummaries` left this gate — and the ratchet —
-    // green while five behaviour cases redded. The evidence is now the call text
-    // of the merge's own filter, which exists nowhere else in the file.
-    "lens-diagnostics:mode-full": gated(LENS_DIAGNOSTICS_FILE, "`lens_diagnostics mode=full` report.", ["applyFindingPolicy", "reconcileProjectDiagnosticsSnapshot"], [
-        "applyFindingPolicy(summary.diagnostics, {",
-        "reconcileProjectDiagnosticsSnapshot(",
-    ]),
-    "lens-diagnostics:mode-all": gated(LENS_DIAGNOSTICS_FILE, "`lens_diagnostics mode=all` report (widget-state read).", ["reconcileStaleWidgetFiles", "reconcileStaleWidgetDependencyBlockers"], ["reconcileStaleWidgetFiles(", "reconcileStaleWidgetDependencyBlockers("]),
-    // #1634 review round F3: this was the most important gap — the tool's
-    // DEFAULT mode rendered cached `file:line` findings with zero freshness
-    // check. `applyDeltaFreshnessGate` (this file's sibling in
-    // tools/lens-diagnostics.ts) now routes the actionable/quality-warnings
-    // caches through the shared gate using each report's own `generatedAt`.
-    // Round R3: mode=delta has a THIRD arm — the persisted project-diagnostics
-    // delta report, rendered by `appendProjectDiagnosticsDeltaLines` — which
-    // carried the identical unfixed shape. It now gates the same way, against
-    // its own `generatedAt`.
-    "lens-diagnostics:mode-delta": gated(LENS_DIAGNOSTICS_FILE, "`lens_diagnostics mode=delta` report (the tool's DEFAULT mode) — " +
-        "re-serves the actionable-warnings/code-quality-warnings caches AND " +
-        "the persisted project-diagnostics delta report.", ["gateFindingsByPathFreshness"], [
-        '"lens-diagnostics-delta": {',
-        "applyDeltaFreshnessGate(",
-        '"lens-diagnostics-delta-project": {',
-    ]),
-    "widget-state:footer": gated("clients/widget-state.ts", "TUI footer blocking/error/warning tally.", ["reconcileStaleWidgetFiles", "isBlocking"], ["isBlocking(diagnostic)", "reconcileStaleWidgetFiles()"]),
-    "agent-nudge:context-message": labeled("clients/agent-nudge.ts", "Post-edit file-touch nudge injected via `context`.", "Not a scanner finding store: no severity, no cited line, no cache — the " +
-        "accumulator is drained and cleared at the moment of injection, so the " +
-        "content IS the current state by construction.", "live"),
-    "test-runner-delivery:custom-entry": labeled("clients/test-runner-delivery.ts", "Post-agent test-runner failures in a non-context custom entry.", "The cache remains authoritative for pull diagnostics and the commit guard; this surface appends only after provenance validation and an idle recheck.", "live"),
-    "project-diagnostics:persisted-snapshot": gated(LENS_DIAGNOSTICS_FILE, "Cross-session persisted project-diagnostics snapshot read.", ["reconcileProjectDiagnosticsSnapshot"], ["reconcileProjectDiagnosticsSnapshot("]),
-    // ── #2028: the remaining agent-facing surfaces ──────────────────────────
-    // Registered after #2028's root-cause review found the 🔴 STOP block
-    // rendering stale/deleted-file blockers because its surface was never in
-    // this registry — the exact "gated or labeled, never neither" gap this
-    // module exists to close.
-    "tool-call:stop-blocker": gated("clients/pipeline.ts", "Per-edit 🔴 STOP blocker output appended to the write/edit tool result.", ["dropFindingsForMissingPaths"], ['store: "stop-blocker"']),
-    // The freshness stack itself (own-file mtime + reverse-dependency mtimes
-    // via isEntryFresh, plus the #1095 content binding) lives inside
-    // clients/lsp/workspace-diagnostics-cache.ts; the two evidence calls are
-    // the tool's literal entry points into that gated path.
-    "lsp-diagnostics:tool-output": gated("tools/lsp-diagnostics.ts", "`lsp_diagnostics` batch/directory sweep results. Cache hits replay through " +
-        "the shared workspace-diagnostics cache: createWorkspaceDiagnosticsCacheContext " +
-        "is the tool's entry, and its lookup() applies the #671/#672 freshness stack " +
-        "(own-file mtime + reverse-dependency mtimes via isEntryFresh) plus the " +
-        "#1095 content binding. #3088: every route out of this tool — fresh, " +
-        "cache replay, single file, directory — also passes applyProbeFindingPolicy, " +
-        "the stored-disposition / .pi-lens.json rule-policy / inline pi-lens-ignore " +
-        "stack the per-edit dispatch path and mode=full apply.", [
-        "createWorkspaceDiagnosticsCacheContext",
-        "isEntryFresh",
-        "cacheCtx.lookup",
-        "applyProbeFindingPolicy",
-    ], [
-        "createWorkspaceDiagnosticsCacheContext(resolvedCwd)",
-        "cacheCtx.lookup(file, scopeKey)",
-        "applyProbeFindingPolicy(",
-    ]),
-    "git-guard:commit-blocked": labeled("clients/git-guard.ts", "Git-guard commit/push 🔴 COMMIT BLOCKED verdict (--lens-guard).", "Synchronous preflight rejection returned inline with the failed git " +
-        "command — no stored state is delivered, so nothing can go stale between " +
-        "detection and delivery.", "live"),
-    "shared-checkout-guard:worktree-mutation-blocked": labeled("clients/shared-checkout-guard.ts", "Shared-checkout 🔴 WORKING-TREE CHANGE BLOCKED verdict (--lens-checkout-guard).", "Synchronous preflight rejection returned inline with the failed git " +
-        "command. Both inputs are read at decision time — the instance registry " +
-        "and `git status` — so no stored finding is replayed and nothing can go " +
-        "stale between detection and delivery.", "live"),
-    "read-guard-tool-lines:preflight-errors": labeled("clients/read-guard-tool-lines.ts", "Read-guard hashline BLOCKED / RE-READ REQUIRED / PARTIAL APPLY / " +
-        "ALREADY APPLIED preflight errors (#2402).", "Computed fresh per edit attempt and returned as that attempt's rejection — " +
-        "no cached findings are replayed, so there is no staleness window. The " +
-        "PARTIAL APPLY and ALREADY APPLIED variants describe the same attempt's " +
-        "commit outcome; applied-edit recognition reads RuntimeCoordinator's " +
-        "session-scoped record, which resets with the session.", "live"),
-    "mutating-tool:adapter-preflight-errors": labeled("clients/mutating-tool.ts", "Shape-adapter BLOCKED preflight errors for hashline edit inputs the " +
-        "adapter recognized but could not resolve to a range (#2423).", "Computed fresh from the tool input on each attempt and returned as that " +
-        "attempt's rejection, so there is no staleness window. The adapters " +
-        "read only the call's own arguments; nothing cached is replayed.", "live"),
-    "tool-call:duplicate-export-blocker": labeled("clients/runtime-tool-call.ts", "Duplicate-export STOP rejection returned inline with the failed edit.", "Synchronous preflight rejection computed per edit attempt; no stored state.", "live"),
-    "agent-behavior:thrashing-notice": labeled("clients/agent-behavior-client.ts", "In-result thrashing/blind-write detection notice.", "Ephemeral notice computed at detection time inside the same tool result — " +
-        "no persistence and no cache, so nothing can be stale.", "live"),
-};
-function assertPartialStatusHasReason(id, entry) {
-    if (entry.status === "partial" && !entry.partialReason) {
-        throw new Error(`finding-delivery-gate: surface "${id}" is status=partial but names no partialReason`);
-    }
-}
-function assertGatedShapeIsWellFormed(id, entry) {
-    if (!Array.isArray(entry.gates) || entry.gates.length === 0) {
-        throw new Error(`finding-delivery-gate: surface "${id}" is mode=gated but names no gate`);
-    }
-    if (!Array.isArray(entry.evidence) || entry.evidence.length === 0) {
-        throw new Error(`finding-delivery-gate: surface "${id}" is mode=gated but names no evidence`);
-    }
-}
-function assertLabeledShapeIsWellFormed(id, entry) {
-    if (!entry.reason || !entry.ageSource) {
-        throw new Error(`finding-delivery-gate: surface "${id}" is mode=labeled but is missing reason/ageSource`);
-    }
-    // "live" surfaces call no age-formatting helper — nothing to grep for.
-    // Every other ageSource claims a real cache, so it must be provable.
-    if (entry.ageSource !== "live" && entry.evidence.length === 0) {
-        throw new Error(`finding-delivery-gate: surface "${id}" claims ageSource "${entry.ageSource}" but names no evidence`);
-    }
-}
-/**
- * Enforce #1634's "no third state" rule: every registered surface is either
- * `gated` (names at least one gate) or `labeled` (names a reason and an age
- * source) — never a malformed/undeclared third shape. Throws naming the
- * offending surface id, so a bad registration fails loudly instead of
- * silently rendering ungated.
- */
-export function assertNoDeliveryBypass(registry = DELIVERY_SURFACES) {
-    for (const [id, entry] of Object.entries(registry)) {
-        assertPartialStatusHasReason(id, entry);
-        if (entry.mode === "gated") {
-            assertGatedShapeIsWellFormed(id, entry);
-            continue;
-        }
-        if (entry.mode === "labeled") {
-            assertLabeledShapeIsWellFormed(id, entry);
-            continue;
-        }
-        throw new Error(`finding-delivery-gate: surface "${id}" has unrecognized mode ${JSON.stringify(entry.mode)} — must be "gated" or "labeled"`);
-    }
-}

package/node_modules/pi-lens/dist/clients/finding-identity.js

@@ -1,88 +0,0 @@
-/**
- * Shared "finding identity" primitive (#1816 item 2, unifying the #533
- * canonicalization fix that only reached one of three copies).
- *
- * Three call sites independently hand-rolled the same shape — a hash over
- * `relativeFile|tool|rule|...|normalizedMessage` — to derive a stable id for
- * a diagnostic/finding: `diagnostic-dispositions.ts` (dd:/ddw:),
- * `actionable-warnings.ts` (aw:), and `code-quality-warnings.ts` (cq:). Only
- * `diagnostic-dispositions.ts`'s `relativeFile` routed both `cwd` and
- * `filePath` through `normalizeMapKey` before computing the relative path
- * (see the #1024/#210-class comment this module's `relativeFile` carries
- * forward) — the other two hashed the RAW inputs, so a drive-letter-case or
- * slash-variant `filePath` produced a different id in the warning stores
- * than dispositions would compute for the identical file. This module is the
- * single source for all three: one canonicalizing `relativeFile`, one
- * `normalizeMessage`, one `hashText`, and one hash length.
- *
- * Hash length: dispositions used 12 hex chars, the two warning builders used
- * 10. This module picks 12 (dispositions' length — dispositions is the older,
- * more heavily-audited call site) for every finding id going forward.
- * Callers that persist ids in a keyed on-disk store (only
- * `actionable-warnings.ts` does; see its own module doc) are responsible for
- * back-compat lookups against ids computed under their PRE-#1816 formula —
- * this module does not attempt migration itself, since it has no way to know
- * which callers persist and which are ephemeral-per-turn.
- */
-import { createHash } from "node:crypto";
-import * as path from "node:path";
-import { normalizeMapKey } from "./path-utils.js";
-/** Every finding id in this codebase truncates its sha256 hex digest to this
- * many characters. Single source so the three call sites this module
- * unifies (and any future one) can't drift back apart the way the pre-#1816
- * 10-vs-12 split did. */
-export const FINDING_ID_HASH_LENGTH = 12;
-/** Exported so a cross-check against a live diagnostic's message (e.g.
- * lens-diagnostic-mark's widget match) folds whitespace/case the same way id
- * derivation does — a second, slightly different normalizer would make a
- * real match invisible. */
-export function normalizeMessage(message) {
-    return message.replace(/\s+/g, " ").trim().toLowerCase();
-}
-export function hashText(value, length = FINDING_ID_HASH_LENGTH) {
-    return createHash("sha256").update(value).digest("hex").slice(0, length);
-}
-/**
- * Canonicalize BOTH `filePath` and `cwd` through `normalizeMapKey` (realpath
- * + case-fold on Windows) BEFORE computing the relative path, so two callers
- * holding different path FORMS of the same file (raw vs. already-normalized,
- * a Windows drive/segment case difference, a slash variant) converge on the
- * identical relative-path component instead of silently diverging into two
- * different finding ids for the same file (the #533 orphaned-record class).
- * `normalizeMapKey` is idempotent, so an already-canonical caller pays no
- * behavior change, only the realpath I/O — acceptable here because finding
- * ids are computed far less often than a per-write hot-path map key.
- */
-export function relativeFile(filePath, cwd) {
-    const canonicalCwd = normalizeMapKey(cwd);
-    const canonicalFile = normalizeMapKey(filePath);
-    const rel = path.relative(canonicalCwd, canonicalFile).replace(/\\/g, "/");
-    return rel && !rel.startsWith("..") ? rel : canonicalFile;
-}
-/**
- * Shared finding-id builder. `prefix` carries the caller's own namespace
- * (`"dd:"`, `"ddw:"`, `"aw:"`, `"cq:"`, ...) so distinct finding families
- * never collide in a shared store. `parts` is the caller's own ordered,
- * domain-specific identity fields (tool/rule/code/normalizedMessage/line/
- * lineContentHash/...) — this function only supplies the canonical
- * `relativeFile` component and the hash/prefix wiring.
- *
- * Both `undefined` AND `null` entries fold to `""` (review-round F4,
- * #1816), matching the `String(x ?? "")` idiom every pre-#1816 id builder
- * used. `null` is in the parts type despite every caller's field being
- * declared `T | undefined` in TypeScript: those fields (`Diagnostic.code`,
- * `.rule`, etc.) are frequently assigned straight from `JSON.parse`'d tool
- * output, which defeats the static type at runtime — a runner that emits
- * `"code": null` produces a real `null`, not `undefined`. Folding only
- * `undefined` would silently hash that as the string `"null"` instead of
- * `""`, diverging from every other id-construction path for the exact same
- * finding — a fresh, narrower instance of the #533 divergence class this
- * module exists to eliminate.
- */
-export function stableFindingId(prefix, args) {
-    const joined = [
-        relativeFile(args.filePath, args.cwd),
-        ...args.parts.map((part) => part === undefined || part === null ? "" : String(part)),
-    ].join("|");
-    return `${prefix}${hashText(joined)}`;
-}