# Pitfall Log / 踩坑日志

项目：yantrikos/yantrikdb-server

摘要：发现 25 个潜在踩坑项，其中 1 个为 high/blocking；最高优先级：配置坑 - 来源证据：Design: idempotency_key on /v1/remember (+ batch per-item keys) — agreement-#4 shared-surface issue。

## 1. 配置坑 · 来源证据：Design: idempotency_key on /v1/remember (+ batch per-item keys) — agreement-#4 shared-surface issue

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：Design: idempotency_key on /v1/remember (+ batch per-item keys) — agreement-#4 shared-surface issue
- 对用户的影响：可能影响升级、迁移或版本选择。
- 证据：community_evidence:github | https://github.com/yantrikos/yantrikdb-server/issues/58 | 来源讨论提到 node 相关条件，需在安装/试用前复核。

## 2. 安装坑 · 依赖 Docker 环境

- 严重度：medium
- 证据强度：runtime_trace
- 发现：安装/运行入口包含 Docker 命令：docker run -p 7438:7438 ghcr.io/yantrikos/yantrikdb:latest curl -X POST http://localhost:7438/v1/remember
- 对用户的影响：非工程用户可能没有 Docker，启动成本明显增加。
- 复现命令：`docker run -p 7438:7438 ghcr.io/yantrikos/yantrikdb:latest curl -X POST http://localhost:7438/v1/remember`
- 证据：identity.distribution | https://github.com/yantrikos/yantrikdb-server | docker run -p 7438:7438 ghcr.io/yantrikos/yantrikdb:latest curl -X POST http://localhost:7438/v1/remember

## 3. 安装坑 · 失败模式：installation: python3.14 support missing.

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: python3.14 support missing.
- 对用户的影响：Developers may fail before the first successful local run: python3.14 support missing.
- 证据：failure_mode_cluster:github_issue | https://github.com/yantrikos/yantrikdb-server/issues/43 | python3.14 support missing.

