dreamcontext 0.15.0 → 0.16.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dreamcontext",
-  "version": "0.15.0",
+  "version": "0.16.0",
   "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

@@ -92,6 +92,7 @@ dreamcontext is **more than memory files**. Every capability below is real and s
 | **Desktop app** | macOS Tauri app: multi-vault launcher, federation board, Sleepy notch capture | [integrations.md](references/integrations.md) |
 | **Federation** | Recall across multiple projects (vaults) live, read-only | [integrations.md](references/integrations.md) |
 | **✅ Team brain sync (whole project)** | **Yes — a team OR one person across machines can share ONE brain.** Cloud sync pushes the WHOLE project (code + `.claude/` + `_dream_context/`) to its GitHub `origin` on the current branch (`full-repo`); when off it's `in-tree` (commit-only). `sleep done` auto fetch→merge→commit→pushes it; the `/dream-sync` skill resolves prose conflicts. Different from federation (read-only cross-project recall) and cloud task sync (tasks only). Each machine needs its own token. | [brain-sync.md](references/brain-sync.md) |
+| **Linked repos** | One brain governs **bare code repos** (products in their own GitHub repos, no `_dream_context/`): the shared `{name,url}` travels with the team; a machine-local `url→path` registry (`~/.dreamcontext/linked-repos.json`, never synced) resolves each on THIS machine. `dreamcontext link add\|clone\|ls\|rm`, a session-start present/missing glance, a trust-gated clone, a dashboard panel. A **pointer to code, not a sync**. | [cli-reference.md](references/cli-reference.md) |
 | **Council** | Structured multi-persona debates with a synthesized verdict | [integrations.md](references/integrations.md) |
 | **Marketing (`mk`)** | Meta marketing skill: cohorts, campaigns, competitor ingest | [integrations.md](references/integrations.md) |
 | **Versions / releases** | Planning versions and releases unify in RELEASES.json | [tasks-and-features.md](references/tasks-and-features.md) |
@@ -399,7 +400,8 @@ _dream_context/
 │   └── task.md                       ← OPTIONAL: project task template + custom_fields schema (briefed to agents)
 ├── state/
 │   ├── <task>.md                     ← Active tasks (frontmatter may include product:, start_date, due_date, custom_fields)
