@chendpoc/pi-memory 0.2.1 → 0.2.2

package/README.md

@@ -1,3 +1,7 @@
+<p align="center">
+  <img src="./assets/pi-memory-logo.png" alt="pi-memory logo" width="720" />
+</p>
+
 # @chendpoc/pi-memory
 
 <p align="center">
@@ -9,7 +13,7 @@ Cross-session episodic memory for the [Pi coding agent](https://pi.dev).
 
 `pi-memory` gives Pi a local, auditable memory layer across sessions. It keeps durable facts in **`MEMORY.md` as the source of truth**, derives a vector index in `memory.vec.sqlite`, and injects relevant private context through Preflight before the main model answers.
 
-## What It Does
+## 🧠 What It Does
 
 Pi already has compaction for long sessions. That solves "this conversation is too long"; it does not solve "a new session forgot my preferences, project conventions, prior decisions, and unresolved todos."
 
@@ -21,14 +25,15 @@ durable facts -> MEMORY.md -> derived vector index -> per-turn Preflight recall
 
 It provides:
 
-- **Explicit memory** through `/remember`.
-- **Automatic durable fact export** from Pi compaction.
-- **Shutdown queue recovery** for short or missed sessions.
-- **Per-turn private recall** before the main model runs.
-- **Human-editable storage** in Markdown, with vector search as a rebuildable index.
-- **Offline maintenance** for consolidation, dedupe, overflow handling, and queue draining.
+- ✍️ **Explicit memory** through `/remember`.
+- 🔁 **Automatic durable fact export** from Pi compaction.
+- 📥 **Shutdown queue recovery** for short or missed sessions.
+- 🔦 **Per-turn private recall** before the main model runs.
+- 📄 **Human-editable storage** in Markdown, with vector search as a rebuildable index.
+- 🔌 **Local UDS sidecar** for vector retrieval and reindexing, without opening an HTTP port.
+- ⏳ **Daemon-friendly maintenance**: shutdown enqueues metadata, while consolidation and queue draining can run offline.
 
-## Installation
+## 📦 Installation
 
 Requirements:
 
@@ -36,10 +41,10 @@ Requirements:
 - pnpm
 - Pi extension runtime packages supplied by Pi
 
-Install as a package in the Pi extension environment:
+Install from Pi:
 
 ```bash
-pnpm add @chendpoc/pi-memory
+pi install npm:@chendpoc/pi-memory
 ```
 
 For local development from this repository:
@@ -61,17 +66,29 @@ Enable the extension through Pi's extension loading mechanism. This package decl
 }
 ```
 
-Initialize memory explicitly when needed:
+### 🌱 Memory workspace (automatic)
+
+You usually **do not need to run `pi-memory init` manually**. The same bootstrap (`initializeMemoryWorkspace`) runs automatically and **never overwrites a non-empty `MEMORY.md`**:
+
+| When | What happens |
+| --- | --- |
+| **`pnpm install`** | `postinstall` runs `pi-memory init` (or a pre-build fallback) |
+| **First Pi session** | `session_start` → `MemoryStore.ensureInitialized()` |
+| **Manual (optional)** | `pi-memory init` |
+
+Run `pi-memory init` explicitly only when:
+
+- You set **`PI_MEMORY_AGENT_DIR`** after install (postinstall may have seeded the default path).
+- Install scripts were skipped (`--ignore-scripts` or corporate policy).
+- You want to bootstrap before opening Pi, or verify setup with `pi-memory status`.
 
 ```bash
