@imunitic/synapse 0.13.17 → 0.14.1

package/bin/synapse-setup.cjs

@@ -239,13 +239,9 @@ function configureClaude() {
   const rendered = renderHooksTemplate(path.join(PKG_ROOT, "harness", "claude", "hooks.json"), hookBin);
   settings.hooks = mergeHooksInto(settings.hooks, rendered);
 
-  // The npm-install counterpart to $CLAUDE_PLUGIN_ROOT -- conf.zig's own
-  // resolveConfPath and session_start.zig's synapse-claude.md/Index.md.template
-  // lookups both check this env var now that there's no plugin marketplace
-  // to set CLAUDE_PLUGIN_ROOT for them. Points at PKG_ROOT, the same
-  // relative shape CLAUDE_PLUGIN_ROOT used to point at plugins/synapse/ --
-  // synapse-claude.md, Index.md.template, and every *.conf.template sit
-  // directly under it.
+  // SYNAPSE_CONTENT_ROOT points at PKG_ROOT: the config resolution in
+  // Conf_Files and the session-start hook look up synapse-claude.md,
+  // Index.md.template and every *.conf.template directly under it.
   settings.env = settings.env || {};
   settings.env.SYNAPSE_CONTENT_ROOT = PKG_ROOT;
 

package/commands/synapse-rebuild-full.md

@@ -148,5 +148,5 @@ note live containing only the leftovers, trimmed of everything that did get merg
   only the wipe-with-preservation step before it and the note-merge step after it.
 - The wipe itself is `synapse graph-wipe` (via `synapse graph-wipe`), mirroring
   `synapse graph-clean` as the only other destructive tool in the system.
-- Resolves the namespace the same way `/synapse-init` and `/synapse-rebuild-diff` do -- one chain, in `core/identity.zig`
+- Resolves the namespace the same way `/synapse-init` and `/synapse-rebuild-diff` do -- one chain, in `Core.Identity`
   — never re-derives repo/branch/remote independently.

package/harness/codex/skills/synapse-rebuild-full/SKILL.md

@@ -146,4 +146,4 @@ note live containing only the leftovers, trimmed of everything that did get merg
 - The wipe itself is `synapse graph-wipe` (via `synapse graph-wipe`), mirroring
   `synapse graph-clean` as the only other destructive tool in the system.
 - Resolves the namespace the same way the synapse-init and synapse-rebuild-diff skills do -- one
-  chain, in `core/identity.zig` — never re-derives repo/branch/remote independently.
+  chain, in `Core.Identity` — never re-derives repo/branch/remote independently.

package/harness/opencode/plugin/synapse.js

@@ -2,7 +2,7 @@
 // Code's hooks.json already calls, translating OpenCode's plugin callbacks
 // into the same stdin JSON payload / stdout `hookSpecificOutput` shape the
 // binary already reads and writes. No engine change -- see
-// `src/apps/hook/main.zig`'s own doc comment for that contract.
+// `src/hooks/synapse-hooks-dispatch.ads`'s own doc comment for that contract.
 //
 // Ported to the OpenCode v2 plugin API (2.0.x). The v2 loader rejects this
 // file's old shape outright at load time -- it requires a default export

package/lib/resolve-binaries.cjs

@@ -15,9 +15,9 @@ const path = require("path");
 const CLI_NAME = "synapse";
 const HOOK_NAME = "synapse-hook";
 
-// Matches process.platform/process.arch directly (not a Zig target triple)
+// Matches process.platform/process.arch directly (not a compiler target triple)
 // since that's what npm's own `os`/`cpu` fields select against -- the
-// release pipeline maps its Zig target names to this naming once, at
+// release pipeline maps its target names to this naming once, at
 // publish time, not here.
 function platformPackageName() {
   return `@imunitic/synapse-${process.platform}-${process.arch}`;

package/package.json

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

package/skills/synapse-node-authoring/SKILL.md

@@ -44,7 +44,7 @@ conf file actually lives"): the first tier with a file at all wins, whether or n
 sets `SYNAPSE_AUTHOR_POOL` — a `synapse.conf` at `~/.claude/` is not consulted when one already
 exists at the XDG tier, even if the XDG one is silent on this key. Absent, empty, or malformed
 all fall through to `0`. **This is read by you, the orchestrating agent, directly — not by any
-Zig binary.** Nothing compiled dispatches subagents, so there is nothing for a `synapse` flag to
+compiled binary.** Nothing compiled dispatches subagents, so there is nothing for a `synapse` flag to
 feed. The conf file is the shared home for the setting; the reader is markdown, not code.
 
 `pool = 0` is not "a pool of zero workers" — go to §2. `pool >= 1` is a real worker pool — go
@@ -142,7 +142,7 @@ convention. State it here, every time, rather than assuming it travels for free.
 ### 3d. Verify on completion, retry once, then fall back
 
 When a completion notification arrives, read `b-NN.md` yourself — this is a check you read the
-file for, same as the section check next to it, not a shell one-liner (`core/query.zig` is this
+file for, same as the section check next to it, not a shell one-liner (`Core.Frontmatter` is this
 codebase's own tested, compiled frontmatter reader — a fresh hand-rolled `grep`/`sed`/`awk`
 pattern here would drift from it the same way the gap this section exists to close first
 happened). Confirm the file exists, opens with

package/skills/synapse-orientation/SKILL.md

@@ -406,9 +406,9 @@ discipline — never assume a patch worked from reading it:
 
 A per-file "this file depends on library L" edge narrows an ambiguous reference (a name defined in
 more than one node) to the candidate the referencing file actually declares a dependency on —
-`core/links.zig`'s own real signal for that case, read from `synapse-dependency-rules.conf`
+`Core.Links`' own real signal for that case, read from `synapse-dependency-rules.conf`
 (`SYNAPSE_DEPENDENCY_RULES_CONF` overrides the path), a second registry alongside
-`synapse-namespace-rules.conf` and reusing the exact same `core/namespace.Rule`/`Registry` shape
+`synapse-namespace-rules.conf` and reusing the exact same `Core.Namespace.Rule`/`Registry` shape
 unchanged — a rule per extension, `kind` `in-file` or `build-file`, ordered `prefix`/`terminator`,
 first match wins, no per-language branching in code. A separate file, not a second key on the same
 one: an extension can need both a namespace rule (what a file *is*) and a dependency rule (what a

package/synapse.conf.template

@@ -44,7 +44,7 @@ SYNAPSE_GRAMMARS_DIR="$HOME/.cache/synapse/grammars"
 # -- the safest choice and the only one that preserves cross-node authorial
 # memory. N>=1 fans out to a worker pool of that size instead, each node
 # written by an isolated subagent. Read directly by the orchestrating agent
-# when it runs /synapse-init, not by any Zig binary -- nothing compiled
+# when it runs /synapse-init, not by any compiled binary -- nothing compiled
 # dispatches subagents.
 #SYNAPSE_AUTHOR_POOL=0