@imunitic/synapse 0.2.9 → 0.2.11

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -96,11 +96,9 @@ unchanged for anyone who has never touched an XDG config directory.
96
96
  7. Format the new task ID **zero-padded to 3 digits** (`{prefix}-001`, `{prefix}-030`,
97
97
  `{prefix}-037`, ...), matching the org-roam-era convention — widening
98
98
  naturally past 3 digits if a prefix ever needs it.
99
- 8. **Prepend the resolved task ID to the title itself** the final title
100
- becomes `{task-id} {original title}` (em dash). Use this same final
101
- title for both the `title` frontmatter field and the `# ` heading, and
102
- use the resolved task ID for `task_id`. Don't let the frontmatter task
103
- ID and the visible title disagree.
99
+ 8. **The title itself is never prefixed with the task ID.** `task_id` lives in frontmatter only —
100
+ the same convention `note_id` already uses for bare and design notes, now consistent across all
101
+ three kinds. `title`, the `# ` heading, and the filename all stay exactly the given topic.
104
102
 
105
103
  `/synapse-design-note`/`/synapse-task-note` read the same conf file directly for the same reason —
106
104
  they don't duplicate this resolution logic, just this file.
@@ -68,8 +68,8 @@ Follow `/synapse-note`'s task-mode procedure exactly (its "Creating the note" se
68
68
  duplicate that scaffolding here, just supply its inputs:
69
69
 
70
70
  - **Title:** a short, plain description of the compiled plan (e.g. "Rollup direct storage
71
- implementation") — `/synapse-note --task` resolves the project prefix and `task_id` and prepends
72
- them itself.
71
+ implementation") — stays exactly this, never prefixed with the resolved `task_id`; `/synapse-note
72
+ --task` resolves the project prefix and `task_id` itself and puts them in frontmatter only.
73
73
  - **Project:** derive from the source design note's `project:` frontmatter — that prefix is already
74
74
  resolved (the design note went through `/synapse-design-note`'s resolution when it was created,
75
75
  which reads/appends the resolved `synapse-projects.conf`, per `/synapse-note`'s tiered lookup),
@@ -133,7 +133,7 @@ Claude: [reads designs/{PROJECT} — Rollup direct storage.md, Status: Ready]
133
133
 
134
134
  Project already known: {PROJECT} → {prefix}-005.
135
135
 
136
- Created: tasks/{PROJECT}/{prefix}-005 — Rollup direct storage implementation.md
136
+ Created: tasks/{PROJECT}/Rollup direct storage implementation.md (task_id: {prefix}-005)
137
137
  Linked back from designs/{PROJECT} — Rollup direct storage.md.
138
138
 
139
139
  Status transitions happen automatically via the synapse-task skill once you start work.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@imunitic/synapse",
3
- "version": "0.2.9",
3
+ "version": "0.2.11",
4
4
  "description": "Memory for Claude Code, Codex CLI, and OpenCode: a durable Obsidian vault plus a per-repo code graph.",
5
5
  "repository": {
6
6
  "type": "git",
@@ -22,9 +22,9 @@
22
22
  "*.conf.template"
23
23
  ],
24
24
  "optionalDependencies": {
25
- "@imunitic/synapse-darwin-arm64": "0.2.9",
26
- "@imunitic/synapse-linux-x64": "0.2.9",
27
- "@imunitic/synapse-linux-arm64": "0.2.9"
25
+ "@imunitic/synapse-darwin-arm64": "0.2.11",
26
+ "@imunitic/synapse-linux-x64": "0.2.11",
27
+ "@imunitic/synapse-linux-arm64": "0.2.11"
28
28
  },
29
29
  "license": "SEE LICENSE IN LICENSE"
30
30
  }