-pi-memory init
+pi-memory init   # optional; see above
 ```
 
-Initialization never overwrites a non-empty `MEMORY.md`.
-
-## Why Choose `pi-memory`
+## ✨ Why Choose `pi-memory`
 
-### Agent Before / After
+### 🔄 Agent Before / After
 
 | Situation | Without `pi-memory` | With `pi-memory` |
 | --- | --- | --- |
@@ -82,18 +99,30 @@ Initialization never overwrites a non-empty `MEMORY.md`.
 | Vector sidecar is down | A hard dependency would break the turn. | Preflight silently falls back to Markdown or injects nothing; the model still runs. |
 | Memory grows | A file can become noisy and unbounded. | 150-line `MEMORY.md` cap, `auto-*.md` overflow, consolidate merge/dedupe. |
 
-### Key Advantages
+### 🌟 Key Advantages
 
-- **Markdown Ground Truth**: `MEMORY.md` and `auto-*.md` can be opened, reviewed, edited, grepped, copied, or versioned.
-- **Derived index, not hidden state**: `memory.vec.sqlite` can be deleted and rebuilt from Markdown.
-- **Preflight recall**: Memory is injected before the main model answers instead of hoping the model calls a search tool.
-- **Hot-path budget**: Default Preflight budget is **800ms**, with QueryIntent, sidecar query, and fallback all bounded.
-- **Protected user notes**: `/remember` writes `[user]` entries that consolidate must not remove or rewrite.
-- **Sidecar isolation**: embedding, vector scan, MMR, stats, and reindex run outside the extension process, while writes stay owned by `MemoryStore`.
-- **Subagent policy**: root sessions get Memory Cap + Episodic Preflight; subagents get Memory Cap only by default.
-- **Graceful fallback**: if sidecar recall is empty, timed out, or unavailable, the turn still runs.
+- 📓 **Markdown Ground Truth**: `MEMORY.md` and `auto-*.md` can be opened, reviewed, edited, grepped, copied, or versioned.
+- 🏗️ **Derived index, not hidden state**: `memory.vec.sqlite` can be deleted and rebuilt from Markdown.
+- 🔎 **Preflight recall**: Memory is injected before the main model answers instead of hoping the model calls a search tool.
+- ⏱️ **Hot-path budget**: Default Preflight budget is **800ms**, with QueryIntent, sidecar query, and fallback all bounded.
+- 🔒 **Protected user notes**: `/remember` writes `[user]` entries that consolidate must not remove or rewrite.
+- 🔗 **UDS, not HTTP**: the agent talks to the sidecar over `node:net` Unix domain sockets with JSONL frames, so there is no local HTTP server or port to secure.
+- 🏭 **Sidecar process isolation**: embedding, vector scan, MMR, stats, and reindex run in a spawned Node process, while writes stay owned by `MemoryStore`.
+- 💤 **Daemon-safe writes**: `session_shutdown` only appends metadata; heavier consolidation and shutdown-queue draining are intended for `pi-memory maintenance` or background scheduling.
+- 👥 **Subagent policy**: root sessions get Memory Cap + Episodic Preflight; subagents get Memory Cap only by default.
+- ☂️ **Graceful fallback**: if sidecar recall is empty, timed out, or unavailable, the turn still runs.
+
+### ⚙️ Runtime Choices
+
+| Choice | Why it matters |
+| --- | --- |
+| `MEMORY.md` as Ground Truth | Durable memory remains inspectable and editable instead of becoming opaque database state. |
+| UDS JSONL over `node:net` | Local IPC stays private to the machine, avoids HTTP ports, and keeps request/response framing simple. |
+| Spawned sidecar process | Vector query/reindex work is isolated from the Pi extension process; failures degrade to Markdown fallback. |
+| Offline `maintenance` job | Consolidation and shutdown-queue draining can run outside the interactive agent turn. |
+| Bounded Preflight | QueryIntent, sidecar query, cache, and fallback all share a tight latency budget. |
 
-### Comparison
+### ⚖️ Comparison
 
 `pi-memory` is not trying to be every memory system. The value is a specific Pi-native loop: Markdown ground truth, Preflight injection, sidecar retrieval, compaction export, and offline maintenance.
 
@@ -115,9 +144,9 @@ Where other systems are stronger:
 - Mem0: hosted multi-tenant memory API.
 - Letta: autonomous context repositories and sleep-time memory work.
 
-## How It Works
+## ⚙️ How It Works
 
-### Architecture
+### 🏗️ Architecture
 
 ```text
 Pi extension process
@@ -142,14 +171,14 @@ Pi extension process
   `- consolidate scheduler
        `- merge/dedupe -> rewrite Ground Truth -> reindex
 
-Sidecar process over UDS JSONL
+Sidecar process over UDS JSONL (`node:net`, no HTTP port)
   |- ping
   |- stats
   |- query: embed -> cosine scan -> MMR
   `- reindex: upsert chunks into memory.vec.sqlite
 ```
 
-### Read Path
+### 🔎 Read Path
 
 Root session:
 
