@vibe-agent-toolkit/cli 0.1.41-rc.7 → 0.1.41

package/dist/utils/issue-rendering.js

@@ -85,6 +85,29 @@ export function formatIssueLines(issue, indent = '') {
     }
     return lines;
 }
+/**
+ * Render the run-level findings section — findings that belong to the whole
+ * invocation rather than to any one skill (ALLOW_UNUSED is the only producer).
+ *
+ * Shared by `vat skills validate` and `vat skills build` so the two commands
+ * name the same concept the same way. Attributing these to a skill is the
+ * misreading the heading exists to prevent: `validation.allow` is declared once
+ * for the package, so an entry that matched nothing is a fact about the run.
+ *
+ * Returns `[]` for an empty set; callers own their surrounding blank lines.
+ */
+export function formatRunIssueLines(runIssues) {
+    if (runIssues.length === 0)
+        return [];
+    const lines = [
+        'Run-level (project config, not any one skill):',
+        `  ${formatIssueSetHeading(runIssues)}:`,
+    ];
+    for (const issue of runIssues) {
+        lines.push(...formatIssueLines(issue, '    '));
+    }
+    return lines;
+}
 /** Identity of an issue for de-duplication across the two post-build channels. */
 function issueIdentity(issue) {
     return [
@@ -124,6 +147,130 @@ export function collectPostBuildIssues(result) {
     }
     return merged;
 }
+/**
+ * Project a set of issues onto its counts: severity buckets plus a per-code tally.
+ *
+ * Severity counting delegates to `countBySeverity` — there must be exactly one
+ * severity collapse in this codebase (see this module's header). That delegation
+ * carries its rule with it: `ignore` findings land in NO severity bucket, because
+ * the adopter's `validation.allow` config silenced them.
+ *
+ * They do still appear in `codes`, because they were emitted — a code the adopter
+ * allow-listed would otherwise be invisible in every summary, which is the one
+ * place a reviewer would look to notice an allow-list that has quietly grown.
+ *
+ * `codes` is ordered descending by count, ties broken by code name ascending.
+ * Insertion order is the YAML serialization order, so the ordering is the feature:
+ * the first row names the dominant finding without the reader tallying anything.
+ */
+export function summarizeFindings(issues) {
+    const counts = countBySeverity(issues);
+    const tally = new Map();
+    for (const issue of issues) {
+        const code = String(issue.code);
+        tally.set(code, (tally.get(code) ?? 0) + 1);
+    }
+    // `Object.fromEntries` over a sorted array, rather than keyed assignment into a
+    // record: it preserves the sort as insertion order without a dynamic index write.
+    const codes = Object.fromEntries([...tally.entries()].sort(([codeA, countA], [codeB, countB]) => countB - countA || codeA.localeCompare(codeB)));
+    return {
+        ...(counts.errors > 0 ? { errors: counts.errors } : {}),
+        ...(counts.warnings > 0 ? { warnings: counts.warnings } : {}),
+        ...(counts.info > 0 ? { info: counts.info } : {}),
+        codes,
+    };
+}
+/**
+ * The findings a human-facing report renders IN FULL at a given verbosity.
+ *
+ * One policy, spelled once, because the three verbs that report findings —
+ * `vat skills validate`, `vat skills build`, `vat audit` — each grew their own
+ * answer and landed on three different ones: validate collapsed every severity
+ * into a per-skill count line, while build and audit printed every occurrence.
+ * On a 90-skill adopter that read as 804 lines against 6,552 and 26,480, for
+ * the same corpus.
+ *
+ * The rule is asymmetric on purpose, and the asymmetry is the whole point:
+ *
+ * - **`error` is always rendered in full**, at every verbosity. An error is what
+ *   failed the run, there are few of them, and every one is actionable. Collapsing
+ *   an error into a count means the reader must re-run with a flag to learn what
+ *   broke — which is strictly worse than the verbosity it was meant to fix. This
+ *   is the direction the module header warns about: a collapse that hides the
+ *   thing you needed produces silence, not a false alarm.
+ * - **`warning` and `info` collapse into the caller's summary line** unless
+ *   `verbose`. These are the high-cardinality findings (one adopter skill carries
+ *   348 `LINK_DROPPED_BY_DEPTH` warnings alone), and a count plus a per-code tally
+ *   answers "what is going on here?" without the reader scrolling past 348 near-
+ *   identical blocks.
+ * - **`ignore` never renders**, at any verbosity: the adopter's `validation.allow`
+ *   config silenced it deliberately. It stays visible in `summarizeFindings`'
+ *   `codes` tally, which is where a quietly-growing allow-list is noticed.
+ *
+ * This decides only WHICH findings are rendered, never HOW. Each lane keeps its
+ * own heading and summary line — those legitimately differ — so this can be shared
+ * without forcing one layout onto three commands.
+ *
+ * The machine-readable document is NOT filtered by this. `vat audit`'s YAML and
+ * `vat skills build`'s `issueCounts` carry every finding at every verbosity;
+ * anything else would silently break consumers that parse them.
+ */
+export function issuesToRenderAtVerbosity(issues, verbose) {
+    return issues.filter((issue) => issue.severity !== 'ignore' && (verbose || issue.severity === 'error'));
+}
+/**
+ * How many findings `--verbose` would render that this verbosity does not.
+ *
+ * Derived from {@link issuesToRenderAtVerbosity} rather than re-stating its rule,
+ * so the number a report quotes can never contradict the policy that produced it.
+ * Allow-suppressed findings are in neither set, so they are correctly not counted
+ * as "hidden by verbosity" — they were hidden by the adopter's own config.
+ */
+export function countCollapsedFindings(issues, verbose) {
+    return (issuesToRenderAtVerbosity(issues, true).length
+        - issuesToRenderAtVerbosity(issues, verbose).length);
+}
+/**
+ * The one sentence that tells a reader findings exist that they cannot see.
+ *
+ * A collapsed block is otherwise a heading with nothing beneath it — the
+ * reassuring silence this module's header warns about. `vat audit` has printed
+ * this line all along and `vat skills build` did not; one helper rather than a
+ * second phrasing of the same idea, because two wordings for one concept is how
+ * the severity collapse came to be spelled five different ways.
+ *
+ * `report` names the verb whose YAML the reader should open ("audit", "build").
+ * That clause is only honest for a command that publishes full `issues:` arrays;
+ * do not pass a report name for a verb that publishes counts alone.
+ *
+ * Returns `undefined` when nothing was collapsed, so callers print nothing rather
+ * than a "0 findings not shown" line.
+ */
+export function formatCollapsedFindingsHint(collapsed, report) {
+    if (collapsed <= 0)
+        return undefined;
+    return (`\n${collapsed} warning/info finding(s) not shown — re-run with --verbose, `
+        + `or read this ${report}'s YAML report on stdout, which lists every finding.`);
+}
+/**
+ * How many files LINK TRAVERSAL put in a bundle, in prose: `1 file`, `11 files`.
+ *
+ * Deliberately not called the bundle's file count, which is what it reads like and
+ * is not: `files.dependencies` carries only what the link-graph walk discovered, so
+ * every file `files:` copied in — each glob match, plus any explicit entry the walk
+ * had not already bundled — is absent from the total. A bundle holding SKILL.md, one
+ * linked doc and one declared artifact prints `2 files`. That undercount is issue
+ * #177 and is deliberately NOT patched here; this wording is only the part that can
+ * be made true today, so nobody reads the number as an inventory of the output.
+ *
+ * The `+ 1` is the bundle's root `SKILL.md`, which `files.dependencies` does not
+ * list — spelled once here rather than at each progress line, so the two build
+ * lanes cannot come to disagree about whether the root document counts.
+ */
+export function formatPackagedFileCount(result) {
+    const total = result.files.dependencies.length + 1;
+    return `${total} file${total === 1 ? '' : 's'}`;
+}
 /** Sum severity counts across lanes (per-skill → per-plugin → per-run). */
 export function sumSeverityCounts(counts) {
     return counts.reduce((acc, c) => ({

package/dist/utils/issue-rendering.js.map

@@ -1 +1 @@
-{"version":3,"file":"issue-rendering.js","sourceRoot":"","sources":["../../src/utils/issue-rendering.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AAEH,OAAO,EACL,eAAe,GAGhB,MAAM,kCAAkC,CAAC;AAG1C,OAAO,EAAE,iBAAiB,EAAE,MAAM,mBAAmB,CAAC;AAEtD;;;;;GAKG;AACH,MAAM,eAAe,GAAgD;IACnE,KAAK,EAAE,OAAO;IACd,OAAO,EAAE,SAAS;IAClB,IAAI,EAAE,MAAM;IACZ,MAAM,EAAE,SAAS;CAClB,CAAC;AAEF,gDAAgD;AAChD,MAAM,UAAU,aAAa,CAAC,QAAqC;IACjE,OAAO,eAAe,CAAC,QAAQ,CAAC,CAAC;AACnC,CAAC;AAED;;;;;;GAMG;AACH,MAAM,UAAU,uBAAuB,CAAC,MAAsB;IAC5D,MAAM,KAAK,GAAa,EAAE,CAAC;IAC3B,IAAI,MAAM,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QACtB,KAAK,CAAC,IAAI,CAAC,GAAG,MAAM,CAAC,MAAM,SAAS,MAAM,CAAC,MAAM,KAAK,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,GAAG,EAAE,CAAC,CAAC;IACxE,CAAC;IACD,IAAI,MAAM,CAAC,QAAQ,GAAG,CAAC,EAAE,CAAC;QACxB,KAAK,CAAC,IAAI,CAAC,GAAG,MAAM,CAAC,QAAQ,WAAW,MAAM,CAAC,QAAQ,KAAK,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,GAAG,EAAE,CAAC,CAAC;IAC9E,CAAC;IACD,IAAI,MAAM,CAAC,IAAI,GAAG,CAAC,EAAE,CAAC;QACpB,KAAK,CAAC,IAAI,CAAC,GAAG,MAAM,CAAC,IAAI,OAAO,CAAC,CAAC;IACpC,CAAC;IACD,OAAO,KAAK,CAAC,MAAM,KAAK,CAAC,CAAC,CAAC,CAAC,aAAa,CAAC,CAAC,CAAC,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAC/D,CAAC;AAED;;;;;;GAMG;AACH,MAAM,UAAU,qBAAqB,CACnC,MAAkC,EAClC,IAAa;IAEb,MAAM,SAAS,GAAG,IAAI,KAAK,SAAS,IAAI,IAAI,KAAK,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,GAAG,IAAI,GAAG,CAAC;IACtE,MAAM,KAAK,GAAG,MAAM,CAAC,MAAM,CAAC;IAC5B,MAAM,SAAS,GAAG,uBAAuB,CAAC,eAAe,CAAC,MAAM,CAAC,CAAC,CAAC;IACnE,OAAO,GAAG,KAAK,IAAI,SAAS,QAAQ,KAAK,KAAK,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,GAAG,KAAK,SAAS,GAAG,CAAC;AAC9E,CAAC;AAED;;;;;GAKG;AACH,MAAM,UAAU,gBAAgB,CAAC,KAAsB,EAAE,MAAM,GAAG,EAAE;IAClE,MAAM,KAAK,GAAG;QACZ,GAAG,MAAM,IAAI,aAAa,CAAC,KAAK,CAAC,QAAQ,CAAC,MAAM,MAAM,CAAC,KAAK,CAAC,IAAI,CAAC,KAAK,MAAM,CAAC,KAAK,CAAC,OAAO,CAAC,EAAE;KAC/F,CAAC;IACF,MAAM,MAAM,GAAG,iBAAiB,CAAC,KAAK,CAAC,CAAC;IACxC,IAAI,MAAM,KAAK,SAAS,EAAE,CAAC;QACzB,KAAK,CAAC,IAAI,CAAC,GAAG,MAAM,eAAe,MAAM,EAAE,CAAC,CAAC;IAC/C,CAAC;IACD,IAAI,KAAK,CAAC,GAAG,EAAE,CAAC;QACd,KAAK,CAAC,IAAI,CAAC,GAAG,MAAM,UAAU,MAAM,CAAC,KAAK,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC;IACrD,CAAC;IACD,OAAO,KAAK,CAAC;AACf,CAAC;AAED,kFAAkF;AAClF,SAAS,aAAa,CAAC,KAAsB;IAC3C,OAAO;QACL,KAAK,CAAC,IAAI;QACV,KAAK,CAAC,QAAQ;QACd,KAAK,CAAC,QAAQ,IAAI,EAAE;QACpB,KAAK,CAAC,IAAI,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,MAAM,CAAC,KAAK,CAAC,IAAI,CAAC;QAClD,KAAK,CAAC,KAAK,IAAI,EAAE;QACjB,KAAK,CAAC,OAAO;KACd,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AACf,CAAC;AAED;;;;;;;;;;;;GAYG;AACH,MAAM,UAAU,sBAAsB,CAAC,MAA0B;IAC/D,MAAM,IAAI,GAAG,IAAI,GAAG,EAAU,CAAC;IAC/B,MAAM,MAAM,GAAsB,EAAE,CAAC;IACrC,KAAK,MAAM,KAAK,IAAI;QAClB,GAAG,CAAC,MAAM,CAAC,eAAe,IAAI,EAAE,CAAC;QACjC,GAAG,CAAC,MAAM,CAAC,mBAAmB,EAAE,SAAS,IAAI,EAAE,CAAC;KACjD,EAAE,CAAC;QACF,MAAM,QAAQ,GAAG,aAAa,CAAC,KAAK,CAAC,CAAC;QACtC,IAAI,IAAI,CAAC,GAAG,CAAC,QAAQ,CAAC;YAAE,SAAS;QACjC,IAAI,CAAC,GAAG,CAAC,QAAQ,CAAC,CAAC;QACnB,MAAM,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;IACrB,CAAC;IACD,OAAO,MAAM,CAAC;AAChB,CAAC;AAED,2EAA2E;AAC3E,MAAM,UAAU,iBAAiB,CAAC,MAAiC;IACjE,OAAO,MAAM,CAAC,MAAM,CAClB,CAAC,GAAG,EAAE,CAAC,EAAE,EAAE,CAAC,CAAC;QACX,MAAM,EAAE,GAAG,CAAC,MAAM,GAAG,CAAC,CAAC,MAAM;QAC7B,QAAQ,EAAE,GAAG,CAAC,QAAQ,GAAG,CAAC,CAAC,QAAQ;QACnC,IAAI,EAAE,GAAG,CAAC,IAAI,GAAG,CAAC,CAAC,IAAI;KACxB,CAAC,EACF,EAAE,MAAM,EAAE,CAAC,EAAE,QAAQ,EAAE,CAAC,EAAE,IAAI,EAAE,CAAC,EAAE,CACpC,CAAC;AACJ,CAAC"}
+{"version":3,"file":"issue-rendering.js","sourceRoot":"","sources":["../../src/utils/issue-rendering.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AAEH,OAAO,EACL,eAAe,GAGhB,MAAM,kCAAkC,CAAC;AAG1C,OAAO,EAAE,iBAAiB,EAAE,MAAM,mBAAmB,CAAC;AAEtD;;;;;GAKG;AACH,MAAM,eAAe,GAAgD;IACnE,KAAK,EAAE,OAAO;IACd,OAAO,EAAE,SAAS;IAClB,IAAI,EAAE,MAAM;IACZ,MAAM,EAAE,SAAS;CAClB,CAAC;AAEF,gDAAgD;AAChD,MAAM,UAAU,aAAa,CAAC,QAAqC;IACjE,OAAO,eAAe,CAAC,QAAQ,CAAC,CAAC;AACnC,CAAC;AAED;;;;;;GAMG;AACH,MAAM,UAAU,uBAAuB,CAAC,MAAsB;IAC5D,MAAM,KAAK,GAAa,EAAE,CAAC;IAC3B,IAAI,MAAM,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QACtB,KAAK,CAAC,IAAI,CAAC,GAAG,MAAM,CAAC,MAAM,SAAS,MAAM,CAAC,MAAM,KAAK,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,GAAG,EAAE,CAAC,CAAC;IACxE,CAAC;IACD,IAAI,MAAM,CAAC,QAAQ,GAAG,CAAC,EAAE,CAAC;QACxB,KAAK,CAAC,IAAI,CAAC,GAAG,MAAM,CAAC,QAAQ,WAAW,MAAM,CAAC,QAAQ,KAAK,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,GAAG,EAAE,CAAC,CAAC;IAC9E,CAAC;IACD,IAAI,MAAM,CAAC,IAAI,GAAG,CAAC,EAAE,CAAC;QACpB,KAAK,CAAC,IAAI,CAAC,GAAG,MAAM,CAAC,IAAI,OAAO,CAAC,CAAC;IACpC,CAAC;IACD,OAAO,KAAK,CAAC,MAAM,KAAK,CAAC,CAAC,CAAC,CAAC,aAAa,CAAC,CAAC,CAAC,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AAC/D,CAAC;AAED;;;;;;GAMG;AACH,MAAM,UAAU,qBAAqB,CACnC,MAAkC,EAClC,IAAa;IAEb,MAAM,SAAS,GAAG,IAAI,KAAK,SAAS,IAAI,IAAI,KAAK,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,GAAG,IAAI,GAAG,CAAC;IACtE,MAAM,KAAK,GAAG,MAAM,CAAC,MAAM,CAAC;IAC5B,MAAM,SAAS,GAAG,uBAAuB,CAAC,eAAe,CAAC,MAAM,CAAC,CAAC,CAAC;IACnE,OAAO,GAAG,KAAK,IAAI,SAAS,QAAQ,KAAK,KAAK,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,GAAG,KAAK,SAAS,GAAG,CAAC;AAC9E,CAAC;AAED;;;;;GAKG;AACH,MAAM,UAAU,gBAAgB,CAAC,KAAsB,EAAE,MAAM,GAAG,EAAE;IAClE,MAAM,KAAK,GAAG;QACZ,GAAG,MAAM,IAAI,aAAa,CAAC,KAAK,CAAC,QAAQ,CAAC,MAAM,MAAM,CAAC,KAAK,CAAC,IAAI,CAAC,KAAK,MAAM,CAAC,KAAK,CAAC,OAAO,CAAC,EAAE;KAC/F,CAAC;IACF,MAAM,MAAM,GAAG,iBAAiB,CAAC,KAAK,CAAC,CAAC;IACxC,IAAI,MAAM,KAAK,SAAS,EAAE,CAAC;QACzB,KAAK,CAAC,IAAI,CAAC,GAAG,MAAM,eAAe,MAAM,EAAE,CAAC,CAAC;IAC/C,CAAC;IACD,IAAI,KAAK,CAAC,GAAG,EAAE,CAAC;QACd,KAAK,CAAC,IAAI,CAAC,GAAG,MAAM,UAAU,MAAM,CAAC,KAAK,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC;IACrD,CAAC;IACD,OAAO,KAAK,CAAC;AACf,CAAC;AAED;;;;;;;;;;GAUG;AACH,MAAM,UAAU,mBAAmB,CAAC,SAAqC;IACvE,IAAI,SAAS,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,EAAE,CAAC;IACtC,MAAM,KAAK,GAAG;QACZ,gDAAgD;QAChD,KAAK,qBAAqB,CAAC,SAAS,CAAC,GAAG;KACzC,CAAC;IACF,KAAK,MAAM,KAAK,IAAI,SAAS,EAAE,CAAC;QAC9B,KAAK,CAAC,IAAI,CAAC,GAAG,gBAAgB,CAAC,KAAK,EAAE,MAAM,CAAC,CAAC,CAAC;IACjD,CAAC;IACD,OAAO,KAAK,CAAC;AACf,CAAC;AAED,kFAAkF;AAClF,SAAS,aAAa,CAAC,KAAsB;IAC3C,OAAO;QACL,KAAK,CAAC,IAAI;QACV,KAAK,CAAC,QAAQ;QACd,KAAK,CAAC,QAAQ,IAAI,EAAE;QACpB,KAAK,CAAC,IAAI,KAAK,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,MAAM,CAAC,KAAK,CAAC,IAAI,CAAC;QAClD,KAAK,CAAC,KAAK,IAAI,EAAE;QACjB,KAAK,CAAC,OAAO;KACd,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;AACf,CAAC;AAED;;;;;;;;;;;;GAYG;AACH,MAAM,UAAU,sBAAsB,CAAC,MAA0B;IAC/D,MAAM,IAAI,GAAG,IAAI,GAAG,EAAU,CAAC;IAC/B,MAAM,MAAM,GAAsB,EAAE,CAAC;IACrC,KAAK,MAAM,KAAK,IAAI;QAClB,GAAG,CAAC,MAAM,CAAC,eAAe,IAAI,EAAE,CAAC;QACjC,GAAG,CAAC,MAAM,CAAC,mBAAmB,EAAE,SAAS,IAAI,EAAE,CAAC;KACjD,EAAE,CAAC;QACF,MAAM,QAAQ,GAAG,aAAa,CAAC,KAAK,CAAC,CAAC;QACtC,IAAI,IAAI,CAAC,GAAG,CAAC,QAAQ,CAAC;YAAE,SAAS;QACjC,IAAI,CAAC,GAAG,CAAC,QAAQ,CAAC,CAAC;QACnB,MAAM,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;IACrB,CAAC;IACD,OAAO,MAAM,CAAC;AAChB,CAAC;AA0BD;;;;;;;;;;;;;;;GAeG;AACH,MAAM,UAAU,iBAAiB,CAAC,MAAkC;IAClE,MAAM,MAAM,GAAG,eAAe,CAAC,MAAM,CAAC,CAAC;IAEvC,MAAM,KAAK,GAAG,IAAI,GAAG,EAAkB,CAAC;IACxC,KAAK,MAAM,KAAK,IAAI,MAAM,EAAE,CAAC;QAC3B,MAAM,IAAI,GAAG,MAAM,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;QAChC,KAAK,CAAC,GAAG,CAAC,IAAI,EAAE,CAAC,KAAK,CAAC,GAAG,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC;IAC9C,CAAC;IAED,gFAAgF;IAChF,kFAAkF;IAClF,MAAM,KAAK,GAAG,MAAM,CAAC,WAAW,CAC9B,CAAC,GAAG,KAAK,CAAC,OAAO,EAAE,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,KAAK,EAAE,MAAM,CAAC,EAAE,CAAC,KAAK,EAAE,MAAM,CAAC,EAAE,EAAE,CAC7D,MAAM,GAAG,MAAM,IAAI,KAAK,CAAC,aAAa,CAAC,KAAK,CAAC,CAC9C,CACF,CAAC;IAEF,OAAO;QACL,GAAG,CAAC,MAAM,CAAC,MAAM,GAAG,CAAC,CAAC,CAAC,CAAC,EAAE,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;QACvD,GAAG,CAAC,MAAM,CAAC,QAAQ,GAAG,CAAC,CAAC,CAAC,CAAC,EAAE,QAAQ,EAAE,MAAM,CAAC,QAAQ,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;QAC7D,GAAG,CAAC,MAAM,CAAC,IAAI,GAAG,CAAC,CAAC,CAAC,CAAC,EAAE,IAAI,EAAE,MAAM,CAAC,IAAI,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;QACjD,KAAK;KACN,CAAC;AACJ,CAAC;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAkCG;AACH,MAAM,UAAU,yBAAyB,CACvC,MAAkC,EAClC,OAAgB;IAEhB,OAAO,MAAM,CAAC,MAAM,CAClB,CAAC,KAAK,EAAE,EAAE,CAAC,KAAK,CAAC,QAAQ,KAAK,QAAQ,IAAI,CAAC,OAAO,IAAI,KAAK,CAAC,QAAQ,KAAK,OAAO,CAAC,CAClF,CAAC;AACJ,CAAC;AAED;;;;;;;GAOG;AACH,MAAM,UAAU,sBAAsB,CACpC,MAAkC,EAClC,OAAgB;IAEhB,OAAO,CACL,yBAAyB,CAAC,MAAM,EAAE,IAAI,CAAC,CAAC,MAAM;UAC5C,yBAAyB,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC,MAAM,CACpD,CAAC;AACJ,CAAC;AAED;;;;;;;;;;;;;;;GAeG;AACH,MAAM,UAAU,2BAA2B,CACzC,SAAiB,EACjB,MAAc;IAEd,IAAI,SAAS,IAAI,CAAC;QAAE,OAAO,SAAS,CAAC;IACrC,OAAO,CACL,KAAK,SAAS,8DAA8D;UAC1E,gBAAgB,MAAM,sDAAsD,CAC/E,CAAC;AACJ,CAAC;AAED;;;;;;;;;;;;;;GAcG;AACH,MAAM,UAAU,uBAAuB,CAAC,MAA0B;IAChE,MAAM,KAAK,GAAG,MAAM,CAAC,KAAK,CAAC,YAAY,CAAC,MAAM,GAAG,CAAC,CAAC;IACnD,OAAO,GAAG,KAAK,QAAQ,KAAK,KAAK,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,GAAG,EAAE,CAAC;AAClD,CAAC;AAED,2EAA2E;AAC3E,MAAM,UAAU,iBAAiB,CAAC,MAAiC;IACjE,OAAO,MAAM,CAAC,MAAM,CAClB,CAAC,GAAG,EAAE,CAAC,EAAE,EAAE,CAAC,CAAC;QACX,MAAM,EAAE,GAAG,CAAC,MAAM,GAAG,CAAC,CAAC,MAAM;QAC7B,QAAQ,EAAE,GAAG,CAAC,QAAQ,GAAG,CAAC,CAAC,QAAQ;QACnC,IAAI,EAAE,GAAG,CAAC,IAAI,GAAG,CAAC,CAAC,IAAI;KACxB,CAAC,EACF,EAAE,MAAM,EAAE,CAAC,EAAE,QAAQ,EAAE,CAAC,EAAE,IAAI,EAAE,CAAC,EAAE,CACpC,CAAC;AACJ,CAAC"}

package/dist/utils/issue-severity.d.ts

@@ -0,0 +1,51 @@
+/**
+ * The ONE place a `validation.severity` override is applied to already-materialized
+ * findings.
+ *
+ * Every lane that reports findings has to answer the same question — "the adopter
+ * configured this code, so what severity does this issue actually carry?" — and the
+ * lanes answered it differently for as long as each owned its own copy. Measured on
+ * one PR, across a 3-lane × 7-cell matrix driven end to end:
+ *
+ *  - `vat verify`'s packaged-content phase resolved properly, both directions.
+ *  - `vat audit` computed the merged override map correctly and then consulted it
+ *    for exactly one value (`!== 'ignore'`), so `ignore` worked and `error` /
+ *    `warning` / `info` were silent no-ops. An adopter promoting a code to `error`
+ *    saw `severity: warning`, `errors: 0`, `status: warning`.
+ *  - `vat verify`'s marketplace phase never met a resolver at all.
+ *
+ * That is not three bugs, it is one missing module. Anything that re-severities
+ * findings imports this; nobody writes a fourth copy. Same rule as
+ * `resolveAssetReference` and `resolveSkillReference` in CLAUDE.md.
+ */
+import { type ValidationIssue } from '@vibe-agent-toolkit/agent-schema';
+/** A `validation.severity` map as it appears in config, or nothing. */
+export interface SeverityOverrides {
+    severity?: Record<string, string> | undefined;
+}
+/**
+ * Re-severity findings against a `validation.severity` map, dropping the codes
+ * resolved to `ignore`.
+ *
+ * **Resolution, not just suppression.** Dropping `ignore` codes is the half that is
+ * easy to write and the half that looks finished: the documented opt-out starts
+ * working, so the escape hatch appears fixed. The promote direction is the half that
+ * gets forgotten, and it is the one an adopter reaches for when they want a code to
+ * fail their build. A filter that only knows how to delete answers "can I silence
+ * this?" and silently ignores "can I enforce this?".
+ *
+ * Note what each consumer does with the result. Status is re-derived from the
+ * returned severities by every caller, so a promotion moves the reported status.
+ * Whether it also moves the process exit code is the CALLER's contract, not this
+ * function's — `vat verify` derives its exit code from severity, while `vat audit`
+ * is advisory and its exit code is tracked separately. Do not "fix" that here.
+ *
+ * An un-overridden code short-circuits rather than round-tripping through
+ * {@link resolveSeverity}. Two reasons, and the second is load-bearing: the answer
+ * would be the registry default, which is already the severity the issue carries
+ * (`materializeIssue` built it from that same registry); and `resolveSeverity`
+ * indexes `CODE_REGISTRY` unguarded, so handing it a non-registry code would throw
+ * rather than pass the issue through.
+ */
+export declare function resolveIssueSeverity(issues: readonly ValidationIssue[], validation: SeverityOverrides | undefined): ValidationIssue[];
+//# sourceMappingURL=issue-severity.d.ts.map

package/dist/utils/issue-severity.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"issue-severity.d.ts","sourceRoot":"","sources":["../../src/utils/issue-severity.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;GAmBG;AAEH,OAAO,EAAmC,KAAK,eAAe,EAAE,MAAM,kCAAkC,CAAC;AAEzG,uEAAuE;AACvE,MAAM,WAAW,iBAAiB;IAChC,QAAQ,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,GAAG,SAAS,CAAC;CAC/C;AAED;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,wBAAgB,oBAAoB,CAClC,MAAM,EAAE,SAAS,eAAe,EAAE,EAClC,UAAU,EAAE,iBAAiB,GAAG,SAAS,GACxC,eAAe,EAAE,CAenB"}

package/dist/utils/issue-severity.js

@@ -0,0 +1,63 @@
+/**
+ * The ONE place a `validation.severity` override is applied to already-materialized
+ * findings.
+ *
+ * Every lane that reports findings has to answer the same question — "the adopter
+ * configured this code, so what severity does this issue actually carry?" — and the
+ * lanes answered it differently for as long as each owned its own copy. Measured on
+ * one PR, across a 3-lane × 7-cell matrix driven end to end:
+ *
+ *  - `vat verify`'s packaged-content phase resolved properly, both directions.
+ *  - `vat audit` computed the merged override map correctly and then consulted it
+ *    for exactly one value (`!== 'ignore'`), so `ignore` worked and `error` /
+ *    `warning` / `info` were silent no-ops. An adopter promoting a code to `error`
+ *    saw `severity: warning`, `errors: 0`, `status: warning`.
+ *  - `vat verify`'s marketplace phase never met a resolver at all.
+ *
+ * That is not three bugs, it is one missing module. Anything that re-severities
+ * findings imports this; nobody writes a fourth copy. Same rule as
+ * `resolveAssetReference` and `resolveSkillReference` in CLAUDE.md.
+ */
+import { resolveSeverity } from '@vibe-agent-toolkit/agent-schema';
+/**
+ * Re-severity findings against a `validation.severity` map, dropping the codes
+ * resolved to `ignore`.
+ *
+ * **Resolution, not just suppression.** Dropping `ignore` codes is the half that is
+ * easy to write and the half that looks finished: the documented opt-out starts
+ * working, so the escape hatch appears fixed. The promote direction is the half that
+ * gets forgotten, and it is the one an adopter reaches for when they want a code to
+ * fail their build. A filter that only knows how to delete answers "can I silence
+ * this?" and silently ignores "can I enforce this?".
+ *
+ * Note what each consumer does with the result. Status is re-derived from the
+ * returned severities by every caller, so a promotion moves the reported status.
+ * Whether it also moves the process exit code is the CALLER's contract, not this
+ * function's — `vat verify` derives its exit code from severity, while `vat audit`
+ * is advisory and its exit code is tracked separately. Do not "fix" that here.
+ *
+ * An un-overridden code short-circuits rather than round-tripping through
+ * {@link resolveSeverity}. Two reasons, and the second is load-bearing: the answer
+ * would be the registry default, which is already the severity the issue carries
+ * (`materializeIssue` built it from that same registry); and `resolveSeverity`
+ * indexes `CODE_REGISTRY` unguarded, so handing it a non-registry code would throw
+ * rather than pass the issue through.
+ */
+export function resolveIssueSeverity(issues, validation) {
+    const overrides = validation?.severity;
+    if (overrides === undefined)
+        return [...issues];
+    const resolved = [];
+    for (const issue of issues) {
+        if (!(issue.code in overrides)) {
+            resolved.push(issue);
+            continue;
+        }
+        const severity = resolveSeverity(issue.code, { severity: overrides });
+        if (severity === 'ignore')
+            continue;
+        resolved.push(severity === issue.severity ? issue : { ...issue, severity });
+    }
+    return resolved;
+}
+//# sourceMappingURL=issue-severity.js.map

package/dist/utils/issue-severity.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"issue-severity.js","sourceRoot":"","sources":["../../src/utils/issue-severity.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;GAmBG;AAEH,OAAO,EAAkB,eAAe,EAAwB,MAAM,kCAAkC,CAAC;AAOzG;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,MAAM,UAAU,oBAAoB,CAClC,MAAkC,EAClC,UAAyC;IAEzC,MAAM,SAAS,GAAG,UAAU,EAAE,QAAQ,CAAC;IACvC,IAAI,SAAS,KAAK,SAAS;QAAE,OAAO,CAAC,GAAG,MAAM,CAAC,CAAC;IAEhD,MAAM,QAAQ,GAAsB,EAAE,CAAC;IACvC,KAAK,MAAM,KAAK,IAAI,MAAM,EAAE,CAAC;QAC3B,IAAI,CAAC,CAAC,KAAK,CAAC,IAAI,IAAI,SAAS,CAAC,EAAE,CAAC;YAC/B,QAAQ,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;YACrB,SAAS;QACX,CAAC;QACD,MAAM,QAAQ,GAAG,eAAe,CAAC,KAAK,CAAC,IAAiB,EAAE,EAAE,QAAQ,EAAE,SAAS,EAAE,CAAC,CAAC;QACnF,IAAI,QAAQ,KAAK,QAAQ;YAAE,SAAS;QACpC,QAAQ,CAAC,IAAI,CAAC,QAAQ,KAAK,KAAK,CAAC,QAAQ,CAAC,CAAC,CAAC,KAAK,CAAC,CAAC,CAAC,EAAE,GAAG,KAAK,EAAE,QAAQ,EAAE,CAAC,CAAC;IAC9E,CAAC;IACD,OAAO,QAAQ,CAAC;AAClB,CAAC"}

package/dist/utils/output.d.ts

@@ -2,6 +2,60 @@
  * Output utilities for structured data
  * YAML output on stdout, logs on stderr
  */
+/**
+ * Write `content` to stdout SYNCHRONOUSLY, in a loop until every byte is handed
+ * over.
+ *
+ * `process.stdout.write` is asynchronous whenever stdout is a PIPE, and every
+ * command in this CLI calls `process.exit()` the moment it has written its
+ * summary. `process.exit` does not drain a pending write, so everything past the
+ * first pipe buffer (64 KB on Linux/macOS) was silently discarded — with exit
+ * code 0, so nothing signalled the loss. An interactive TTY is unbuffered and
+ * looked perfect, which is why this survived: it only bites the piped consumer
+ * this CLI's own docs recommend (`vat command | jq .status`).
+ *
+ * `writeSync` cannot return before the bytes reach the pipe, so `process.exit`
+ * has nothing left to lose. The loop is required because a single `writeSync`
+ * may accept fewer bytes than offered.
+ *
+ * This is the same fix `help-loader.ts` applied to `--help --verbose`; it lives
+ * here so both callers share one implementation rather than two copies of a
+ * subtle loop.
+ */
+export declare function writeStdoutSync(content: string): void;
+/**
+ * A synchronous write primitive: `(buffer, offset, length) => bytesWritten`.
+ *
+ * Matches `fs.writeSync`'s shape so the real one drops straight in, while a test
+ * can supply one that returns short counts or throws EAGAIN on demand.
+ */
+export type SyncWriter = (buffer: Buffer, offset: number, length: number) => number;
+export interface WriteAllSyncOptions {
+    /** Override {@link MAX_CONSECUTIVE_EAGAIN_RETRIES}. Tests use a tiny budget. */
+    maxConsecutiveRetries?: number;
+    /** Override the backoff. Tests pass a no-op to drive the bound instantly. */
+    waitBetweenRetries?: (consecutiveRetries: number) => void;
+}
+/**
+ * Drive `write` until every byte of `buffer` has been accepted.
+ *
+ * Split out from {@link writeStdoutSync} because the things that make this loop
+ * necessary — a short write, and an EAGAIN retry on a momentarily-full
+ * non-blocking pipe — are both hard to provoke on a real fd and trivial to state
+ * against an injected writer. The fd-1 wiring stays a one-liner above, so the
+ * only part with branching logic is the part that can be unit tested.
+ *
+ * The EAGAIN retry is BOUNDED. A reader that stops draining without closing the
+ * pipe (`vat … | consumer-that-wanders-off`) leaves it permanently full, so
+ * every retry raises EAGAIN forever; an unbounded loop turns that into a hang
+ * with no output and no error — strictly worse than the truncation this replaced.
+ * Exhausting the budget throws, so the failure is visible and the exit code is
+ * non-zero, rather than the bytes quietly going missing.
+ *
+ * @throws the underlying error for any failure other than EAGAIN; an `Error`
+ * naming the unwritten remainder when the retry budget is exhausted.
+ */
+export declare function writeAllSync(write: SyncWriter, buffer: Buffer, options?: WriteAllSyncOptions): void;
 /**
  * Write a single YAML document to stdout, opened with `---`.
  *
@@ -22,11 +76,6 @@
  * @param data - Data to serialize as YAML
  */
 export declare function writeYamlOutput(data: unknown): void;
-/**
- * Flush stdout before writing to stderr
- * Prevents output corruption when streams are merged
- */
-export declare function flushStdout(): Promise<void>;
 /**
  * Write a test-format finding to stderr.
  *

package/dist/utils/output.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"output.d.ts","sourceRoot":"","sources":["../../src/utils/output.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAIH;;;;;;;;;;;;;;;;;;GAkBG;AACH,wBAAgB,eAAe,CAAC,IAAI,EAAE,OAAO,GAAG,IAAI,CAOnD;AAED;;;GAGG;AACH,wBAAsB,WAAW,IAAI,OAAO,CAAC,IAAI,CAAC,CAQjD;AAED;;;;;;;;;;GAUG;AACH,wBAAgB,oBAAoB,CAClC,IAAI,EAAE,MAAM,EACZ,IAAI,EAAE,MAAM,EACZ,MAAM,EAAE,MAAM,EACd,QAAQ,EAAE,MAAM,EAChB,OAAO,EAAE,MAAM,GACd,IAAI,CAEN"}
+{"version":3,"file":"output.d.ts","sourceRoot":"","sources":["../../src/utils/output.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAMH;;;;;;;;;;;;;;;;;;;GAmBG;AACH,wBAAgB,eAAe,CAAC,OAAO,EAAE,MAAM,GAAG,IAAI,CAKrD;AAED;;;;;GAKG;AACH,MAAM,MAAM,UAAU,GAAG,CAAC,MAAM,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,KAAK,MAAM,CAAC;AAoCpF,MAAM,WAAW,mBAAmB;IAClC,gFAAgF;IAChF,qBAAqB,CAAC,EAAE,MAAM,CAAC;IAC/B,6EAA6E;IAC7E,kBAAkB,CAAC,EAAE,CAAC,kBAAkB,EAAE,MAAM,KAAK,IAAI,CAAC;CAC3D;AAED;;;;;;;;;;;;;;;;;;GAkBG;AACH,wBAAgB,YAAY,CAC1B,KAAK,EAAE,UAAU,EACjB,MAAM,EAAE,MAAM,EACd,OAAO,GAAE,mBAAwB,GAChC,IAAI,CA+BN;AAED;;;;;;;;;;;;;;;;;;GAkBG;AACH,wBAAgB,eAAe,CAAC,IAAI,EAAE,OAAO,GAAG,IAAI,CAWnD;AAED;;;;;;;;;;GAUG;AACH,wBAAgB,oBAAoB,CAClC,IAAI,EAAE,MAAM,EACZ,IAAI,EAAE,MAAM,EACZ,MAAM,EAAE,MAAM,EACd,QAAQ,EAAE,MAAM,EAChB,OAAO,EAAE,MAAM,GACd,IAAI,CAEN"}

package/dist/utils/output.js

@@ -2,7 +2,111 @@
  * Output utilities for structured data
  * YAML output on stdout, logs on stderr
  */
+import { writeSync } from 'node:fs';
 import * as yaml from 'yaml';
+/**
+ * Write `content` to stdout SYNCHRONOUSLY, in a loop until every byte is handed
+ * over.
+ *
+ * `process.stdout.write` is asynchronous whenever stdout is a PIPE, and every
+ * command in this CLI calls `process.exit()` the moment it has written its
+ * summary. `process.exit` does not drain a pending write, so everything past the
+ * first pipe buffer (64 KB on Linux/macOS) was silently discarded — with exit
+ * code 0, so nothing signalled the loss. An interactive TTY is unbuffered and
+ * looked perfect, which is why this survived: it only bites the piped consumer
+ * this CLI's own docs recommend (`vat command | jq .status`).
+ *
+ * `writeSync` cannot return before the bytes reach the pipe, so `process.exit`
+ * has nothing left to lose. The loop is required because a single `writeSync`
+ * may accept fewer bytes than offered.
+ *
+ * This is the same fix `help-loader.ts` applied to `--help --verbose`; it lives
+ * here so both callers share one implementation rather than two copies of a
+ * subtle loop.
+ */
+export function writeStdoutSync(content) {
+    writeAllSync((buffer, offset, length) => writeSync(1, buffer, offset, length), Buffer.from(content, 'utf8'));
+}
+/**
+ * How many CONSECUTIVE EAGAIN retries — retries during which the writer accepted
+ * zero bytes — are tolerated before the write is declared stalled.
+ *
+ * Consecutive, not cumulative: a large payload to a slow reader legitimately
+ * EAGAINs thousands of times in total, and every one of those is followed by
+ * progress. What is never legitimate is the pipe staying full while the process
+ * on the other end takes nothing at all. Combined with the wait below, the
+ * budget is roughly ten seconds of a completely stalled reader.
+ */
+const MAX_CONSECUTIVE_EAGAIN_RETRIES = 10_000;
+/** Consecutive retries to spin on before sleeping between attempts. */
+const EAGAIN_SPIN_RETRIES = 16;
+/**
+ * Sleep synchronously. Required because this whole path exists to run to
+ * completion before `process.exit`, so it cannot yield to the event loop; a
+ * timer would never fire. `Atomics.wait` on a never-notified buffer is the one
+ * primitive that blocks the thread without burning CPU.
+ */
+function sleepSync(ms) {
+    Atomics.wait(new Int32Array(new SharedArrayBuffer(4)), 0, 0, ms);
+}
+/**
+ * Spin for the first few retries — a draining pipe frees space in microseconds,
+ * and paying a millisecond for that would be absurd — then back off to a real
+ * sleep so a genuinely stalled reader is waited out rather than spun on.
+ */
+function defaultWaitBetweenRetries(consecutiveRetries) {
+    if (consecutiveRetries > EAGAIN_SPIN_RETRIES)
+        sleepSync(1);
+}
+/**
+ * Drive `write` until every byte of `buffer` has been accepted.
+ *
+ * Split out from {@link writeStdoutSync} because the things that make this loop
+ * necessary — a short write, and an EAGAIN retry on a momentarily-full
+ * non-blocking pipe — are both hard to provoke on a real fd and trivial to state
+ * against an injected writer. The fd-1 wiring stays a one-liner above, so the
+ * only part with branching logic is the part that can be unit tested.
+ *
+ * The EAGAIN retry is BOUNDED. A reader that stops draining without closing the
+ * pipe (`vat … | consumer-that-wanders-off`) leaves it permanently full, so
+ * every retry raises EAGAIN forever; an unbounded loop turns that into a hang
+ * with no output and no error — strictly worse than the truncation this replaced.
+ * Exhausting the budget throws, so the failure is visible and the exit code is
+ * non-zero, rather than the bytes quietly going missing.
+ *
+ * @throws the underlying error for any failure other than EAGAIN; an `Error`
+ * naming the unwritten remainder when the retry budget is exhausted.
+ */
+export function writeAllSync(write, buffer, options = {}) {
+    const maxRetries = options.maxConsecutiveRetries ?? MAX_CONSECUTIVE_EAGAIN_RETRIES;
+    const wait = options.waitBetweenRetries ?? defaultWaitBetweenRetries;
+    let written = 0;
+    let consecutiveRetries = 0;
+    while (written < buffer.length) {
+        try {
+            const n = write(buffer, written, buffer.length - written);
+            // A writer that reports no progress would spin forever. Treat it as a
+            // failure rather than hang the CLI.
+            if (n <= 0) {
+                throw new Error(`Refusing to loop forever: writer accepted ${n} bytes of ${buffer.length - written} remaining`);
+            }
+            written += n;
+            consecutiveRetries = 0;
+        }
+        catch (error) {
+            // A non-blocking pipe whose buffer is momentarily full raises EAGAIN; a
+            // reader that is draining will free space, so retry. Anything else is a
+            // genuine write failure.
+            if (error.code !== 'EAGAIN')
+                throw error;
+            consecutiveRetries++;
+            if (consecutiveRetries > maxRetries) {
+                throw new Error(`Write stalled: ${maxRetries} consecutive EAGAIN retries with no progress after ${written} of ${buffer.length} bytes. The reader is not draining the pipe.`);
+            }
+            wait(consecutiveRetries);
+        }
+    }
+}
 /**
  * Write a single YAML document to stdout, opened with `---`.
  *
@@ -23,26 +127,16 @@ import * as yaml from 'yaml';
  * @param data - Data to serialize as YAML
  */
 export function writeYamlOutput(data) {
-    process.stdout.write('---\n');
-    process.stdout.write(yaml.stringify(data, {
+    // Deliberately the ordinary stream write, NOT writeStdoutSync: this summary
+    // follows human-readable progress output written via console.log, and a
+    // synchronous fd-1 write would jump ahead of anything still buffered there.
+    // Completeness is guaranteed instead by makeStdioBlocking() at startup, which
+    // makes BOTH channels synchronous and keeps them in order.
+    process.stdout.write(`---\n${yaml.stringify(data, {
         indent: 2,
         lineWidth: 120,
         aliasDuplicateObjects: false,
-    }));
-}
-/**
- * Flush stdout before writing to stderr
- * Prevents output corruption when streams are merged
- */
-export async function flushStdout() {
-    return new Promise((resolve) => {
-        if (process.stdout.writableNeedDrain) {
-            process.stdout.once('drain', resolve);
-        }
-        else {
-            resolve();
-        }
-    });
+    })}`);
 }
 /**
  * Write a test-format finding to stderr.

package/dist/utils/output.js.map

@@ -1 +1 @@
-{"version":3,"file":"output.js","sourceRoot":"","sources":["../../src/utils/output.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,OAAO,KAAK,IAAI,MAAM,MAAM,CAAC;AAE7B;;;;;;;;;;;;;;;;;;GAkBG;AACH,MAAM,UAAU,eAAe,CAAC,IAAa;IAC3C,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC;IAC9B,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,IAAI,CAAC,SAAS,CAAC,IAAI,EAAE;QACxC,MAAM,EAAE,CAAC;QACT,SAAS,EAAE,GAAG;QACd,qBAAqB,EAAE,KAAK;KAC7B,CAAC,CAAC,CAAC;AACN,CAAC;AAED;;;GAGG;AACH,MAAM,CAAC,KAAK,UAAU,WAAW;IAC/B,OAAO,IAAI,OAAO,CAAO,CAAC,OAAO,EAAE,EAAE;QACnC,IAAI,OAAO,CAAC,MAAM,CAAC,iBAAiB,EAAE,CAAC;YACrC,OAAO,CAAC,MAAM,CAAC,IAAI,CAAC,OAAO,EAAE,OAAO,CAAC,CAAC;QACxC,CAAC;aAAM,CAAC;YACN,OAAO,EAAE,CAAC;QACZ,CAAC;IACH,CAAC,CAAC,CAAC;AACL,CAAC;AAED;;;;;;;;;;GAUG;AACH,MAAM,UAAU,oBAAoB,CAClC,IAAY,EACZ,IAAY,EACZ,MAAc,EACd,QAAgB,EAChB,OAAe;IAEf,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,GAAG,IAAI,IAAI,IAAI,IAAI,MAAM,KAAK,QAAQ,KAAK,OAAO,IAAI,CAAC,CAAC;AAC/E,CAAC"}
+{"version":3,"file":"output.js","sourceRoot":"","sources":["../../src/utils/output.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,OAAO,EAAE,SAAS,EAAE,MAAM,SAAS,CAAC;AAEpC,OAAO,KAAK,IAAI,MAAM,MAAM,CAAC;AAE7B;;;;;;;;;;;;;;;;;;;GAmBG;AACH,MAAM,UAAU,eAAe,CAAC,OAAe;IAC7C,YAAY,CACV,CAAC,MAAM,EAAE,MAAM,EAAE,MAAM,EAAE,EAAE,CAAC,SAAS,CAAC,CAAC,EAAE,MAAM,EAAE,MAAM,EAAE,MAAM,CAAC,EAChE,MAAM,CAAC,IAAI,CAAC,OAAO,EAAE,MAAM,CAAC,CAC7B,CAAC;AACJ,CAAC;AAUD;;;;;;;;;GASG;AACH,MAAM,8BAA8B,GAAG,MAAM,CAAC;AAE9C,uEAAuE;AACvE,MAAM,mBAAmB,GAAG,EAAE,CAAC;AAE/B;;;;;GAKG;AACH,SAAS,SAAS,CAAC,EAAU;IAC3B,OAAO,CAAC,IAAI,CAAC,IAAI,UAAU,CAAC,IAAI,iBAAiB,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC,EAAE,CAAC,EAAE,EAAE,CAAC,CAAC;AACnE,CAAC;AAED;;;;GAIG;AACH,SAAS,yBAAyB,CAAC,kBAA0B;IAC3D,IAAI,kBAAkB,GAAG,mBAAmB;QAAE,SAAS,CAAC,CAAC,CAAC,CAAC;AAC7D,CAAC;AASD;;;;;;;;;;;;;;;;;;GAkBG;AACH,MAAM,UAAU,YAAY,CAC1B,KAAiB,EACjB,MAAc,EACd,UAA+B,EAAE;IAEjC,MAAM,UAAU,GAAG,OAAO,CAAC,qBAAqB,IAAI,8BAA8B,CAAC;IACnF,MAAM,IAAI,GAAG,OAAO,CAAC,kBAAkB,IAAI,yBAAyB,CAAC;IAErE,IAAI,OAAO,GAAG,CAAC,CAAC;IAChB,IAAI,kBAAkB,GAAG,CAAC,CAAC;IAE3B,OAAO,OAAO,GAAG,MAAM,CAAC,MAAM,EAAE,CAAC;QAC/B,IAAI,CAAC;YACH,MAAM,CAAC,GAAG,KAAK,CAAC,MAAM,EAAE,OAAO,EAAE,MAAM,CAAC,MAAM,GAAG,OAAO,CAAC,CAAC;YAC1D,sEAAsE;YACtE,oCAAoC;YACpC,IAAI,CAAC,IAAI,CAAC,EAAE,CAAC;gBACX,MAAM,IAAI,KAAK,CAAC,6CAA6C,CAAC,aAAa,MAAM,CAAC,MAAM,GAAG,OAAO,YAAY,CAAC,CAAC;YAClH,CAAC;YACD,OAAO,IAAI,CAAC,CAAC;YACb,kBAAkB,GAAG,CAAC,CAAC;QACzB,CAAC;QAAC,OAAO,KAAK,EAAE,CAAC;YACf,wEAAwE;YACxE,wEAAwE;YACxE,yBAAyB;YACzB,IAAK,KAA+B,CAAC,IAAI,KAAK,QAAQ;gBAAE,MAAM,KAAK,CAAC;YACpE,kBAAkB,EAAE,CAAC;YACrB,IAAI,kBAAkB,GAAG,UAAU,EAAE,CAAC;gBACpC,MAAM,IAAI,KAAK,CACb,kBAAkB,UAAU,sDAAsD,OAAO,OAAO,MAAM,CAAC,MAAM,8CAA8C,CAC5J,CAAC;YACJ,CAAC;YACD,IAAI,CAAC,kBAAkB,CAAC,CAAC;QAC3B,CAAC;IACH,CAAC;AACH,CAAC;AAED;;;;;;;;;;;;;;;;;;GAkBG;AACH,MAAM,UAAU,eAAe,CAAC,IAAa;IAC3C,4EAA4E;IAC5E,wEAAwE;IACxE,4EAA4E;IAC5E,8EAA8E;IAC9E,2DAA2D;IAC3D,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,QAAQ,IAAI,CAAC,SAAS,CAAC,IAAI,EAAE;QAChD,MAAM,EAAE,CAAC;QACT,SAAS,EAAE,GAAG;QACd,qBAAqB,EAAE,KAAK;KAC7B,CAAC,EAAE,CAAC,CAAC;AACR,CAAC;AAED;;;;;;;;;;GAUG;AACH,MAAM,UAAU,oBAAoB,CAClC,IAAY,EACZ,IAAY,EACZ,MAAc,EACd,QAAgB,EAChB,OAAe;IAEf,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,GAAG,IAAI,IAAI,IAAI,IAAI,MAAM,KAAK,QAAQ,KAAK,OAAO,IAAI,CAAC,CAAC;AAC/E,CAAC"}

package/dist/utils/relativize-paths.d.ts

@@ -0,0 +1,45 @@
+/**
+ * Re-basing report `path` values onto the run's single stated root.
+ *
+ * A report states its coordinate system ONCE — `root:` — and every `path`
+ * beneath it is relative to that. Producers keep absolute paths internally on
+ * purpose: an absolute path is the identity every internal map keys on (compat
+ * results, visited-path de-duplication, registry caches), and unlike a
+ * `location` it is trivially recoverable, since an absolute path plus a known
+ * root yields the relative form. Re-basing therefore happens once, at the
+ * document boundary, and this module is that one place.
+ *
+ * Deliberately NOT a deep walk over every `path`-named property: re-basing is
+ * not idempotent (`relative(root, someRelativeValue)` resolves the value
+ * against the process cwd and produces nonsense), so a helper that guesses
+ * which values are absolute would silently corrupt an already-relative one.
+ * The caller names the nested carriers it owns instead.
+ */
+/** The minimum shape this module re-bases: anything carrying a `path`. */
+export interface PathEntry {
+    path: string;
+}
+/**
+ * Re-base one absolute path onto `root`, as a forward-slashed relative path.
+ *
+ * Pointing a report AT a single resource makes that resource the root, which
+ * relativizes to the empty string. That is spelled `.` — the POSIX name for
+ * "the root itself" — so no consumer has to special-case a blank value, and
+ * `join(root, path)` still resolves.
+ */
+export declare function relativizePath(absolutePath: string, root: string): string;
+/**
+ * Re-base the `path` of every entry — and of every entry inside the nested
+ * carriers named by `nestedKeys`, at any depth — onto `root`.
+ *
+ * Returns new objects; the input is never mutated.
+ *
+ * @param entries - Report entries carrying absolute `path` values.
+ * @param root - The single root the document states.
+ * @param nestedKeys - Names of array-valued properties whose elements also
+ *   carry an absolute `path` (audit passes `['linkedFiles']`). Omitting a
+ *   carrier leaves its paths absolute, which is how a document ends up in two
+ *   coordinate systems — so a producer that adds a carrier must name it here.
+ */
+export declare function relativizePathEntries<T extends PathEntry>(entries: readonly T[], root: string, nestedKeys?: readonly string[]): T[];
+//# sourceMappingURL=relativize-paths.d.ts.map

package/dist/utils/relativize-paths.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"relativize-paths.d.ts","sourceRoot":"","sources":["../../src/utils/relativize-paths.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AAIH,0EAA0E;AAC1E,MAAM,WAAW,SAAS;IACxB,IAAI,EAAE,MAAM,CAAC;CACd;AAED;;;;;;;GAOG;AACH,wBAAgB,cAAc,CAAC,YAAY,EAAE,MAAM,EAAE,IAAI,EAAE,MAAM,GAAG,MAAM,CAGzE;AA+BD;;;;;;;;;;;;GAYG;AACH,wBAAgB,qBAAqB,CAAC,CAAC,SAAS,SAAS,EACvD,OAAO,EAAE,SAAS,CAAC,EAAE,EACrB,IAAI,EAAE,MAAM,EACZ,UAAU,GAAE,SAAS,MAAM,EAAO,GACjC,CAAC,EAAE,CAEL"}