dreamcontext 0.8.6 → 0.8.7

package/dist/skill-packs/excalidraw/SKILL.md

@@ -231,13 +231,28 @@ _dream_context/knowledge/diagrams/
 │   ├── my-board.excalidraw.md   ← generated board (do NOT hand-edit scene JSON)
 │   ├── my-board.board.cjs       ← generator (dark sibling — excluded from index/recall)
 │   └── my-board.json            ← spec / source of truth (dark sibling — excluded)
+├── competitors/                 ← optional category subfolder (groups many boards)
+│   └── acme/
+│       └── acme.excalidraw.md
 └── legacy-flat.excalidraw.md    ← flat layout still works; no forced migration
 ```
 
-**Dark siblings**: any file inside a `diagrams/<title>/` folder that is NOT the board itself
-is automatically excluded from the index, recall corpus, snapshot, and dashboard list.
-This includes generator scripts (`.board.cjs`), spec JSON, and any helper `.md` notes.
-They are tooling — they do not pollute memory.
+**Category subfolders** are optional and free-form: `diagrams/<category>/<title>/<title>.excalidraw.md`.
+The dashboard Knowledge view renders the whole `diagrams/` subtree as a nested, collapsible folder
+tree (each board shows a sketch icon), so a large diagram set stays navigable instead of collapsing
+into one flat list. A board's own `<title>/` folder is always its innermost folder. Note: a
+`.board.cjs` that `require()`s shared helpers by relative path must use a depth that matches its
+actual location.
+
+**Dark siblings**: tooling files inside a `diagrams/<title>/` folder are automatically excluded
+from the index, recall corpus, snapshot, and dashboard list — generator scripts (`.board.cjs`),
+spec JSON, and frontmatter-less helper `.md` notes. They are tooling — they do not pollute memory.
+
+**Companion knowledge is the exception**: a `.md` beside a board that carries `name:` frontmatter
+is indexed as first-class knowledge (not a dark sibling). This lets you co-locate a board with its
+detailed write-up — e.g. `acme/acme.excalidraw.md` next to `acme/acme.teardown.md` — and have the
+teardown recall normally. Only frontmatter-less notes stay dark, so good organization no longer
+costs you recall.
 
 **Flat layout** (`diagrams/<title>.excalidraw.md`) works without any migration. Use the
 per-title folder when you want to keep the board + generator + spec together cleanly.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dreamcontext",
-  "version": "0.8.6",
+  "version": "0.8.7",
   "description": "dreamcontext — the persistent brain for your AI agents. Remembers what you built, knows how your project works.",
   "type": "module",
   "bin": {

package/skill/SKILL.md

@@ -443,11 +443,13 @@ Excalidraw boards (`.excalidraw.md`) are first-class knowledge files. Two layout
 
 **Per-title folder** (preferred convention): `knowledge/diagrams/<title>/<title>.excalidraw.md`
 
+**Optional category subfolder** (for many diagrams): group boards under a category, e.g. `knowledge/diagrams/<category>/<title>/<title>.excalidraw.md` (`diagrams/competitors/acme/acme.excalidraw.md`, `diagrams/system/recall/recall.excalidraw.md`). The dashboard Knowledge view renders these as a nested, collapsible folder tree, so categories stay navigable instead of collapsing into one flat Diagrams list. Nesting is free-form and any depth; the board still lives in its own `<title>/` folder. Generators that `require()` shared helpers via a relative path must account for the extra depth.
+
 Rules:
 - **REQUIRED frontmatter**: every board MUST have `name:` and `description:` fields. Boards with no `## Text Elements` section fall back to description-only recall — make it descriptive.
 - **Do NOT hand-edit scene JSON.** The `.excalidraw.md` file is generated output. Build a spec and run the generator (`.board.cjs`). Edit the spec, not the board.
 - **Spec is the source of truth.** If the spec and the board ever disagree, the spec wins. Commit both.
-- **Dark siblings**: all files inside a `knowledge/diagrams/<title>/` folder that are NOT the board itself (generator scripts `.board.cjs`, spec `.json`, helper `.md`) are excluded from the index, recall corpus, snapshot, and dashboard. They are tooling artifacts — they do NOT surface in memory.
+- **Dark siblings**: tooling files inside a `knowledge/diagrams/<title>/` folder — generator scripts (`.board.cjs`), spec `.json`, and frontmatter-less helper `.md` — are excluded from the index, recall corpus, snapshot, and dashboard. **Exception:** a companion `.md` that carries `name:` frontmatter is indexed as first-class knowledge, so you can co-locate a board with its detailed teardown (`acme/acme.excalidraw.md` + `acme/acme.teardown.md`) and have it recall normally. Only frontmatter-less notes stay dark.
 - **Memory indexes only frontmatter + ## Text Elements**: scene JSON, base64, and element ids are stripped before indexing. A 2 MB board with rich Text Elements is as searchable as a tiny board. The dashboard renderer still receives the raw body (with full scene JSON) via the detail API route.
 - **Migration is opt-in**: flat boards stay flat unless you explicitly ask for reorganization. Use `dreamcontext migrations pending` to see pending migration tasks; use `dreamcontext migrations apply-diagrams` to opt-in to organizing flat boards into per-title folders.
 

