@imunitic/synapse 0.2.13 → 0.3.1

package/commands/synapse-vault-tidy.md

@@ -33,7 +33,7 @@ Requires the `synapse` CLI on `PATH`, resolving a vault with a working `LinkGrap
 `sb — Obsidian CLI as ObsidianStore's transport` and `sb — DiskStore's own index, Obsidian becomes
 optional`). Both real coding-vault backends have one now — `obsidian` reaching the CLI when
 reachable and falling back to `disk`'s own implementation otherwise, `disk` always local. If
-`SYNAPSE_VAULT_STORE` ever resolves to a backend with no `LinkGraph` at all, these commands exit 1
+`SYNAPSE_VAULT_INTEGRATIONS` ever resolves to a backend with no `LinkGraph` at all, these commands exit 1
 saying so; stop and report that rather than falling back to anything else.
 
 This command reaches the vault store only through the `synapse` CLI's `vault-*` subcommands, the
@@ -101,7 +101,7 @@ findings for the Step 6 proposal instead of a silent edit:
 
 - **Broken links** — every `vault-unresolved` row whose `source` is in scope. Before writing the
   finding, check the vault's own local git history to say *why* it's broken instead of leaving that
-  to guesswork — a `SYNAPSE_VAULT_STORE=git` vault has one, since every agent-driven edit commits
+  to guesswork — a `SYNAPSE_VAULT_INTEGRATIONS=git` vault has one, since every agent-driven edit commits
   into it automatically. Resolve the vault's filesystem path the same way `synapse.conf` already does
   (`SYNAPSE_VAULT_DIR`), skip this sub-step entirely if `{vault}/.git` doesn't exist, and never let a
   missing/unreachable git repo block the rest of the finding — worst case it's reported with no

package/harness/codex/skills/synapse-vault-tidy/SKILL.md

@@ -33,7 +33,7 @@ Requires the `synapse` CLI on `PATH`, resolving a vault with a working link grap
 (`synapse vault-backlinks`/`vault-links`/`vault-unresolved`/`vault-orphans`/`vault-deadends`). Both
 real coding-vault backends have one — `disk` (the default) always local, `obsidian` reaching a
 running app when reachable and falling back to `disk`'s own implementation otherwise. If
-`SYNAPSE_VAULT_STORE` ever resolves to a backend with no link graph at all, these commands exit 1
+`SYNAPSE_VAULT_INTEGRATIONS` ever resolves to a backend with no link graph at all, these commands exit 1
 saying so; stop and report that rather than falling back to anything else.
 
 This skill reaches the vault store only through the `synapse` CLI's `vault-*` subcommands, the same
@@ -101,7 +101,7 @@ findings for the Step 6 proposal instead of a silent edit:
 
 - **Broken links** — every `vault-unresolved` row whose `source` is in scope. Before writing the
   finding, check the vault's own local git history to say *why* it's broken instead of leaving that
-  to guesswork — a `SYNAPSE_VAULT_STORE=git` vault has one, since every agent-driven edit commits
+  to guesswork — a `SYNAPSE_VAULT_INTEGRATIONS=git` vault has one, since every agent-driven edit commits
   into it automatically. Resolve the vault's filesystem path the same way its own conf file already
   does (`SYNAPSE_VAULT_DIR`), skip this sub-step entirely if `{vault}/.git` doesn't exist, and never
   let a missing/unreachable git repo block the rest of the finding — worst case it's reported with no

package/harness/opencode/plugin/synapse.js

@@ -20,7 +20,7 @@
 // `args.oldString`, `args.newString`) -- both share `filePath`, matching
 // Claude Code's `Write`/`Edit` sharing `tool_input.file_path`. Fired on
 // write/edit tools for `staleness` -- the vault's own version control
-// (`SYNAPSE_VAULT_STORE=git`) commits from inside `synapse`'s own CLI
+// (`SYNAPSE_VAULT_INTEGRATIONS=git`) commits from inside `synapse`'s own CLI
 // (`vault-write`/`vault-patch`) itself now, needing no `PostToolUse`-style
 // hook here or on any other harness.
 //

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@imunitic/synapse",
-  "version": "0.2.13",
+  "version": "0.3.1",
   "description": "Memory for Claude Code, Codex CLI, and OpenCode: a durable Obsidian vault plus a per-repo code graph.",
   "repository": {
     "type": "git",
@@ -22,9 +22,9 @@
     "*.conf.template"
   ],
   "optionalDependencies": {
-    "@imunitic/synapse-darwin-arm64": "0.2.13",
-    "@imunitic/synapse-linux-x64": "0.2.13",
-    "@imunitic/synapse-linux-arm64": "0.2.13"
+    "@imunitic/synapse-darwin-arm64": "0.3.1",
+    "@imunitic/synapse-linux-x64": "0.3.1",
+    "@imunitic/synapse-linux-arm64": "0.3.1"
   },
   "license": "SEE LICENSE IN LICENSE"
 }

package/skills/synapse-vault/SKILL.md

@@ -90,7 +90,7 @@ verification that cannot fail in the direction you are worried about is not a ve
 
 ## If you do destroy something
 
-On a `SYNAPSE_VAULT_STORE=git` vault, every edit commits automatically, so the intact version is one
+On a `SYNAPSE_VAULT_INTEGRATIONS=git` vault, every edit commits automatically, so the intact version is one
 `git show <sha>:<path>` away in the vault's own git history -- a vault-wide undo for destructive tool
 calls, not merely a record of intentional edits. The default `disk` backend keeps no history at all,
 so this safety net only exists once that backend is chosen.

package/synapse-claude.md

@@ -101,11 +101,11 @@ The vault is reached through the `synapse` CLI — `synapse vault-read`/`vault-w
 `vault-search`/`vault-search-text`/`vault-doc-map`/`vault-patch`/`vault-backlinks`/`vault-links`/
 `vault-unresolved`/`vault-orphans`/`vault-deadends`/`vault-ambiguous`/`vault-rename` — for reads
 *and* for writes, never by resolving a vault path or calling an `mcp__obsidian__*` tool directly.