@@ -174,7 +203,7 @@ Sidecar results
   -> if empty: no injection
 ```
 
-### Write Paths
+### ✍️ Write Paths
 
 | Path | Trigger | LLM? | Blocking? | Purpose |
 | --- | --- | --- | --- | --- |
@@ -183,7 +212,7 @@ Sidecar results
 | Shutdown Queue | `session_shutdown` + `pi-memory maintenance` | Only offline, when no compaction summary exists | No during shutdown | Recover facts from short or missed sessions |
 | Consolidate | overflow >= 12, 7 days, or daily cron | Optional | Offline/background | Dedupe, merge, prune obsolete todos |
 
-## Data And Memory Format
+## 💾 Data And Memory Format
 
 All artifacts live under one memory agent directory.
 
@@ -233,7 +262,7 @@ Rules:
 - Overflow entries spill to `auto-*.md`, with a pointer in `MEMORY.md`.
 - Vector chunks are derived from entries; by default long entries split beyond `PI_MEMORY_CHUNK_MAX_CHARS=512`.
 
-## Configuration
+## 🎛️ Configuration
 
 Optional env file locations are loaded in this order:
 
@@ -262,7 +291,7 @@ Common variables:
 
 See [`.env.example`](./.env.example) for the full list.
 
-### Embedders
+### 🛰️ Embedders
 
 | Embedder | Use When | Notes |
 | --- | --- | --- |
@@ -272,7 +301,7 @@ See [`.env.example`](./.env.example) for the full list.
 
 The Vector Index stores embedding provider, model, and dimension metadata. When they change, old chunks are cleared and rebuilt.
 
-## Commands
+## ⌨️ Commands
 
 Inside Pi:
 
@@ -284,11 +313,11 @@ Inside Pi:
 CLI:
 
 ```bash
-pi-memory init
 pi-memory status
 pi-memory maintenance --cron --verbose
 pi-memory consolidate --force --verbose
 pi-memory drain-shutdown-queue --verbose
+pi-memory init   # optional — usually automatic after install + first session
 ```
 
 `maintenance` is the recommended scheduler entrypoint:
@@ -304,7 +333,7 @@ Scheduler templates:
 - [`templates/consolidate.cmd.example`](./templates/consolidate.cmd.example)
 - [`templates/schtasks.example.txt`](./templates/schtasks.example.txt)
 
-## Diagnostics
+## 🩺 Diagnostics
 
 Use `/memory-status` or `pi-memory status` to inspect:
 
@@ -335,7 +364,7 @@ Use `PI_MEMORY_DEBUG=1` to log Preflight timings:
 }
 ```
 
-## Non-Goals
+## 🚫 Non-Goals
 
 - Replacing Pi compaction.
 - Replacing session search; use a dedicated session-search extension for old conversations.
@@ -344,7 +373,7 @@ Use `PI_MEMORY_DEBUG=1` to log Preflight timings:
 - Storing full chat transcripts as memory.
 - Adding multi-second reflection to every user turn.
 
