@imunitic/synapse 0.4.7 → 0.6.0

package/package.json

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

package/schema/graph-node/v1.yaml

@@ -0,0 +1,96 @@
+# Declared keys are the full v1 spec; enforcement is a deliberate subset -- unknown note fields are ignored, never an error.
+# `sources` is declared last on purpose: `field_order: relative` requires every other declared
+# field to sit ahead of it in the actual file, so a small, frequently-looked-up scalar is never
+# behind a `sources:` block that can run to hundreds of `path`/`hash` pairs on a large repo.
+schema: synapse-note-schema/v1
+id: graph-node/v1
+
+frontmatter:
+  field_order: relative
+  fields:
+    schema:
+      type: string
+      required: true
+      const: graph-node/v1
+    title:
+      type: string
+      required: true
+      min_length: 1
+    summary:
+      type: string
+      required: true
+      min_length: 1
+    node_type:
+      type: string
+      required: true
+      const: synapse-node
+    project:
+      type: string
+      required: true
+      min_length: 1
+    branch:
+      type: string
+      required: true
+      min_length: 1
+    sources_digest:
+      type: string
+      required: true
+      pattern: '^[0-9a-f]{64}$'
+    stale:
+      type: boolean
+      required: true
+    built_at:
+      type: string
+      required: true
+      pattern: '^[0-9]{4}-[0-9]{2}-[0-9]{2} [0-9]{2}:[0-9]{2}$'
+    commit:
+      type: string
+      required: false
+    crux_path:
+      type: string
+      required: false
+    crux_lines:
+      type: string
+      required: false
+    grounded_in:
+      type: any
+      required: false
+    sources:
+      type: any
+      required: true
+
+body:
+  h1:
+    required: true
+    count: 1
+    equals: frontmatter.title
+  # Crux and Links are `synapse-node-format`'s documented convention for every
+  # authored node, but nothing has ever structurally required either heading
+  # to exist -- `write-node`'s own crux/grounded_in extraction is scoped to
+  # `## Crux` only when present, never required. Required here would be a new
+  # constraint this schema doesn't need to introduce to do its actual job
+  # (field order, schema identity); Summary/Sources/Notes are required because
+  # `write-node` always emits all three unconditionally today, so requiring
+  # them adds no new constraint at all.
+  sections:
+    - title: Summary
+      level: 2
+      required: true
+      non_empty: true
+    - title: Crux
+      level: 2
+      required: false
+      non_empty: true
+    - title: Links
+      level: 2
+      required: false
+    - title: Sources
+      level: 2
+      required: true
+      non_empty: true
+    - title: Notes
+      level: 2
+      required: true
+  section_order: relative
+
+checks: []

package/schema/vault-design-note/v1.yaml

@@ -93,3 +93,11 @@ checks:
   - equals:
       values: [frontmatter.created, frontmatter.updated]
       when: create
+
+lints:
+  - no_hard_wrap: body.prose
+    severity: warn
+  - no_id_prefix_in_title:
+      title: frontmatter.title
+      id: frontmatter.note_id
+    severity: warn

package/schema/vault-note/v1.yaml

@@ -65,3 +65,7 @@ checks:
   - equals:
       values: [frontmatter.created, frontmatter.updated]
       when: create
+
+lints:
+  - no_hard_wrap: body.prose
+    severity: warn

package/schema/vault-task-note/v1.yaml

@@ -91,3 +91,11 @@ checks:
       field: frontmatter.status
       value: TODO
       when: create
+
+lints:
+  - no_hard_wrap: body.prose
+    severity: warn
+  - no_id_prefix_in_title:
+      title: frontmatter.title
+      id: frontmatter.task_id
+    severity: warn

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

@@ -55,7 +55,11 @@ to orient someone already inside. A node without one is an error, not a default.
   finds its node via this list). Do **not** trim it to a handful of "representative" files —
   doing so silently destroys that lookup, leaves the node unable to answer "which files am I
   about", and reduces hash verification to whatever survived the trim. Readability pressure
-  belongs on `## Sources` below, never here.
+  belongs on `## Sources` below, never here. Always the *last* frontmatter field — on a large
+  project it can run to hundreds of `path`/`hash` pairs, and every other field stays ahead of it so
+  a single-key lookup never has to scan past it. `graph-node/v1`'s schema enforces this order
+  directly (`field_order: relative`); this document and `synapse write-node`'s own emission order
+  agree with it, not the other way around.
 - **`sources_digest`:** `sha256` over the sorted `path:hash` lines of `sources` (see "Computing
   `sources_digest`" below). Lets a staleness check answer "has this node changed" by reading one
   field instead of every hash.
@@ -149,18 +153,19 @@ to orient someone already inside. A node without one is an error, not a default.
 
 ```yaml
 ---
+schema: graph-node/v1
 title: "World — entity/component/resource core"
 node_type: synapse-node
 project: acme
+sources_digest: <sha256 over the sorted "path:hash" lines>
+stale: false
+built_at: "<now>"
 sources:
   - path: acme_ecs/world.ml
     hash: <git hash-object output>
   - path: acme_ecs/world.mli
     hash: <git hash-object output>
   # ... every file the node covers, not a selection
-sources_digest: <sha256 over the sorted "path:hash" lines>
-stale: false
-built_at: "<now>"
 ---
 
 # World — entity/component/resource core