package/skill-packs/excalidraw/SKILL.md

@@ -231,13 +231,28 @@ _dream_context/knowledge/diagrams/
 │   ├── my-board.excalidraw.md   ← generated board (do NOT hand-edit scene JSON)
 │   ├── my-board.board.cjs       ← generator (dark sibling — excluded from index/recall)
 │   └── my-board.json            ← spec / source of truth (dark sibling — excluded)
+├── competitors/                 ← optional category subfolder (groups many boards)
+│   └── acme/
+│       └── acme.excalidraw.md
 └── legacy-flat.excalidraw.md    ← flat layout still works; no forced migration
 ```
 
-**Dark siblings**: any file inside a `diagrams/<title>/` folder that is NOT the board itself
-is automatically excluded from the index, recall corpus, snapshot, and dashboard list.
-This includes generator scripts (`.board.cjs`), spec JSON, and any helper `.md` notes.
-They are tooling — they do not pollute memory.
+**Category subfolders** are optional and free-form: `diagrams/<category>/<title>/<title>.excalidraw.md`.
+The dashboard Knowledge view renders the whole `diagrams/` subtree as a nested, collapsible folder
+tree (each board shows a sketch icon), so a large diagram set stays navigable instead of collapsing
+into one flat list. A board's own `<title>/` folder is always its innermost folder. Note: a
+`.board.cjs` that `require()`s shared helpers by relative path must use a depth that matches its
+actual location.
+
+**Dark siblings**: tooling files inside a `diagrams/<title>/` folder are automatically excluded
+from the index, recall corpus, snapshot, and dashboard list — generator scripts (`.board.cjs`),
+spec JSON, and frontmatter-less helper `.md` notes. They are tooling — they do not pollute memory.
+
+**Companion knowledge is the exception**: a `.md` beside a board that carries `name:` frontmatter
+is indexed as first-class knowledge (not a dark sibling). This lets you co-locate a board with its
+detailed write-up — e.g. `acme/acme.excalidraw.md` next to `acme/acme.teardown.md` — and have the
+teardown recall normally. Only frontmatter-less notes stay dark, so good organization no longer
+costs you recall.
 
 **Flat layout** (`diagrams/<title>.excalidraw.md`) works without any migration. Use the
 per-title folder when you want to keep the board + generator + spec together cleanly.

package/dist/dashboard/assets/channel-Do_JtUNy.js

@@ -1 +0,0 @@
-import{aq as o,ar as n}from"./index-Di8SAJL6.js";const t=(r,a)=>o.lang.round(n.parse(r)[a]);export{t as c};

package/dist/dashboard/assets/classDiagram-6PBFFD2Q-Dj8SIYaT.js

@@ -1 +0,0 @@
-import{s as a,c as s,a as e,C as t}from"./chunk-4TB4RGXK-DGTUpfCU.js";import{_ as i}from"./index-Di8SAJL6.js";import"./chunk-FMBD7UC4-DIteC6lG.js";import"./chunk-YZCP3GAM--p-GHUD7.js";import"./chunk-55IACEB6-BnK0E2R4.js";import"./chunk-EDXVE4YY-B3YEC9QU.js";var u={parser:e,get db(){return new t},renderer:s,styles:a,init:i(r=>{r.class||(r.class={}),r.class.arrowMarkerAbsolute=r.arrowMarkerAbsolute},"init")};export{u as diagram};

package/dist/dashboard/assets/classDiagram-v2-HSJHXN6E-Dj8SIYaT.js

@@ -1 +0,0 @@
-import{s as a,c as s,a as e,C as t}from"./chunk-4TB4RGXK-DGTUpfCU.js";import{_ as i}from"./index-Di8SAJL6.js";import"./chunk-FMBD7UC4-DIteC6lG.js";import"./chunk-YZCP3GAM--p-GHUD7.js";import"./chunk-55IACEB6-BnK0E2R4.js";import"./chunk-EDXVE4YY-B3YEC9QU.js";var u={parser:e,get db(){return new t},renderer:s,styles:a,init:i(r=>{r.class||(r.class={}),r.class.arrowMarkerAbsolute=r.arrowMarkerAbsolute},"init")};export{u as diagram};

package/dist/dashboard/assets/clone-BpmzOucO.js

@@ -1 +0,0 @@
-import{b as r}from"./graph-CDuZp5IO.js";var e=4;function a(o){return r(o,e)}export{a as c};