## 4. 安装坑 · 来源证据：Peer-sync capability exchange: make oplog format-version downgrades explicit (follow-up to #52)

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Peer-sync capability exchange: make oplog format-version downgrades explicit (follow-up to #52)
- 对用户的影响：可能影响升级、迁移或版本选择。
- 证据：community_evidence:github | https://github.com/yantrikos/yantrikdb-server/issues/53 | 来源讨论提到 node 相关条件，需在安装/试用前复核。

## 5. 安装坑 · 来源证据：python3.14 support missing.

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：python3.14 support missing.
- 对用户的影响：可能阻塞安装或首次运行。
- 证据：community_evidence:github | https://github.com/yantrikos/yantrikdb-server/issues/43 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

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

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

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

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

## 8. 运行坑 · 运行可能依赖外部服务

- 严重度：medium
- 证据强度：source_linked
- 发现：项目说明出现 external service/cloud/webhook/database 等运行依赖关键词。
- 对用户的影响：本地安装成功不等于能力可用，外部服务不可用会阻断体验。
- 证据：packet_text.keyword_scan | https://github.com/yantrikos/yantrikdb-server | matched external service / cloud / webhook / database keyword

## 9. 维护坑 · 失败模式：migration: Design: idempotency_key on /v1/remember (+ batch per-item keys) — agreement-#4 shared-surface...

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this migration risk before relying on the project: Design: idempotency_key on /v1/remember (+ batch per-item keys) — agreement-#4 shared-surface issue
- 对用户的影响：Developers may hit a documented source-backed failure mode: Design: idempotency_key on /v1/remember (+ batch per-item keys) — agreement-#4 shared-surface issue
- 证据：failure_mode_cluster:github_issue | https://github.com/yantrikos/yantrikdb-server/issues/58 | Design: idempotency_key on /v1/remember (+ batch per-item keys) — agreement-#4 shared-surface issue

## 10. 维护坑 · 失败模式：migration: Peer-sync capability exchange: make oplog format-version downgrades explicit (follow-up to #52)

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this migration risk before relying on the project: Peer-sync capability exchange: make oplog format-version downgrades explicit (follow-up to #52)
- 对用户的影响：Developers may hit a documented source-backed failure mode: Peer-sync capability exchange: make oplog format-version downgrades explicit (follow-up to #52)
- 证据：failure_mode_cluster:github_issue | https://github.com/yantrikos/yantrikdb-server/issues/53 | Peer-sync capability exchange: make oplog format-version downgrades explicit (follow-up to #52)

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

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

- 严重度：medium
- 证据强度：source_linked
- 发现：no_demo
- 证据：downstream_validation.risk_items | https://github.com/yantrikos/yantrikdb-server | no_demo; severity=medium

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

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

## 14. 运行坑 · 失败模式：performance: v0.8.22

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this performance risk before relying on the project: v0.8.22
- 对用户的影响：Upgrade or migration may change expected behavior: v0.8.22
- 证据：failure_mode_cluster:github_release | https://github.com/yantrikos/yantrikdb-server/releases/tag/v0.8.22 | v0.8.22

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

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

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

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

## 17. 维护坑 · 失败模式：maintenance: v0.10.0

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: v0.10.0
- 对用户的影响：Upgrade or migration may change expected behavior: v0.10.0
- 证据：failure_mode_cluster:github_release | https://github.com/yantrikos/yantrikdb-server/releases/tag/v0.10.0 | v0.10.0

## 18. 维护坑 · 失败模式：maintenance: v0.8.19

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: v0.8.19
- 对用户的影响：Upgrade or migration may change expected behavior: v0.8.19
- 证据：failure_mode_cluster:github_release | https://github.com/yantrikos/yantrikdb-server/releases/tag/v0.8.19 | v0.8.19

## 19. 维护坑 · 失败模式：maintenance: v0.8.20

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: v0.8.20
- 对用户的影响：Upgrade or migration may change expected behavior: v0.8.20
- 证据：failure_mode_cluster:github_release | https://github.com/yantrikos/yantrikdb-server/releases/tag/v0.8.20 | v0.8.20

## 20. 维护坑 · 失败模式：maintenance: v0.8.21

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: v0.8.21
- 对用户的影响：Upgrade or migration may change expected behavior: v0.8.21
- 证据：failure_mode_cluster:github_release | https://github.com/yantrikos/yantrikdb-server/releases/tag/v0.8.21 | v0.8.21

## 21. 维护坑 · 失败模式：maintenance: v0.8.23

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: v0.8.23
- 对用户的影响：Upgrade or migration may change expected behavior: v0.8.23
- 证据：failure_mode_cluster:github_release | https://github.com/yantrikos/yantrikdb-server/releases/tag/v0.8.23 | v0.8.23

## 22. 维护坑 · 失败模式：maintenance: v0.8.24

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: v0.8.24
- 对用户的影响：Upgrade or migration may change expected behavior: v0.8.24
- 证据：failure_mode_cluster:github_release | https://github.com/yantrikos/yantrikdb-server/releases/tag/v0.8.24 | v0.8.24

## 23. 维护坑 · 失败模式：maintenance: v0.8.25

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: v0.8.25
- 对用户的影响：Upgrade or migration may change expected behavior: v0.8.25
- 证据：failure_mode_cluster:github_release | https://github.com/yantrikos/yantrikdb-server/releases/tag/v0.8.25 | v0.8.25

## 24. 维护坑 · 失败模式：maintenance: v0.8.26

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: v0.8.26
- 对用户的影响：Upgrade or migration may change expected behavior: v0.8.26
- 证据：failure_mode_cluster:github_release | https://github.com/yantrikos/yantrikdb-server/releases/tag/v0.8.26 | v0.8.26

## 25. 维护坑 · 失败模式：maintenance: v0.8.27

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this maintenance risk before relying on the project: v0.8.27
- 对用户的影响：Upgrade or migration may change expected behavior: v0.8.27
- 证据：failure_mode_cluster:github_release | https://github.com/yantrikos/yantrikdb-server/releases/tag/v0.8.27 | v0.8.27