@4da/mcp-server 5.0.4 → 6.0.0

package/dist/live/cargo-platform.js

@@ -0,0 +1,178 @@
+// SPDX-License-Identifier: Apache-2.0
+/**
+ * Which crates in a Cargo workspace are actually built on THIS host.
+ *
+ * Cargo.lock is target-agnostic: it lists every crate for every platform the
+ * tree can compile for. So a Windows machine's lockfile still contains the
+ * whole Linux GTK3 stack that Tauri pulls in — `gtk`, `gdk`, `atk`, `glib`,
+ * `gdkx11`, `gdkwayland-sys`, `gtk3-macros` — none of which are ever compiled
+ * there. Advisories against them are unreachable noise on that host.
+ *
+ * `vulnerability_scan` claimed to filter for exactly this ("Advisories are
+ * filtered to the host platform") while reporting `platform_inactive_packages:
+ * 0` and listing nine Linux-only crates on a Windows box. The gate it relied on
+ * only ever saw `[target.'cfg(...)'.dependencies]` entries from a manifest,
+ * which covers DIRECT platform-gated deps and cannot see transitives — and the
+ * GTK3 cluster is entirely transitive.
+ *
+ * Cargo.lock is also FEATURE-agnostic: it lists every optional dependency,
+ * including the ones no enabled feature turns on. `cargo tree` resolves both
+ * axes — target AND features — and is what the build itself does.
+ *
+ * This used `cargo metadata --filter-platform <triple>`, which resolves only
+ * the target axis. Measured on 4DA's own workspace, 2026-09-08, host
+ * `x86_64-pc-windows-msvc`:
+ *
+ * | mechanism                                   | distinct crates | `quinn-proto` |
+ * |---------------------------------------------|-----------------|---------------|
+ * | `Cargo.lock`                                | 788             | present       |
+ * | `cargo metadata --filter-platform <triple>` | 560             | **present**   |
+ * | `cargo tree` (host, default features)       | 538             | absent        |
+ *
+ * `cargo metadata` keeps the `reqwest -> quinn` edge even though `reqwest`'s
+ * enabled feature set contains no `http3` — so `quinn-proto`, a crate that has
+ * never been compiled on this machine, counted as built-on-host. It was
+ * Preemption's #1 item on 2026-09-07 (HIGH, "version-confirmed"). `cargo tree`
+ * excludes it. Same predicate, same answer, as the app's
+ * `src-tauri/src/ace/cargo_resolve.rs`.
+ *
+ * When cargo is unavailable the answer is `null` — *unknown*, never "nothing is
+ * inactive". Callers surface that distinction rather than quietly asserting a
+ * filter they did not run.
+ */
+import { execFileSync } from "node:child_process";
+import * as fs from "node:fs";
+import * as os from "node:os";
+import * as path from "node:path";
+import { fileSignature } from "./file-signature.js";
+/** Rust target triple for the current host, or null for a platform we do not map. */
+export function hostTriple() {
+    const arch = process.arch === "x64" ? "x86_64" : process.arch === "arm64" ? "aarch64" : null;
+    if (!arch)
+        return null;
+    switch (process.platform) {
+        case "win32":
+            return `${arch}-pc-windows-msvc`;
+        case "darwin":
+            return `${arch}-apple-darwin`;
+        case "linux":
+            return `${arch}-unknown-linux-gnu`;
+        default:
+            return null;
+    }
+}
+/**
+ * Per-directory memo, valid only while the workspace's Cargo.lock and
+ * Cargo.toml are unchanged. The MCP server now re-resolves dependencies when a
+ * lockfile changes, and server processes live for days (2026-09-10: two were
+ * older than the lockfile they answered for). A memo keyed on the directory
+ * alone would hand a re-resolution the OLD crate set, and every crate the new
+ * lockfile added would read as not-built-on-host, hiding its advisories under
+ * platform_inactive.
+ */
+const cache = new Map();
+/** Reset the memo. Tests only. */
+export function _resetCargoPlatformCache() {
+    cache.clear();
+}
+/**
+ * Crate names cargo resolves for this host in the workspace at `dir`.
+ *
+ * Returns `null` — meaning *unknown*, never "nothing" — when there is no
+ * Cargo.toml, no host triple mapping, or cargo is missing/fails. A `null` must
+ * never be treated as an empty set: that would mark every crate inactive and
+ * silently hide real advisories.
+ */
+export function activeCratesForHost(dir) {
+    const key = path.resolve(dir);
+    const signature = `${fileSignature(path.join(key, "Cargo.lock"))}|${fileSignature(path.join(key, "Cargo.toml"))}`;
+    const memo = cache.get(key);
+    if (memo !== undefined && memo.signature === signature)
+        return memo.crates;
+    const crates = computeActiveCrates(key);
+    cache.set(key, { signature, crates });
+    return crates;
+}
+function computeActiveCrates(dir) {
+    if (!hostTriple())
+        return null;
+    if (!fs.existsSync(path.join(dir, "Cargo.toml")))
+        return null;
+    let raw;
+    try {
+        const { args, cwd, targetDir } = cargoTreeInvocation(dir);
+        fs.mkdirSync(cwd, { recursive: true });
+        raw = execFileSync("cargo", args, {
+            cwd,
+            env: { ...process.env, CARGO_TARGET_DIR: targetDir },
+            encoding: "utf8",
+            maxBuffer: 64 * 1024 * 1024,
+            stdio: ["ignore", "pipe", "ignore"],
+            timeout: 30_000,
+            windowsHide: true,
+        });
+    }
+    catch {
+        // cargo absent, not a workspace, offline resolution impossible, a stale
+        // lockfile, a held package-cache lock, or a timeout.
+        return null;
+    }
+    const names = parseTreeNames(raw);
+    // An empty result is not a credible answer for a real workspace; treat it
+    // as unknown so nothing gets marked inactive on a parse quirk.
+    return names.size > 0 ? names : null;
+}
+/**
+ * How `cargo tree` is invoked for the workspace at `dir`.
+ *
+ * cargo runs from a server-owned scratch directory and reaches the project
+ * only through `--manifest-path`. cargo and rustup take their configuration
+ * (`.cargo/config.toml`, `rust-toolchain.toml`) from the working directory and
+ * its parents, so running inside the scanned project would let files in that
+ * project configure the toolchain this server invokes. A scanned project is
+ * untrusted input. `CARGO_TARGET_DIR` points at the same scratch directory so
+ * cargo's metadata writes never land in the user's tree either.
+ *
+ * Exported for tests.
+ */
+export function cargoTreeInvocation(dir) {
+    const scratch = path.join(os.tmpdir(), "4da-mcp-cargo-resolve");
+    return {
+        args: [
+            "tree",
+            "--manifest-path",
+            path.join(path.resolve(dir), "Cargo.toml"),
+            // Never touch the network or mutate the lockfile from a read-only
+            // scan. `--locked` also means a lockfile out of step with the manifest
+            // fails loudly here rather than being silently re-resolved.
+            "--offline",
+            "--locked",
+            // One package per line, no tree glyphs: `name vX.Y.Z [(...)]`.
+            "--prefix",
+            "none",
+            // dev-dependencies are compiled by `cargo test`, so an advisory
+            // against one is reachable. proc-macro deps ride along with normal.
+            "--edges",
+            "normal,build,dev",
+        ],
+        cwd: scratch,
+        targetDir: scratch,
+    };
+}
+/**
+ * Crate names from `cargo tree --prefix none` output.
+ *
+ * Exported for tests: the parser is the part that can silently degrade to an
+ * empty set, and an empty set is the one answer that must never be believed.
+ */
+export function parseTreeNames(stdout) {
+    const names = new Set();
+    for (const line of stdout.split(/\r?\n/)) {
+        const token = line.split(/\s+/).find((t) => t.length > 0);
+        // A package line starts with a crate name. Anything else — a blank line,
+        // a `[dev-dependencies]` header from a future cargo, a warning — is not.
+        if (token && /^[A-Za-z0-9._+-]+$/.test(token))
+            names.add(token);
+    }
+    return names;
+}

