@imunitic/synapse 0.13.5 → 0.13.7

package/commands/synapse-design-note.md

@@ -238,7 +238,7 @@ edit history here worth tracking separately.
 ## Filename
 
 `designs/{project}/{Topic}.md` — grouped one level deeper into a per-project
-subfolder named by the note's own `project:` frontmatter value (e.g. `designs/eon/`,
+subfolder named by the note's own `project:` frontmatter value (e.g. `designs/widget/`,
 `designs/synapse/`), the same mapping `tasks/{project}/` uses. Sanitize filesystem-illegal
 characters (`/ : * ? " < > |`). No slug, no numbering — vault filenames are the title itself.
 

package/commands/synapse-init.md

@@ -40,8 +40,8 @@ No arguments — always operates on the repo containing the current working dire
 Every step below needs the same three facts, resolved once up front:
 
 1. **Repo root:** `git rev-parse --show-toplevel`.
-2. **Namespace key:** `{repo}@{branch}`, resolved by `synapse_namespace` in
-   `synapse namespace` — never derived by hand here, since every component resolves it the same way
+2. **Namespace key:** `{repo}@{branch}`, resolved by `synapse namespace`
+   (`core.identity.namespace`) — never derived by hand here, since every component resolves it the same way
    from that one place and a second derivation is how they start disagreeing. The repo half comes
    from the *remote's* basename, not the directory: a linked worktree's directory name differs from
    its parent's, and that difference is exactly what must not matter. The branch half is
@@ -51,8 +51,8 @@ Every step below needs the same three facts, resolved once up front:
    and `stale` describing a single tree, and it means a branch switch leaves the old graph intact
    rather than invalidating it wholesale.
 
-   **On a detached HEAD, stop.** There is no branch, so there is no key — `synapse_namespace` exits
-   1 and says so. Do not invent one, and do not fall back to the directory name: every detached
+   **On a detached HEAD, stop.** There is no branch, so there is no key — `synapse namespace` exits
+   1 with `core.identity.detached_message`. Do not invent one, and do not fall back to the directory name: every detached
    checkout everywhere would collide on the same value. Tell the user to check out a branch first.
 
    Distinct from the short task-prefix scheme (`project-name=prefix`) used by

package/commands/synapse-note.md

