@vibgrate/cli 2026.720.2 → 2026.720.3

package/dist/index.d.ts

@@ -2,7 +2,7 @@ import { G as GraphNode, a as GraphEdge, A as Area, R as ResolverKind, V as VgGr
 export { C as Centrality, D as DerivedBy, e as EpistemicTier, f as FactConfidence, g as FactKind, h as GraphMeta, N as NodeKind, P as Provenance, S as SCHEMA_VERSION, i as Span, T as Toolchain, U as Unknown } from './types-BgNa-FZQ.js';
 import { Server } from '@modelcontextprotocol/sdk/server/index.js';
 
-declare const VERSION = "2026.720.2";
+declare const VERSION = "2026.720.3";
 
 /**
  * Analysis stage: importance, centrality, hubs, communities, and surprise.
@@ -660,11 +660,14 @@ declare function readSavings(root: string, days: number, now: number, ratePerM?:
  * ledger by ./ledger-tail.ts, so agents that shell out to `vg` instead of
  * calling MCP tools still show up here.
  *
- * Privacy: everything here lives and dies with the process — nothing is
+ * Privacy: everything here lives and dies with the serve session — nothing is
  * persisted or uploaded, so the display is always on (GUARDRAILS §3.4 applies
  * to the opt-in ledger/upload, which remain separate and off by default).
  * Counts only — never code, paths beyond what the operator already sees, or
- * question text.
+ * question text. Sibling serve processes in the same repo (an assistant's own
+ * spawned stdio server) surface their counts to a TTY display through the
+ * ephemeral live-stats bus (./live-stats.ts) — same counts-only data, swept
+ * on exit.
  *
  * Output discipline: stderr only. Under stdio transport, stdout IS the MCP
  * protocol stream and carries nothing else.

package/dist/index.js

@@ -1,6 +1,6 @@
-export { ASSISTANTS, FREE_PACK, GraphIndex, GraphSource, ResourceLimitError, SCHEMA_VERSION, SKIP_DIRS, SKIP_FILES, TOOLS, UsageError, addLibrary, analyze, applyCoverage, applyStaticTestLinkage, assistantById, buildFacts, buildGraph, buildModuleResolver, cosine, coveringTests, createServer, decodeScipIndex, defaultGraphPath, inventory as dependencyInventory, detectRunner, discover, discoverModels, driftCount, driftFor, enrichOnline, exportGraph, findNodes, formatForExt, getNodeEmbeddings, groundGraph, hasDrift, identifierParts, impactOf, installAssistant, isTestFile, libId, loadCatalog, loadCoverage, loadEmbedder, loadGraph, loadSnapshot, nodeById, nodeEmbedText, parseGraph, parseJsonc, probeFreshness, queryGraph, queryGraphSemantic, readDoc, readSavings, recordSaving, refreshIfStale, relativeResolver, renderHtml, renderReport, resolveLib, resolveLimits, resolveOne, saveCatalog, savingsRecorded, scipEdges, serializeGraph, serveStdio, shortestPath, stableStringify, testsToRun, uninstallAssistant, verifyDeterminism, vibgrateDir, writeArtifacts, writeSnapshot } from './chunk-7R4O5CZD.js';
+export { ASSISTANTS, FREE_PACK, GraphIndex, GraphSource, ResourceLimitError, SCHEMA_VERSION, SKIP_DIRS, SKIP_FILES, TOOLS, UsageError, addLibrary, analyze, applyCoverage, applyStaticTestLinkage, assistantById, buildFacts, buildGraph, buildModuleResolver, cosine, coveringTests, createServer, decodeScipIndex, defaultGraphPath, inventory as dependencyInventory, detectRunner, discover, discoverModels, driftCount, driftFor, enrichOnline, exportGraph, findNodes, formatForExt, getNodeEmbeddings, groundGraph, hasDrift, identifierParts, impactOf, installAssistant, isTestFile, libId, loadCatalog, loadCoverage, loadEmbedder, loadGraph, loadSnapshot, nodeById, nodeEmbedText, parseGraph, parseJsonc, probeFreshness, queryGraph, queryGraphSemantic, readDoc, readSavings, recordSaving, refreshIfStale, relativeResolver, renderHtml, renderReport, resolveLib, resolveLimits, resolveOne, saveCatalog, savingsRecorded, scipEdges, serializeGraph, serveStdio, shortestPath, stableStringify, testsToRun, uninstallAssistant, verifyDeterminism, vibgrateDir, writeArtifacts, writeSnapshot } from './chunk-ZFDVHKID.js';
 export { LANGUAGES, allLanguageIds, grammarsSourceDir, langById, langForExtension, parseSource } from './chunk-BHA7QIPD.js';
-export { VERSION } from './chunk-OD5654VF.js';
+export { VERSION } from './chunk-B6ZWB3WH.js';
 import { redactUrlCredentials, redactSecrets } from './chunk-RXP66R2E.js';
 import './chunk-GI6W53LM.js';
 import { execFileSync } from 'child_process';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vibgrate/cli",
-  "version": "2026.720.2",
+  "version": "2026.720.3",
   "description": "vg — local codebase intelligence CLI + MCP server for AI coding agents: deterministic code graph, drift reporting, and version-correct library docs (Apache-2.0)",
   "//mcpName": "Official MCP registry ownership proof: the registry fetches the published npm package and requires this field to match the com.vibgrate/ai-context server entry (see docs/marketing/mcp-registry/README.md). Must ship in the published @vibgrate/cli package.json.",
   "mcpName": "com.vibgrate/ai-context",

package/skills/vg/SKILL.md

@@ -3,26 +3,31 @@ name: vg
 description: Query the local code graph (vg) for structure, impact, and navigation instead of grepping/reading many files.
 ---
 
+<!-- vg:v2 · managed by `vg install` — auto-refreshed when these instructions evolve; remove this line to opt out -->
+
 # vg — the code map
 
 This repo has a deterministic code graph built by `vg`. Prefer it over reading or
 grepping many files — it is smaller, more relevant context, and free.
 
-## Prefer the MCP tools
+## Use the MCP tools — not the CLI
 
-If the `vg` MCP server is registered (it is after `vg install`), call its
-read-only tools directly — they are the **fastest** path. The server keeps the
-map parsed, the relation index warm, and the embedding model loaded across calls,
-so each query is cheaper than spawning the CLI fresh. Use:
+When the `vg` MCP server is registered (it is after `vg install`), **always call
+its read-only tools instead of shelling out to the CLI.** The server keeps the
+map parsed, the relation index warm, and the embedding model loaded across
+calls, so an MCP call answers in milliseconds — while every CLI invocation pays
+Node startup plus a fresh map parse, hundreds of times more. Tools:
 `query_graph`, `get_node`, `impact_of`, `find_path`, `list_hubs`, `list_areas`,
 `get_graph_summary`, `search_symbols`. They are side-effect-free and
 auto-approvable, and the server records which client is calling automatically.
+Reach for the CLI only when the MCP server is genuinely unavailable — never as
+the first resort.
 
-## If you use the `vg` CLI instead
+## CLI fallback — only when the MCP server is unavailable
 
-When the MCP server isn't available, use the CLI — and **always pass
-`--client=<your-ai>`** so your calls are counted (that's how the CLI-vs-MCP split
-is measured and the tools improved):
+If (and only if) no `vg` MCP server is available, use the CLI — and **always
+pass `--client=<your-ai>`** so your calls are counted (that's how the CLI-vs-MCP split is
+measured and the tools improved):
 
 - **Understand code:** `vg "<question>" --client=<your-ai>` — a budget-bounded, fact-annotated context block.
 - **Find a symbol:** `vg show <name> --client=<your-ai>` — what it is, what it calls, what calls it.
@@ -37,6 +42,21 @@ is measured and the tools improved):
 - **Version-correct docs:** `vg lib <name>` returns drift-annotated, version-
   specific usage docs for a library — inject these instead of guessing an API.
 
+### Library-docs discipline
+
+When a task needs a library's API, use the docs tools before web search or
+training-data recall — they are official content matched to the version **this
+project has installed**, and they win when the two conflict.
+
+- **Workflow:** `resolve_library` once per library, then `library_docs` with the
+  returned `targetId` and a focused query (good: "zod refine custom error
+  message"; bad: "zod"). Never guess a targetId.
+- **Budget:** at most **3 docs calls per task**. If 2 `library_docs` calls have
+  not surfaced the section you need, read the package source under
+  `node_modules` instead of searching again.
+- **Skip the docs tools** for language built-ins, stable well-known syntax, or
+  an API already shown in the current context — they add nothing there.
+
 ## Keep it fresh
 
 The map keeps itself fresh: `vg ask` and the MCP tools detect changed files

package/dist/baseline-WIZAFIJS.js

@@ -1,6 +0,0 @@
-export { baselineCommand, runBaseline } from './chunk-DDQ5JGBV.js';
-import './chunk-OD5654VF.js';
-import './chunk-RXP66R2E.js';
-import './chunk-GI6W53LM.js';
-//# sourceMappingURL=baseline-WIZAFIJS.js.map
-//# sourceMappingURL=baseline-WIZAFIJS.js.map