云服务部-叶林立
312bb2ba5a
从官方 Git 仓库导入 chandra447/pi-hermes-memory 在 tag v0.9.10 （df624056a2e8c68bc89ba0a81e1c120856ec9665，2026-10-02）的源码快照。 本次仅导入源码，尚未接入组合包：package.json、加载顺序、依赖与权限策略 均未改动。 - 原样导入 src/、tests/、docs/、scripts/、README、CHANGELOG、PLAN、 AGENTS 与 LICENSE；该快照共 156 个上游文件。 - 剔除嵌套 .git、上游 .github 工作流、.ralph/、.claude/、node_modules、 覆盖率与构建产物。 - 新增中文 UPSTREAM.md，记录来源，以及启用前必须完成的待决事项： 在 pi-compaction 之前注册加载顺序、better-sqlite3 版本与根 allowScripts 对齐、strip-ansi 解析确认。 - 说明选择 tag 而非 main 的原因：导入时上游 main 已领先至 24fcd8ad26fc27badb8d7dbaf8034645de07b893（2026-10-11），选 tag 是为 对应一个已发布、可复现的版本。 尚未接线。启用前还需反转 tests/extension-load.test.ts 中"不得加载 Hermes"的断言，并同步 pi-tool-search 分组、权限策略与文档。 验证：快照 156 个上游文件全部导入，目录内仅多出 UPSTREAM.md 一份； 已确认与上游 main 内容存在差异，证明取的是 tag 而非 main。
2.1 KiB
v0.6.6 Changelog
Bug Fixes
Fix legacy SQLite upgrade error: no such column: category
Some users upgrading from older versions had an existing sessions.db with a legacy
memories table that did not include v0.6 failure-memory columns. During schema init,
creating idx_memories_category failed and /memory-index-sessions crashed with:
❌ Session indexing failed: no such column: category
Fix:
- Added automatic legacy schema migration in
DatabaseManager - Detects missing
memoriescolumns and adds them idempotently:categoryfailure_reasontool_statecorrected_to
- Retries schema initialization after migration
- Added regression test:
should migrate legacy memories table without category column
v0.6.5 Changelog
Bug Fixes
Auto-review no longer blocks interactive chat (#10)
The background auto-review was awaiting pi.exec() inside the turn_end handler, which
blocked the chat from responding while the review subprocess ran. Fixed by making the
review subprocess fire-and-forget — the turn_end handler returns immediately, and the
subprocess completes asynchronously.
pi.exec()is no longer awaited — handler returns immediatelyreviewInProgressguard resets in.then()/.catch()callbacks- Overlapping reviews are still prevented by the guard
- Notifications are delivered via
.then()callback once the subprocess completes
Auto-review failures on Windows no longer show errors (#9)
On Windows git-bash, pi exec subprocesses could exit with code 1 producing
[hermes] auto-review failed (exit=1): unknown error messages every few turns. Fixed by
making auto-review truly best-effort — non-zero exit codes and spawn errors are silently
ignored.
- Suppressed error notifications for non-zero exit codes
- Suppressed error notifications for subprocess failures (timeout, signal, spawn)
- The next review cycle will retry automatically
Crash safety
- Snapshot-building code (
getBranch(), message parsing) is wrapped in a minimal try/catch to handle expired sessions gracefully - Early return resets
reviewInProgressguard to unblock future reviews