@imunitic/synapse 0.13.12 → 0.13.14

package/commands/synapse-design-note.md

@@ -1,6 +1,5 @@
 ---
-description: Start or continue a free-form, cross-project design discussion, written to Synapse Vault rather than tied to one repo — thinking through a problem/approach/tradeoffs out loud before anything is built. Use whenever the user wants to open, resume, or reason through a design ("let's create/write a design note", "let's think through X", "let's design this", "let's talk this through"). Not for a note that's already ready to become tracked work (that's synapse-task-note), or a plain vault note with no design framing (that's synapse-note, whose project-resolution logic this command reuses).
-disable-model-invocation: true
+description: Start or continue a design discussion as a Synapse Vault design note.
 ---
 
 # Synapse Design Note: Cross-Project Personal Design Discussion

package/commands/synapse-init.md

@@ -1,6 +1,5 @@
 ---
-description: Build a repo's Synapse Graph namespace from scratch — enumerate tracked files, orient into the repo's own symbol vocabulary, cluster into manifest.tsv, gate cluster quality, compute the link graph, author each node's prose, and write the two derived projections (_index.bin, Index.md). This is the only way a project gets a Synapse namespace in the first place — nothing else in the system creates one unprompted. Also handles the lighter re-run case for an already-initialized project (sweeping unassigned files into existing nodes, never re-clustering). Use whenever the user wants to set up Synapse for a repo for the first time ("init synapse here", "build the code graph", "set up the namespace") or asks to sweep newly-unassigned files into an existing graph. Not for repairing drift in an existing namespace (that's synapse-rebuild-diff) or a full wipe-and-rebuild (that's synapse-rebuild-full).
-disable-model-invocation: true
+description: Build this repo's Synapse code-graph namespace from scratch, or sweep unassigned files into an existing one.
 ---
 
 # Synapse Init: Build or Refresh a Repo's Code-Graph Namespace

package/commands/synapse-note.md

@@ -1,6 +1,5 @@
 ---
-description: Create a plain note in Synapse Vault (bare mode — title + frontmatter, category resolved from Index.md), a tracked task note (--task, scaffolds the checklist skeleton synapse-task expects), list every tracked task (--list), or search existing notes (--search) before creating a new one. Use for a note with no design framing, or any task note not compiled from a design discussion. Not for starting/continuing a design conversation (that's synapse-design-note) or compiling a Ready one into a task (that's synapse-task-note) — both of those delegate to this command themselves.
-disable-model-invocation: true
+description: Create a plain or task note in Synapse Vault, list tracked tasks, or search existing notes.
 ---
 
 Create a note in Synapse Vault with the title and options, list existing notes, or search existing notes: $ARGUMENTS

package/commands/synapse-rebuild-diff.md

@@ -1,7 +1,6 @@
 ---
 name: synapse-rebuild-diff
-description: Manually bring a repo's Synapse namespace back in line after major same-branch drift — a pull, a rebase, or a long absence. Triages each drifted node into reseat / patch-from-diff / re-orient rather than rebuilding everything. Refuses outright on a cross-branch mismatch; for a full rebuild from scratch, use /synapse-rebuild-full instead.
-disable-model-invocation: true
+description: Bring this repo's Synapse namespace back in line after same-branch drift: a pull, a rebase, or a long absence.
 ---
 
 # Synapse Rebuild Diff: Reconcile a Namespace After Same-Branch Drift
@@ -39,8 +38,8 @@ Manually, when you already expect major drift:
   bad cases at once — renames *and* new paths), a `sed -i`, generated code that the build rewrote from a
   schema, a dependency bump, or a moved submodule pointer.
 
-Run it whenever the graph has fallen behind: the SessionStart line reports how many commits HEAD is
-past it, and `synapse query drift` shows what changed. A small drift after an ordinary pull is an
+Run it whenever the graph has fallen behind: the SessionStart line reports how many nodes claim
+files changed since they were built, and `synapse query drift` shows what changed. A small drift after an ordinary pull is an
 ordinary run, with a few nodes in the *patch-from-diff* class. Between runs, Tier 1 flags what a
 session edits and the `synapse-node` skill regenerates a stale node lazily when its body is needed.
 

package/commands/synapse-rebuild-full.md