package/dist/live/changelog-classify.d.ts

@@ -0,0 +1,41 @@
+/**
+ * Changelog entry classification and sanitisation.
+ *
+ * A changelog is third-party text that ends up in an agent's context, so
+ * every entry is cleaned before it leaves this module: ASCII control
+ * characters and the zero-width / bidi-override code points that make text
+ * render differently from how it reads (U+200B–U+200F, U+202A–U+202E,
+ * U+2066–U+2069, U+FEFF) are stripped, whitespace is collapsed, and each
+ * entry is capped at 400 characters so one runaway paragraph cannot crowd
+ * out the rest of the report.
+ *
+ * Classification is keyword-based on purpose: changelogs follow no schema,
+ * and a wrong guess is cheap here because every entry carries its text — the
+ * kind decides ordering and what concise mode keeps, never whether an entry
+ * exists. An explicit section heading ("### Breaking Changes", keep-a-
+ * changelog's "### Removed" / "### Deprecated" / "### Security") outranks
+ * keywords in the line itself.
+ */
+export type EntryKind = "breaking" | "deprecation" | "security" | "change";
+export declare const MAX_ENTRY_CHARS = 400;
+/** Strip control and invisible/bidi characters, collapse whitespace, cap length. */
+export declare function sanitizeEntry(text: string, cap?: number): string;
+/** Kind of a single changelog line by its own wording. */
+export declare function classifyText(text: string): EntryKind;
+/**
+ * What a sub-heading (or a label-only bullet such as express's "* remove:")
+ * says about the entries under it:
+ * - an EntryKind: the author's explicit call ("BREAKING CHANGES", "⚠",
+ *   changesets' "Major Changes", "Security", "Deprecated");
+ * - "removal": a removal list ("Removed", "remove:", "API changes"), breaking
+ *   except for internal clean-up and deprecation notices filed under it (axios
+ *   1.0 removed "unused imports" there; nix files deprecations under Removed);
+ * - "additive": additions and fixes ("Added", "Fixed", "Features", "Other"),
+ *   where only an explicit marker makes an entry breaking ("Added a clear()
+ *   function ... removed from an axios instance" is not a removal).
+ */
+export type EntryContext = EntryKind | "removal" | "additive";
+/** Context implied by a heading or label, or null when it carries no signal ("### Changed"). */
+export declare function classifyHeading(heading: string): EntryContext | null;
+/** Final kind: an explicit heading or bullet parent wins; removal and additive contexts refine the line's wording. */
+export declare function classifyEntry(text: string, context: EntryContext | null): EntryKind;

