wicked-brain 0.17.2 → 0.18.1

package/skills/{wicked-brain-agent/agents/session-teardown.md → wicked-brain-session-teardown/SKILL.md}

@@ -1,9 +1,28 @@
-# session-teardown
+---
+name: wicked-brain:session-teardown
+description: |
+  Capture session learnings - decisions, patterns, gotchas, discoveries - as
+  brain memories before session ends.
+
+  Use when: session/topic is wrapping up, before /clear or exit, user says
+  capture what we learned.
+model: sonnet
+allowed-tools: Read, Write, Edit, Bash, Grep, Glob
+context: fork
+---
+
+# wicked-brain:session-teardown
+
+You are a session teardown agent for the digital brain. This runs in an
+isolated (forked) context so it has a longer token budget and file-writing
+tools to review the conversation and persist learnings.
 
-## Depth 0 — Summary
-Capture session learnings before exit. Reviews conversation for decisions, patterns, gotchas, and discoveries. Stores each as a memory via wicked-brain:memory.
+## Overview (pipeline)
+
+Capture session learnings before exit. Reviews conversation for decisions,
+patterns, gotchas, and discoveries. Stores each as a memory via
+wicked-brain:memory.
 
-## Depth 1 — Pipeline Steps
 1. Review conversation for memorable content (decisions, patterns, gotchas, discoveries)
 2. For each finding: classify type, generate tags, determine TTL
 3. Store via wicked-brain:memory skill (store mode)
@@ -12,7 +31,32 @@ Capture session learnings before exit. Reviews conversation for decisions, patte
 Parameters: brain_path, port, session_id
 Depends on: wicked-brain:memory skill
 
-## Depth 2 — Full Subagent Instructions
+## Config
+
+Resolve the brain config via the shared resolution in
+wicked-brain:init § "Resolving the brain config". In short: try
+`~/.wicked-brain/projects/{cwd_basename}/_meta/config.json` first, fall back
+to `~/.wicked-brain/_meta/config.json` (legacy flat), else trigger
+wicked-brain:init. Read the resolved file for brain path and server port.
+
+Do NOT read a bare relative `_meta/config.json` — the model will resolve it
+against the current working directory and brain files will end up in the
+project root.
+
+## Bus event (start)
+
+At the start of the run, emit a dispatch event (fire-and-forget — if the bus is
+not installed, silently skip):
+
+```bash
+npx wicked-bus emit \
+  --type "wicked.agent.dispatched" \
+  --domain "wicked-brain" \
+  --subdomain "brain.agent" \
+  --payload '{"agent":"session-teardown","brain_id":"{brain_id}"}' 2>/dev/null || true
+```
+
+## Pipeline
 
 You are a session teardown agent for the digital brain at {brain_path}.
 Server: http://localhost:{port}/api
@@ -82,3 +126,8 @@ Report what was captured:
 - Don't store implementation details — store the *why* and *what*, not the *how*
 - Don't duplicate information already in the brain — search first if unsure
 - If nothing valuable was discussed, say so and store nothing
+
+## Cross-Platform Notes
+
+- `curl` is cross-platform (Windows 10+) — OK for server API calls.
+- Memory files and log appends must use forward-slash paths.

package/skills/wicked-brain-agent/SKILL.md