@@ -32,7 +32,7 @@ Categorize:
 - **Prefixed notes**: `task_id` matches `{prefix}-\d+`. Group by the distinct prefix found (whatever
   prefixes actually appear — don't assume a fixed set). Within each prefix, split further into:
   - **Open**: `status` is `TODO`, `IN-PROGRESS`, or `REVIEW` (or missing — treat as open)
-  - **Closed**: `status` is `DONE`, `CANCELED`, or `CANCELLED`
+  - **Closed**: `status` is `DONE` or `CANCELED`
 - **Other notes**: no `task_id`, or one that doesn't match `{prefix}-\d+`
 
 Sort each prefix group's notes numerically by task id (`{prefix}-9` before `{prefix}-10`); sort other notes alphabetically by title. Report one section per prefix found — "{prefix} notes — open", "{prefix} notes — closed" — plus "Other notes", each line as `{task-id or filename} — {title} [{status}]`. Omit a section header if it has zero entries. End with a total count.

package/commands/synapse-rebuild-full.md

@@ -32,7 +32,7 @@ No arguments — always operates on the repo and branch containing the current w
 - Requires the `synapse` CLI on `PATH`. If it errors (no vault configured), say so and stop —
   same requirement `/synapse-init` has.
 - Must be run from inside a git repository, on a named branch (not detached `HEAD`) — same
-  requirement `/synapse-init` has, since `synapse_namespace` needs a branch to key on.
+  requirement `/synapse-init` has, since `synapse namespace` needs a branch to key on.
 
 ## Procedure
 

package/commands/synapse-task-note.md

@@ -35,7 +35,7 @@ Use those instead of reinventing a parallel view.
   nothing to compile. Reopen it with `/synapse-design-note \"{topic}\"` and mark it Ready if that's
   changed."
 - A task note already exists for this design (check the design note's `> Compiled task:` annotation,
-  or `search_query` for a `tasks/` note linking to it) → show its current state (title, `status:`,
+  or `synapse vault-search-text` for a `tasks/` note linking to it) → show its current state (title, `status:`,
   checked/total) and ask: view it, or recompile (only on explicit confirmation — recompiling rewrites
   the checklist, so any progress on items that no longer exist is lost).
 

package/commands/synapse-vault-tidy.md

@@ -83,8 +83,9 @@ just two fields (`title`, `created` — see `synapse-note`'s bare-mode format),
 guessing:
 
 - Missing `title` → the filename with its `.md` extension stripped.
-- Missing `created` → `stat.ctime`, formatted `YYYY-MM-DD HH:MM` to match every other note's
-  convention.
+- Missing `created` → `stat.ctime`, formatted as RFC3339 with a numeric offset (`synapse now`'s
+  own shape) to match every other note's real `created`/`updated` convention — not `built_at`'s
+  coarser `YYYY-MM-DD HH:MM`, which is graph-node-only.
 
 Apply with `synapse frontmatter set <path> <key> <value>` (or `vault-patch --frontmatter`, which
 delegates to the same byte-preserving mechanism) — either writes exactly this one field and leaves
@@ -154,7 +155,7 @@ proposal, for the vault owner to act on.
 ## Step 6: Compose the proposal
 
 One note, `inbox/Vault tidy — {YYYY-MM-DD}.md` (fetch machine local time, never infer it), written
-via `vault_write` (creates `inbox/` automatically if it doesn't exist yet; if `inbox/` isn't already
+via `vault-write` (creates `inbox/` automatically if it doesn't exist yet; if `inbox/` isn't already
 in `Index.md`'s folder list, add it there in the same pass, matching the folder-layout rule every
 other command that can create a top-level folder already follows). Two sections:
 

package/harness/codex/skills/synapse-design-note/SKILL.md

@@ -231,6 +231,10 @@ already follows above, just additive instead of pruned. Named `References` rathe
 `## Links` for something unrelated (source files, typed relations) in that other kind of note
 sharing the same vault.
 
+Any string scalar that is all digits (e.g. a numeric-looking title) must be quoted: an
+unquoted all-digit value is parsed as an integer, which fails a `type: string` schema
+field. `title`, `project`, `note_id`, and both timestamps are quoted above.
+
 Resolve tags through the `synapse-vault` skill's configured vocabulary procedure. Fetch machine
 local time once (`synapse now`) — never infer it — and use the exact same value for `created` and
 `updated`.
@@ -241,7 +245,7 @@ edit history here worth tracking separately.
 ## Filename
 
 `designs/{project}/{Topic}.md` — grouped one level deeper into a per-project
-subfolder named by the note's own `project:` frontmatter value (e.g. `designs/eon/`,
+subfolder named by the note's own `project:` frontmatter value (e.g. `designs/widget/`,
 `designs/synapse/`), the same mapping tasks use. Sanitize filesystem-illegal
 characters (`/ : * ? " < > |`). No slug, no numbering — vault filenames are the title itself.
 

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

@@ -250,6 +250,11 @@ or supplied directly by a caller like the synapse-task-note skill):
 
    {constraints or context}
    ```
+
+   Quote every scalar string value. In particular, a value that is all digits
+   (a numeric-looking `title`, or any future numeric id) must be quoted — an
+   unquoted all-digit value is parsed as an integer and fails a `type: string`
+   schema field.
 5. Write it with `synapse vault-write <path>` (content on stdin). Task mode: path
    `tasks/{project}/{filename}.md` (project resolved in "Resolving the
    project folder" above). Bare mode: path `{category}/{filename}.md`

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

@@ -155,7 +155,7 @@ proposal, for the vault owner to act on.
 ## Step 6: Compose the proposal
 
 One note, `inbox/Vault tidy — {YYYY-MM-DD}.md` (fetch machine local time, never infer it), written
-via `vault_write` (creates `inbox/` automatically if it doesn't exist yet; if `inbox/` isn't already
+via `vault-write` (creates `inbox/` automatically if it doesn't exist yet; if `inbox/` isn't already
 in the index note's folder list, add it there in the same pass, matching the folder-layout rule every
 other skill that can create a top-level folder already follows). Two sections:
 

package/package.json

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

package/skills/synapse-node/SKILL.md

@@ -14,7 +14,7 @@ speculatively.
 
 Whenever a `synapse/{project}/{Node}.md` file is about to be read **for its content to actually be
 used** (orienting on a subsystem, answering a question about it, deciding where to make a change)
-— not for a `vault_list`/title-only skim. Run this procedure *before* trusting what comes back from
+— not for a `vault-list`/title-only skim. Run this procedure *before* trusting what comes back from
 that read. This is the one Synapse mechanism that isn't a hook: a hook is compiled code with no
 reasoning, and classifying whether a file "fits" a node is exactly the kind of judgment call that
 needs one.
@@ -133,7 +133,7 @@ needs one.
 
      It replaces only the generated region and re-emits everything after the closing fence verbatim,
      which is what makes the `## Notes` guarantee enforceable rather than a promise.
-   - **Never hand-write the frontmatter**, with `vault_patch` at `targetType: frontmatter` or
+   - **Never hand-write the frontmatter**, with `vault-patch --frontmatter <key>` or
      otherwise. `--frontmatter` only ever writes a single scalar value, so it can't represent
      `sources:`/`grounded_in:` at all, and enumerating the rest of a node's fields by hand one call
      at a time is how `summary` and `commit` get silently dropped — which then breaks the next
@@ -195,7 +195,7 @@ needs one.
 - Never treat the script's exit 1 as a clean result. It means the check could not run.
 - Never regenerate a node that neither the script nor its `stale:` flag named — regeneration is real
   cost, reserved for actual staleness.
-- Never `vault_read` a hub node just to read its summary. Offset past the frontmatter (step 3).
+- Never `vault-read` a hub node just to read its summary. Offset past the frontmatter (step 3).
 - Never silently fold a regeneration or an unassigned-file attachment into normal output — both
   get an explicit, visible announcement line.
 - `## Notes` content is sacrosanct across regeneration — if a rewrite would touch it, that's a bug

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

@@ -9,11 +9,9 @@ Loaded wherever a *batch* of nodes needs prose written, not a single lazy regene
 is the `synapse-node` skill's job, one node, triggered by a stale read). Today's caller is
 `/synapse-init`'s node-authoring step. `/synapse-rebuild-full` inherits this for free — it
 delegates to `/synapse-init`'s procedure by reference rather than repeating it.
-`/synapse-rebuild-diff`'s *re-orient* class is a natural second caller (see the design's own
-Open Questions and the vault's `inbox/wire synapse-rebuild-diff's re-orient class onto the
-parallel-authoring skill` note) but is not wired to this skill yet — it still
-gathers its facts ad hoc rather than through `rank --lists`/`link-graph`, and needs that fixed
-first.
+`/synapse-rebuild-diff`'s *re-orient* class is a natural second caller but is not wired to this
+skill yet — it still gathers its facts ad hoc rather than through `rank --lists`/`link-graph`,
+and needs that fixed first.
 
 This skill owns two things: **deciding how many authors run at once**, and **the standing
 contract every author works under**, whichever pool size is in play. Which nodes need
@@ -132,23 +130,22 @@ flowing text.
 
 Same model as the orchestrating session, no override — matches the constraint that "a
 parallel author produces exactly what a sequential one does," and keeps the quality
-comparison in the design's own checklist item to one variable (isolation/concurrency) rather
-than two (that, plus a cheaper model).
+comparison to one variable (isolation/concurrency) rather than two (that, plus a cheaper model).
 
 **Why this is spelled out explicitly rather than assumed inherited:** a prior pooled run shipped
-hard-wrapped nodes despite the vault's no-hard-wrap rule living in global `CLAUDE.md`
-instructions — evidently not reliably carried into a fresh subagent's behavior on its own.
-Loading `synapse-node-format` does not cover it either, since that skill is about the node's
-structure, not the vault's prose-formatting convention. State it here, every time, rather than
-assuming it travels for free.
+hard-wrapped nodes despite the vault's own no-hard-wrap convention (every paragraph is one
+continuous line in the source, letting the viewer soft-wrap it) — evidently not reliably carried
+into a fresh subagent's behavior on its own. Loading `synapse-node-format` does not cover it
+either, since that skill is about the node's structure, not the vault's prose-formatting
+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 (this codebase's own
-frontmatter reader deliberately avoids `grep`/`sed`/`awk` for exactly this field, per
-`core/query.zig`'s docstring — a hand-rolled pattern here would drift from it the same way the
-gap this section exists to close first happened). Confirm the file exists, opens with
+file for, same as the section check next to it, not a shell one-liner (`core/query.zig` 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
 frontmatter carrying a non-empty `summary:` field (`synapse-node-format`'s own contract — see
 its "Each `b-NN.md` opens with its own one-line summary in frontmatter" line), and has
 `## Summary`, `## Crux`, and `## Links` sections. Pass → dispatch the next queued node (§3b) and
@@ -177,9 +174,8 @@ Not a synonym for §2. It still bundles a brief, dispatches to an isolated subag
 and retries-then-falls-back — only the concurrency is 1. Useful on its own terms: it isolates
 whether a quality difference against the sequential baseline comes from *isolation* (no
 author sees another's output or memory — present even at pool 1) or from *concurrency*
-itself (only present at pool ≥ 2). Reach for it specifically when running the design's
-still-open "compare prose quality against a sequential build" checklist item, before
-committing to a higher pool size.
+itself (only present at pool ≥ 2). Reach for it specifically when comparing prose quality
+against a sequential build, before committing to a higher pool size.
 
 ## Guardrails
 
@@ -188,13 +184,12 @@ committing to a higher pool size.
   read-only during it — this is what removes the concurrent-writer problem rather than merely
   managing it.
 - **No author reads another node's brief or body.** Overlap in *source* reads (two nodes'
-  file lists sharing a path) is expected and accepted — see the design's Open Questions — but
-  an author's own inputs are its brief and nothing else.
+  file lists sharing a path) is expected and accepted, but an author's own inputs are its
+  brief and nothing else.
 - **Never grow the pool mid-run.** The size is resolved once at the start (§1); do not read
   `synapse.conf` again partway through a build.
 - **A retry gets the same brief, not a rewritten one.** If the brief itself was the problem,
   fixing it is a §3a-level fix (regenerate every brief and restart), not something to
   improvise per-node inside the retry.
 - **`part_of` is never computed, at any pool size.** It is containment, not reference, and