-## Development
+## 🛠️ Development
 
 ```bash
 pnpm typecheck
@@ -354,12 +383,12 @@ pnpm build
 
 The sidecar IPC test opens a Unix domain socket. If it fails with `listen EPERM` inside a restricted sandbox, run the test in a normal local shell.
 
-## Docs
+## 📚 Docs
 
 - [Chinese README](./doc/README-zh.md)
 - [Roadmap](./doc/ROADMAP.md)
 - [UBIQUITOUS_LANGUAGE.md](./UBIQUITOUS_LANGUAGE.md) - domain glossary
 
-## License
+## 📜 License
 
 MIT

package/doc/README-zh.md

@@ -1,3 +1,7 @@
+<p align="center">
+  <img src="../assets/pi-memory-logo.png" alt="pi-memory logo" width="720" />
+</p>
+
 # @chendpoc/pi-memory
 
 <p align="center">
@@ -9,7 +13,7 @@ Pi coding agent 的跨 session 情景记忆扩展。
 
 `pi-memory` 给 Pi 增加一层本地、可审计的跨 session 记忆。它把长期事实保存在 **`MEMORY.md` 这个 Ground Truth** 里，把 `memory.vec.sqlite` 作为派生向量索引，并在主模型回答前通过 Preflight 注入相关的私有上下文。
 
-## 这个 Package 做什么
+## 🧠 这个 Package 做什么
 
 Pi 已经有长 session compaction，它解决的是“当前对话太长了怎么办”；但它不解决“新开 session 后忘记用户偏好、项目约定、历史决策和未完成 TODO”的问题。
 
@@ -21,14 +25,15 @@ Pi 已经有长 session compaction，它解决的是“当前对话太长了怎
 
 它提供：
 
-- 通过 `/remember` 写入显式记忆。
-- 从 Pi compaction 自动导出长期事实。
-- 用 Shutdown Queue 补捞短 session 或漏处理 session。
-- 在主模型运行前做每轮私有记忆召回。
-- 用 Markdown 保存人类可编辑的事实，向量搜索只是可重建索引。
-- 离线 maintenance 负责 consolidate、去重、overflow 处理和 queue drain。
+- ✍️ 通过 `/remember` 写入显式记忆。
+- 🔁 从 Pi compaction 自动导出长期事实。
+- 📥 用 Shutdown Queue 补捞短 session 或漏处理 session。
+- 🔦 在主模型运行前做每轮私有记忆召回。
+- 📄 用 Markdown 保存人类可编辑的事实，向量搜索只是可重建索引。
+- 🔌 通过本地 UDS sidecar 做向量召回和 reindex，不打开 HTTP 端口。
+- ⏳ daemon 友好的维护路径：shutdown 只追加元数据，consolidate 和 queue drain 可以离线执行。
 
-## 安装与启用
+## 📦 安装与启用
 
 要求：
 
@@ -36,10 +41,10 @@ Pi 已经有长 session compaction，它解决的是“当前对话太长了怎
 - pnpm
 - Pi 提供的 extension runtime packages
 
-在 Pi extension 环境中安装包：
+通过 Pi 安装：
 
 ```bash
-pnpm add @chendpoc/pi-memory
+pi install npm:@chendpoc/pi-memory
 ```
 
 从本仓库本地开发：
@@ -61,17 +66,29 @@ pnpm test
 }
 ```
 
-需要时可显式初始化记忆：
+### 🌱 记忆工作区（自动初始化）
+
+**大多数用户不需要手动运行 `pi-memory init`。** 同一套 bootstrap（`initializeMemoryWorkspace`）会自动执行，且**不会覆盖非空的 `MEMORY.md`**：
+
+| 时机 | 行为 |
+| --- | --- |
+| **`pnpm install`** | `postinstall` 执行 `pi-memory init`（或 pre-build 回退脚本） |
+| **首次 Pi session** | `session_start` → `MemoryStore.ensureInitialized()` |
+| **手动（可选）** | `pi-memory init` |
+
+仅在以下情况需要显式运行 `pi-memory init`：
+
+- 安装**之后**才设置 **`PI_MEMORY_AGENT_DIR`**（postinstall 可能已按默认路径初始化）。
+- 安装脚本被跳过（`--ignore-scripts` 或企业策略）。
+- 想在打开 Pi 之前先 bootstrap，或配合 `pi-memory status` 做排查。
 
 ```bash
-pi-memory init
+pi-memory init   # 可选；见上文
 ```
 
-初始化不会覆盖非空 `MEMORY.md`。
-
-## 为什么选择 `pi-memory`
+## ✨ 为什么选择 `pi-memory`
 
-### Agent 使用前后差异
+### 🔄 Agent 使用前后差异
 
 | 场景 | 未使用 `pi-memory` | 使用 `pi-memory` 后 |
 | --- | --- | --- |
@@ -82,18 +99,30 @@ pi-memory init
 | 向量 sidecar 不可用 | 如果是硬依赖，会直接影响对话。 | Preflight 静默回退到 Markdown 或空注入，主模型照常运行。 |
 | 记忆持续增长 | 文件容易变成无边界流水账。 | `MEMORY.md` 150 行上限，`auto-*.md` 溢出，consolidate 合并去重。 |
 
-### 核心优势
+### 🌟 核心优势
 
