@imunitic/synapse 0.2.7 → 0.2.8

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.
@@ -30,9 +30,11 @@ of scope — foundational files, not taxonomy notes.
30
30
 
31
31
  Requires the `synapse` CLI on `PATH`, resolving a vault with a working `LinkGraph`
32
32
  (`synapse vault-backlinks`/`vault-links`/`vault-unresolved`/`vault-orphans`/`vault-deadends` — see
33
- `sb — Obsidian CLI as ObsidianStore's transport`). If `SYNAPSE_VAULT_STORE` resolves to a backend
34
- with no `LinkGraph` yet, these commands exit 1 saying so; stop and report that rather than falling
35
- back to anything else.
33
+ `sb — Obsidian CLI as ObsidianStore's transport` and `sb DiskStore's own index, Obsidian becomes
34
+ optional`). Both real coding-vault backends have one now `obsidian` reaching the CLI when
35
+ reachable and falling back to `disk`'s own implementation otherwise, `disk` always local. If
36
+ `SYNAPSE_VAULT_STORE` ever resolves to a backend with no `LinkGraph` at all, these commands exit 1
37
+ saying so; stop and report that rather than falling back to anything else.
36
38
 
37
39
  This command reaches the vault store only through the `synapse` CLI's `vault-*` subcommands, the
38
40
  same door every other skill uses — no MCP tool, no direct `ObsidianStore` call. `vault-links`/
@@ -30,9 +30,11 @@ there is no argument to parse, every run produces the same one-pass sweep.
30
30
  ## Prerequisites
31
31
 
32
32
  Requires the `synapse` CLI on `PATH`, resolving a vault with a working link graph
33
- (`synapse vault-backlinks`/`vault-links`/`vault-unresolved`/`vault-orphans`/`vault-deadends`). If
34
- `SYNAPSE_VAULT_STORE` resolves to a backend with no link graph yet, these commands exit 1 saying so;
35
- stop and report that rather than falling back to anything else.
33
+ (`synapse vault-backlinks`/`vault-links`/`vault-unresolved`/`vault-orphans`/`vault-deadends`). Both
34
+ real coding-vault backends have one `disk` (the default) always local, `obsidian` reaching a
35
+ running app when reachable and falling back to `disk`'s own implementation otherwise. If
36
+ `SYNAPSE_VAULT_STORE` ever resolves to a backend with no link graph at all, these commands exit 1
37
+ saying so; stop and report that rather than falling back to anything else.
36
38
 
37
39
  This skill reaches the vault store only through the `synapse` CLI's `vault-*` subcommands, the same
38
40
  door every other skill uses — no MCP tool, no direct `ObsidianStore` call. `vault-links`/
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@imunitic/synapse",
3
- "version": "0.2.7",
3
+ "version": "0.2.8",
4
4
  "description": "Memory for Claude Code, Codex CLI, and OpenCode: a durable Obsidian vault plus a per-repo code graph.",
5
5
  "repository": {
6
6
  "type": "git",
@@ -22,9 +22,9 @@
22
22
  "*.conf.template"
23
23
  ],
24
24
  "optionalDependencies": {
25
- "@imunitic/synapse-darwin-arm64": "0.2.7",
26
- "@imunitic/synapse-linux-x64": "0.2.7",
27
- "@imunitic/synapse-linux-arm64": "0.2.7"
25
+ "@imunitic/synapse-darwin-arm64": "0.2.8",
26
+ "@imunitic/synapse-linux-x64": "0.2.8",
27
+ "@imunitic/synapse-linux-arm64": "0.2.8"
28
28
  },
29
29
  "license": "SEE LICENSE IN LICENSE"
30
30
  }
package/synapse-claude.md CHANGED
@@ -96,17 +96,18 @@ a real yes/no answer, not a formality to wave past.
96
96
 
97
97
  The vault is reached through the `synapse` CLI — `synapse vault-read`/`vault-write`/`vault-list`/
98
98
  `vault-search`/`vault-search-text`/`vault-doc-map`/`vault-patch`/`vault-backlinks`/`vault-links`/
99
- `vault-unresolved`/`vault-orphans`/`vault-deadends` — for reads *and* for writes, never by resolving
100
- a vault path or calling an `mcp__obsidian__*` tool directly. Which concrete store the CLI talks to
101
- (today, an Obsidian vault reached through its own official CLI; also a plain-disk vault,
102
- `SYNAPSE_VAULT_STORE=disk`) is resolved once, inside the compiled binary, from
103
- `SYNAPSE_VAULT_STORE`/`SYNAPSE_VAULT_DIR` — never something a skill or an agent turn needs to know or
104
- branch on. Today that means Obsidian running headless at login, with no plugin, no cert, no MCP
105
- server needed: `read`/`write`/`list` are plain disk I/O against the vault folder, and
106
- `search`/the link graph go through Obsidian's own CLI over its local socket — off by default, so a
107
- `vault-search-text`/`vault-backlinks`/etc. failure is worth mentioning **Settings General
108
- Advanced Command line interface** for, alongside stopping on it (see the precondition-failure
109
- rule below).
99
+ `vault-unresolved`/`vault-orphans`/`vault-deadends`/`vault-ambiguous`/`vault-rename` — for reads
100
+ *and* for writes, never by resolving a vault path or calling an `mcp__obsidian__*` tool directly.
101
+ Which concrete store the CLI talks to (`SYNAPSE_VAULT_STORE=disk`, the default; or `obsidian`,
102
+ opted into for a running Obsidian app's own live search relevance and graph data) is resolved once,
103
+ inside the compiled binary, from `SYNAPSE_VAULT_STORE`/`SYNAPSE_VAULT_DIR` — never something a skill
104
+ or an agent turn needs to know or branch on. By default that means no Obsidian dependency
105
+ whatsoever: `read`/`write`/`list`/`search`/the link graph/rename are all plain disk I/O and direct
106
+ computation against the vault folder. Under the opted-in `obsidian` backend, `search`/the link
107
+ graph/rename go through Obsidian's own CLI over its local socket instead when Obsidian is running,
108
+ falling back to the same disk-backed behavior automatically and silently (a one-line stderr note,
109
+ nothing an agent turn needs to react to) whenever it isn't — no precondition to check or fail on
110
+ either way.
110
111
 
111
112
  **Every write to a note goes through `synapse vault-write` or `vault-patch`. Never the `Write`/`Edit`
112
113
  tools on the on-disk path, and never a raw `mcp__obsidian__*` tool call either** — not for a one-line
@@ -2,6 +2,15 @@
2
2
  # synapse.conf anywhere. Edit the path below for this machine.
3
3
  SYNAPSE_VAULT_DIR="$HOME/Obsidian/YourVault"
4
4
 
5
+ # Default "disk" if unset: reads/writes the vault folder directly, no
6
+ # dependency on Obsidian being open at all -- search and the link graph
7
+ # (backlinks/links/unresolved/orphans/deadends/ambiguous) are computed by
8
+ # DiskStore's own scan. Set to "obsidian" to prefer a running Obsidian
9
+ # app's own live search relevance and graph data instead, falling back to
10
+ # the same disk-backed behavior automatically whenever Obsidian isn't
11
+ # reachable.
12
+ #SYNAPSE_VAULT_STORE="obsidian"
13
+
5
14
  # Where Synapse clones/builds tree-sitter grammars (shared across every
6
15
  # project -- not per-repo). Safe to leave at the default.
7
16
  SYNAPSE_GRAMMARS_DIR="$HOME/.cache/synapse/grammars"