@tznthou/ccrecall 0.4.7 → 0.5.0

package/README.md

@@ -11,13 +11,9 @@ A local memory service for Claude Code — indexes your conversation history, re
 
 ---
 
-> 📐 **v0.3.0 — Trust split (breaking change for harvest write path)**
+> 📐 **v0.5.0 — The knife-field release: one pipeline, nothing dead**
 >
-> The SessionEnd hook now writes to a low-trust `session_journal` table instead of `memories`. Journal entries are scored, surfaced via `/health` (`journalPendingCount`), and **do not appear in `recall_query` / `recall_context` results** until you run `ccmem promote <id>`. Manual `recall_save` is unchanged — it still writes directly to high-trust `memories`.
->
-> The rule scorer is no longer on the persistence gate; it informs trust grade and promotion priority instead. Background reasoning at [issue #21](https://github.com/tznthou/ccRecall/issues/21).
->
-> Pre-0.3.0 memories stay queryable as-is. The v22 schema migration runs automatically on first daemon startup; existing rows are not touched. New harvest goes to journal from now on.
+> Post-session extraction via Haiku (~$0.001/session) has been the primary memory write path since v0.4.1, hardened across v0.4.2–v0.4.8. v0.5.0 removes everything that pipeline made obsolete — the journal review queue (zero promotions in its entire history), the rule scorer, checkpoints, and 8 caller-less HTTP endpoints — and rebuilds the replay-dedup registry as compact 64-bit hashes (database: 114MB → 42MB measured). Manual `recall_save` remains available for in-session saves.
 
 ---
 
@@ -41,12 +37,11 @@ ccRecall is the "memory" counterpart to [ccRewind](https://github.com/tznthou/cc
 | **FTS5 full-text search** | Sub-100ms keyword search across all conversation history, fast enough for hook injection |
 | **CJK / mixed-script search** | Trigram tokenizer indexes Chinese / Japanese / Korean text; per-token AND LIKE fallback handles short queries like `UI 記憶` that trigram alone can't match |
 | **Incremental indexing** | Only re-indexes sessions that changed (mtime diffing), handles resumed sessions via UUID dedup |
-| **Metacognition** | `knowledge_map` aggregates topic mentions from sessions + memories. Depth derived from mention count (shallow / medium / deep). Exposed via `/metacognition/check` and MCP `recall_context` |
+| **Metacognition** | `knowledge_map` aggregates topic mentions from sessions + memories. Depth derived from mention count (shallow / medium / deep). Exposed via MCP `recall_context` |
 | **Forgetting curve** | Memories compress over time: raw → summary → one-liner → deleted. Confidence decays on unused memories. Background maintenance tick runs every 5 min |
-| **Trust two-tier** (v0.3.0) | Hooks write to a low-trust `session_journal` (reviewable, never recalled directly); manual `recall_save` writes high-trust `memories`. Promote candidates with `ccmem promote <id>`; rejected entries auto-clear after 7 days |
 | **Cross-project memory** (v0.4.1) | Memories surface across projects via topic intersection — if two projects share a `knowledge_map` topic, high-confidence memories from one appear in the other's startup injection (max 3 rows, confidence ≥ 0.8 gate) |
 | **Watch mode** | chokidar-based JSONL watcher picks up new sessions within 2 s; periodic 10 min full-resync covers missed filesystem events |
-| **Rescue reindex** | `/session/end` retries a reindex on cache miss — no fresh-session race between the hook and the daemon |
+| **Rescue reindex** | `/session/end` and `/session/last` both retry a reindex on miss, and `/session/last` staleness-gates via `notBefore` — no fresh-session race between the hook, the wrapper, and the daemon |
 | **Auto-start (macOS)** | `ccmem install-daemon` registers a LaunchAgent so the service stays up across reboots |
 | **Read-only** | Never modifies `~/.claude/` — only reads JSONL logs |
 
@@ -61,24 +56,64 @@ flowchart TB
     end
 
     subgraph Core["ccRecall Service (port 7749)"]
+        Watcher["Watcher<br/>chokidar, 2 s debounce"]
         Scanner["Scanner<br/>find JSONL files"]
         Parser["Parser<br/>parse conversations"]
         Summarizer["Summarizer<br/>rule-based extraction"]
-        DB["SQLite + FTS5<br/>index & search"]
-        API["HTTP API<br/>12 endpoints"]
+        DB[("SQLite + FTS5<br/>index & search")]
+        API["HTTP API<br/>5 endpoints"]
     end
 
-    subgraph Consumers["Context Injection"]
+    subgraph Consumers["Consumers"]
         Hook["Claude Code Hooks<br/>SessionStart / SessionEnd"]
+        Wrapper["Extraction wrapper<br/>post-session Haiku pass"]
         MCP["MCP Server<br/>recall_query / recall_save"]
     end
 
-    JSONL --> Scanner --> Parser --> Summarizer --> DB
-    DB --> API
-    API --> Hook
-    API --> MCP
+    JSONL --> Watcher --> Scanner --> Parser --> Summarizer --> DB
+    DB <--> API
+    Hook -->|"inject / end-confirm"| API
+    Wrapper -->|"GET /session/last"| API
+    MCP <-->|"shared SQLite via WAL"| DB
+```
+
+Arrows point in the direction of the call: hooks and the extraction wrapper talk to the daemon over HTTP, while the MCP server is a separate process that opens the same SQLite file directly (WAL mode) — it never goes through the HTTP API.
+
+### Session lifecycle
+
+How the two timing-sensitive ends of a session actually flow:
+
+```mermaid
+sequenceDiagram
+    participant CC as Claude Code
+    participant H as Hooks
+    participant R as ccRecall
+    participant W as Wrapper
+    participant X as Haiku extractor
+
+    rect rgb(235, 244, 255)
+    Note over CC,R: Session start
+    CC->>H: SessionStart
+    H->>R: GET /memory/startup
+    R-->>H: 3-tier memory pick (< 300 tokens)
+    H-->>CC: inject into context
+    end
+
+    Note over CC,R: During the session, the watcher<br/>reindexes JSONL writes (2 s debounce)
+
+    rect rgb(255, 244, 235)
+    Note over CC,X: Session end
+    CC->>H: SessionEnd
+    H->>R: POST /session/end (index confirm + rescue)
+    W->>R: GET /session/last?notBefore=launch_ts
+    R-->>W: sessionId (staleness-gated, subagent-filtered)
+    W->>X: text-only transcript
+    X->>R: recall_save × 0–5 (via MCP)
+    end
 ```
 
+The `notBefore` gate keeps a stale session from being extracted twice; the subagent filter keeps an Agent-tool side-session from shadowing the real one. Both guards exist because the wrapper queries within seconds of session close, racing the watcher.
+
 ---
 
 ## Tech Stack
@@ -90,7 +125,7 @@ flowchart TB
 | FTS5 | Full-text search | Built into SQLite, trigram tokenizer with LIKE fallback for short CJK / mixed-script queries |
 | Native `http` | HTTP server | No Express — minimal surface, localhost only |
 | chokidar | Filesystem watcher | Cross-platform JSONL change detection with 2 s debounce + single-flight |
-| vitest | Testing | 608 tests across 38 files, integration-style |
+| vitest | Testing | 629 tests across 39 files, integration-style |
 | `@modelcontextprotocol/sdk` | MCP server | stdio transport, shared SQLite via WAL |
 
 ---
@@ -132,20 +167,17 @@ curl "http://127.0.0.1:7749/memory/query?q=authentication&limit=5"
 
 ## API Endpoints
 
-| Endpoint | Method | Description | Status |
+Five endpoints, each with a live caller — v0.5.0 removed the other eight
+(`/journal/*`, `/memory/save`, `/memory/context`, `/metacognition/check`,
+`/session/checkpoint`, `/lint/warnings`); they now return 404.
+
+| Endpoint | Method | Description | Caller |
 |----------|--------|-------------|--------|
-| `/health` | GET | Service health + DB stats + integrity check status + `journalPendingCount` (since v0.3.0) | Live |
-| `/memory/query?q=...&limit=...&project=...` | GET | FTS5 search across memories with optional project filter (journal entries excluded by design) | Live |
-| `/memory/save` | POST | Save a memory entry (origin-checked) | Live |
-| `/session/end` | POST | Harvest a finished session into `session_journal` (idempotent; was `memories` pre-0.3.0) | Live |
-| `/journal/pending` | GET | List journal entries awaiting promotion review | Live (v0.3.0) |
-| `/journal/promote` | POST | Atomically promote a journal entry into `memories` | Live (v0.3.0) |
-| `/journal/reject` | POST | Soft-delete a journal entry (cleared after 7-day TTL by decay sweep) | Live (v0.3.0) |
-| `/memory/context?session_id=...` | GET | Session context lookup | Stub |
-| `/metacognition/check?projectId=...[&topic=...]` | GET | Knowledge map: summary (top/recent/stale topics + counts) or topic detail (memories + related topics) | Live |
-| `/session/checkpoint` | POST | Mid-session snapshot into dedicated `session_checkpoints` table (not harvested as memory) | Live |
-| `/lint/warnings` | GET | Lint report: orphan (session deleted) + stale (low-confidence, long-idle) memory warnings | Live |
-| `/session/last?cwd=...` | GET | Most recent session metadata for a project path (used by post-session extraction wrapper) | Live (v0.4.1) |
+| `/health` | GET | Service health + DB stats + integrity check status | CLI, extraction wrapper |
+| `/memory/startup?project=...` | GET | SessionStart-tier retrieval: cold + recent-confidence + FTS fallback, token-budgeted | SessionStart hook |
+| `/memory/query?q=...&limit=...&project=...` | GET | FTS5 search across memories with optional project filter | SessionStart hook (keyword tier) |
+| `/session/end` | POST | Confirm the just-ended session is indexed (rescue reindex on miss) | SessionEnd hook |
+| `/session/last?cwd=...` | GET | Most recent session metadata for a project path (staleness-gated via `notBefore`) | Extraction wrapper |
 
 ## MCP Tools
 
@@ -197,21 +229,10 @@ Daemon and hook lifecycle (macOS):
 | `ccmem uninstall-daemon` | Stop and remove the LaunchAgent |
 | `ccmem install-hooks` | Merge SessionStart / SessionEnd entries into `~/.claude/settings.json` |
 | `ccmem uninstall-hooks` | Remove ccRecall's hook entries (other hooks untouched) |
+| `ccmem cleanup --orphans` | List (and with `--yes`, delete) memories whose session rows are gone |
 
-Journal review (since v0.3.0):
-
-| Command | Purpose |
-|---------|---------|
-| `ccmem promote <id>` | Promote a journal entry into `memories`. Optional `--type` (default `discovery`) and `--confidence` (default `0.7`) |
-| `ccmem reject <id>` | Soft-delete a journal entry; cleaned up after the 7-day TTL by the decay sweep |
-
-Surface pending candidates:
-
-```bash
-curl http://127.0.0.1:7749/journal/pending
-# or just check the count
-curl http://127.0.0.1:7749/health | jq .journalPendingCount
-```
+`ccmem promote` / `ccmem reject` were removed in v0.5.0 along with the
+journal pipeline they reviewed.
 
 ---
 
@@ -232,8 +253,6 @@ ccRecall lives alongside Claude Code's built-in auto memory (`~/.claude/projects
 
 ccRecall's value is the long tail that auto memory can't cover (nobody hand-curates 500 sessions of notes). If Claude defaults to both, auto memory wins because it's already loaded and curated. ccRecall earns its keep when the curated index misses.
 
-**Within ccRecall there's now a second trust split** (since v0.3.0). The SessionEnd hook writes to a low-trust `session_journal` table that `recall_query` does **not** read. Promote a candidate to high-trust `memories` with `ccmem promote <id>` to make it queryable. Manual `recall_save` skips the journal entirely — it writes straight to memories. The point is to let the harvester record broadly while keeping recall results clean.
-
 ---
 
 ## Running as a service (macOS)
@@ -265,7 +284,7 @@ Full manual-install, troubleshooting, and uninstall docs:
 [docs/launchd.md](docs/launchd.md).
 
 Linux/Windows equivalents (systemd unit, Windows service) are planned for
-Phase 5. For now, run under `nohup` or your process manager of choice.
+a future release. For now, run under `nohup` or your process manager of choice.
 
 ---
 
@@ -315,8 +334,7 @@ ccRecall/
 │   │   ├── indexer.ts            # Indexing pipeline orchestrator
 │   │   ├── memory-service.ts     # Memory lifecycle (touch / delete / update)
 │   │   ├── compression.ts        # L0→L1→L2→delete state machine
-│   │   ├── lint.ts               # Orphan / stale memory detection
-│   │   ├── maintenance-coordinator.ts  # Background compression tick + journal decay sweep
+│   │   ├── maintenance-coordinator.ts  # Background compression tick
 │   │   ├── watcher.ts            # chokidar JSONL watcher (Phase 4e)
 │   │   └── log-safe.ts           # scrubErrorMessage — log-injection defence
 │   ├── api/
@@ -326,8 +344,7 @@ ccRecall/
 │   │   ├── server.ts             # MCP stdio server entry (shebang bin)
 │   │   └── tools.ts              # recall_query + recall_context + recall_save
 │   ├── cli/
-│   │   ├── daemon.ts             # install-daemon / uninstall-daemon (macOS)
-│   │   └── journal.ts            # ccmem promote / reject (since v0.3.0)
+│   │   └── daemon.ts             # install-daemon / uninstall-daemon (macOS)
 │   └── index.ts                  # HTTP entry point + subcommand dispatch
 ├── hooks/
 │   ├── session-start.mjs         # Inject memories on SessionStart (stdout)
@@ -337,11 +354,10 @@ ccRecall/
 │   ├── tutorial.md               # End-user walkthrough (install → MCP → usage)
 │   ├── architecture.md           # Daemon design rationale (contributor-oriented)
 │   └── launchd.md                # macOS LaunchAgent install/troubleshoot
-├── tests/                        # 608 tests across 38 files (parser, scanner,
+├── tests/                        # 524 tests across 34 files (parser, scanner,
 │   │                             # summarizer, database, indexer, e2e, MCP,
 │   │                             # memories, hooks, watcher, CLI, migrations,
-│   │                             # FTS5 CJK edge cases, integrity monitor,
-│   │                             # session_journal DAO, promote+reject, sweep, ...)
+│   │                             # FTS5 CJK edge cases, integrity monitor, ...)
 │   └── fixtures/                 # Sample JSONL + shared test helpers
 ├── .mcp.json.example             # MCP client config template
 └── NOTICE / SECURITY.md / CONTRIBUTING.md / CODE_OF_CONDUCT.md
@@ -392,9 +408,9 @@ The real trigger was simpler: I kept re-explaining the same architecture to Clau
 | Version | Theme | Status |
 |---------|-------|--------|
 | **v0.3.x** | Manual save, automatic recall — memories come from explicit `recall_save` calls; SessionStart hook and MCP tools inject them into future sessions | Released |
-| **v0.4.0** | Startup-v1 default + tool description hardening | Released |
-| **v0.4.1** | Key-based upsert dedup, post-session memory extraction via Haiku, cross-project memory visibility via topic intersection | Released |
-| **v0.5+** | Scorer/journal/harvester deprecation, L1 keyword injection, memory lifecycle history | Planned |
+| **v0.4.x** | Post-session extraction via Haiku, cross-project memory via topic intersection, extraction pipeline hardening (race gates, compression integrity, subagent filtering, security) | Released |
+| **v0.5.0** | The knife field: journal/scorer/harvester pipelines removed (zero promotions ever), endpoints 13 → 5, `message_uuids` dual-hash rebuild (DB 114MB → 42MB) | Released |
+| **v0.5+** | CJK-aware topic extraction (`\p{Script=Han}` tokenizer + Chinese stopwords), L1 keyword injection, README → manifesto | Planned |
 
 Tracked in [GitHub Issues](https://github.com/tznthou/ccRecall/issues).
 

package/README_ZH.md

@@ -11,13 +11,9 @@ Claude Code 的本地記憶服務——索引你的對話歷史，按需召回
 
 ---
 
-> 📐 **v0.3.0 — Trust 二層拆分（harvest 寫入路徑 breaking change）**
+> 📐 **v0.5.0 — 砍刀場版本：一條管線，零死代碼**
 >
-> SessionEnd hook 改寫到新建的 low-trust `session_journal` 表，不再寫 `memories`。Journal 條目會評分、透過 `/health` 的 `journalPendingCount` 露出，**`recall_query` / `recall_context` 不會直接召回 journal 條目**，需要先 `ccmem promote <id>` 升級。Manual `recall_save` 不變——仍直寫 high-trust `memories`。
->
-> Rule scorer 不再卡在 persistence gate；改成提供 trust grade 與 promote 優先序。完整 rationale 見 [issue #21](https://github.com/tznthou/ccRecall/issues/21)。
->
-> 0.3.0 之前的 memories 仍可正常查詢。v22 schema migration 在 daemon 第一次啟動時自動跑，既有 row 不會被動。新 harvest 從現在起寫 journal。
+> Post-session extraction via Haiku（約 $0.001/session）自 v0.4.1 起就是主要記憶寫入路徑，v0.4.2–v0.4.8 逐版強化。v0.5.0 把這條管線淘汰掉的東西一次清完——journal 審閱佇列（史上零 promotion）、規則 scorer、checkpoints、8 個零 caller 的 HTTP endpoint——並把 replay 去重登記表重建為精巧的 64-bit hash（資料庫實測 114MB → 42MB）。Manual `recall_save` 仍可用於 session 中即時存記憶。
 
 ---
 
@@ -41,12 +37,11 @@ ccRecall 是 [ccRewind](https://github.com/tznthou/ccRewind)（對話回放 GUI
 | **FTS5 全文搜尋** | 所有對話歷史的關鍵詞搜尋 <100ms，快到可以在 hook 中注入 |
 | **CJK / 中英混合搜尋** | Trigram tokenizer 索引中日韓文字；短 token 查詢（如 `UI 記憶`）以 per-token AND LIKE fallback 補齊，避開 trigram 對 <3 字 token 的盲區 |
 | **增量索引** | 只重新索引有變動的 session（mtime 比對），透過 UUID 去重處理接續 session |
-| **元認知** | `knowledge_map` 聚合 session + memory 的主題提及。由 mention count 衍生深度（shallow / medium / deep）。透過 `/metacognition/check` 與 MCP `recall_context` 暴露 |
+| **元認知** | `knowledge_map` 聚合 session + memory 的主題提及。由 mention count 衍生深度（shallow / medium / deep）。透過 MCP `recall_context` 暴露 |
 | **遺忘曲線** | 記憶隨時間壓縮：原始→摘要→一行結論→刪除。未使用的記憶信心衰減。背景維護 tick 每 5 分鐘跑一次 |
-| **Trust 二層**（v0.3.0） | Hook 寫入 low-trust `session_journal`（可審閱、不被 recall）；manual `recall_save` 寫 high-trust `memories`。用 `ccmem promote <id>` 升級候選；reject 後 7 天 TTL 自動清 |
 | **跨專案記憶**（v0.4.1） | 記憶透過 topic intersection 跨專案浮出——若兩個專案的 `knowledge_map` 有共同 topic，高信心記憶會出現在另一個專案的 startup injection（最多 3 條，confidence ≥ 0.8 gate） |
 | **Watch mode** | 基於 chokidar 的 JSONL watcher 在 2 秒內偵測新 session；每 10 分鐘 full-resync 補救 FS 事件漏接 |
-| **Rescue reindex** | `/session/end` 遇到 cache miss 時會重 index 再試一次——hook 和 daemon 間不會有 fresh-session race |
+| **Rescue reindex** | `/session/end` 和 `/session/last` 都會在 miss 時重 index 再試一次，`/session/last` 另有 `notBefore` staleness gate——hook、wrapper、daemon 三方不會有 fresh-session race |
 | **macOS 自動啟動** | `ccmem install-daemon` 安裝 LaunchAgent，重開機自動復原服務 |
 | **純唯讀** | 絕不修改 `~/.claude/`——只讀取 JSONL 記錄 |
 
@@ -61,24 +56,64 @@ flowchart TB
     end
 
     subgraph Core["ccRecall 服務（port 7749）"]
+        Watcher["Watcher<br/>chokidar，2 秒 debounce"]
         Scanner["Scanner<br/>掃描 JSONL 檔案"]
         Parser["Parser<br/>解析對話"]
         Summarizer["Summarizer<br/>規則式萃取"]
-        DB["SQLite + FTS5<br/>索引與搜尋"]
-        API["HTTP API<br/>12 個端點"]
+        DB[("SQLite + FTS5<br/>索引與搜尋")]
+        API["HTTP API<br/>5 個端點"]
     end
 
-    subgraph Consumers["Context 注入"]
+    subgraph Consumers["使用端"]
         Hook["Claude Code Hooks<br/>SessionStart / SessionEnd"]
+        Wrapper["Extraction wrapper<br/>session 結束後的 Haiku 抽取"]
         MCP["MCP Server<br/>recall_query / recall_save"]
     end
 
-    JSONL --> Scanner --> Parser --> Summarizer --> DB
-    DB --> API
-    API --> Hook
-    API --> MCP
+    JSONL --> Watcher --> Scanner --> Parser --> Summarizer --> DB
+    DB <--> API
+    Hook -->|"注入 / 收尾確認"| API
+    Wrapper -->|"GET /session/last"| API
+    MCP <-->|"WAL 模式共用 SQLite"| DB
+```
+
+箭頭方向代表「誰呼叫誰」：hooks 和 extraction wrapper 走 HTTP 找 daemon；MCP server 則是獨立進程，直接開同一個 SQLite 檔（WAL 模式）——完全不經過 HTTP API。
+
+### Session 生命週期
+
+一個 session 頭尾兩端（都是跟時間賽跑的環節）實際怎麼跑：
+
+```mermaid
+sequenceDiagram
+    participant CC as Claude Code
+    participant H as Hooks
+    participant R as ccRecall
+    participant W as Wrapper
+    participant X as Haiku 抽取器
+
+    rect rgb(235, 244, 255)
+    Note over CC,R: Session 開始
+    CC->>H: SessionStart
+    H->>R: GET /memory/startup
+    R-->>H: 三層記憶挑選（< 300 tokens）
+    H-->>CC: 注入 context
+    end
+
+    Note over CC,R: Session 進行中，watcher 持續<br/>增量索引 JSONL（2 秒 debounce）
+
+    rect rgb(255, 244, 235)
+    Note over CC,X: Session 結束
+    CC->>H: SessionEnd
+    H->>R: POST /session/end（確認已索引 + rescue）
+    W->>R: GET /session/last?notBefore=launch_ts
+    R-->>W: sessionId（過 staleness gate、濾掉 subagent）
+    W->>X: 純文字 transcript
+    X->>R: recall_save × 0–5 筆（經 MCP）
+    end
 ```
 
+`notBefore` gate 擋掉「抽到上一個舊 session」的重複抽取；subagent 過濾擋掉 Agent tool 側線 session 蓋台。這兩道防線存在的原因是同一個：wrapper 在 session 關閉後幾秒內就查詢，跟 watcher 的索引在賽跑。
+
 ---
 
 ## 技術棧
@@ -90,7 +125,7 @@ flowchart TB
 | FTS5 | 全文搜尋 | SQLite 內建、trigram tokenizer，短 token / 中英混合查詢透過 LIKE fallback 補齊 |
 | 原生 `http` | HTTP 伺服器 | 不用 Express——最小表面積、僅 localhost |
 | chokidar | 檔案系統 watcher | 跨平台 JSONL 變動偵測，2 秒 debounce + single-flight |
-| vitest | 測試 | 608 個測試（38 檔案）、整合式風格 |
+| vitest | 測試 | 629 個測試（39 檔案）、整合式風格 |
 | `@modelcontextprotocol/sdk` | MCP server | stdio transport，透過 WAL 共用 SQLite |
 
 ---
@@ -132,20 +167,17 @@ curl "http://127.0.0.1:7749/memory/query?q=authentication&limit=5"
 
 ## API 端點
 
-| 端點 | 方法 | 說明 | 狀態 |
-|------|------|------|------|
-| `/health` | GET | 服務健康 + DB 統計 + integrity 檢查狀態 + `journalPendingCount`（v0.3.0 新增） | 已上線 |
-| `/memory/query?q=...&limit=...&project=...` | GET | FTS5 跨 session 搜尋，可選 project 過濾（journal 條目 by design 不含） | 已上線 |
-| `/memory/save` | POST | 儲存記憶條目（Origin 驗證） | 已上線 |
-| `/session/end` | POST | 把結束的 session 寫入 `session_journal`（idempotent；0.3.0 前是寫 `memories`） | 已上線 |
-| `/journal/pending` | GET | 列出待 promote 審閱的 journal 條目 | 已上線（v0.3.0） |
-| `/journal/promote` | POST | atomic 把 journal 條目升級到 `memories` | 已上線（v0.3.0） |
-| `/journal/reject` | POST | soft-delete journal 條目（7 天 TTL，由 decay sweep 清理） | 已上線（v0.3.0） |
-| `/memory/context?session_id=...` | GET | Session context 查詢 | Stub |
-| `/metacognition/check?projectId=...[&topic=...]` | GET | 知識地圖：summary（top/recent/stale topics + counts）或 topic detail（memories + related topics） | 已上線 |
-| `/session/checkpoint` | POST | 會話中途快照寫入獨立 `session_checkpoints` 表（不會被 harvest 成 memory） | 已上線 |
-| `/lint/warnings` | GET | Lint 報告：orphan（session 已刪）+ stale（低信心、長期未用）記憶警告 | 已上線 |
-| `/session/last?cwd=...` | GET | 回傳專案路徑的最新 session metadata（post-session extraction wrapper 使用） | 已上線（v0.4.1） |
+五個端點，每個都有活的 caller——v0.5.0 移除了其餘八個
+（`/journal/*`、`/memory/save`、`/memory/context`、`/metacognition/check`、
+`/session/checkpoint`、`/lint/warnings`），現在一律回 404。
+
+| 端點 | 方法 | 說明 | Caller |
+|------|------|------|--------|
+| `/health` | GET | 服務健康 + DB 統計 + integrity 檢查狀態 | CLI、extraction wrapper |
+| `/memory/startup?project=...` | GET | SessionStart 級檢索：cold + recent-confidence + FTS fallback，帶 token 預算 | SessionStart hook |
+| `/memory/query?q=...&limit=...&project=...` | GET | FTS5 跨記憶搜尋，可選 project 過濾 | SessionStart hook（keyword 層） |
+| `/session/end` | POST | 確認剛結束的 session 已被索引（miss 時 rescue reindex） | SessionEnd hook |
+| `/session/last?cwd=...` | GET | 回傳專案路徑的最新 session metadata（`notBefore` staleness gate） | Extraction wrapper |
 
 ## MCP 工具
 
@@ -195,21 +227,9 @@ Daemon 與 hook 生命週期（macOS）：
 | `ccmem uninstall-daemon` | 停掉並移除 LaunchAgent |
 | `ccmem install-hooks` | 把 SessionStart / SessionEnd 條目合併進 `~/.claude/settings.json` |
 | `ccmem uninstall-hooks` | 移除 ccRecall 自己的 hook 條目（其他 hook 不動） |
+| `ccmem cleanup --orphans` | 列出（加 `--yes` 則刪除）session 已消失的 orphan 記憶 |
 
-Journal 審閱（v0.3.0 新增）：
-
-| 指令 | 用途 |
-|------|------|
-| `ccmem promote <id>` | 把 journal 條目升級到 `memories`。可選 `--type`（預設 `discovery`）、`--confidence`（預設 `0.7`） |
-| `ccmem reject <id>` | soft-delete journal 條目；7 天 TTL 後由 decay sweep 清掉 |
-
-查待 promote 候選：
-
-```bash
-curl http://127.0.0.1:7749/journal/pending
-# 或只看計數
-curl http://127.0.0.1:7749/health | jq .journalPendingCount
-```
+`ccmem promote` / `ccmem reject` 已於 v0.5.0 隨 journal 管線一併移除。
 
 ---
 
@@ -230,8 +250,6 @@ ccRecall 和 Claude Code 內建的 auto memory（`~/.claude/projects/*/memory/`
 
 ccRecall 的價值在長尾——幾百個 session 不可能全手工整理。如果 Claude 兩邊都試，auto memory 永遠會贏（本來就在 context 裡而且已經被策展）。ccRecall 存在的意義是：策展索引漏掉時，長尾那堆還在資料庫裡可以撈出來。
 
-**ccRecall 內部從 v0.3.0 起多了一層 trust 拆分。** SessionEnd hook 寫到 low-trust `session_journal` 表——`recall_query` 不會去讀那裡。要讓某筆候選進到查詢結果，跑 `ccmem promote <id>` 升級到 high-trust `memories`。Manual `recall_save` 完全不經 journal——直接寫 memories。設計目的：讓 harvester 廣捕，但 recall 結果保持乾淨。
-
 ---
 
 ## 作為服務運行（macOS）
@@ -260,7 +278,7 @@ installer 的行為：
 
 完整手動安裝、troubleshooting、uninstall 文件：[docs/launchd.md](docs/launchd.md)。
 
-Linux/Windows 對應版本（systemd unit、Windows service）列在 Phase 5。目前
+Linux/Windows 對應版本（systemd unit、Windows service）列在未來版本。目前
 Linux 可用 `nohup` 或自選 process manager。
 
 ---
@@ -308,8 +326,7 @@ ccRecall/
 │   │   ├── indexer.ts                # 索引 pipeline 調度
 │   │   ├── memory-service.ts         # 記憶生命週期(touch / delete / update)
 │   │   ├── compression.ts            # L0→L1→L2→delete 狀態機
-│   │   ├── lint.ts                   # Orphan / stale 記憶偵測
-│   │   ├── maintenance-coordinator.ts # 背景壓縮 tick + journal decay sweep
+│   │   ├── maintenance-coordinator.ts # 背景壓縮 tick
 │   │   ├── watcher.ts                # chokidar JSONL watcher(Phase 4e)
 │   │   └── log-safe.ts               # scrubErrorMessage — log-injection 防護
 │   ├── api/
@@ -319,8 +336,7 @@ ccRecall/
 │   │   ├── server.ts                 # MCP stdio server 入口(含 shebang)
 │   │   └── tools.ts                  # recall_query + recall_context + recall_save
 │   ├── cli/
-│   │   ├── daemon.ts                 # install-daemon / uninstall-daemon(macOS)
-│   │   └── journal.ts                # ccmem promote / reject(v0.3.0 新增)
+│   │   └── daemon.ts                 # install-daemon / uninstall-daemon(macOS)
 │   └── index.ts                      # HTTP 入口 + 子指令分派
 ├── hooks/
 │   ├── session-start.mjs             # SessionStart 注入記憶(stdout)
@@ -330,11 +346,10 @@ ccRecall/
 │   ├── tutorial_zh.md                # 使用者教學（安裝 → MCP → 日常使用）
 │   ├── architecture_zh.md            # Daemon 設計取捨（給 contributor 看）
 │   └── launchd.md                    # macOS LaunchAgent 安裝/troubleshoot
-├── tests/                            # 608 個測試橫跨 38 檔案（parser、scanner、
+├── tests/                            # 524 個測試橫跨 34 檔案（parser、scanner、
 │   │                                 # summarizer、database、indexer、e2e、MCP、
 │   │                                 # memories、hooks、watcher、CLI、migrations、
-│   │                                 # FTS5 CJK edge cases、integrity monitor、
-│   │                                 # session_journal DAO、promote+reject、sweep 等）
+│   │                                 # FTS5 CJK edge cases、integrity monitor 等）
 │   └── fixtures/                     # 測試用 JSONL + 共用 helpers
 ├── .mcp.json.example                 # MCP client 設定範本
 └── NOTICE / SECURITY.md / CONTRIBUTING.md / CODE_OF_CONDUCT.md
@@ -385,9 +400,9 @@ Anthropic Claude Code 團隊的 Thariq 在 2026 年 4 月[發表了 context 管
 | 版本 | 主題 | 狀態 |
 |------|------|------|
 | **v0.3.x** | 手動存、自動召回——記憶來自明確的 `recall_save` 呼叫；SessionStart hook 和 MCP 工具在未來 session 注入 | 已釋出 |
-| **v0.4.0** | Startup-v1 預設 + tool description 強化 | 已釋出 |
-| **v0.4.1** | Key-based upsert dedup、post-session memory extraction via Haiku、跨專案 topic intersection 記憶可見性 | 已釋出 |
-| **v0.5+** | Scorer/journal/harvester 降級、L1 keyword injection、memory lifecycle history | 規劃中 |
+| **v0.4.x** | Post-session extraction via Haiku、跨專案 topic intersection 記憶、萃取管線強化（race gate、壓縮完整性、subagent 過濾、安全性） | 已釋出 |
+| **v0.5.0** | 砍刀場：journal/scorer/harvester 管線移除（史上零 promotion）、端點 13 → 5、`message_uuids` 雙 hash 重建（DB 114MB → 42MB） | 已釋出 |
+| **v0.5+** | CJK topic 抽取（`\p{Script=Han}` tokenizer + 中文 stopwords）、L1 keyword injection、README → manifesto | 規劃中 |
 
 追蹤於 [GitHub Issues](https://github.com/tznthou/ccRecall/issues)。
 

package/dist/api/routes.d.ts

@@ -1,16 +1,6 @@
 import http from 'node:http';
 import type { Database } from '../core/database.js';
-import type { SessionMeta, OutcomeStatus, JournalEntryInput } from '../core/types.js';
 import type { IntegrityCheckRecord } from '../core/integrity-monitor.js';
-export declare function inferConfidence(outcome: OutcomeStatus): number;
-/** P1 (#21): hook auto-harvester 改寫 session_journal 不寫 memories;
- *  manual recall_save 仍直寫 memories。promote 路徑 (C4) 會把 journal entry
- *  搬到 memories table 並設 confidence。
- *
- *  Score 重算: summarizer 已用 scorer 過 noise/process-report hard floor,
- *  但 score + reasons metadata 沒儲在 sessions.harvest_text。重算成本低
- *  (regex 對 <2KB 文字),換 schema 不變的代價可接受。 */
-export declare function buildJournalCandidate(session: SessionMeta): JournalEntryInput | null;
 /** Coalesces concurrent rescue calls onto one underlying run. The SessionEnd
  *  hook (/session/end) and the extraction wrapper (/session/last) both fire
  *  within the same session close — without this each miss stacks its own full

package/dist/api/routes.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"routes.d.ts","sourceRoot":"","sources":["../../src/api/routes.ts"],"names":[],"mappings":"AACA,OAAO,IAAI,MAAM,WAAW,CAAA;AAG5B,OAAO,KAAK,EAAE,QAAQ,EAAe,MAAM,qBAAqB,CAAA;AAOhE,OAAO,KAAK,EACwB,WAAW,EAAE,aAAa,EAE5D,iBAAiB,EAClB,MAAM,kBAAkB,CAAA;AAEzB,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,8BAA8B,CAAA;AA6DxE,wBAAgB,eAAe,CAAC,OAAO,EAAE,aAAa,GAAG,MAAM,CAI9D;AAED;;;;;;2CAM2C;AAC3C,wBAAgB,qBAAqB,CAAC,OAAO,EAAE,WAAW,GAAG,iBAAiB,GAAG,IAAI,CAcpF;AAgED;;;;;gCAKgC;AAChC,wBAAgB,cAAc,CAAC,GAAG,EAAE,MAAM,OAAO,CAAC,IAAI,CAAC,GAAG,MAAM,OAAO,CAAC,IAAI,CAAC,CAM5E;AAED,MAAM,WAAW,qBAAqB;IACpC;;mDAE+C;IAC/C,aAAa,CAAC,EAAE,MAAM,OAAO,CAAC,IAAI,CAAC,CAAA;IACnC;;gFAE4E;IAC5E,OAAO,CAAC,EAAE,MAAM,CAAA;IAChB;;6EAEyE;IACzE,MAAM,CAAC,EAAE,MAAM,CAAA;IACf;;4EAEwE;IACxE,gBAAgB,CAAC,EAAE;QAAE,aAAa,IAAI,oBAAoB,GAAG,IAAI,CAAA;KAAE,CAAA;CACpE;AAED,wBAAgB,oBAAoB,CAClC,EAAE,EAAE,QAAQ,EACZ,IAAI,GAAE,qBAA0B,IAI9B,KAAK,IAAI,CAAC,eAAe,EACzB,KAAK,IAAI,CAAC,cAAc,KACvB,OAAO,CAAC,IAAI,CAAC,CA6djB"}
+{"version":3,"file":"routes.d.ts","sourceRoot":"","sources":["../../src/api/routes.ts"],"names":[],"mappings":"AACA,OAAO,IAAI,MAAM,WAAW,CAAA;AAG5B,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,qBAAqB,CAAA;AAMnD,OAAO,KAAK,EAAE,oBAAoB,EAAE,MAAM,8BAA8B,CAAA;AAqCxE;;;;;gCAKgC;AAChC,wBAAgB,cAAc,CAAC,GAAG,EAAE,MAAM,OAAO,CAAC,IAAI,CAAC,GAAG,MAAM,OAAO,CAAC,IAAI,CAAC,CAM5E;AAED,MAAM,WAAW,qBAAqB;IACpC;;mDAE+C;IAC/C,aAAa,CAAC,EAAE,MAAM,OAAO,CAAC,IAAI,CAAC,CAAA;IACnC;;gFAE4E;IAC5E,OAAO,CAAC,EAAE,MAAM,CAAA;IAChB;;6EAEyE;IACzE,MAAM,CAAC,EAAE,MAAM,CAAA;IACf;;4EAEwE;IACxE,gBAAgB,CAAC,EAAE;QAAE,aAAa,IAAI,oBAAoB,GAAG,IAAI,CAAA;KAAE,CAAA;CACpE;AAED,wBAAgB,oBAAoB,CAClC,EAAE,EAAE,QAAQ,EACZ,IAAI,GAAE,qBAA0B,IAI9B,KAAK,IAAI,CAAC,eAAe,EACzB,KAAK,IAAI,CAAC,cAAc,KACvB,OAAO,CAAC,IAAI,CAAC,CA8NjB"}