@@ -1,7 +1,6 @@
 ---
 name: synapse-rebuild-full
-description: Wipe a repo's Synapse namespace and rebuild it from scratch via /synapse-init, for the case where diff-driven triage isn't the right tool — the graph has drifted too far, or a clean rebuild is just wanted directly. Preserves any hand-written `## Notes` content first and auto-merges what it can back into the new nodes. For ordinary same-branch drift, use /synapse-rebuild-diff instead — it's cheaper and never deletes a node outright.
-disable-model-invocation: true
+description: Wipe and rebuild this repo's Synapse namespace from scratch, keeping hand-written Notes.
 ---
 
 # Synapse Rebuild Full: Wipe and Rebuild a Namespace From Scratch

package/commands/synapse-status.md

@@ -1,6 +1,5 @@
 ---
-description: Print a read-only report of what in Synapse Vault currently needs a human decision -- design notes still Discussing, design notes marked Ready with no compiled task yet, Ready design notes with open questions still outstanding, task notes with unchecked items, and task notes stuck in REVIEW. Use whenever the user wants a status check on the vault ("what's outstanding", "what needs my attention", "vault status", "what did we leave open"). Never modifies anything -- a report only, not a task-management action. Not for creating, continuing, or listing a specific note kind (that's synapse-note/synapse-design-note/synapse-task-note's own --list modes) -- this is the one cross-cutting view over all of them at once.
-disable-model-invocation: true
+description: Read-only report of what in Synapse Vault currently needs a human decision.
 ---
 
 # Synapse Status: Vault-Wide Attention Report

package/commands/synapse-task-note.md

@@ -1,6 +1,5 @@
 ---
-description: Compile a Ready design note into a single tracked, checklist-based task note in Synapse Vault — delegates the actual note creation to synapse-note --task under the hood. Use whenever the user wants to turn a settled design discussion into actionable, tracked work ("let's compile a task note", "let's turn this into a task", "make this a task now") — not for starting or continuing the design discussion itself (that's synapse-design-note).
-disable-model-invocation: true
+description: Compile a Ready design note into one tracked task note in Synapse Vault.
 ---
 
 # Synapse Task Note: Compile a Design into a Tracked Checklist

package/commands/synapse-vault-tidy.md

@@ -1,6 +1,5 @@
 ---
-description: Run one on-demand vault-tidy pass over Synapse Vault -- surface recategorization candidates (notes that no longer fit their folder, clusters that deserve a new top-level category, categories that have gone stale) into a single inbox/ proposal, silently fill in the one class of missing-frontmatter default that has an unambiguous fix, and fold the rest of note health (broken links, orphaned notes, duplicate titles) into that same proposal since none of them has a safe mechanical repair either. Use whenever the user wants the vault's own organization checked or tidied ("tidy the vault", "check vault health", "any notes drifted out of their folder", "find orphaned/duplicate notes"). Never invoked automatically -- no SessionStart wiring, no autonomous scheduling; run it yourself, or under your own /loop if you want a cadence. Scoped to everything except designs/, tasks/, and synapse/ (the code graph's own generated namespace), which stay entirely /synapse-status's (the first two) or /synapse-init's (the third) territory.
-disable-model-invocation: true
+description: One on-demand tidy pass over Synapse Vault: recategorization and note-health findings as a single proposal.
 ---
 
 # Synapse Vault Tidy: Recategorization Proposals and Note-Health Fixes

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

@@ -38,8 +38,8 @@ Manually, when you already expect major drift:
   at once — renames *and* new paths), a `sed -i`, generated code that the build rewrote from a
   schema, a dependency bump, or a moved submodule pointer.
 
-Run it whenever the graph has fallen behind: the SessionStart line reports how many commits HEAD is
-past it, and `synapse query drift` shows what changed. A small drift after an ordinary pull is an
+Run it whenever the graph has fallen behind: the SessionStart line reports how many nodes claim
+files changed since they were built, and `synapse query drift` shows what changed. A small drift after an ordinary pull is an
 ordinary run, with a few nodes in the *patch-from-diff* class. Between runs, Tier 1 flags what a
 session edits and the `synapse-node` skill regenerates a stale node lazily when its body is needed.
 

package/package.json

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