-  deriving it from directory nesting would turn a folder layout into a claim about concepts —
-  the same reasoning the design's own Alternatives section already rejected this on.
+  deriving it from directory nesting would turn a folder layout into a claim about concepts.

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

@@ -60,6 +60,8 @@ to orient someone already inside. A node without one is an error, not a default.
   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.
+- **`branch`:** the branch half of the namespace key (`synapse namespace --branch`), filled in by
+  the writer — never hand-authored.
 - **`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.
@@ -157,6 +159,7 @@ schema: graph-node/v1
 title: "World — entity/component/resource core"
 node_type: synapse-node
 project: acme
+branch: main
 sources_digest: <sha256 over the sorted "path:hash" lines>
 stale: false
 built_at: "<now>"

package/skills/synapse-query/SKILL.md

@@ -88,14 +88,14 @@ resolve the specific symbol-level question:
 ## Guardrails
 
 - **Never grep the whole repo before checking `synapse/{project}/Index.md`**, unless this repo has
-  no Synapse namespace at all (`vault_list` on `synapse/{project}/` comes back empty). Before
+  no Synapse namespace at all (`vault-list` on `synapse/{project}/` comes back empty). Before
   concluding there's nothing to consult, check whether the task actually concerns a *different*
   checkout — `synapse query --namespace <repo>@<branch> body "{Node}"` reaches that repo's graph
   without switching directories or checking it out. Only when no namespace anywhere covers the task
   is there truly nothing to consult; say so and proceed normally.
 - **Never treat a node's summary as ground truth for a symbol-level claim** it wasn't built to make
   precisely — see "When a node isn't enough" above.
-- **Never `vault_read` a node just to read its prose — including a node in another checkout's
+- **Never `vault-read` a node just to read its prose — including a node in another checkout's
   namespace.** That pulls the full frontmatter, which can run to megabytes on a hub node. Use
   `synapse query body` (add `--namespace <repo>@<branch>` for a graph outside this checkout) — see
   the cost note above.

package/skills/synapse-vault/SKILL.md

@@ -34,8 +34,11 @@ synapse vault-read <path>                  the whole note -- no partial/targeted
 ```
 
 `vault-search`'s JsonLogic filter and `--fields` projection both stop at frontmatter/tags/content/