package/dist/live/changelog-classify.js

@@ -0,0 +1,207 @@
+// SPDX-License-Identifier: Apache-2.0
+/**
+ * Changelog entry classification and sanitisation.
+ *
+ * A changelog is third-party text that ends up in an agent's context, so
+ * every entry is cleaned before it leaves this module: ASCII control
+ * characters and the zero-width / bidi-override code points that make text
+ * render differently from how it reads (U+200B–U+200F, U+202A–U+202E,
+ * U+2066–U+2069, U+FEFF) are stripped, whitespace is collapsed, and each
+ * entry is capped at 400 characters so one runaway paragraph cannot crowd
+ * out the rest of the report.
+ *
+ * Classification is keyword-based on purpose: changelogs follow no schema,
+ * and a wrong guess is cheap here because every entry carries its text — the
+ * kind decides ordering and what concise mode keeps, never whether an entry
+ * exists. An explicit section heading ("### Breaking Changes", keep-a-
+ * changelog's "### Removed" / "### Deprecated" / "### Security") outranks
+ * keywords in the line itself.
+ */
+export const MAX_ENTRY_CHARS = 400;
+const CONTROL = /[\u0000-\u0009\u000B-\u001F\u007F]/g;
+const INVISIBLE = /[​-‏‪-‮⁦-⁩]/g;
+/** Strip control and invisible/bidi characters, collapse whitespace, cap length. */
+export function sanitizeEntry(text, cap = MAX_ENTRY_CHARS) {
+    const clean = text.replace(INVISIBLE, "").replace(CONTROL, " ").replace(/\s+/g, " ").trim();
+    return clean.length > cap ? `${clean.slice(0, cap - 1)}…` : clean;
+}
+/**
+ * Explicit markers: these win even over a security keyword in the same line.
+ * Upper-case BREAKING and conventional-commit `feat!:` are case-sensitive
+ * markers; the prose form must not be negated — tokio 1.44.0's entry
+ * "We determined this change is not a breaking change" was counted as
+ * breaking on the first live run.
+ */
+// `BREAKING` but not the file name `BREAKING-CHANGES.md` (ratatui links it from routine entries);
+// a leading "Breaking -" / "[Breaking]" label too (webpack-merge 5, handlebars-rust).
+// Case-sensitive on purpose: lowercase "breaking" is prose, handled (with negation) below.
+const EXPLICIT_BREAKING_MARKER = /\bBREAKING\b(?![-_.]\w)|⚠|^\s*\*{0,2}\w+(?:\([^)]*\))?!:|^\s*\*{0,2}[Bb]reaking\*{0,2}\s*(?::|[-–—]\s)|^\s*\[(?:[Bb]reaking|[Rr]emoved)\]/;
+/**
+ * Text ABOUT breaking changes rather than one: a pointer to the list ("⚠️ List
+ * of breaking changes can be found here"), a CI label check, a docs fix
+ * (ratatui 0.24-0.26: 8 of 16 marker-based flags on 2026-10-03 were these).
+ */
+const META_BREAKING = /\b(?:list|lists|see|found|documented|described|summary|guide|doc|docs|documentation|label|labels|check|technically|despite|mentioning)\b[^.]{0,40}\bbreaking[- ]changes?\b|\bbreaking[- ]changes?\b[^.]{0,30}\b(?:can be found|are (?:listed|documented|described)|described|label|labels|doc|docs|documentation)\b|BREAKING[-_]CHANGES/i;
+/**
+ * Intent, not a change: "We reserve the right to drop support for ...",
+ * "will be removed in a future release".
+ */
+const FUTURE_INTENT = /\b(?:reserve the right|will(?: be)?|may(?: be)?|might|plan(?:s|ning)? to|intend(?:s)? to|in (?:a|the) future|eventually)\b[^.]{0,40}\b(?:drop|dropp|remov|renam|deprecat)/i;
+/** A fix-led entry ("Fixed nightly build where Generator was renamed to Coroutine"): removal words in it are prose. */
+const LEADING_FIX = /^\W*(?:\*\*[^*]{1,40}\*\*:?\s*)?(?:fix|fixed|fixes|fixing)\b/i;
+/**
+ * "breaking change" in prose, except when negated, when it is a compound
+ * ("reproducibility-breaking": rand 0.9's changed outputs, not its API), and
+ * when it names another crate's release (regex 1.10: "`regex-syntax` breaking
+ * change release"). Measured 2026-10-02 against a 3-rater panel.
+ */
+const EXPLICIT_BREAKING_PROSE = /(?<!\bnot (?:a )?|\bnon[- ]|\bno |-)\bbreaking[- ]changes?\b(?! release)/i;
+/** A yank notice mentions breakage without being a change to the API ("Yanked ... due to unforeseen breaking change"). */
+const YANK_NOTICE = /\byanked\b/i;
+/**
+ * Inline labels that say an entry is NOT a breaking change (axum's
+ * `**fixed:** Removed the warning about breaking changes from README`,
+ * conventional `fix:` / `docs:`). Such entries keep only their security and
+ * deprecation signal; removal/rename keywords inside them are prose.
+ */
+const NON_BREAKING_LABEL = /^\s*\*{0,2}(?:fixed|fix|fixes|added|add|feat|features?|docs?|perf|chore|internal|improved|tests?|ci|build|refactor|style)(?:\([^)]*\))?\*{0,2}:\*{0,2}\s/i;
+const SECURITY = /\bsecurity\b|\bCVE-\d{4}-\d+|\bGHSA-[\w-]+|\bRUSTSEC-\d{4}-\d+|vulnerab/i;
+/**
+ * Wording that changes the API a caller compiles or runs against. Each pattern
+ * is narrower than the keyword it replaced: bare "no longer" also matched
+ * "No longer panics when ..." (a fix), bare "MSRV" matched "Add
+ * `Cargo.lock.msrv` file", and only past-tense "removed"/"renamed" were seen,
+ * so rand 0.9's "Rename fn `thread_rng()` to `rng()`" was missed.
+ *
+ * Removal and rename wording is breaking unless what went is internal (see
+ * INTERNAL_CHANGE); the other API wording stands whatever else the line mentions
+ * ("MSRV is now 1.70 because of a dependency update").
+ */
+const REMOVAL_HEURISTIC = new RegExp([
+    "\\bremoved\\b",
+    "\\bremoves\\b",
+    "\\b(?:has|have|was|were) been dropped\\b",
+    "\\brenamed?\\b",
+    // The removed thing is the object of "remove": a code name within a few words
+    // ("Remove first parameter (`rng`) of ..."), not a backtick somewhere later
+    // ("Remove a window when ... `cd`able", a security fix).
+    "^\\W*(?:remove|delete)\\b(?:\\s+[\\w-]+){0,3}\\s*\\(?`",
+    // ... or a qualified name without backticks ("remove Socket#rooms object").
+    "^\\W*(?:remove|delete)\\b(?:\\s+[\\w-]+){0,2}\\s+[A-Za-z_]\\w*(?:#|::|\\.)[A-Za-z_]",
+].join("|"), "i");
+/** Wording that changes the API or its requirements, whatever else the line mentions. */
+const BREAKING_HEURISTIC = new RegExp([
+    // Not "no longer require(s)": that is a relaxation ("`Data::get_ref()` no longer
+    // requires `T: Sized`", four actix-web 4 entries the panel called non-breaking).
+    "\\bno longer (?:accepts?|returns?|supports?|exports?|exported|exposed|re-?exports?|available|provides?|allow(?:s|ed)?|implements?|public|includes?|ships?|compiles?|works? with)\\b",
+    "\\bcan no longer\\b",
+    "\\bnow (?:also )?returns?\\b",
+    // Rust: marking a public type non-exhaustive breaks exhaustive matches and struct literals.
+    "\\b(?:now )?marked (?:as )?`?#\\[non_exhaustive\\]",
+    "\\bdrop(?:ped|s)? (?:support|compatibility)\\b",
+    "\\bdropped\\b.*\\b(?:support|compatibility)\\b",
+    // A raise names a version: "Bump MSRV to 1.63"; "Update MSRV in cron job" (config 0.14, CI) does not.
+    // A window of .{0,60}, not [^.]: versions carry dots ("MSRV: Rust 1.64.0 or later is now required").
+    "\\b(?:bump|bumped|raise|raised|increase|increased|update|updated|require|requires|now)\\b.{0,60}\\b(?:MSRV|minimum supported rust version|rust-version)\\b.{0,30}\\d+\\.\\d+",
+    // A raise names the new version ("MSRV is now 1.70", "MSRV: Rust 1.64.0 or later");
+    // "Move MSRV metadata to `Cargo.toml`" names none.
+    "\\b(?:MSRV|minimum supported rust version)\\b.{0,60}?\\b(?:is now|to|bumped to|raised to|increased to)\\s+(?:rust\\s+|rustc\\s+)?v?\\d",
+    "\\b(?:MSRV|minimum supported rust version)\\b.{0,60}\\d+\\.\\d+.{0,20}\\bor later\\b",
+    "\\bnow (?:requires?|required|returns?|takes?|accepts? only)\\b",
+    "\\b(?:function|method|type|the) signatures?\\b",
+    "\\bsignatures? (?:of|has|have|changed)\\b",
+    "\\b(?:changed?|new|different)\\b[^.]{0,30}\\b(?:return|argument|parameter) types?\\b",
+    "\\b(?:return|argument|parameter) types? (?:have |has )?(?:changed|change)\\b",
+    "\\btypes have changed\\b",
+    // An API that now implements/returns/takes a different type; "Use `Cell` instead
+    // of `RefCell` in `Format`" is an internal choice, not an API change.
+    "\\b(?:implements?|returns?|takes?|accepts?|requires?|yields?|expects?)\\b[^.]{0,40}`[^`]+`\\s+instead of\\s+`[^`]+`",
+    "\\(instead of `",
+    // An API that now receives/uses a different type, or moved out of the crate
+    // (actix-web 4: "`guard::fn_guard` functions now receives a `&GuardContext`",
+    // "`test::start`; moved to new `actix-test` crate").
+    "\\bnow (?:receives?|uses?)\\b[^.]{0,30}`",
+    "\\bmoved (?:in)?to (?:the |a )?(?:new |separate )?`?[\\w-]+`? (?:crate|package|module)\\b",
+    "\\bto keep the (?:old|previous|former) behaviou?r\\b",
+    "\\bincompatib",
+].join("|"), "i");
+/** Removals that change nothing a caller sees: "Removed unused imports", "Removed Webpack". */
+const INTERNAL_CHANGE = /\b(?:unused|unneeded|unnecessary|internal(?:ly)?|dead code|tests?|ci|lint(?:ing)?|typos?|comments?|docs?|documentation|readme|redundant|duplicated?|webpack|dev-?dependenc(?:y|ies)|dependency|warnings?|examples?|benchmarks?|release process|build process|tooling|usage|incorrect|wrong|erroneous|stray|spurious)\b/i;
+const DEPRECATION = /deprecat/i;
+/**
+ * An entry whose main verb is "deprecate" is a deprecation even when it names
+ * the replacement ("Deprecated `Itertools::group_by` (renamed `chunk_by`)"):
+ * the old name still works.
+ */
+const LEADING_DEPRECATION = /^\W*(?:\*\*[^*]{1,40}\*\*:?\s*)?(?:deprecated?|deprecates|deprecating)\b/i;
+/** Kind of a single changelog line by its own wording. */
+export function classifyText(text) {
+    if (META_BREAKING.test(text))
+        return SECURITY.test(text) ? "security" : "change";
+    if (EXPLICIT_BREAKING_MARKER.test(text))
+        return "breaking";
+    if (NON_BREAKING_LABEL.test(text)) {
+        if (SECURITY.test(text))
+            return "security";
+        return DEPRECATION.test(text) ? "deprecation" : "change";
+    }
+    if (YANK_NOTICE.test(text))
+        return "change";
+    if (LEADING_DEPRECATION.test(text))
+        return "deprecation";
+    // A rename that keeps the old name working ("Rename `x => y`, deprecating the old name").
+    if (/\brenam/i.test(text) && DEPRECATION.test(text) && !/\bremov/i.test(text))
+        return "deprecation";
+    if (EXPLICIT_BREAKING_PROSE.test(text))
+        return "breaking";
+    if (SECURITY.test(text))
+        return "security";
+    if (FUTURE_INTENT.test(text))
+        return DEPRECATION.test(text) ? "deprecation" : "change";
+    if (BREAKING_HEURISTIC.test(text))
+        return "breaking";
+    if (REMOVAL_HEURISTIC.test(text) && !INTERNAL_CHANGE.test(text) && !LEADING_FIX.test(text))
+        return "breaking";
+    if (DEPRECATION.test(text))
+        return "deprecation";
+    return "change";
+}
+const ADDITIVE_HEADING = /^\W*(?:added|adds|new|new features?|features?|enhancements?|improvements?|fixed|fixes|bug ?fixes|performance(?: improvements)?|perf|optimi[sz]ations?|docs?|documentation|tests?|testing|internal|chores?|ci|build|refactor(?:ing)?|misc(?:ellaneous)?|other(?: changes)?)\W*$/i;
+/** Context implied by a heading or label, or null when it carries no signal ("### Changed"). */
+export function classifyHeading(heading) {
+    if (/(?<!-)\bbreaking\b|⚠|incompatib|migration|\bmajor changes?\b/i.test(heading))
+        return "breaking";
+    if (/\bremov(?:e|ed|als?)\b|\bapi changes?\b/i.test(heading))
+        return "removal";
+    if (/security|vulnerab/i.test(heading))
+        return "security";
+    if (/deprecat/i.test(heading))
+        return "deprecation";
+    if (ADDITIVE_HEADING.test(heading))
+        return "additive";
+    return null;
+}
+/** Final kind: an explicit heading or bullet parent wins; removal and additive contexts refine the line's wording. */
+export function classifyEntry(text, context) {
+    if (context === "breaking" || context === "security" || context === "deprecation") {
+        // A security line under "Breaking" stays breaking: the heading is the author's own call.
+        return context;
+    }
+    if (context === "removal") {
+        if (META_BREAKING.test(text))
+            return "change";
+        if (EXPLICIT_BREAKING_MARKER.test(text))
+            return "breaking";
+        if (DEPRECATION.test(text) && !/\bremov/i.test(text))
+            return "deprecation";
+        return INTERNAL_CHANGE.test(text) ? "change" : "breaking";
+    }
+    if (context === "additive") {
+        if (!META_BREAKING.test(text) && EXPLICIT_BREAKING_MARKER.test(text))
+            return "breaking";
+        if (SECURITY.test(text))
+            return "security";
+        return DEPRECATION.test(text) ? "deprecation" : "change";
+    }
+    return classifyText(text);
+}

