@goondocks/myco 0.5.0 → 0.5.1

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.
@@ -12,7 +12,7 @@
12
12
  "source": {
13
13
  "source": "npm",
14
14
  "package": "@goondocks/myco",
15
- "version": "0.4.4"
15
+ "version": "0.5.0"
16
16
  },
17
17
  "description": "Collective agent intelligence — captures session knowledge and serves it back via MCP",
18
18
  "license": "MIT",
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "myco",
3
- "version": "0.5.0",
3
+ "version": "0.5.1",
4
4
  "description": "Collective agent intelligence — captures session knowledge and serves it back to your team via MCP",
5
5
  "author": {
6
6
  "name": "goondocks-co",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@goondocks/myco",
3
- "version": "0.5.0",
3
+ "version": "0.5.1",
4
4
  "description": "Collective agent intelligence — Claude Code plugin",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -140,7 +140,7 @@ View daemon logs for debugging when sessions aren't being captured, observations
140
140
  { "level": "warn", "component": "processor", "limit": 20 }
141
141
  ```
142
142
 
143
- Components: `daemon`, `processor`, `hooks`, `lifecycle`, `embeddings`, `lineage`, `watcher`.
143
+ Components: `daemon`, `processor`, `hooks`, `lifecycle`, `embeddings`, `lineage`, `watcher`, `digest`, `curation`.
144
144
 
145
145
  ### myco_supersede — Mark a spore as replaced
146
146
 
@@ -237,6 +237,25 @@ Options:
237
237
  - `--session <id>` — reprocess a single session (partial ID match)
238
238
  - `--index-only` — skip LLM extraction, just re-index and re-embed existing notes
239
239
 
240
+ ### Digest management
241
+
242
+ ```
243
+ node <plugin-root>/dist/src/cli.js digest # Run incremental digest cycle
244
+ node <plugin-root>/dist/src/cli.js digest --tier 3000 # Reprocess a specific tier (clean slate)
245
+ node <plugin-root>/dist/src/cli.js digest --full # Reprocess all tiers from scratch
246
+ ```
247
+
248
+ ### Vault curation
249
+
250
+ Supersession happens automatically on every spore write. For vault-wide cleanup, see `references/cli-usage.md` for full flags:
251
+
252
+ ```
253
+ node <plugin-root>/dist/src/cli.js curate # Scan and supersede stale spores
254
+ node <plugin-root>/dist/src/cli.js curate --dry-run # Preview without writing
255
+ ```
256
+
257
+ For patterns on when to manually supersede or consolidate, see `references/wisdom.md`.
258
+
240
259
  ### Other maintenance commands
241
260
 
242
261
  ```
@@ -287,6 +287,54 @@ Run this after changing the embedding model (via `setup-llm`) to regenerate all
287
287
 
288
288
  ---
289
289
 
290
+ ### `digest` — Run a digest cycle on demand
291
+
292
+ Trigger a digest cycle manually. Use `--tier` to reprocess a specific tier from scratch (all substrate, no previous extract), or `--full` for a complete rebuild of all tiers.
293
+
294
+ | Flag | Type | Description |
295
+ |------|------|-------------|
296
+ | `--tier <number>` | number | Reprocess a specific tier (clean slate) |
297
+ | `--full` | boolean | Reprocess all tiers from scratch |
298
+
299
+ When `--tier` or `--full` is used, the cycle reads all vault notes (ignoring the last-cycle timestamp) and skips the previous extract, producing a fresh synthesis.
300
+
301
+ **Examples:**
302
+
303
+ ```sh
304
+ # Run an incremental cycle (same as what the metabolism timer does)
305
+ node ${CLAUDE_PLUGIN_ROOT}/dist/src/cli.js digest
306
+
307
+ # Reprocess tier 3000 from scratch
308
+ node ${CLAUDE_PLUGIN_ROOT}/dist/src/cli.js digest --tier 3000
309
+
310
+ # Full rebuild of all tiers
311
+ node ${CLAUDE_PLUGIN_ROOT}/dist/src/cli.js digest --full
312
+ ```
313
+
314
+ ---
315
+
316
+ ### `curate` — Scan vault and supersede stale spores
317
+
318
+ Scans all active spores, clusters them by semantic similarity within each observation type, and asks the LLM which older spores are outdated. Superseded spores are preserved with lineage metadata — never deleted.
319
+
320
+ | Flag | Type | Description |
321
+ |------|------|-------------|
322
+ | `--dry-run` | boolean | Run LLM evaluation but print results without writing |
323
+
324
+ **Examples:**
325
+
326
+ ```sh
327
+ # Scan and supersede stale spores
328
+ node ${CLAUDE_PLUGIN_ROOT}/dist/src/cli.js curate
329
+
330
+ # Preview what would be superseded
331
+ node ${CLAUDE_PLUGIN_ROOT}/dist/src/cli.js curate --dry-run
332
+ ```
333
+
334
+ Note: `--dry-run` still runs LLM calls (to evaluate clusters) — it just skips the writes. Use it to review before running on a vault for the first time.
335
+
336
+ ---
337
+
290
338
  ### `reprocess` — Re-extract observations from transcripts
291
339
 
292
340
  Re-reads session transcripts, re-extracts observations with the current LLM, and re-indexes. Existing spores are preserved — new extractions are additive.
@@ -2,9 +2,19 @@
2
2
 
3
3
  When you notice patterns in vault spores — recurring themes, conflicting advice, outdated observations — use these tools to keep the vault clean and its knowledge sharp.
4
4
 
5
+ ## Automatic Curation
6
+
7
+ Myco automatically checks for supersession every time a new spore is written. After the spore is saved and embedded, a fire-and-forget pipeline searches for semantically similar active spores of the same observation type and asks the LLM whether any are now outdated. If so, they're marked superseded automatically. This means most vault hygiene happens without manual intervention.
8
+
9
+ For vault-wide cleanup (e.g., after a large refactor), use the CLI:
10
+ ```sh
11
+ node ${CLAUDE_PLUGIN_ROOT}/dist/src/cli.js curate --dry-run # preview
12
+ node ${CLAUDE_PLUGIN_ROOT}/dist/src/cli.js curate # execute
13
+ ```
14
+
5
15
  ## Supersede
6
16
 
7
- Use `myco_supersede` when a newer spore replaces an older one.
17
+ Use `myco_supersede` for manual supersession when you spot a stale spore that automatic curation missed.
8
18
 
9
19
  **Signals:**
10
20
  - A decision was reversed in a later session