@imunitic/synapse 0.2.6 → 0.2.8

package/commands/synapse-status.md

@@ -43,7 +43,7 @@ frontmatter (unlike task notes) -- a content match, scoped to `designs/`. Needs
 synapse vault-search --fields frontmatter.title <<'EOF'
 {"and": [
   {"glob": ["designs/*", {"var": "path"}]},
-  {"regexp": ["## Status\\nDiscussing", {"var": "content"}]}
+  {"regexp": ["## Status\nDiscussing", {"var": "content"}]}
 ]}
 EOF
 ```
@@ -57,7 +57,7 @@ only the title:
 synapse vault-search --fields frontmatter.title <<'EOF'
 {"and": [
   {"glob": ["designs/*", {"var": "path"}]},
-  {"regexp": ["## Status\\nReady", {"var": "content"}]},
+  {"regexp": ["## Status\nReady", {"var": "content"}]},
   {"!": [{"regexp": ["Compiled task:", {"var": "content"}]}]}
 ]}
 EOF
@@ -74,22 +74,24 @@ rather than reading the note again:
 synapse vault-search --fields frontmatter.title,content <<'EOF'
 {"and": [
   {"glob": ["designs/*", {"var": "path"}]},
-  {"regexp": ["## Open Questions\\n- ", {"var": "content"}]}
+  {"regexp": ["## Open Questions\n- ", {"var": "content"}]}
 ]}
 EOF
 ```
 
-Do not chain further `and`/`regexp` conditions onto this query to sort matches by status -- compound
-`regexp` conditions against `content` have been observed to return results that are logically
-impossible (a query with strictly more AND-ed conditions returning *more* matches than one with
-fewer), so any query beyond a single `glob` + single `regexp` pair is unverified and not to be
-trusted here. Instead, take two things from each row's `content` column directly, no second call
-needed for either: the line following `## Status` (normally `Discussing`/`Ready`/`Reference`, but a
-note written before the three-word convention can carry free text instead, e.g. `Superseded by
-[[...]]` -- report that verbatim rather than forcing it into a bucket, surfacing an odd note beats
-losing it) and the target of a `> Compiled task: [[...]]` line, if present -- that's the compiled
-task, parsed straight out of the wikilink text rather than resolved through any vault-wide link
-index.
+This spans every status, so take two things from each row's `content` column directly instead of
+chaining further status-specific `regexp` branches onto the query: the line following `## Status`
+(normally `Discussing`/`Ready`/`Reference`, but a note written before the three-word convention can
+carry free text instead, e.g. `Superseded by [[...]]` -- report that verbatim rather than forcing it
+into a bucket, surfacing an odd note beats losing it) and the target of a `> Compiled task: [[...]]`
+line, if present -- that's the compiled task, parsed straight out of the wikilink text rather than
+resolved through any vault-wide link index.
+
+A `regexp` pattern containing a literal newline (`\n`) must be written with a single backslash, byte-
+for-byte, in the JSON text piped to `vault-search` -- the heredocs above are unquoted-delimiter
+(`<<'EOF'`), so nothing here re-escapes it; `\\n` would reach the JSON parser as a literal backslash
+followed by `n`, never matching a real line break, and every one of this command's five queries would
+silently stop finding anything under a multi-line pattern.
 
 **4. Open task notes with at least one unchecked item.** Task notes carry `status:` in frontmatter,
 unlike design notes -- filter there first, and request `content` to count `- [ ]` lines directly from

package/commands/synapse-vault-tidy.md

@@ -30,9 +30,11 @@ of scope — foundational files, not taxonomy notes.
 
 Requires the `synapse` CLI on `PATH`, resolving a vault with a working `LinkGraph`
 (`synapse vault-backlinks`/`vault-links`/`vault-unresolved`/`vault-orphans`/`vault-deadends` — see
-`sb — Obsidian CLI as ObsidianStore's transport`). If `SYNAPSE_VAULT_STORE` resolves to a backend
-with no `LinkGraph` yet, these commands exit 1 saying so; stop and report that rather than falling
-back to anything else.
+`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
+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
 same door every other skill uses — no MCP tool, no direct `ObsidianStore` call. `vault-links`/

package/harness/codex/skills/synapse-status/SKILL.md

@@ -45,7 +45,7 @@ frontmatter (unlike task notes) -- a content match, scoped to `designs/`. Needs
 synapse vault-search --fields frontmatter.title <<'EOF'
 {"and": [
   {"glob": ["designs/*", {"var": "path"}]},
-  {"regexp": ["## Status\\nDiscussing", {"var": "content"}]}
+  {"regexp": ["## Status\nDiscussing", {"var": "content"}]}
 ]}
 EOF
 ```
@@ -59,7 +59,7 @@ title -- "`Ready` and missing that line" is a direct signal, not fuzzy title-mat
 synapse vault-search --fields frontmatter.title <<'EOF'
 {"and": [
   {"glob": ["designs/*", {"var": "path"}]},
-  {"regexp": ["## Status\\nReady", {"var": "content"}]},
+  {"regexp": ["## Status\nReady", {"var": "content"}]},
   {"!": [{"regexp": ["Compiled task:", {"var": "content"}]}]}
 ]}
 EOF
