@swarmvaultai/engine 0.1.29 → 0.1.30

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -45,6 +45,7 @@ import {
45
45
  loadVaultSchema,
46
46
  loadVaultSchemas,
47
47
  pathGraphVault,
48
+ pushGraphNeo4j,
48
49
  queryGraphVault,
49
50
  queryVault,
50
51
  runWatchCycle,
@@ -65,13 +66,18 @@ The engine also exports the main runtime types for providers, graph artifacts, p
65
66
 
66
67
  ```ts
67
68
  import {
69
+ addInput,
70
+ benchmarkVault,
68
71
  compileVault,
69
72
  exploreVault,
70
73
  exportGraphHtml,
74
+ exportGraphFormat,
75
+ getWatchStatus,
71
76
  importInbox,
72
77
  initVault,
73
78
  installGitHooks,
74
79
  loadVaultSchemas,
80
+ pushGraphNeo4j,
75
81
  queryGraphVault,
76
82
  queryVault,
77
83
  runWatchCycle,
@@ -100,6 +106,12 @@ console.log(exploration.hubPath);
100
106
 
101
107
  await exportGraphHtml(rootDir, "./exports/graph.html");
102
108
  await exportGraphFormat(rootDir, "graphml", "./exports/graph.graphml");
109
+ await pushGraphNeo4j(rootDir, {
110
+ uri: "bolt://127.0.0.1:7687",
111
+ username: "neo4j",
112
+ passwordEnv: "NEO4J_PASSWORD",
113
+ dryRun: true
114
+ });
103
115
 
104
116
  await runWatchCycle(rootDir, { repo: true });
105
117
  console.log(await getWatchStatus(rootDir));
@@ -212,6 +224,7 @@ This matters because many "OpenAI-compatible" backends only implement part of th
212
224
  - `startMcpServer(rootDir)` runs the MCP server over stdio
213
225
  - `exportGraphHtml(rootDir, outputPath)` exports the graph workspace as a standalone HTML file
214
226
  - `exportGraphFormat(rootDir, "svg" | "graphml" | "cypher", outputPath)` exports the graph into interoperable file formats
227
+ - `pushGraphNeo4j(rootDir, options)` upserts the current graph into Neo4j over Bolt/Aura with shared-database-safe `vaultId` namespacing
215
228
 
216
229
  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.
217
230