-path -- there is no `links`/`backlinks`/`unresolvedLinks` equivalent (no whole-vault wikilink index
-exists yet), and `vault-read` always returns the full body, never one section on its own -- request
+path -- links aren't filterable through search itself, though a dedicated whole-vault wikilink
+index does exist as its own set of subcommands (`vault-backlinks`/`vault-links`/`vault-unresolved`/
+`vault-orphans`/`vault-deadends`/`vault-ambiguous`/`vault-rename`), reach for one of those directly
+instead of trying to express a link query through `vault-search`. `vault-read` always returns the
+full body, never one section on its own -- request
 exactly what you need with `--fields` instead of over-fetching, and pull a specific section out of
 `vault-read`'s output locally when that's all you actually need.
 
@@ -110,15 +113,15 @@ Every new note is created through an authoring command, never by freeforming a f
 - `/synapse-note` (bare mode) creates plain notes in any category -- `research/`,
   `scratchpad/`, `inbox/`, anything that is not a tracked task or a design note. It mints the
   frontmatter (`schema`, `title`, `note_id`, `created`, `updated`, `tags`) to the note schema's
-  contract, including full-timestamp format.
+  contract, sampling `created`/`updated` from `synapse now`.
 - `/synapse-note --task` creates tracked task notes under `tasks/{project}/`.
 - `/synapse-design-note` and `/synapse-task-note` handle design discussions and compiled tasks --
   both delegate the file-minting mechanics to `/synapse-note` internally.
 
 `vault-write` is for *editing existing notes*, or the rare read-modify-write round trip. If a
 direct creation is ever genuinely unavoidable, follow bare mode's frontmatter contract exactly
-(`schema`/`title`/`note_id`/`created`/`updated`/`tags`, full `%Y-%m-%d %H:%M:%S %Z` timestamps)
-rather than improvising a shape.
+(`schema`/`title`/`note_id`/`created`/`updated`/`tags`, with `created`/`updated` taken from
+`synapse now` -- never hand-typed) rather than improvising a shape.
 
 Schemas are opt-in by declaration: a note whose frontmatter declares `schema:` is held to that
 schema's contract on every `vault-write`/`vault-patch`; a note without the field is never