@herbertgao/pi-extensions 2026.10.0 → 2026.10.2

package/node_modules/pi-lens/dist/clients/cargo-manifest.js

@@ -1,422 +0,0 @@
-/**
- * Minimal Cargo.toml reading — table-section slicing plus string-array and
- * scalar-string parsing.
- *
- * Single source of truth (AGENTS.md: "a hand-maintained list that mirrors a
- * registry is a defect"; the same rule applies to a second regex TOML
- * reader). `extractTomlTableSection`/`parseTomlStringArray` originated in
- * `clients/lsp/server.ts`'s rust-analyzer workspace-root hoisting
- * (#1671/#1693) and now live here so `clients/formatters.ts`'s rustfmt
- * `--edition` resolution (#2466) reuses the exact same parser instead of a
- * second hand-rolled one. `clients/lsp/server.ts` re-imports them from here.
- *
- * The ONE Cargo.toml reader in the tree (#2473): `clients/review-graph/
- * workspace-modules.ts`'s `scanCargoModules`/`detectWorkspaceType` used to
- * carry an independent regex TOML reader (`extractTomlArray`/
- * `extractTomlSection`/`extractTomlString`) for module-graph construction — a
- * third copy, folded onto `readCargoPackageName`/`readCargoWorkspaceMembers`/
- * `readCargoDependencyNames` below. That fold also fixed a latent defect:
- * the old `extractTomlString` was NOT table-scoped — it scanned the whole
- * file for the first `key = "value"` line regardless of which table it fell
- * under, so a member manifest with a `name` key under an EARLIER non-package
- * table (a `[[bin]] name = "..."` or `[package.metadata.*]` block preceding
- * `[package]`) silently returned the wrong crate name. `readCargoPackageName`
- * is table-scoped via `extractTomlTableSection` like every other reader here.
- *
- * Review round 2 (PR #2480) hardened the fold itself: `extractTomlTableSection`
- * and `parseTomlStringArray` now run everything through {@link normalizeToml}
- * (CRLF→LF, plus a per-line `#`-to-EOL comment strip that respects quoted
- * strings) before any regex runs, and both the table heading and its
- * terminator are anchored with `[ \t]*` rather than bare `^` so an indented
- * heading or sub-table is read the same way the pre-fold, per-line `.trim()`d
- * reader read it. `readCargoWorkspaceMembers` also gained `[workspace]`
- * table-scoping and a sibling `readCargoWorkspaceExclude`, both now reused by
- * `clients/lsp/server.ts` instead of that file hand-composing the same two
- * primitives itself.
- *
- * #2480's fold missed a THIRD `[workspace]` presence check: `clients/lsp/
- * server.ts`'s `RustWorkspaceRoot` walk-up carried its own
- * `/^\s*\[workspace\]/m.test(...)`, four lines above the call it had already
- * folded onto this file's readers. {@link hasCargoWorkspaceTable} closes that
- * gap (#2498) — the one presence check every caller (that walk-up, and both
- * of {@link resolveCargoPackageEdition}'s own checks below) now shares.
- */
-import { readFile } from "node:fs/promises";
-import * as os from "node:os";
-import * as path from "node:path";
-import { logExtension } from "./extension-log.js";
-import { findNearestMarkerRoot, isAtOrAboveHomeDir } from "./path-utils.js";
-export async function readTextFileOrUndefined(filePath) {
-    try {
-        return await readFile(filePath, "utf-8");
-    }
-    catch {
-        return undefined;
-    }
-}
-/**
- * Strip a `#`-to-end-of-line TOML comment from one line, leaving a `#`
- * character INSIDE a single- or double-quoted string alone (a version spec or
- * path containing a literal `#` is unusual but legal TOML). A whole-line
- * comment (the line's first non-whitespace character is `#`) reduces to "".
- */
-function stripTomlLineComment(line) {
-    let quote = null;
-    for (let i = 0; i < line.length; i++) {
-        const ch = line[i];
-        if (quote) {
-            if (ch === quote)
-                quote = null;
-            continue;
-        }
-        if (ch === '"' || ch === "'") {
-            quote = ch;
-            continue;
-        }
-        if (ch === "#")
-            return line.slice(0, i);
-    }
-    return line;
-}
-/**
- * Normalize CRLF to LF and strip `#`-to-EOL comments line by line. Every
- * regex-based reader below runs on the result.
- *
- * The CRLF→LF pass is DEFENSIVE, not the fix for a real match failure —
- * review round 2, F2 originally claimed a CRLF manifest's `\r` broke the
- * heading/terminator `$` anchor; it does not, because ECMAScript's
- * multiline `$`/`^` treat a bare `\r` as a line terminator on its own (same
- * as `\n`), so the `adv-e-crlf` fixture passes this suite even with this
- * `.replace(/\r\n/g, "\n")` call removed (review round 3, F2 — verified by
- * mutation: dropping the line left all tests green). It stays as
- * belt-and-braces normalization — a single LF-only code path for every
- * downstream regex is simpler to reason about than "also correct on `\r\n`
- * by an ECMAScript technicality" — and because `.split("\n")` below would
- * otherwise leave a trailing `\r` on each line for {@link stripTomlLineComment}
- * to walk past.
- *
- * The comment-strip pass IS load-bearing (review round 2, F1 — the pre-fold
- * `extractTomlArray` stripped comments per line before collecting; the
- * fold's single multi-line regex scan dropped that pass, so a commented-out
- * `# "member",` line stayed live because nothing removed it before the
- * quoted-string scan ran over the whole bracketed span). A commented-out
- * entry must never survive into a captured table/array body.
- *
- * A leading UTF-8 BOM (`\uFEFF`) is stripped first — valid at the start of a
- * Cargo.toml (rust-lang/cargo#2031) — because it sits OUTSIDE every reader's
- * heading/key anchor below (`[ \t]*`, not `\s*`) and would otherwise hide a
- * table or key on the file's very first line. #2498's `RustWorkspaceRoot`
- * walk-up used to carry its own `/^\s*\[workspace\]/m` check, and ES's `\s`
- * class DOES include `\uFEFF` — so that hand-rolled regex accepted a
- * BOM-prefixed manifest by accident; folding it onto this shared reader
- * without this strip would have silently regressed that shape (review round
- * 2, F4).
- */
-function normalizeToml(content) {
-    return content
-        .replace(/^\uFEFF/, "")
-        .replace(/\r\n/g, "\n")
-        .split("\n")
-        .map(stripTomlLineComment)
-        .join("\n");
-}
-/**
- * Slice out ONE top-level TOML table's raw body — from its `[name]` heading
- * to the next top-level `[...]`/`[[...]]` heading or EOF. `members`/`exclude`
- * must be read from the `[workspace]` table specifically: `[package]` has its
- * OWN `exclude` key (the standard cargo-publish exclude list, conventionally
- * written above `[workspace]` in a virtual-manifest-less root crate), and a
- * whole-file regex would misread it as workspace membership (#1671 F4).
- *
- * Both the heading and the terminating next-heading are anchored with
- * `[ \t]*` rather than bare `^` — TOML does not require a table heading to
- * start in column 0, and the pre-fold reader (which `.trim()`ed each line
- * before comparing) accepted an indented `  [package]` or `  [dependencies.
- * tokio]` sub-table. The column-0-only anchor this fold shipped with missed
- * both: an indented `[package]` heading never matched at all (the table read
- * as absent), and an indented sub-table heading never terminated the parent
- * slice (its keys leaked into the parent table's body) — review round 2, F2.
- *
- * Returns `undefined` when the table is ABSENT and `""` when the table IS
- * present but has an empty body (its heading is immediately followed by EOF
- * or the next heading, e.g. `[workspace]` as the last line of the file with
- * no trailing newline, or `[workspace]   `/`[workspace] # root` at EOF) —
- * review round 3, F1. Both used to collapse to the same `""` sentinel, so a
- * caller checking `!== ""` to mean "table present" silently misread a
- * present-but-empty table as absent. Callers that only care about the table's
- * CONTENT (feeding the result to {@link parseTomlStringArray}/
- * {@link parseTomlScalarString}, which both already treat `undefined` as "no
- * match") are unaffected; callers that check PRESENCE must compare against
- * `undefined`, not `""`.
- */
-export function extractTomlTableSection(content, tableName) {
-    const normalized = normalizeToml(content);
-    const heading = new RegExp(`^[ \\t]*\\[${tableName}\\][ \\t]*(?:#.*)?$`, "m");
-    const match = heading.exec(normalized);
-    if (!match)
-        return undefined;
-    const rest = normalized.slice(match.index + match[0].length);
-    const nextHeading = rest.match(/^[ \t]*\[{1,2}[^\]]+\]{1,2}[ \t]*(?:#.*)?$/m);
-    return nextHeading?.index !== undefined
-        ? rest.slice(0, nextHeading.index)
-        : rest;
-}
-export function parseTomlStringArray(content, key) {
-    if (content === undefined)
-        return [];
-    const normalized = normalizeToml(content);
-    const match = normalized.match(new RegExp(`^[ \\t]*${key}[ \\t]*=[ \\t]*\\[([\\s\\S]*?)\\]`, "m"));
-    if (!match)
-        return [];
-    return [...match[1].matchAll(/"([^"]*)"|'([^']*)'/g)].map((m) => (m[1] ?? m[2] ?? "").trim());
-}
-/**
- * Read a scalar `key = "value"` / `key = 'value'` line out of a TOML table
- * section. Anchored to line-start so `swift-edition = "..."` never matches a
- * `key` of `edition`, and a dotted-key inheritance line (`edition.workspace =
- * true`) never matches either — the literal key is immediately followed by
- * `=`, not `.`.
- */
-function parseTomlScalarString(content, key) {
-    if (content === undefined)
-        return undefined;
-    const match = content.match(new RegExp(`^[ \\t]*${key}[ \\t]*=[ \\t]*(?:"([^"]*)"|'([^']*)')`, "m"));
-    if (!match)
-        return undefined;
-    return match[1] ?? match[2];
-}
-/**
- * True when `content` declares a `[workspace]` table — table-scoped and
- * comment/indentation/CRLF-tolerant like every other reader here, because it
- * IS `extractTomlTableSection` underneath. Presence is `!== undefined`, not a
- * truthiness check on the returned string: an empty `[workspace]` table (a
- * heading with no keys) returns `""`, which reads as falsy but is a valid
- * "table present" answer (`extractTomlTableSection`'s own doc comment covers
- * this — review round 3, F1).
- *
- * Exists so a caller that only needs the yes/no answer does not hand-roll a
- * `\[workspace\]` regex to get it — that regex, four lines above
- * `cargoWorkspaceDeclaresMember` in `clients/lsp/server.ts`, was behaviorally
- * identical to this call under every probed shape (comments, indentation,
- * CRLF, trailing content) but sat outside the one Cargo.toml reader #2473
- * consolidated the rest of this file's callers onto (#2498).
- */
-export function hasCargoWorkspaceTable(content) {
-    return hasTomlTable(content, "workspace");
-}
-/**
- * True when `content` declares the table `tableName` — the yes/no half of
- * {@link extractTomlTableSection}, for readers that only need presence.
- * `tableName` is a regex SOURCE (it is interpolated into the heading pattern),
- * so a dotted table escapes its dots: `"tool\\.uv\\.workspace"`.
- *
- * Exists so a second file does not re-derive the `!== undefined` comparison
- * that {@link hasCargoWorkspaceTable} exists to hold: `clients/
- * python-environment.ts`'s uv-workspace discovery carried a private
- * `hasUvWorkspaceTable` that was this function's body with a different table
- * name (review round 2, F5). The `!== undefined` (not a truthy test) is the
- * load-bearing part both callers share: an empty table — a heading with no
- * keys — extracts as `""`, which is falsy but IS "table present".
- */
-export function hasTomlTable(content, tableName) {
-    return extractTomlTableSection(content, tableName) !== undefined;
-}
-/**
- * Read a crate's `[package] name`, table-scoped to the `[package]` section
- * specifically (#2473) — NOT the first `name = "..."` line in the file. A
- * member manifest commonly has other tables with their own `name` key
- * (`[[bin]] name = "..."`, `[package.metadata.*]` blocks); reading unscoped
- * silently returns whichever happens to sit first in the file.
- */
-export function readCargoPackageName(content) {
-    const packageSection = extractTomlTableSection(content, "package");
-    return parseTomlScalarString(packageSection, "name");
-}
-/**
- * Read `members` off a (typically root/virtual) Cargo.toml for workspace
- * expansion, table-scoped to `[workspace]` (review round 2, F4). A whole-file
- * `members` regex silently also matches `[workspace.metadata.*] members =
- * [...]` or any other table happening to declare a same-named key — the
- * exact "unscoped read of a same-named key under an unrelated table" defect
- * shape `readCargoPackageName` above was already fixed for (#2473), except
- * this reader shipped the fold WITHOUT that scoping and called it out
- * explicitly as intentional in the comment this replaces. It also duplicated
- * `clients/lsp/server.ts`'s independent, already-correctly-scoped
- * `extractTomlTableSection(content, "workspace")` + `parseTomlStringArray`
- * hand-composition for its own `members`/`exclude` read — the SAME
- * single-source-of-truth violation #2473 was filed to close for the OTHER
- * two Cargo.toml readers. `clients/lsp/server.ts` now calls this function
- * (and {@link readCargoWorkspaceExclude} below) instead of re-composing the
- * two primitives itself.
- */
-export function readCargoWorkspaceMembers(content) {
-    return parseTomlStringArray(extractTomlTableSection(content, "workspace"), "members");
-}
-/**
- * Read `exclude` off a (typically root/virtual) Cargo.toml, table-scoped to
- * `[workspace]` — `[package]` has its OWN `exclude` key (the cargo-publish
- * exclude list; see {@link extractTomlTableSection}'s doc comment), so an
- * unscoped read would misread it as workspace exclusion (#1671 F4). Companion
- * to {@link readCargoWorkspaceMembers}; both replace `clients/lsp/server.ts`'s
- * former hand-composed `extractTomlTableSection` + `parseTomlStringArray`
- * pair (review round 2, F4).
- */
-export function readCargoWorkspaceExclude(content) {
-    return parseTomlStringArray(extractTomlTableSection(content, "workspace"), "exclude");
-}
-/**
- * List the dependency names declared directly under `[dependencies]` (key
- * only — not the version/spec value, which may be a bare string, an inline
- * table, or workspace-inherited).
- */
-export function readCargoDependencyNames(content) {
-    const section = extractTomlTableSection(content, "dependencies");
-    if (section === undefined)
-        return [];
-    const names = [];
-    // `section` is already comment-stripped by `extractTomlTableSection`'s
-    // `normalizeToml` pass (quote-aware). A second, non-quote-aware
-    // `line.split("#", 1)[0]` re-strip here was redundant AND could wrongly
-    // truncate a line whose value legitimately contains a `#` inside a quoted
-    // string — deleted (review round 3, F4).
-    for (const rawLine of section.split(/\r?\n/)) {
-        const line = rawLine.trim();
-        const match = line.match(/^([A-Za-z0-9_-]+)\s*=/);
-        if (match)
-            names.push(match[1]);
-    }
-    return names;
-}
-/**
- * True when `key` is declared as workspace-inherited: the dotted-key form
- * (`edition.workspace = true`) or the inline-table form
- * (`edition = { workspace = true }`).
- */
-function isTomlKeyWorkspaceInherited(content, key) {
-    if (content === undefined)
-        return false;
-    const dotted = new RegExp(`^[ \\t]*${key}\\.workspace[ \\t]*=[ \\t]*true`, "m");
-    const inline = new RegExp(`^[ \\t]*${key}[ \\t]*=[ \\t]*\\{[^}\\n]*\\bworkspace[ \\t]*=[ \\t]*true`, "m");
-    return dotted.test(content) || inline.test(content);
-}
-/**
- * rustfmt's `--edition` is a closed enum — 2015/2018/2021/2024 as of rustfmt
- * itself, NOT any four-digit string. A manifest typo (`edition = "2019"`) or
- * an edition newer than the installed rustfmt understands would otherwise be
- * passed straight through `--edition`, and rustfmt rejects an edition it
- * doesn't recognize outright — turning EVERY `.rs` format into a hard
- * `outcome: "failed"` where the pre-#2466 bare command formatted fine (#2466
- * review round 2, F2). When Rust stabilizes a new edition, append it to this
- * set — rustfmt's own enum is the forcing function for this list, not a
- * pattern match on digit count.
- */
-const SUPPORTED_RUSTFMT_EDITIONS = new Set(["2015", "2018", "2021", "2024"]);
-/**
- * Validate a manifest-read edition value against rustfmt's actual enum
- * before letting a caller pass it through `--edition`. A defined-but-invalid
- * value (as opposed to "no edition found at all") is a config anomaly worth
- * a debug trail, not a silent swap to `undefined` — logs the rejected value
- * so a future report of "rustfmt still not carrying edition X" has the exact
- * string that got refused.
- */
-function validatedEdition(value, filePath) {
-    if (value === undefined)
-        return undefined;
-    if (SUPPORTED_RUSTFMT_EDITIONS.has(value))
-        return value;
-    logExtension({
-        subsystem: "format",
-        message: "resolveCargoPackageEdition: manifest edition is not a rustfmt-supported value; falling back to the static rustfmt command",
-        level: "debug",
-        metadata: { rejectedEdition: value, filePath },
-    });
-    return undefined;
-}
-/** Read `[workspace.package] edition` out of a manifest that declares it. */
-function readWorkspacePackageEdition(content) {
-    const workspaceSection = extractTomlTableSection(content, "workspace.package");
-    return parseTomlScalarString(workspaceSection, "edition");
-}
-/**
- * Resolve the four-digit `edition` for the Cargo package that owns
- * `filePath`, so a formatter/build tool that needs it doesn't default to an
- * older edition than the source actually uses (#2466 — rustfmt silently
- * rejecting valid Rust 2024 syntax under an older default edition).
- *
- * - Finds the nearest readable `Cargo.toml` from `filePath` via the shared
- *   `findNearestMarkerRoot` walker (home-ceiling guarded, depth-capped —
- *   AGENTS.md walk-confinement; never a private walk-up loop).
- * - Reads `[package] edition` directly when present.
- * - When the package declares `edition.workspace = true` (or the inline-table
- *   equivalent):
- *   - First checks whether the package's OWN manifest also declares
- *     `[workspace]` — a root crate can be its own workspace root (`[package]`
- *     + `[workspace]` + `[workspace.package]` all in one file, a documented,
- *     common Cargo shape) — before climbing past it (#2466 review round 2,
- *     F1).
- *   - Otherwise climbs ancestors — same home-ceiling guard — for the nearest
- *     one that DECLARES `[workspace]` (Cargo's own workspace-root rule, not
- *     merely the nearest ancestor Cargo.toml: an intermediate manifest for an
- *     unrelated plain package is skipped, not treated as the answer — #2466
- *     review round 2, F1), then reads that root's `[workspace.package]
- *     edition`.
- * - Every edition value (direct or inherited) is checked against rustfmt's
- *   actual enum (`SUPPORTED_RUSTFMT_EDITIONS`), not just "looks like four
- *   digits" (#2466 review round 2, F2).
- * - Returns `undefined` on any miss (unreadable manifest, no `[package]`
- *   table, unsupported/invalid value, unresolved inheritance): callers fall
- *   back to their pre-existing default argv rather than guessing.
- *
- * `homeDir` defaults to `os.homedir()` and exists as a parameter so tests can
- * inject a nearer ceiling and prove the guard actually stops a climb (#2466
- * review round 2, F5) — production callers never pass it.
- */
-export async function resolveCargoPackageEdition(filePath, homeDir = os.homedir()) {
-    const startDir = path.dirname(path.resolve(filePath));
-    const packageDir = findNearestMarkerRoot(startDir, ["Cargo.toml"], {
-        homeDir,
-    });
-    if (!packageDir)
-        return undefined;
-    const packageContent = await readTextFileOrUndefined(path.join(packageDir, "Cargo.toml"));
-    if (packageContent === undefined)
-        return undefined;
-    const packageSection = extractTomlTableSection(packageContent, "package");
-    const direct = parseTomlScalarString(packageSection, "edition");
-    if (direct !== undefined)
-        return validatedEdition(direct, filePath);
-    if (!isTomlKeyWorkspaceInherited(packageSection, "edition"))
-        return undefined;
-    // The package's own manifest may ALSO be the workspace root — check it
-    // before climbing so this common shape doesn't fall through to searching
-    // ancestors for a `[workspace.package]` that's actually right here. Table
-    // PRESENCE is `!== undefined`, not `!== ""` (review round 3, F1): an
-    // empty `[workspace]` table (heading with no keys, e.g. the last line of
-    // the file with no trailing newline) reads as `""`, the SAME value
-    // `extractTomlTableSection` returns for "table absent" — a `!== ""` check
-    // would misread this common non-virtual-workspace-root shape as "no
-    // [workspace] here" and wrongly climb past it.
-    if (hasCargoWorkspaceTable(packageContent)) {
-        return validatedEdition(readWorkspacePackageEdition(packageContent), filePath);
-    }
-    let current = path.dirname(packageDir);
-    for (let depth = 0; depth < 64; depth++) {
-        if (isAtOrAboveHomeDir(current, homeDir))
-            return undefined;
-        const ancestorContent = await readTextFileOrUndefined(path.join(current, "Cargo.toml"));
-        // Cargo's own rule: the workspace root is the nearest ancestor
-        // Cargo.toml that DECLARES `[workspace]`. An intermediate manifest for
-        // an unrelated package (no `[workspace]` table) is not it — keep
-        // climbing past it instead of stopping here. `!== undefined`, not
-        // `!== ""` — see the same-shaped check above (review round 3, F1).
-        if (ancestorContent !== undefined &&
-            hasCargoWorkspaceTable(ancestorContent)) {
-            return validatedEdition(readWorkspacePackageEdition(ancestorContent), filePath);
-        }
-        const parent = path.dirname(current);
-        if (parent === current)
-            return undefined;
-        current = parent;
-    }
-    return undefined;
-}

package/node_modules/pi-lens/dist/clients/cascade-budget.js

@@ -1,196 +0,0 @@
-/**
- * Cascade neighbour-budget sizing (#1462).
- *
- * The flat neighbour cap (40) and the turn-end settle wait (5000 ms) were set in
- * two different files with nothing relating them. Dogfood 2026-08-15 measured
- * what that costs: n=50 cascades, median 30 ms, max 3.88 s at nbr=40 — and with
- * a `reverse_deps_cache` refresh ahead of the graph build (2046 ms for
- * `logger.ts`) the run overran the turn_end cap, so `cascade_settle_wait`
- * returned `settled: 0` and the finding arrived a turn late.
- *
- * ## What a slow run actually costs
- *
- * It is NOT lost. `RuntimeCoordinator.settleCascadeRuns` re-parks a promise
- * still in flight at the cap, `agent_settled` gives it a second and more
- * generous drain (`cascade_carry_over_settle`, `quietWindowWaitMs`, 15 000 ms),
- * and `beginTurn` deliberately keeps `_pendingCascadeRuns` so anything still
- * running surfaces at a later turn_end — that is #1443, and pre-#450 these
- * findings were always awaited. So the real trade is:
- *
- *   full neighbour set, one turn late   vs.   a narrowed set, on time,
- *                                             with the remainder lost for good
- *
- * Narrowing is therefore only worth paying for when it genuinely converts a
- * late run into an on-time one. That gives three zones, and the derivation
- * below is exactly those three:
- *
- *   fits         the full walk still fits the on-time window — nothing to do
- *   narrowed     the RESCUE BAND: the full walk no longer fits but a shorter
- *                one does, so trading the tail for on-time delivery buys
- *                something real
- *   past-rescue  not even a floor-sized walk fits any more, so narrowing would
- *                drop neighbours permanently AND still miss the window. Keep
- *                the full budget and let the carry-over deliver it complete.
- *                This is the cold-session case: a fresh graph build measures up
- *                to ~19 s (see `runtime-coordinator.ts`'s carry-over note), and
- *                a floor-sized stub there is strictly worse than pre-#1462.
- *
- * One more guard, for the same reason. If the on-time window could not fit a
- * full walk even at zero prelude, there is no LATE run to rescue — every
- * cascade would be permanently downsized because a *wait* was configured small.
- * That is a budget change wearing a timeout's clothes, so the derivation stands
- * down entirely (`no-rescue-window`) and the flat cap applies. This is what
- * keeps `PI_LENS_CASCADE_SETTLE_WAIT_MS` from doubling as a neighbour-count
- * knob: at the 5000/100/40 defaults the band is a prelude of 1.0–4.5 s, and
- * shrinking the wait to 1000 ms disables narrowing rather than capping every
- * cascade at ~10 neighbours.
- */
-import { recordDegradationOnce } from "./degradation-ledger.js";
-import { toPositiveFinite } from "./env-utils.js";
-// The knobs only, never the scheduler — this module is arithmetic and has no
-// business depending on a task registry to read two numbers (#1462 review N4).
-// Note it buys nothing at load time: `runtime-config.js` below already reaches
-// `pidusage` via `lens-config.js`.
-import { isQuietWindowEnabled, quietWindowWaitMs, } from "./quiet-window-config.js";
-import { RUNTIME_CONFIG } from "./runtime-config.js";
-/**
- * Bounded wait for the turn's deferred cascade computes (#450) to settle before
- * they are merged at turn_end. A late compute is carried over, never dropped.
- *
- * `0` is a meaningful setting (never block turn_end), so this deliberately does
- * NOT use `lazyEnvNumber` — that helper treats 0 as "unset" and would silently
- * restore the 5000 ms default.
- */
-export function cascadeSettleWaitMs() {
-    const raw = Number(process.env.PI_LENS_CASCADE_SETTLE_WAIT_MS);
-    return Number.isFinite(raw) && raw >= 0 ? raw : 5000;
-}
-/** The budget floor, and the minimum any env override of the cap can produce. */
-const MIN_NEIGHBOUR_BUDGET = RUNTIME_CONFIG.pipeline.cascadeMaxFiles;
-/**
- * The flat per-run cap: the most neighbours a cascade walks. Still the ceiling
- * — the derivation below only ever narrows it, and only inside the rescue band.
- */
-const DEFAULT_NEIGHBOUR_BUDGET = 40;
-export const CASCADE_NEIGHBOUR_BUDGET = Math.max(MIN_NEIGHBOUR_BUDGET, Number.parseInt(process.env.PI_LENS_CASCADE_NEIGHBOUR_BUDGET ?? "40", 10) ||
-    DEFAULT_NEIGHBOUR_BUDGET);
-/**
- * True when `PI_LENS_CASCADE_NEIGHBOUR_BUDGET` moved the ceiling away from the
- * default (#1462 review F-E). Raising it far enough can push
- * `ceiling * perNeighbourMs` past the settle window, so EVERY cascade reads
- * `no-rescue-window` — the whole derivation disarmed by a cap change nobody
- * meant as a timeout change. Read once at load, same lifetime as the constant
- * it describes.
- */
-const NEIGHBOUR_BUDGET_OVERRIDDEN = process.env.PI_LENS_CASCADE_NEIGHBOUR_BUDGET !== undefined &&
-    CASCADE_NEIGHBOUR_BUDGET !== DEFAULT_NEIGHBOUR_BUDGET;
-/**
- * Marginal wall-clock cost of one more neighbour in the walk, in ms. Calibrated
- * on the 2026-08-15 dogfood tail: 3.88 s at nbr=40 and 3.71 s at nbr=38, both
- * ~97 ms per neighbour. Touches fan out in parallel, so this is the observed
- * marginal cost under LSP contention, not one touch's own latency.
- *
- * It is an ESTIMATE, and the derivation is sensitive to it: if the true cost is
- * materially above this, a walk sized against it still overruns (the rescue
- * fails and the tail was dropped for nothing). `scripts/bench-cascade-budget.mjs
- * --true-cost-ms=<n>` measures that sensitivity directly. Rounded UP from the
- * measurement so the estimate errs toward narrowing less.
- */
-const DEFAULT_NEIGHBOUR_COST_MS = 100;
-/** Read per call — sized once per cascade run, never on a hot path. */
-function neighbourCostMs() {
-    return (toPositiveFinite(process.env.PI_LENS_CASCADE_NEIGHBOUR_COST_MS) ||
-        DEFAULT_NEIGHBOUR_COST_MS);
-}
-function neighbourFloor() {
-    return (toPositiveFinite(process.env.PI_LENS_CASCADE_NEIGHBOUR_FLOOR) ||
-        MIN_NEIGHBOUR_BUDGET);
-}
-/**
- * Size one run's neighbour walk against the on-time window supplied by its
- * caller.
- *
- * `elapsedMs` is arithmetic input, not an observation made by this function.
- * The production caller measures it against the active turn_end settle window
- * and passes that elapsed time here. When that boundary is unavailable, the
- * caller passes zero to preserve the flat cap. Legacy callers may still pass
- * deferred run age for compatibility.
- *
- * Every override exists so the derivation can be tested and benchmarked as a
- * pure function; the function itself does not observe a deferred run's age.
- */
-export function deriveCascadeNeighbourBudget(options) {
-    const ceiling = options.ceiling ?? CASCADE_NEIGHBOUR_BUDGET;
-    // The floor can never exceed the ceiling — a floor above the cap would make
-    // the derived budget LARGER than the flat one it exists to bound.
-    const floor = Math.min(ceiling, options.floor ?? neighbourFloor());
-    const onTimeMs = options.settleWaitMs ?? cascadeSettleWaitMs();
-    const perNeighbourMs = options.perNeighbourMs ?? neighbourCostMs();
-    const elapsedMs = toPositiveFinite(options.elapsedMs);
-    const remainingMs = onTimeMs - elapsedMs;
-    const deliveryWindowMs = onTimeMs +
-        (options.quietDrainMs ??
-            (isQuietWindowEnabled() ? quietWindowWaitMs() : 0));
-    const full = { budget: ceiling, ceiling, remainingMs, deliveryWindowMs };
-    // No on-time window at all, or one too small to ever fit a full walk. There
-    // is no late run to rescue here, only every run to shrink — stand down.
-    //
-    // Boundary, acknowledged rather than special-cased: at exactly
-    // `onTimeMs === ceiling * perNeighbourMs` this does not fire and the `fits`
-    // zone has zero width, so ANY prelude narrows. Not slightly, either — at
-    // 4000/100/40 a 2 s prelude gives 20 and a 3.5 s prelude gives the floor.
-    // Left alone because the narrowing is honest at that setting: with the
-    // window sized to exactly one full walk, a run that has spent any of it
-    // really would miss, so every one of those cuts is a genuine rescue rather
-    // than the `no-rescue-window` case this guard exists to catch. What it does
-    // cost is headroom — see the divisor bands in the bench's `--sweep` text.
-    if (onTimeMs <= 0 || onTimeMs < ceiling * perNeighbourMs) {
-        // #1462 review F-E: name the override, once per session, when it is the
-        // REASON the derivation stood down — not when a caller under test asked
-        // for a specific ceiling, and not on every one of the cascades this
-        // disarms for the rest of the session.
-        if (options.ceiling === undefined && NEIGHBOUR_BUDGET_OVERRIDDEN) {
-            recordDegradationOnce({
-                kind: "cascade-budget-override-disarmed",
-                subject: "cascade-neighbour-budget",
-                reason: `PI_LENS_CASCADE_NEIGHBOUR_BUDGET=${CASCADE_NEIGHBOUR_BUDGET} needs ` +
-                    `${ceiling * perNeighbourMs}ms to walk the full cap, which exceeds ` +
-                    `the ${onTimeMs}ms settle window — the rescue band is disarmed and ` +
-                    `every cascade keeps the flat (overridden) cap`,
-            });
-        }
-        return { ...full, zone: "no-rescue-window" };
-    }
-    // The full walk still fits. Nothing to buy.
-    if (remainingMs >= ceiling * perNeighbourMs) {
-        return { ...full, zone: "fits" };
-    }
-    // Past rescue: not even a floor-sized walk fits, so narrowing would drop the
-    // tail permanently and still miss the window. The carry-over delivers the
-    // whole set one turn later instead.
-    //
-    // #1462 review F-B, kept rather than shrunk: one dogfood log measured this
-    // zone at 0/1090 cascades, and asked whether a 3-zone module earns its keep
-    // at that frequency. It was measured against the WRITE-relative clock this
-    // same round fixed, which charges elapsed time no cascade actually spent
-    // waiting — so it under-counts how often a genuinely slow compute (a cold
-    // graph build, ~19 s) overlaps an already-running settle window, which is
-    // exactly what this zone exists to catch (F3, a real regression the first
-    // review round found: a floor-sized stub on that cold-start case is
-    // strictly worse than pre-#1462). Reachability under the corrected clock
-    // has not been re-measured; shrinking on a stale sample would trade a
-    // cheap, already-tested guard against a proven regression for a paper
-    // simplification. Revisit if a post-fix dogfood window confirms it still
-    // never fires.
-    if (remainingMs < floor * perNeighbourMs) {
-        return { ...full, zone: "past-rescue" };
-    }
-    // The rescue band: a shorter walk lands on time.
-    return {
-        budget: Math.min(ceiling, Math.max(floor, Math.floor(remainingMs / perNeighbourMs))),
-        ceiling,
-        remainingMs,
-        deliveryWindowMs,
-        zone: "narrowed",
-    };
-}