@swarmvaultai/engine 0.1.29 → 0.1.31

package/README.md

@@ -45,6 +45,7 @@ import {
   loadVaultSchema,
   loadVaultSchemas,
   pathGraphVault,
+  pushGraphNeo4j,
   queryGraphVault,
   queryVault,
   runWatchCycle,
@@ -65,13 +66,18 @@ The engine also exports the main runtime types for providers, graph artifacts, p
 
 ```ts
 import {
+  addInput,
+  benchmarkVault,
   compileVault,
   exploreVault,
   exportGraphHtml,
+  exportGraphFormat,
+  getWatchStatus,
   importInbox,
   initVault,
   installGitHooks,
   loadVaultSchemas,
+  pushGraphNeo4j,
   queryGraphVault,
   queryVault,
   runWatchCycle,
@@ -100,6 +106,12 @@ console.log(exploration.hubPath);
 
 await exportGraphHtml(rootDir, "./exports/graph.html");
 await exportGraphFormat(rootDir, "graphml", "./exports/graph.graphml");
+await pushGraphNeo4j(rootDir, {
+  uri: "bolt://127.0.0.1:7687",
+  username: "neo4j",
+  passwordEnv: "NEO4J_PASSWORD",
+  dryRun: true
+});
 
 await runWatchCycle(rootDir, { repo: true });
 console.log(await getWatchStatus(rootDir));
@@ -172,6 +184,7 @@ This matters because many "OpenAI-compatible" backends only implement part of th
 
 - `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`, `wiki/graph/report.json`, and `wiki/graph/communities/<community>.md`
+- compile propagates semantic tags onto page frontmatter and source-backed graph nodes, and records deterministic `contradicts` edges plus a Contradictions section in the graph report when conflicting claims are found
 - `benchmarkVault(rootDir, { questions })` writes `state/benchmark.json` and folds the latest benchmark summary into `wiki/graph/report.md` and `wiki/graph/report.json`
 - semantic graph query and embedding-backed similarity enrichment cache vectors under `state/embeddings.json` so graph-semantic refresh stays incremental
 - `queryVault(rootDir, { question, save, format, review })` answers against the compiled vault using the same schema layer and saves by default
@@ -195,7 +208,7 @@ This matters because many "OpenAI-compatible" backends only implement part of th
 - `syncTrackedReposForWatch(rootDir)` is the repo-watch sync path that defers non-code semantic refresh into `state/watch/`
 - `installGitHooks(rootDir)`, `uninstallGitHooks(rootDir)`, and `getGitHookStatus(rootDir)` manage local `post-commit` and `post-checkout` hook blocks for the nearest git repository
 - `installAgent(rootDir, agent, { hook })` writes agent instructions and returns the primary `target`, all touched `targets`, and optional merge warnings for agents such as Aider
-- `lintVault(rootDir, options)` runs structural lint, optional deep lint, and optional web-augmented evidence gathering
+- `lintVault(rootDir, options)` runs structural lint, optional deep lint, optional contradiction-only filtering through `{ conflicts: true }`, and optional web-augmented evidence gathering
 - `listSchedules(rootDir)`, `runSchedule(rootDir, jobId)`, and `serveSchedules(rootDir)` manage recurring local jobs from config
 - compile, query, explore, lint, and watch also write canonical markdown session artifacts to `state/sessions/`
 - scheduled `query` and `explore` jobs stage saved outputs through approvals when they write artifacts
@@ -212,6 +225,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
 - `exportGraphFormat(rootDir, "svg" | "graphml" | "cypher", outputPath)` exports the graph into interoperable file formats
+- `pushGraphNeo4j(rootDir, options)` upserts the current graph into Neo4j over Bolt/Aura with shared-database-safe `vaultId` namespacing
 
 The MCP surface includes tools for workspace info, page search, page reads, source listing, querying, ingestion, compile, lint, graph report reads, hyperedge reads, 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.