@@ -75,21 +75,23 @@ the status directly out of the returned text rather than reading the note again:
 synapse vault-search --fields frontmatter.title,content <<'EOF'
 {"and": [
   {"glob": ["designs/*", {"var": "path"}]},
-  {"regexp": ["## Open Questions\\n- ", {"var": "content"}]}
+  {"regexp": ["## Open Questions\n- ", {"var": "content"}]}
 ]}
 EOF
 ```
 
-Do not chain further `and`/`regexp` conditions onto this query to sort matches by status -- compound
-`regexp` conditions against `content` have been observed to return results that are logically
-impossible (a query with strictly more AND-ed conditions returning *more* matches than one with
-fewer), so any query beyond a single `glob` + single `regexp` pair is unverified and not to be
-trusted here. Instead, take the line following `## Status` directly out of each row's `content`
-column -- normally `Discussing`/`Ready`/`Reference`, but a design note written before that
-three-word convention was standardized can carry free text there instead (e.g. `Superseded by
-[[...]]`); report that verbatim rather than forcing it into a bucket, surfacing an odd note beats
-losing it, the same reasoning behind reporting a 0-unchecked task instead of hiding it (see Query 4
-below).
+This spans every status, so take the line following `## Status` directly out of each row's `content`
+column instead of chaining further status-specific `regexp` branches onto the query -- normally
+`Discussing`/`Ready`/`Reference`, but a design note written before that three-word convention was
+standardized can carry free text there instead (e.g. `Superseded by [[...]]`); report that verbatim
+rather than forcing it into a bucket, surfacing an odd note beats losing it, the same reasoning behind
+reporting a 0-unchecked task instead of hiding it (see Query 4 below).
+
+A `regexp` pattern containing a literal newline (`\n`) must be written with a single backslash, byte-
+for-byte, in the JSON text piped to `vault-search` -- the heredocs above are unquoted-delimiter
+(`<<'EOF'`), so nothing here re-escapes it; `\\n` would reach the JSON parser as a literal backslash
+followed by `n`, never matching a real line break, and every one of this skill's five queries would
+silently stop finding anything under a multi-line pattern.
 
 **4. Open task notes with at least one unchecked item.** Task notes carry `status:` in frontmatter,
 unlike design notes -- filter there first, and request `content` to count `- [ ]` lines directly from

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

@@ -30,9 +30,11 @@ there is no argument to parse, every run produces the same one-pass sweep.
 ## Prerequisites
 
 Requires the `synapse` CLI on `PATH`, resolving a vault with a working link graph
-(`synapse vault-backlinks`/`vault-links`/`vault-unresolved`/`vault-orphans`/`vault-deadends`). If
-`SYNAPSE_VAULT_STORE` resolves to a backend with no link graph yet, these commands exit 1 saying so;
-stop and report that rather than falling back to anything else.
+(`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
+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
 door every other skill uses — no MCP tool, no direct `ObsidianStore` call. `vault-links`/

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@imunitic/synapse",
-  "version": "0.2.6",
+  "version": "0.2.8",
   "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.6",
-    "@imunitic/synapse-linux-x64": "0.2.6",
-    "@imunitic/synapse-linux-arm64": "0.2.6"
+    "@imunitic/synapse-darwin-arm64": "0.2.8",
+    "@imunitic/synapse-linux-x64": "0.2.8",
+    "@imunitic/synapse-linux-arm64": "0.2.8"
   },
   "license": "SEE LICENSE IN LICENSE"
 }

package/synapse-claude.md

@@ -96,17 +96,18 @@ a real yes/no answer, not a formality to wave past.
 
 The vault is reached through the `synapse` CLI — `synapse vault-read`/`vault-write`/`vault-list`/
 `vault-search`/`vault-search-text`/`vault-doc-map`/`vault-patch`/`vault-backlinks`/`vault-links`/
-`vault-unresolved`/`vault-orphans`/`vault-deadends` — 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
-(today, an Obsidian vault reached through its own official CLI; also a plain-disk vault,
-`SYNAPSE_VAULT_STORE=disk`) is resolved once, inside the compiled binary, from
-`SYNAPSE_VAULT_STORE`/`SYNAPSE_VAULT_DIR` — never something a skill or an agent turn needs to know or
-branch on. Today that means Obsidian running headless at login, with no plugin, no cert, no MCP
-server needed: `read`/`write`/`list` are plain disk I/O against the vault folder, and
-`search`/the link graph go through Obsidian's own CLI over its local socket — off by default, so a
-`vault-search-text`/`vault-backlinks`/etc. failure is worth mentioning **Settings → General →
-Advanced → Command line interface** for, alongside stopping on it (see the precondition-failure
-rule below).
+`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; or `obsidian`,
+opted into for a running Obsidian app's own live search relevance and graph data) is resolved once,
+inside the compiled binary, from `SYNAPSE_VAULT_STORE`/`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
+graph/rename go through Obsidian's own CLI over its local socket instead when Obsidian is running,
+falling back to the same disk-backed behavior automatically and silently (a one-line stderr note,
+nothing an agent turn needs to react to) whenever it isn't — no precondition to check or fail on
+either way.
 
 **Every write to a note goes through `synapse vault-write` or `vault-patch`. Never the `Write`/`Edit`
 tools on the on-disk path, and never a raw `mcp__obsidian__*` tool call either** — not for a one-line

package/synapse.conf.template

@@ -2,6 +2,15 @@
 # synapse.conf anywhere. Edit the path below for this machine.
 SYNAPSE_VAULT_DIR="$HOME/Obsidian/YourVault"
 
+# Default "disk" if unset: reads/writes the vault folder directly, no
+# dependency on Obsidian being open at all -- search and the link graph
+# (backlinks/links/unresolved/orphans/deadends/ambiguous) are computed by
+# DiskStore's own scan. Set to "obsidian" to prefer a running Obsidian
+# app's own live search relevance and graph data instead, falling back to
+# the same disk-backed behavior automatically whenever Obsidian isn't
+# reachable.
+#SYNAPSE_VAULT_STORE="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"