package/dist/live/changelog.d.ts

@@ -0,0 +1,64 @@
+/**
+ * Changelog discovery and parsing for `upgrade_impact`.
+ *
+ * Changelogs follow no schema, so the parser recognises the version-heading
+ * styles actually found in registry archives rather than one spec:
+ *   keep-a-changelog      `## [1.2.3] - 2024-01-01`
+ *   conventional          `## [7.0.0](https://…/compare/…) (2025-06-24)`
+ *   plain / prefixed      `## 1.2.3`, `# v1.2.3 (2024-01-01)`, `### Version 1.2.3`, `## fastembed 5.0.0`
+ *   setext                `1.2.3` underlined with `===` / `---`
+ *   History.md (express)  `1.2.3 / 2020-01-01`
+ * A heading only opens a section when the rest of it looks like a trailer
+ * (date, link, "yanked") — `## Upgrading from 1.x` or `#### Rust 1.70 support`
+ * must stay sub-headings, or a migration guide would split a release in two.
+ *
+ * Entries are bullets, numbered items and loose paragraph lines; indented
+ * continuation lines join the entry above. Fenced code blocks and link
+ * reference definitions are skipped: they are examples and URLs, not changes.
+ */
+import { type EntryKind } from "./changelog-classify.js";
+export interface ChangelogEntry {
+    kind: EntryKind;
+    text: string;
+    /**
+     * The heading, label or parent bullet the entry sits under ("Removed", "remove",
+     * "BREAKING: Functions that accept ..."). Without it "`rt::{Arbiter}` re-exports."
+     * under actix-web's "Removed" reads as harmless, to an agent and to a rater alike.
+     */
+    under?: string;
+}
+export interface ChangelogSection {
+    version: string;
+    date: string | null;
+    entries: ChangelogEntry[];
+}
+/** True for a root-level basename that names a changelog (case-insensitive). */
+export declare function isChangelogName(basename: string): boolean;
+/**
+ * The changelog among archive paths, preferring CHANGELOG over the others and
+ * Markdown over plain text. Null when there is none.
+ */
+export declare function findChangelogFile(paths: Iterable<string>): string | null;
+/**
+ * Version and date from a heading's text, or null when it is not a release
+ * heading. Exported for tests.
+ */
+export declare function parseVersionHeading(raw: string): {
+    version: string;
+    date: string | null;
+} | null;
+/** Parse a changelog into version sections, in document order (usually newest first). */
+export declare function parseChangelog(text: string): ChangelogSection[];
+/** True when `version` lies in (from, to] by semver precedence; unreadable versions are out. */
+export declare function inRange(version: string, from: string, to: string): boolean;
+/**
+ * Sections in (from, to], plus whether the changelog reaches both ends of the
+ * range: its newest section is at or past `to`, and its oldest at or before
+ * `firstInRange` (the earliest release the upgrade crosses). A changelog that
+ * stopped being maintained two majors ago is reported as not covering the
+ * range instead of silently presenting a partial history as the whole one.
+ */
+export declare function selectRange(sections: ChangelogSection[], from: string, to: string, firstInRange: string): {
+    sections: ChangelogSection[];
+    coversRange: boolean;
+};