-Which concrete store the CLI talks to (`SYNAPSE_VAULT_STORE=disk`, the default; `obsidian`, opted
+Which concrete store the CLI talks to (`SYNAPSE_VAULT_INTEGRATIONS unset`, the default; `obsidian`, opted
 into for a running Obsidian app's own live search relevance and graph data; or `git`, opted into for
 the vault to own its own version control -- commit on every write, push/pull in the background) is
 resolved once,
-inside the compiled binary, from `SYNAPSE_VAULT_STORE`/`SYNAPSE_VAULT_DIR` — never something a skill
+inside the compiled binary, from `SYNAPSE_VAULT_INTEGRATIONS`/`SYNAPSE_VAULT_DIR` — never something a skill
 or an agent turn needs to know or branch on. By default that means no Obsidian dependency
 whatsoever: `read`/`write`/`list`/`search`/the link graph/rename are all plain disk I/O and direct
 computation against the vault folder. Under the opted-in `obsidian` backend, `search`/the link

package/synapse.conf.template

@@ -2,23 +2,28 @@
 # synapse.conf anywhere. Edit the path below for this machine.
 SYNAPSE_VAULT_DIR="$HOME/Vault/YourVault"
 
-# Default "disk" if unset: reads/writes the vault folder directly, no
-# external dependency at all -- search and the link graph
+# Unset by default: reads/writes the vault folder directly, no external
+# dependency at all -- search and the link graph
 # (backlinks/links/unresolved/orphans/deadends/ambiguous) are computed by
-# DiskStore's own scan. Set to the name of an extended store instead to
-# prefer a running external app's own live search relevance and graph data,
-# falling back to the same disk-backed behavior automatically whenever that
-# app isn't reachable -- see docs/synapse/synapse-extended-store.md.
-#SYNAPSE_VAULT_STORE="obsidian"
+# DiskStore's own scan. A comma-separated, outer-to-inner list of
+# integrations layers extra behavior on top instead: "obsidian" prefers a
+# running external app's own live search relevance and graph data, falling
+# back to the same disk-backed behavior automatically whenever that app
+# isn't reachable (see docs/synapse/synapse-extended-store.md); "git" owns
+# the vault's own git lifecycle (commit on write, push once enough pile up).
+# "git,obsidian" combines both. The disk store itself is never named -- it's
+# always the implicit innermost element.
+#SYNAPSE_VAULT_INTEGRATIONS="obsidian"
 
 # Where Synapse clones/builds tree-sitter grammars (shared across every
 # project -- not per-repo). Safe to leave at the default.
 SYNAPSE_GRAMMARS_DIR="$HOME/.cache/synapse/grammars"
 
-# How often the Stop hook pushes the vault's auto-commits to its remote,
-# counted in turns. Only acts when the vault actually has an upstream and is
-# genuinely ahead of it, so a remote-less vault (local versioned undo only) is
-# unaffected either way. Set to 0 to never push. Default 5 if unset.
+# When "git" is one of the configured integrations, how many local commits
+# pile up before a detached push runs, counted in commits. Only acts when the
+# vault actually has an upstream and is genuinely ahead of it, so a
+# remote-less vault (local versioned undo only) is unaffected either way. Set
+# to 0 to never push. Default 5 if unset.
 #SYNAPSE_VAULT_PUSH_EVERY=5
 
 # How many nodes /synapse-init authors concurrently in its final step, via the