-- **Markdown Ground Truth**：`MEMORY.md` 和 `auto-*.md` 可以直接打开、审查、编辑、grep、复制或纳入版本控制。
-- **索引不是隐藏事实源**：`memory.vec.sqlite` 可以删除，并从 Markdown 重新构建。
-- **Preflight 召回**：记忆在主模型回答前注入，而不是依赖模型主动调用搜索工具。
-- **热路径有预算**：默认 Preflight 预算是 **800ms**，QueryIntent、sidecar query 和 fallback 都有边界。
-- **用户显式记忆受保护**：`/remember` 写入 `[user]` 条目，consolidate 不能删除或改写。
-- **Sidecar 隔离**：embedding、向量扫描、MMR、stats 和 reindex 在扩展进程外运行；写入仍由 `MemoryStore` 负责。
-- **Subagent 策略**：root session 跑 Memory Cap + Episodic Preflight；subagent 默认只拿 Memory Cap。
-- **优雅降级**：sidecar 召回为空、超时或不可用时，当前 turn 仍然继续。
+- 📓 **Markdown Ground Truth**：`MEMORY.md` 和 `auto-*.md` 可以直接打开、审查、编辑、grep、复制或纳入版本控制。
+- 🏗️ **索引不是隐藏事实源**：`memory.vec.sqlite` 可以删除，并从 Markdown 重新构建。
+- 🔎 **Preflight 召回**：记忆在主模型回答前注入，而不是依赖模型主动调用搜索工具。
+- ⏱️ **热路径有预算**：默认 Preflight 预算是 **800ms**，QueryIntent、sidecar query 和 fallback 都有边界。
+- 🔒 **用户显式记忆受保护**：`/remember` 写入 `[user]` 条目，consolidate 不能删除或改写。
+- 🔗 **UDS，不走 HTTP**：agent 通过 `node:net` Unix domain socket + JSONL frame 和 sidecar 通信，不需要本地 HTTP server，也没有额外端口暴露。
+- 🏭 **Sidecar 进程隔离**：embedding、向量扫描、MMR、stats 和 reindex 在独立 spawn 的 Node 进程中运行；写入仍由 `MemoryStore` 负责。
+- 💤 **daemon-safe 写入路径**：`session_shutdown` 只追加元数据；更重的 consolidate 和 shutdown-queue drain 交给 `pi-memory maintenance` 或后台调度。
+- 👥 **Subagent 策略**：root session 跑 Memory Cap + Episodic Preflight；subagent 默认只拿 Memory Cap。
+- ☂️ **优雅降级**：sidecar 召回为空、超时或不可用时，当前 turn 仍然继续。
+
+### ⚙️ Runtime 选择
+
+| 选择 | 为什么重要 |
+| --- | --- |
+| `MEMORY.md` 作为 Ground Truth | 长期记忆保持可审查、可编辑，而不是变成不透明数据库状态。 |
+| 基于 `node:net` 的 UDS JSONL | IPC 只在本机发生，避免 HTTP 端口，同时保持简单的 request/response frame。 |
+| spawn 独立 sidecar 进程 | 向量 query/reindex 与 Pi extension 进程隔离；失败时可降级到 Markdown fallback。 |
+| 离线 `maintenance` job | consolidate 和 shutdown-queue drain 可以在交互 turn 之外执行。 |
+| 有预算的 Preflight | QueryIntent、sidecar query、cache 和 fallback 都在明确延迟边界内运行。 |
 
-### 对比
+### ⚖️ 对比
 
 `pi-memory` 不试图成为所有 memory 系统的集合。它的价值是一个 Pi-native 闭环：Markdown ground truth、Preflight 注入、sidecar 检索、compaction export 和离线 maintenance。
 
@@ -115,9 +144,9 @@ pi-memory init
 - Mem0：托管多租户 memory API。
 - Letta：自主 context repository 和 sleep-time memory work。
 
-## 工作方式
+## ⚙️ 工作方式
 
-### 架构
+### 🏗️ 架构
 
 ```text
 Pi 扩展进程
@@ -142,14 +171,14 @@ Pi 扩展进程
   `- consolidate scheduler
        `- 合并/去重 -> 重写 Ground Truth -> reindex
 
-通过 UDS JSONL 通信的 Sidecar 进程
+通过 UDS JSONL 通信的 Sidecar 进程（`node:net`，不走 HTTP 端口）
   |- ping
   |- stats
   |- query: embed -> cosine scan -> MMR
   `- reindex: upsert chunks into memory.vec.sqlite
 ```
 
-### 读取路径
+### 🔎 读取路径
 
 Root session：
 
@@ -174,7 +203,7 @@ Sidecar 结果
   -> 仍为空：不注入
 ```
 
