# Pitfall Log / 踩坑日志

项目：h-wata/kioku-mesh

摘要：发现 23 个潜在踩坑项，其中 0 个为 high/blocking；最高优先级：安装坑 - 失败模式：installation: mesh-mem v0.2.4。

## 1. 安装坑 · 失败模式：installation: mesh-mem v0.2.4

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: mesh-mem v0.2.4
- 对用户的影响：Upgrade or migration may change expected behavior: mesh-mem v0.2.4
- 证据：failure_mode_cluster:github_release | https://github.com/h-wata/kioku-mesh/releases/tag/v0.2.4 | mesh-mem v0.2.4

## 2. 安装坑 · 失败模式：installation: mesh-mem v0.2.5

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: mesh-mem v0.2.5
- 对用户的影响：Upgrade or migration may change expected behavior: mesh-mem v0.2.5
- 证据：failure_mode_cluster:github_release | https://github.com/h-wata/kioku-mesh/releases/tag/v0.2.5 | mesh-mem v0.2.5

## 3. 安装坑 · 失败模式：installation: mesh-mem v0.3.0

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: mesh-mem v0.3.0
- 对用户的影响：Upgrade or migration may change expected behavior: mesh-mem v0.3.0
- 证据：failure_mode_cluster:github_release | https://github.com/h-wata/kioku-mesh/releases/tag/v0.3.0 | mesh-mem v0.3.0

## 4. 安装坑 · 失败模式：installation: v0.3.1

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: v0.3.1
- 对用户的影响：Upgrade or migration may change expected behavior: v0.3.1
- 证据：failure_mode_cluster:github_release | https://github.com/h-wata/kioku-mesh/releases/tag/v0.3.1 | v0.3.1

## 5. 安装坑 · 失败模式：installation: v0.3.2

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: v0.3.2
- 对用户的影响：Upgrade or migration may change expected behavior: v0.3.2
- 证据：failure_mode_cluster:github_release | https://github.com/h-wata/kioku-mesh/releases/tag/v0.3.2 | v0.3.2

## 6. 安装坑 · 失败模式：installation: v0.3.3

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: v0.3.3
- 对用户的影响：Upgrade or migration may change expected behavior: v0.3.3
- 证据：failure_mode_cluster:github_release | https://github.com/h-wata/kioku-mesh/releases/tag/v0.3.3 | v0.3.3

## 7. 安装坑 · 失败模式：installation: v0.4.0 — Mutual TLS for the mesh

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: v0.4.0 — Mutual TLS for the mesh
- 对用户的影响：Upgrade or migration may change expected behavior: v0.4.0 — Mutual TLS for the mesh
- 证据：failure_mode_cluster:github_release | https://github.com/h-wata/kioku-mesh/releases/tag/v0.4.0 | v0.4.0 — Mutual TLS for the mesh

## 8. 安装坑 · 来源证据：refactor: split store.py monolith before ADR-0019 visibility work

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：refactor: split store.py monolith before ADR-0019 visibility work
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/h-wata/kioku-mesh/issues/167 | 来源类型 github_issue 暴露的待验证使用条件。

## 9. 配置坑 · 可能修改宿主 AI 配置

- 严重度：medium
- 证据强度：source_linked
- 发现：项目面向 Claude/Cursor/Codex/Gemini/OpenCode 等宿主，或安装命令涉及用户配置目录。
- 对用户的影响：安装可能改变本机 AI 工具行为，用户需要知道写入位置和回滚方法。
- 证据：capability.host_targets | https://github.com/h-wata/kioku-mesh | host_targets=mcp_host, claude_code, claude, gemini_cli, codex