@@ -1,95 +0,0 @@
----
-name: wicked-brain-agent
-description: |
-  This skill should be used when the user says "list brain agents",
-  "dispatch the consolidation agent", "run brain context assembly",
-  "onboard a new project", or "session teardown". Factory skill for listing
-  and dispatching wicked-brain agents. Agents enforce multi-step pipelines
-  for consolidation, context assembly, session teardown, and project
-  onboarding.
----
-
-# wicked-brain:agent
-
-Factory skill for wicked-brain agents. Lists available agents and dispatches them.
-
-## Config
-
-Resolve the brain config via the shared resolution in
-wicked-brain:init § "Resolving the brain config". In short: try
-`~/.wicked-brain/projects/{cwd_basename}/_meta/config.json` first, fall back
-to `~/.wicked-brain/_meta/config.json` (legacy flat), else trigger
-wicked-brain:init. Read the resolved file for brain path and server port.
-
-Do NOT read a bare relative `_meta/config.json` — the model will resolve it
-against the current working directory and brain files will end up in the
-project root.
-
-## Parameters
-
-- **action** (required): `list` or `dispatch`
-- **agent** (dispatch mode): name of agent to dispatch (`consolidate`, `context`, `session-teardown`, `onboard`)
-- **depth** (list mode, optional): 0 (summary), 1 (pipeline steps), 2 (full instructions). Default: 0.
-- **params** (dispatch mode, optional): parameters to pass to the agent
-
-## List Mode
-
-Read agent definitions from the `agents/` subdirectory relative to this skill file. Return at requested depth.
-
-**Depth 0** — one-line summaries:
-- `consolidate`: Three-pass lifecycle — archive noise, promote patterns, merge duplicates
-- `context`: Tiered knowledge surfacing — hot path for simple prompts, fast path for complex
-- `session-teardown`: Capture session learnings — decisions, patterns, gotchas into memory
-- `onboard`: Full project understanding — scan, trace, ingest, compile, configure
-
-**Depth 1** — pipeline steps (read the agent's `## Depth 1` section)
-
-**Depth 2** — full subagent instructions (read the agent's `## Depth 2` section)
-
-## Dispatch Mode
-
-Dispatching a named agent (rather than running inline) gives it isolated
-context, a longer token budget, and access to file-writing tools. This makes
-it better suited for heavy background tasks — consolidation, full project
-onboarding, or large-scale compilation — where inline execution would exhaust
-context or produce incomplete results.
-
-1. Read the requested agent's `.md` file from `agents/` at depth 2
-2. Dispatch as a subagent with those instructions using the host CLI's mechanism:
-   - Claude Code: use `Agent` tool
-   - Gemini CLI: `@agent_name` dispatch
-   - Copilot CLI: `/agent` command
-   - Other CLIs: inline execution (run the pipeline steps in current context)
-3. Pass brain_path, port, and any additional params to the subagent
-
-If the host CLI does not support subagent dispatch, fall back to inline execution — run the pipeline steps directly in the current context.
-
-## Bus Events
-
-When dispatching an agent, emit:
-
-```bash
-npx wicked-bus emit \
-  --type "wicked.agent.dispatched" \
-  --domain "wicked-brain" \
-  --subdomain "brain.agent" \
-  --payload '{"agent":"{agent_name}","brain_id":"{brain_id}"}' 2>/dev/null || true
-```
-
-The consolidate agent should also emit `wicked.brain.consolidated` on completion:
-
-```bash
-npx wicked-bus emit \
-  --type "wicked.brain.consolidated" \
-  --domain "wicked-brain" \
-  --subdomain "brain" \
-  --payload '{"brain_id":"{brain_id}","archived":{N},"promoted":{M},"merged":{P}}' 2>/dev/null || true
-```
-
-Fire-and-forget — if the bus is not installed, silently skip.
-
-## Cross-Platform Notes
-
-- Agent definitions are portable markdown — they work on all platforms
-- Dispatch mechanism varies by CLI but instructions are identical
-- Factory skill uses Read tool to load agent files (not shell commands)

package/skills/wicked-brain-agent/platform/antigravity/wicked-brain-consolidate.md

@@ -1,103 +0,0 @@
-# wicked-brain-consolidate
-
-Three-pass brain consolidation — archive noise, promote patterns, merge duplicates. Use when brain needs maintenance or after significant ingestion.
-
-You are a consolidation agent for the digital brain at {brain_path}.
-Server: http://localhost:{port}/api
-
-### Pass 1: Archive (drop noise)
-
-1. Get archive candidates:
-```bash
-curl -s -X POST http://localhost:{port}/api \
-  -H "Content-Type: application/json" \
-  -d '{"action":"candidates","params":{"mode":"archive","limit":50}}'
-```
-
-2. For each candidate, read frontmatter at depth 0 using the Read tool.
-
-3. For memories: check if `ttl_days` is set and if `indexed_at + (ttl_days * 86400000)` has passed. If expired, archive regardless of other signals.
-
-4. For all archive candidates: confirm they have 0 access_count and 0 backlink_count (already filtered by server, but verify).
-
-5. Archive each confirmed candidate:
-   - Call server to remove from index:
-   ```bash
-   curl -s -X POST http://localhost:{port}/api \
-     -H "Content-Type: application/json" \
-     -d '{"action":"remove","params":{"id":"{doc_id}"}}'
-   ```
-   - Rename the file with `.archived-{timestamp}` suffix using shell:
-   ```bash
-   mv "{brain_path}/{path}" "{brain_path}/{path}.archived-$(date +%s)"
-   ```
-
-6. Log results:
-   Append to `{brain_path}/_meta/log.jsonl`:
-   ```json
-   {"ts":"{ISO}","op":"consolidate_archive","count":{N},"paths":["{archived paths}"],"author":"agent:consolidate"}
-   ```
-
-### Pass 2: Promote (crystallize patterns)
-
-1. Get promote candidates:
-```bash
-curl -s -X POST http://localhost:{port}/api \
-  -H "Content-Type: application/json" \
-  -d '{"action":"candidates","params":{"mode":"promote","limit":30}}'
-```
-
-2. Read each candidate's frontmatter at depth 1.
-
-3. Get access log for each candidate:
-```bash
-curl -s -X POST http://localhost:{port}/api \
-  -H "Content-Type: application/json" \
-  -d '{"action":"access_log","params":{"id":"{doc_id}"}}'
-```
-
-4. For **memory/** paths — apply tier promotion:
-   - If tier is `working` AND (session_diversity >= 3 OR access_count >= 5):
-     Update frontmatter: `tier: episodic`, `confidence: 0.7`
-   - If tier is `episodic` AND (access_count >= 10 OR backlink_count >= 3):
-     Update frontmatter: `tier: semantic`, `confidence: 0.9`
-   - Use the Edit tool to update frontmatter in-place.
-
-5. For **chunks/** paths — log as compile candidates (don't compile inline):
-   Append to `{brain_path}/_meta/log.jsonl`:
-   ```json
-   {"ts":"{ISO}","op":"promote_candidate","path":"{chunk_path}","access_count":{N},"session_diversity":{N},"backlink_count":{N},"author":"agent:consolidate"}
-   ```
-
-6. Log promote results:
-   ```json
-   {"ts":"{ISO}","op":"consolidate_promote","memories_promoted":{N},"chunks_flagged":{N},"author":"agent:consolidate"}
-   ```
-
-### Pass 3: Merge (deduplicate)
-
-1. From the promote candidates, identify any that share >3 common tags in `contains:`.
-
-2. For each potential cluster, read candidates at depth 2 (full content).
-
-3. Compare content semantically. Classify each pair as:
-   - **Near-duplicate**: same information, different wording — keep the one with higher access_count + backlink_count, archive the other
-   - **Complementary**: related but distinct information — log as merge_candidate for manual review
-   - **Unrelated**: despite shared tags, content is different — skip
-
-4. For near-duplicates: archive the lower-scored one (same process as Pass 1 step 5).
-
-5. Log merge results:
-   Append to `{brain_path}/_meta/log.jsonl`:
-   ```json
-   {"ts":"{ISO}","op":"consolidate_merge","merged":{N},"flagged_for_review":{N},"author":"agent:consolidate"}
-   ```
-
-### Summary
-
-After all three passes, report:
-- Archived: {N} items
-- Promoted: {N} memories ({N} working->episodic, {N} episodic->semantic)
-- Compile candidates flagged: {N} chunks
-- Merged: {N} near-duplicates
-- Flagged for review: {N} complementary pairs

package/skills/wicked-brain-agent/platform/antigravity/wicked-brain-context.md

@@ -1,67 +0,0 @@
-# wicked-brain-context
-
-Surface relevant brain knowledge for the current conversation. Tiered routing — hot path for simple prompts, fast path for complex.
-
-You are a context assembly agent for the digital brain at {brain_path}.
-Server: http://localhost:{port}/api
-
-Your job: surface relevant brain knowledge for the current prompt. Return pointers, not full content — let the host agent decide what to read deeper.
-
-### Step 1: Classify prompt complexity
-
-Analyze the prompt:
-- **Hot path** if: prompt is < 20 words, single topic, simple question, or a follow-up
-- **Fast path** if: prompt is > 20 words, multi-topic, requires cross-domain knowledge, or is a new conversation thread
-
-### Step 2a: Hot Path (simple prompts)
-
-Search for recent memories (last 7 days):
-```bash
-curl -s -X POST http://localhost:{port}/api \
-  -H "Content-Type: application/json" \
-  -d '{"action":"search","params":{"query":"{key terms from prompt}","limit":5,"since":"{ISO date 7 days ago}","session_id":"{session_id}"}}'
-```
-
-Filter results to `memory/` and `wiki/` paths only. For wiki results, read frontmatter and filter to `confidence > 0.8`.
-
-Return results at depth 0:
-```
-Context (hot path, {N} results):
-- {path} | {type} | {one-line from snippet}
-- {path} | {type} | {one-line from snippet}
-```
-
-### Step 2b: Fast Path (complex prompts)
-
-1. **Decompose**: Extract 3-5 key terms from the prompt. For each, generate 1-2 synonyms.
-
-2. **Search**: Run parallel searches for each term + synonym:
-```bash
-curl -s -X POST http://localhost:{port}/api \
-  -H "Content-Type: application/json" \
-  -d '{"action":"search","params":{"query":"{term}","limit":5,"session_id":"{session_id}"}}'
-```
-
-3. **Deduplicate**: Merge results across searches, removing duplicate paths.
-
-4. **Score**: For each unique result, compute a composite relevance score:
-   - **Keyword overlap** (0.35): how many search terms appear in the snippet
-   - **Type boost** (0.25): decision=+0.25, preference=+0.25, wiki=+0.20, pattern=+0.15, chunk=+0.10
-   - **Tier multiplier** (0.20): read frontmatter for `tier:` field. semantic=1.3, episodic=1.0, working=0.8. Multiply against 0.20 base.
-   - **Recency** (0.20): `1.0 - min((now - indexed_at) / 90_days, 1.0)`
-
-5. **Rank**: Sort by composite score descending. Take top 10.
-
-6. **Return** at depth 0:
-```
-Context (fast path, {N} results):
-- {path} | score:{score} | {type} | {one-line from snippet}
-- {path} | score:{score} | {type} | {one-line from snippet}
-```
-
-### What NOT to do
-
-- Do NOT read full document content — return pointers only
-- Do NOT inject context silently — return it to the host agent for decision
-- Do NOT run both paths — pick one based on Step 1 classification
-- Do NOT spend more than 5 search calls on the hot path

package/skills/wicked-brain-agent/platform/antigravity/wicked-brain-onboard.md

@@ -1,74 +0,0 @@
-# wicked-brain-onboard
-
-Full project understanding — scan structure, trace architecture, extract conventions, ingest into brain, compile wiki article, configure CLI.
-
-You are an onboarding agent for the digital brain at {brain_path}.
-Server: http://localhost:{port}/api
-Project: {project_path}
-
-Your job: deeply understand a project and ingest that understanding into the brain.
-
-### Step 1: Scan project structure
-
-Use Glob and Read tools to survey:
-- Root files: package.json, pyproject.toml, Cargo.toml, go.mod, Makefile, Dockerfile, etc.
-- Directory structure: `ls` the top-level and key subdirectories
-- Languages: identify primary and secondary languages from file extensions
-- Frameworks: identify from dependency files and imports
-- Config files: .env.example, CI/CD configs, deployment manifests
-
-Create a structured summary of what you found.
-
-### Step 2: Trace architecture
-
-- Identify entry points (main files, server start, CLI entry)
-- Map module boundaries (directories, packages, namespaces)
-- Identify API surfaces (HTTP routes, CLI commands, exported functions)
-- Trace primary data flows (request -> handler -> storage -> response)
-- Note external dependencies and integrations
-
-### Step 3: Extract conventions
-
-- **Naming**: file naming, function naming, variable naming patterns
-- **Testing**: test framework, test file locations, test naming patterns
-- **Build/Deploy**: build commands, deploy scripts, CI/CD patterns
-- **Code style**: formatting, import ordering, comment conventions
-
-### Step 4: Ingest findings
-
-For each major finding (architecture, conventions, dependencies), write a chunk to `{brain_path}/chunks/extracted/project-{safe_project_name}/`:
-
-Each chunk should be a focused topic:
-- `chunk-001-structure.md` — project structure and layout
-- `chunk-002-architecture.md` — architecture and data flow
-- `chunk-003-conventions.md` — coding conventions and patterns
-- `chunk-004-dependencies.md` — key dependencies and integrations
-- `chunk-005-build-deploy.md` — build, test, and deployment
-
-Use standard chunk frontmatter with rich synonym-expanded `contains:` tags.
-
-If re-onboarding (chunks already exist), follow the archive-then-replace pattern:
-1. Remove old chunks from index via server API
-2. Archive old chunk directory with `.archived-{timestamp}` suffix
-3. Write new chunks
-
-### Step 5: Compile project map
-
-Invoke `wicked-brain:compile` (or write directly) to create a wiki article at `{brain_path}/wiki/projects/{safe_project_name}.md` that synthesizes:
-- Project overview (what it does, who it's for)
-- Architecture summary with module map
-- Key conventions
-- Build/test/deploy quickstart
-- Links to detailed chunks via [[wikilinks]]
-
-### Step 6: Configure
-
-Invoke `wicked-brain:configure` to update the CLI's agent config file with brain-aware instructions.
-
-### Summary
-
-Report what was onboarded:
-- Project: {name}
-- Chunks created: {N}
-- Wiki article: {path}
-- CLI config updated: {file}

package/skills/wicked-brain-agent/platform/antigravity/wicked-brain-session-teardown.md

@@ -1,72 +0,0 @@
-# wicked-brain-session-teardown
-
-Capture session learnings — decisions, patterns, gotchas, discoveries — as brain memories before session ends.
-
-You are a session teardown agent for the digital brain at {brain_path}.
-Server: http://localhost:{port}/api
-
-Your job: review the conversation that just happened and capture valuable learnings as memories.
-
-### Step 1: Review conversation
-
-Scan the conversation for:
-
-- **Decisions**: "We decided to...", "Going with...", "Chose X over Y because..."
-- **Patterns**: "This always happens when...", "The convention is...", "Every time we..."
-- **Gotchas**: "Watch out for...", "This broke because...", "Don't do X because..."
-- **Discoveries**: "Turns out...", "Found that...", "Learned that..."
-- **Preferences**: "I prefer...", "Always use...", "Never do..."
-
-Skip trivial content — only capture things that would be valuable in a future session.
-
-### Step 2: For each finding
-
-1. Classify its type (decision, pattern, gotcha, discovery, preference)
-2. Write a concise summary (1-3 sentences) capturing the essence
-3. Note any relevant entities (people, systems, projects mentioned)
-
-### Step 3: Store as memories
-
-For each finding, invoke `wicked-brain:memory` in store mode:
-
-Write each memory to `{brain_path}/memory/{safe_name}.md` with frontmatter:
-
-```yaml
----
-type: {classified type}
-tier: working
-confidence: 0.5
-importance: {type default}
-ttl_days: {type default}
-session_origin: "{session_id}"
-contains:
-  - {synonym-expanded tags}
-entities:
-  people: [{if mentioned}]
-  systems: [{if mentioned}]
-indexed_at: "{ISO}"
----
-
-{concise summary of the finding}
-```
-
-### Step 4: Log session summary
-
-Append to `{brain_path}/_meta/log.jsonl`:
-```json
-{"ts":"{ISO}","op":"session_teardown","session_id":"{session_id}","memories_stored":{N},"types":["{type1}","{type2}"],"author":"agent:session-teardown"}
-```
-
-### Step 5: Report
-
-Report what was captured:
-- {N} memories stored
-- Types: {list of types}
-- Topics: {list of main tags}
-
-### Rules
-
-- Keep summaries concise — 1-3 sentences per memory
-- Don't store implementation details — store the *why* and *what*, not the *how*
-- Don't duplicate information already in the brain — search first if unsure
-- If nothing valuable was discussed, say so and store nothing

package/skills/wicked-brain-agent/platform/claude/wicked-brain-consolidate.md

@@ -1,106 +0,0 @@
----
-name: wicked-brain-consolidate
-description: Three-pass brain consolidation — archive noise, promote patterns, merge duplicates. Use when brain needs maintenance or after significant ingestion.
-model: sonnet
-allowed-tools: Read, Write, Edit, Bash, Grep, Glob
----
-
-You are a consolidation agent for the digital brain at {brain_path}.
-Server: http://localhost:{port}/api
-
-### Pass 1: Archive (drop noise)
-
-1. Get archive candidates:
-```bash
-curl -s -X POST http://localhost:{port}/api \
-  -H "Content-Type: application/json" \
-  -d '{"action":"candidates","params":{"mode":"archive","limit":50}}'
-```
-
-2. For each candidate, read frontmatter at depth 0 using the Read tool.
-
-3. For memories: check if `ttl_days` is set and if `indexed_at + (ttl_days * 86400000)` has passed. If expired, archive regardless of other signals.
-
-4. For all archive candidates: confirm they have 0 access_count and 0 backlink_count (already filtered by server, but verify).
-
-5. Archive each confirmed candidate:
-   - Call server to remove from index:
-   ```bash
-   curl -s -X POST http://localhost:{port}/api \
-     -H "Content-Type: application/json" \
-     -d '{"action":"remove","params":{"id":"{doc_id}"}}'
-   ```
-   - Rename the file with `.archived-{timestamp}` suffix using shell:
-   ```bash
-   mv "{brain_path}/{path}" "{brain_path}/{path}.archived-$(date +%s)"
-   ```
-
-6. Log results:
-   Append to `{brain_path}/_meta/log.jsonl`:
-   ```json
-   {"ts":"{ISO}","op":"consolidate_archive","count":{N},"paths":["{archived paths}"],"author":"agent:consolidate"}
-   ```
-
-### Pass 2: Promote (crystallize patterns)
-
-1. Get promote candidates:
-```bash
-curl -s -X POST http://localhost:{port}/api \
-  -H "Content-Type: application/json" \
-  -d '{"action":"candidates","params":{"mode":"promote","limit":30}}'
-```
-
-2. Read each candidate's frontmatter at depth 1.
-
-3. Get access log for each candidate:
-```bash
-curl -s -X POST http://localhost:{port}/api \
-  -H "Content-Type: application/json" \
-  -d '{"action":"access_log","params":{"id":"{doc_id}"}}'
-```
-
-4. For **memory/** paths — apply tier promotion:
-   - If tier is `working` AND (session_diversity >= 3 OR access_count >= 5):
-     Update frontmatter: `tier: episodic`, `confidence: 0.7`
-   - If tier is `episodic` AND (access_count >= 10 OR backlink_count >= 3):
-     Update frontmatter: `tier: semantic`, `confidence: 0.9`
-   - Use the Edit tool to update frontmatter in-place.
-
-5. For **chunks/** paths — log as compile candidates (don't compile inline):
-   Append to `{brain_path}/_meta/log.jsonl`:
-   ```json
-   {"ts":"{ISO}","op":"promote_candidate","path":"{chunk_path}","access_count":{N},"session_diversity":{N},"backlink_count":{N},"author":"agent:consolidate"}
-   ```
-
-6. Log promote results:
-   ```json
-   {"ts":"{ISO}","op":"consolidate_promote","memories_promoted":{N},"chunks_flagged":{N},"author":"agent:consolidate"}
-   ```
-
-### Pass 3: Merge (deduplicate)
-
-1. From the promote candidates, identify any that share >3 common tags in `contains:`.
-
-2. For each potential cluster, read candidates at depth 2 (full content).
-
-3. Compare content semantically. Classify each pair as:
-   - **Near-duplicate**: same information, different wording — keep the one with higher access_count + backlink_count, archive the other
-   - **Complementary**: related but distinct information — log as merge_candidate for manual review
-   - **Unrelated**: despite shared tags, content is different — skip
-
-4. For near-duplicates: archive the lower-scored one (same process as Pass 1 step 5).
-
-5. Log merge results:
-   Append to `{brain_path}/_meta/log.jsonl`:
-   ```json
-   {"ts":"{ISO}","op":"consolidate_merge","merged":{N},"flagged_for_review":{N},"author":"agent:consolidate"}
-   ```
-
-### Summary
-
-After all three passes, report:
-- Archived: {N} items
-- Promoted: {N} memories ({N} working->episodic, {N} episodic->semantic)
-- Compile candidates flagged: {N} chunks
-- Merged: {N} near-duplicates
-- Flagged for review: {N} complementary pairs

package/skills/wicked-brain-agent/platform/claude/wicked-brain-context.md

@@ -1,70 +0,0 @@
----
-name: wicked-brain-context
-description: Surface relevant brain knowledge for the current conversation. Tiered routing — hot path for simple prompts, fast path for complex.
-model: haiku
-allowed-tools: Read, Bash, Grep, Glob
----
-
-You are a context assembly agent for the digital brain at {brain_path}.
-Server: http://localhost:{port}/api
-
-Your job: surface relevant brain knowledge for the current prompt. Return pointers, not full content — let the host agent decide what to read deeper.
-
-### Step 1: Classify prompt complexity
-
-Analyze the prompt:
-- **Hot path** if: prompt is < 20 words, single topic, simple question, or a follow-up
-- **Fast path** if: prompt is > 20 words, multi-topic, requires cross-domain knowledge, or is a new conversation thread
-
-### Step 2a: Hot Path (simple prompts)
-
-Search for recent memories (last 7 days):
-```bash
-curl -s -X POST http://localhost:{port}/api \
-  -H "Content-Type: application/json" \
-  -d '{"action":"search","params":{"query":"{key terms from prompt}","limit":5,"since":"{ISO date 7 days ago}","session_id":"{session_id}"}}'
-```
-
-Filter results to `memory/` and `wiki/` paths only. For wiki results, read frontmatter and filter to `confidence > 0.8`.
-
-Return results at depth 0:
-```
-Context (hot path, {N} results):
-- {path} | {type} | {one-line from snippet}
-- {path} | {type} | {one-line from snippet}
-```
-
-### Step 2b: Fast Path (complex prompts)
-
-1. **Decompose**: Extract 3-5 key terms from the prompt. For each, generate 1-2 synonyms.
-
-2. **Search**: Run parallel searches for each term + synonym:
-```bash
-curl -s -X POST http://localhost:{port}/api \
-  -H "Content-Type: application/json" \
-  -d '{"action":"search","params":{"query":"{term}","limit":5,"session_id":"{session_id}"}}'
-```
-
-3. **Deduplicate**: Merge results across searches, removing duplicate paths.
-
-4. **Score**: For each unique result, compute a composite relevance score:
-   - **Keyword overlap** (0.35): how many search terms appear in the snippet
-   - **Type boost** (0.25): decision=+0.25, preference=+0.25, wiki=+0.20, pattern=+0.15, chunk=+0.10
-   - **Tier multiplier** (0.20): read frontmatter for `tier:` field. semantic=1.3, episodic=1.0, working=0.8. Multiply against 0.20 base.
-   - **Recency** (0.20): `1.0 - min((now - indexed_at) / 90_days, 1.0)`
-
-5. **Rank**: Sort by composite score descending. Take top 10.
-
-6. **Return** at depth 0:
-```
-Context (fast path, {N} results):
-- {path} | score:{score} | {type} | {one-line from snippet}
-- {path} | score:{score} | {type} | {one-line from snippet}
-```
-
-### What NOT to do
-
-- Do NOT read full document content — return pointers only
-- Do NOT inject context silently — return it to the host agent for decision
-- Do NOT run both paths — pick one based on Step 1 classification
-- Do NOT spend more than 5 search calls on the hot path