-### 写入路径
+### ✍️ 写入路径
 
 | 路径 | 触发 | LLM? | 是否阻塞 | 目的 |
 | --- | --- | --- | --- | --- |
@@ -183,7 +212,7 @@ Sidecar 结果
 | Shutdown Queue | `session_shutdown` + `pi-memory maintenance` | 仅离线且无 compaction summary 时 | shutdown 时不阻塞 | 补捞短 session 或漏处理事实 |
 | Consolidate | overflow >= 12、7 天或每日 cron | 可选 | 离线或后台 | 去重、合并、清理过期 TODO |
 
-## 数据和 MEMORY.md 格式
+## 💾 数据和 MEMORY.md 格式
 
 所有产物都放在同一个 memory agent directory 下。
 
@@ -233,7 +262,7 @@ Sidecar 结果
 - 溢出条目写入 `auto-*.md`，并在 `MEMORY.md` 留指针。
 - 向量 chunk 从条目派生；默认超过 `PI_MEMORY_CHUNK_MAX_CHARS=512` 的长条目会拆分。
 
-## 配置
+## 🎛️ 配置
 
 可选 env 文件按以下顺序加载：
 
@@ -262,7 +291,7 @@ Sidecar 结果
 
 完整列表见 [`.env.example`](../.env.example)。
 
-### Embedding Provider
+### 🛰️ Embedding Provider
 
 | Embedder | 适用场景 | 说明 |
 | --- | --- | --- |
@@ -272,7 +301,7 @@ Sidecar 结果
 
 Vector Index 会保存 embedding provider、model 和 dimension 元数据。配置变化时会清空旧 chunks 并重建。
 
-## 命令
+## ⌨️ 命令
 
 Pi 内部：
 
@@ -284,11 +313,11 @@ Pi 内部：
 CLI：
 
 ```bash
-pi-memory init
 pi-memory status
 pi-memory maintenance --cron --verbose
 pi-memory consolidate --force --verbose
 pi-memory drain-shutdown-queue --verbose
+pi-memory init   # 可选 — 安装后 + 首次 session 通常已自动完成
 ```
 
 `maintenance` 是推荐的调度入口：
@@ -304,7 +333,7 @@ consolidate -> drain-shutdown-queue
 - [`templates/consolidate.cmd.example`](../templates/consolidate.cmd.example)
 - [`templates/schtasks.example.txt`](../templates/schtasks.example.txt)
 
-## 诊断
+## 🩺 诊断
 
 使用 `/memory-status` 或 `pi-memory status` 检查：
 
@@ -335,7 +364,7 @@ consolidate -> drain-shutdown-queue
 }
 ```
 
-## 非目标
+## 🚫 非目标
 
 - 不替代 Pi compaction。
 - 不替代 session search；历史对话搜索应使用专门的 session-search 扩展。
@@ -344,7 +373,7 @@ consolidate -> drain-shutdown-queue
 - 不把完整聊天记录当作 memory 存储。
 - 不给每轮用户消息增加多秒级 reflection。
 
-## 开发
+## 🛠️ 开发
 
 ```bash
 pnpm typecheck
@@ -354,12 +383,12 @@ pnpm build
 
 sidecar IPC 测试会打开 Unix domain socket。如果在受限沙盒中因为 `listen EPERM` 失败，请在正常本地 shell 中运行。
 
-## 文档
+## 📚 文档
 
 - [English README](../README.md)
 - [路线图](./ROADMAP-zh.md)
 - [UBIQUITOUS_LANGUAGE.md](../UBIQUITOUS_LANGUAGE.md) - 领域术语表
 
-## 许可证
+## 📜 许可证
 
 MIT

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chendpoc/pi-memory",
-  "version": "0.2.1",
+  "version": "0.2.2",
   "description": "Cross-session episodic memory for Pi agent — MEMORY.md ground truth, JSONL sidecar retrieval, and Preflight injection",
   "type": "module",
   "main": "./dist/index.js",
@@ -44,6 +44,7 @@
     "scripts/init-memory-workspace.mjs",
     "scripts/platform-fs.mjs",
     "scripts/postinstall.mjs",
+    "assets/pi-memory-logo.png",
     "README.md",
     "doc/README-zh.md",
     "doc/ROADMAP.md",