@aistastudio/myc 0.3.7 → 0.3.10

package/README.md

@@ -37,8 +37,8 @@ Install Bun: https://bun.sh
 Installation is one command:
 
 ```bash
-bun install -g @aistastudio/myc   # 3.39 MB compressed, 12.49 MB unpacked, 13 files; no models pulled
-myc --version                     # myc 0.3.7 (schema 1)
+bun install -g @aistastudio/myc   # 3.42 MB compressed, 12.58 MB unpacked, 13 files; no models pulled
+myc --version                     # myc 0.3.10 (schema 1)
 ```
 
 It runs on macOS and Linux. On Windows, use WSL and install Bun and myc inside
@@ -255,6 +255,13 @@ under different keys; `code symbol` reads both.
 Anchors tie knowledge to a span and follow the code as it moves; that half is
 language-agnostic and was verified on Python as well as TypeScript.
 
+When the code is no longer where the anchor put it, the knowledge is not
+deleted — it ranks lower and says why. `recall` marks the row
+`[code moved ×0.64]`, `[code unverified ×0.5]` or `[code gone ×0.2]`: the
+multiplier is the one its score was taken down by (drifted × similarity,
+stale × 0.5, lost × 0.2). Knowledge whose every anchor is lost stays out of
+`prime`, and the footer counts it: `N with code gone hidden`.
+
 ## Migration from beads
 
 ```bash
@@ -350,6 +357,29 @@ episode sess-5jh8je4g050m saved (265 B)
 NEXT     myc show sess-5jh8je4g050m · myc ready --claim
 ```
 
+**Decisions pulled from a compaction are candidates, not facts.** The same hook
+lifts "we decided / because" lines out of the transcript and stores them as
+candidates (`state pending_review`); recall, search, prime and MCP do not
+return them until someone confirms. `prime` names them in its footer —
+`N pending review hidden — myc review` — and `myc review` lists them, this
+session's first, for a person or an agent to settle. Confirming makes the
+candidate knowledge the way a new note is born (embedding and absorb
+classification queued); rejecting retracts it with the reason kept in the node.
+An agent does the same through MCP: `myc_ready` with `review` lists,
+`myc_update` with `confirm` or `reject` settles; the web knowledge base puts
+the two buttons on the candidate's row.
+
+```
+$ myc review
+PENDING REVIEW 2 · 1 in this session's prime · 1 from other sessions · session 3f9c21aa
+$ myc review confirm memory-6k2x…
+$ myc review reject memory-9x1q… --reason "restates the task, not a decision"
+```
+
+A retracted note — a rejected candidate among them — is out of every retrieval
+path, not only replaced versions: superseded, retracted and cancelled are one
+list shared by recall, prime and the status line.
+
 **A status line with what the agent cannot see.** `myc wire --status-line`
 puts one line under Claude Code's prompt — how full the context is, the task
 queue, the code index, the project's memory, and how many of this session's
@@ -401,7 +431,7 @@ last-writer-wins over whole records.
 
 **Guards are proved by mutation.** Every refusal and every invariant is
 accompanied by a mutation that removes it; a guard whose removal breaks no test
-is treated as absent. The full suite: 3438 pass / 0 fail / 16 skip
+is treated as absent. The full suite: 3672 pass / 0 fail / 16 skip
 (`bun test`, 2026-09-11).
 
 ## What myc does