@swarmvaultai/engine 0.1.17 → 0.1.19

package/README.md

@@ -26,16 +26,20 @@ import {
   defaultVaultSchema,
   exploreVault,
   exportGraphHtml,
+  explainGraphVault,
   importInbox,
   ingestInput,
   initVault,
   installAgent,
   getWebSearchAdapterForTask,
   lintVault,
+  listGodNodes,
   listSchedules,
   loadVaultConfig,
   loadVaultSchema,
   loadVaultSchemas,
+  pathGraphVault,
+  queryGraphVault,
   queryVault,
   runSchedule,
   searchVault,
@@ -64,6 +68,9 @@ await compileVault(rootDir, {});
 const saved = await queryVault(rootDir, { question: "What changed most recently?" });
 console.log(saved.savedPath);
 
+const graphQuery = await queryGraphVault(rootDir, "Which nodes bridge the biggest communities?");
+console.log(graphQuery.summary);
+
 const exploration = await exploreVault(rootDir, { question: "What should I investigate next?", steps: 3, format: "report" });
 console.log(exploration.hubPath);
 
@@ -122,17 +129,24 @@ This matters because many "OpenAI-compatible" backends only implement part of th
 
 ### Ingest
 
-- `ingestInput(rootDir, input, { includeAssets, maxAssetSize })` ingests a local path or URL
+- `ingestInput(rootDir, input, { includeAssets, maxAssetSize })` ingests a local file path or URL
+- `ingestDirectory(rootDir, inputDir, { repoRoot, include, exclude, maxFiles, gitignore })` recursively ingests a local directory as a repo-aware code/content source tree
 - `importInbox(rootDir, inputDir?)` recursively imports supported inbox files and browser-clipper style bundles
-- JavaScript, TypeScript, Python, Go, Rust, and Java inputs are treated as code sources and compiled into both source pages and `wiki/code/` module pages
+- JavaScript, TypeScript, Python, Go, Rust, Java, C#, C, C++, and PHP inputs are treated as code sources and compiled into both source pages and `wiki/code/` module pages
+- code manifests can carry `repoRelativePath`, and compile writes `state/code-index.json` so local imports can resolve across an ingested repo tree
 - HTML and markdown URL ingests localize remote image references into `raw/assets/<sourceId>/` by default and rewrite the stored markdown to local relative paths
 
 ### Compile + Query
 
 - `compileVault(rootDir, { approve })` writes wiki pages, graph data, and search state using the vault schema as guidance, or stages a review bundle
+- compile also writes graph orientation pages such as `wiki/graph/report.md` and `wiki/graph/communities/<community>.md`
 - `queryVault(rootDir, { question, save, format, review })` answers against the compiled vault using the same schema layer and saves by default
 - `exploreVault(rootDir, { question, steps, format, review })` runs a save-first multi-step exploration loop and writes a hub page plus step outputs
 - `searchVault(rootDir, query, limit)` searches compiled pages directly
+- `queryGraphVault(rootDir, question, { traversal, budget })` runs deterministic local graph search without a model provider
+- `pathGraphVault(rootDir, from, to)` returns the shortest graph path between two targets
+- `explainGraphVault(rootDir, target)` returns node, community, neighbor, and provenance details
+- `listGodNodes(rootDir, limit)` returns the most connected bridge-heavy graph nodes
 - project-aware compile also builds `wiki/projects/index.md` plus `wiki/projects/<project>/index.md` rollups without duplicating page trees
 - human-authored insight pages in `wiki/insights/` are indexed into search and available to query without being rewritten by compile
 - `chart` and `image` formats save wrapper markdown pages plus local output assets under `wiki/outputs/assets/<slug>/`
@@ -157,7 +171,7 @@ This matters because many "OpenAI-compatible" backends only implement part of th
 - `startMcpServer(rootDir)` runs the MCP server over stdio
 - `exportGraphHtml(rootDir, outputPath)` exports the graph workspace as a standalone HTML file
 
-The MCP surface includes tools for workspace info, page search, page reads, source listing, querying, ingestion, compile, and lint, along with resources for config, graph, manifests, schema, page content, and session artifacts.
+The MCP surface includes tools for workspace info, page search, page reads, source listing, querying, ingestion, compile, lint, and graph-native read operations such as graph query, node explain, neighbor lookup, shortest path, and god-node listing, along with resources for config, graph, manifests, schema, page content, and session artifacts.
 
 ## Artifacts
 
@@ -168,6 +182,7 @@ Running the engine produces a local workspace with these main areas:
 - `raw/sources/`: immutable source copies
 - `raw/assets/`: copied attachments referenced by ingested markdown bundles and remote URL ingests
 - `wiki/`: generated markdown pages, the append-only `log.md` activity trail, staged candidates, saved query outputs, exploration hub pages, and a human-only `insights/` area
+- `wiki/graph/`: generated graph report pages and per-community summaries derived from `state/graph.json`
 - `wiki/outputs/assets/`: local chart/image artifacts and JSON manifests for saved visual outputs
 - `wiki/code/`: generated module pages for ingested code sources
 - `wiki/projects/`: generated project rollups over canonical pages
@@ -175,6 +190,7 @@ Running the engine produces a local workspace with these main areas:
 - `state/manifests/`: source manifests
 - `state/extracts/`: extracted text
 - `state/analyses/`: model analysis output
+- `state/code-index.json`: repo-aware code module aliases and local resolution data
 - `state/graph.json`: compiled graph
 - `state/search.sqlite`: full-text index
 - `state/sessions/`: canonical session artifacts
@@ -183,7 +199,7 @@ Running the engine produces a local workspace with these main areas:
 - `state/jobs.ndjson`: watch-mode automation logs
 
 Saved outputs are indexed immediately into the graph page registry and search index, then linked back into compiled source, concept, and entity pages immediately through the lightweight artifact sync path. New concept and entity pages stage into `wiki/candidates/` first and promote to active pages on the next matching compile. Insight pages are indexed into search and page reads, but compile does not mutate them. Project-scoped pages receive `project_ids`, project tags, and layered root-plus-project schema hashes when all contributing sources resolve to the same configured project.
-Code sources also emit module and symbol nodes into `state/graph.json`, so local imports, exports, inheritance, and same-module call edges are queryable through the same viewer and search pipeline.
+Code sources also emit module, symbol, and parser-backed rationale nodes into `state/graph.json`, so local imports, exports, inheritance, same-module call edges, and rationale links are queryable through the same viewer and search pipeline.
 Ingest, inbox import, compile, query, lint, review, and candidate operations also append human-readable entries to `wiki/log.md`.
 
 ## Notes