# Pitfall Log / 踩坑日志

项目：andrii-su/datoon

摘要：发现 25 个潜在踩坑项，其中 0 个为 high/blocking；最高优先级：配置坑 - 可能修改宿主 AI 配置。

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

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

## 2. 配置坑 · 失败模式：configuration: Token estimate uses cl100k_base, not the tokenizer of target models

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: Token estimate uses cl100k_base, not the tokenizer of target models
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: Token estimate uses cl100k_base, not the tokenizer of target models
- 证据：failure_mode_cluster:github_issue | https://github.com/andrii-su/datoon/issues/42 | Token estimate uses cl100k_base, not the tokenizer of target models

## 3. 配置坑 · 失败模式：configuration: v1.9.0

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

## 4. 配置坑 · 来源证据：Unify reader error taxonomy (ValueError vs DatoonError)

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：Unify reader error taxonomy (ValueError vs DatoonError)
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/andrii-su/datoon/issues/41 | 来源类型 github_issue 暴露的待验证使用条件。

## 5. 配置坑 · 来源证据：YAML reader does not validate that list items are objects

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：YAML reader does not validate that list items are objects
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/andrii-su/datoon/issues/43 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

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

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

## 7. 维护坑 · 失败模式：migration: cli.py imports Sequence from typing (deprecated alias)

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this migration risk before relying on the project: cli.py imports Sequence from typing (deprecated alias)
- 对用户的影响：Developers may hit a documented source-backed failure mode: cli.py imports Sequence from typing (deprecated alias)
- 证据：failure_mode_cluster:github_issue | https://github.com/andrii-su/datoon/issues/44 | cli.py imports Sequence from typing (deprecated alias)

## 8. 维护坑 · 来源证据：cli.py imports Sequence from typing (deprecated alias)

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个维护/版本相关的待验证问题：cli.py imports Sequence from typing (deprecated alias)
- 对用户的影响：可能影响升级、迁移或版本选择。
- 证据：community_evidence:github | https://github.com/andrii-su/datoon/issues/44 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

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

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

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

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

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

## 12. 安全/权限坑 · 来源证据：Token estimate uses cl100k_base, not the tokenizer of target models

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Token estimate uses cl100k_base, not the tokenizer of target models
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/andrii-su/datoon/issues/42 | 来源类型 github_issue 暴露的待验证使用条件。

## 13. 能力坑 · 失败模式：capability: YAML reader does not validate that list items are objects

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: YAML reader does not validate that list items are objects
- 对用户的影响：Developers may hit a documented source-backed failure mode: YAML reader does not validate that list items are objects
- 证据：failure_mode_cluster:github_issue | https://github.com/andrii-su/datoon/issues/43 | YAML reader does not validate that list items are objects

## 14. 能力坑 · 失败模式：conceptual: Unify reader error taxonomy (ValueError vs DatoonError)

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this conceptual risk before relying on the project: Unify reader error taxonomy (ValueError vs DatoonError)
- 对用户的影响：Developers may hit a documented source-backed failure mode: Unify reader error taxonomy (ValueError vs DatoonError)
- 证据：failure_mode_cluster:github_issue | https://github.com/andrii-su/datoon/issues/41 | Unify reader error taxonomy (ValueError vs DatoonError)

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

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

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

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

## 17. 维护坑 · 失败模式：maintenance: v1.5.0

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

## 18. 维护坑 · 失败模式：maintenance: v1.6.0

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

## 19. 维护坑 · 失败模式：maintenance: v1.7.0

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

## 20. 维护坑 · 失败模式：maintenance: v1.7.1

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

## 21. 维护坑 · 失败模式：maintenance: v1.7.2

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

## 22. 维护坑 · 失败模式：maintenance: v1.7.3

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

## 23. 维护坑 · 失败模式：maintenance: v1.7.4

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

## 24. 维护坑 · 失败模式：maintenance: v1.8.0

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

## 25. 维护坑 · 失败模式：maintenance: v1.9.1

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