## 10. 配置坑 · 失败模式：configuration: design: hard authorization — mTLS cert subject ↔ Zenoh ACL for team/user scope (#185 follow-up)

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: design: hard authorization — mTLS cert subject ↔ Zenoh ACL for team/user scope (#185 follow-up)
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: design: hard authorization — mTLS cert subject ↔ Zenoh ACL for team/user scope (#185 follow-up)
- 证据：failure_mode_cluster:github_issue | https://github.com/h-wata/kioku-mesh/issues/191 | design: hard authorization — mTLS cert subject ↔ Zenoh ACL for team/user scope (#185 follow-up)

## 11. 配置坑 · 失败模式：configuration: feat(messaging): ADR-0022 messaging MVP の実装（direct 1:1 + MCP poll + TTL inbox spool）

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: feat(messaging): ADR-0022 messaging MVP の実装（direct 1:1 + MCP poll + TTL inbox spool）
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: feat(messaging): ADR-0022 messaging MVP の実装（direct 1:1 + MCP poll + TTL inbox spool）
- 证据：failure_mode_cluster:github_issue | https://github.com/h-wata/kioku-mesh/issues/185 | feat(messaging): ADR-0022 messaging MVP の実装（direct 1:1 + MCP poll + TTL inbox spool）

## 12. 配置坑 · 失败模式：configuration: v0.4.1

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: v0.4.1
- 对用户的影响：Upgrade or migration may change expected behavior: v0.4.1
- 证据：failure_mode_cluster:github_release | https://github.com/h-wata/kioku-mesh/releases/tag/v0.4.1 | v0.4.1

## 13. 配置坑 · 来源证据：refactor: パッケージ mesh_mem → kioku_mesh リネーム（ADR-0024）

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：refactor: パッケージ mesh_mem → kioku_mesh リネーム（ADR-0024）
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/h-wata/kioku-mesh/issues/187 | 来源类型 github_issue 暴露的待验证使用条件。

## 14. 能力坑 · 能力判断依赖假设

- 严重度：medium
- 证据强度：source_linked
- 发现：README/documentation is current enough for a first validation pass.
- 对用户的影响：假设不成立时，用户拿不到承诺的能力。
- 证据：capability.assumptions | https://github.com/h-wata/kioku-mesh | README/documentation is current enough for a first validation pass.

## 15. 维护坑 · 失败模式：migration: kioku-mesh v0.5.0

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this migration risk before relying on the project: kioku-mesh v0.5.0
- 对用户的影响：Upgrade or migration may change expected behavior: kioku-mesh v0.5.0
- 证据：failure_mode_cluster:github_release | https://github.com/h-wata/kioku-mesh/releases/tag/v0.5.0 | kioku-mesh v0.5.0

## 16. 维护坑 · 维护活跃度未知

- 严重度：medium
- 证据强度：source_linked
- 发现：未记录 last_activity_observed。
- 对用户的影响：新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。
- 证据：evidence.maintainer_signals | https://github.com/h-wata/kioku-mesh | last_activity_observed missing

- 严重度：medium
- 证据强度：source_linked
- 发现：no_demo
- 证据：downstream_validation.risk_items | https://github.com/h-wata/kioku-mesh | no_demo; severity=medium

## 18. 安全/权限坑 · 存在评分风险

- 严重度：medium
- 证据强度：source_linked
- 发现：no_demo
- 对用户的影响：风险会影响是否适合普通用户安装。
- 证据：risks.scoring_risks | https://github.com/h-wata/kioku-mesh | no_demo; severity=medium

## 19. 安全/权限坑 · 来源证据：design: hard authorization — mTLS cert subject ↔ Zenoh ACL for team/user scope (#185 follow-up)

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：design: hard authorization — mTLS cert subject ↔ Zenoh ACL for team/user scope (#185 follow-up)
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/h-wata/kioku-mesh/issues/191 | 来源类型 github_issue 暴露的待验证使用条件。

## 20. 能力坑 · 失败模式：conceptual: refactor: split store.py monolith before ADR-0019 visibility work

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this conceptual risk before relying on the project: refactor: split store.py monolith before ADR-0019 visibility work
- 对用户的影响：Developers may hit a documented source-backed failure mode: refactor: split store.py monolith before ADR-0019 visibility work
- 证据：failure_mode_cluster:github_issue | https://github.com/h-wata/kioku-mesh/issues/167 | refactor: split store.py monolith before ADR-0019 visibility work

## 21. 能力坑 · 失败模式：conceptual: refactor: パッケージ mesh_mem → kioku_mesh リネーム（ADR-0024）

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this conceptual risk before relying on the project: refactor: パッケージ mesh_mem → kioku_mesh リネーム（ADR-0024）
- 对用户的影响：Developers may hit a documented source-backed failure mode: refactor: パッケージ mesh_mem → kioku_mesh リネーム（ADR-0024）
- 证据：failure_mode_cluster:github_issue | https://github.com/h-wata/kioku-mesh/issues/187 | refactor: パッケージ mesh_mem → kioku_mesh リネーム（ADR-0024）

## 22. 维护坑 · issue/PR 响应质量未知

- 严重度：low
- 证据强度：source_linked
- 发现：issue_or_pr_quality=unknown。
- 对用户的影响：用户无法判断遇到问题后是否有人维护。
- 证据：evidence.maintainer_signals | https://github.com/h-wata/kioku-mesh | issue_or_pr_quality=unknown

## 23. 维护坑 · 发布节奏不明确

- 严重度：low
- 证据强度：source_linked
- 发现：release_recency=unknown。
- 对用户的影响：安装命令和文档可能落后于代码，用户踩坑概率升高。
- 证据：evidence.maintainer_signals | https://github.com/h-wata/kioku-mesh | release_recency=unknown