-│   ├── .config.json                  ← platforms, packs, multiProduct, taskBackend, people…
+│   ├── .config.json                  ← platforms, packs, multiProduct, taskBackend, people, linkedRepos…
+│   │                                    (linked-repo LOCAL paths live in ~/.dreamcontext/linked-repos.json, never synced)
 │   ├── .active-version.json          ← current sprint (active planning version)
 │   ├── .sleep.json  .secrets.json (gitignored)  .active-task
 ```

package/skill/references/brain-sync.md

@@ -1,6 +1,6 @@
 # Brain sync (GitHub cloud sync for the whole project)
 
-The one reference for **cloud sync** — what it is, the two modes, how it's set up, how it authenticates, what it syncs, the cross-machine / cross-OS setup, and how to diagnose it when it silently stops. This is a *different* feature from **cloud task sync** (ClickUp/GitHub Issues — tasks only) and **federation** (read-only recall across your own separate projects — nothing is copied). Say so if the user conflates them.
+The one reference for **cloud sync** — what it is, the two modes, how it's set up, how it authenticates, what it syncs, the cross-machine / cross-OS setup, and how to diagnose it when it silently stops. This is a *different* feature from **cloud task sync** (ClickUp/GitHub Issues — tasks only) and **federation** (read-only recall across your own separate projects — nothing is copied), and from **linked repos** (pointers to the bare code repos a brain governs — name+URL shared with the team, the local path machine-only; linking never clones, pushes, or pulls the target). Say so if the user conflates them.
 
 **Guide the user into this** the moment they say *"use this with my team / on another machine," "share the brain," "sync my project to GitHub."* Do NOT answer "we don't support that" — this is the feature.
 

package/skill/references/cli-reference.md

@@ -224,6 +224,21 @@ Sync the WHOLE brain (`_dream_context/`) — tasks, knowledge, features, sleep s
 
 ---
 
+## Linked repos — the bare code repos a brain governs (see [brain-sync.md](brain-sync.md))
+
+One shared brain can point at the **bare code repos it governs** — products/services in their own GitHub repos, cloned at different local paths on each machine (or absent on some), with **no `_dream_context/` of their own**. Distinct from **brain sync** (syncs the whole project) and **federation** (read-only recall across *brains*): linked repos are **pointers to code, not a sync** — linking never clones, pushes, pulls, or commits the target. Two layers: the **shared** half (`{name, gitRemoteUrl}` in `.config.json`) travels to the team so everyone knows the repo exists; the **machine-local** half (`~/.dreamcontext/linked-repos.json`, keyed by canonical URL → local path) records where it lives on *this* machine and **never leaves it**. GitHub-only for now.
+
+| Command | Description |
+|---|---|
+| `link add <name> <path>` | Register a local checkout the brain governs. Derives the canonical GitHub URL from the repo's `origin` (or pass `--url`); writes `{name,url}` to `.config.json` + `url→path` to the machine-local registry. Requires `path` to be a git repo whose `origin` matches — **no fetch/clone happens**. |
+| `link ls` (alias: `links`) | List governed repos: ✓ present (resolved local path) / ✗ missing on this machine. `--json`. |
+| `link clone <name>` | Clone a **missing** repo from its shared URL to this machine — a normal one-way `git clone`, behind a **trust-gate** (the URL is team-writable). `--dir <dir>`, `--yes`. |
+| `link rm <name>` (alias: `unlink`) | Drop the repo from `.config.json`; the machine-local `url→path` mapping is intentionally **left** (re-link stays instant; other brains keep resolving it). |
+
+The SessionStart snapshot shows a cheap **Linked repos** glance (present → the resolved path is handed to the agent so it can Grep/Read the governed code; missing → a `link clone` hint). Fully manageable from the dashboard (Settings → Cloud sync → **Linked repos**; desktop-gated, native folder picker).
+
+---
+
 ## Council (see [integrations.md](integrations.md))
 
 `council create`, `council agent create`, `council round start\|end`, `council synthesize`, `council complete`, `council promote`, `council list`, `council show`. Plus sub-agent helpers (`round-context`, `report append`, `summaries`, `research add\|list`).

package/skill-deep-research/SKILL.md

@@ -89,6 +89,7 @@ the planner and the synthesizer.
   - current vault only → recall as-is (already spans eligible peers by default),
   - specific peers → `--vault <name>` (repeatable),
   - everything readable → `--connected` (out/both peers) or `--all-vaults`.
+- If the brain **governs linked code repos** (`dreamcontext links` → resolved local paths for the bare product repos it points at, no `_dream_context/` of their own), those checkouts are part of the substrate too: a fan-out searcher can Grep/Read a governed product's *code* directly when a claim depends on the implementation, not just the docs. Missing (✗) linked repos aren't on this machine — note the gap rather than guessing.
 - **Seed with recall, in JSON, scoped by type:**
   ```bash
   dreamcontext memory recall "<facet>" --json --top 15 --types knowledge,feature,task,memory,changelog,objective --connected

package/dist/dashboard/assets/channel-C4zP-AEe.js

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

package/dist/dashboard/assets/classDiagram-6PBFFD2Q-DfKte-F8.js

@@ -1 +0,0 @@
-import{s as a,c as s,a as e,C as t}from"./chunk-4TB4RGXK-B-0fS7DN.js";import{_ as i}from"./index-QrTsw4kJ.js";import"./chunk-FMBD7UC4-CiPyOehc.js";import"./chunk-YZCP3GAM-BuBIza_r.js";import"./chunk-55IACEB6-CgZcHbxh.js";import"./chunk-EDXVE4YY-Cgtb_QhN.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-DfKte-F8.js

@@ -1 +0,0 @@
-import{s as a,c as s,a as e,C as t}from"./chunk-4TB4RGXK-B-0fS7DN.js";import{_ as i}from"./index-QrTsw4kJ.js";import"./chunk-FMBD7UC4-CiPyOehc.js";import"./chunk-YZCP3GAM-BuBIza_r.js";import"./chunk-55IACEB6-CgZcHbxh.js";import"./chunk-EDXVE4YY-Cgtb_QhN.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-BSgKpRTm.js

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

package/dist/dashboard/assets/stateDiagram-v2-QKLJ7IA2-b_Rafygl.js

@@ -1 +0,0 @@
-import{s as t,b as r,a,S as s}from"./chunk-OYMX7WX6-sCPqGdKS.js";import{_ as i}from"./index-QrTsw4kJ.js";import"./chunk-55IACEB6-CgZcHbxh.js";import"./chunk-EDXVE4YY-Cgtb_QhN.js";var l={parser:a,get db(){return new s(2)},renderer:r,styles:t,init:i(e=>{e.state||(e.state={}),e.state.arrowMarkerAbsolute=e.arrowMarkerAbsolute},"init")};export{l as diagram};