# Pitfall Log / 踩坑日志

项目：salishforge/memforge

摘要：发现 15 个潜在踩坑项，其中 0 个为 high/blocking；最高优先级：安装坑 - 失败模式：installation: v3.0.0-beta.3。

## 1. 安装坑 · 失败模式：installation: v3.0.0-beta.3

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: v3.0.0-beta.3
- 对用户的影响：Upgrade or migration may change expected behavior: v3.0.0-beta.3
- 证据：failure_mode_cluster:github_release | https://github.com/salishforge/memforge/releases/tag/v3.0.0-beta.3 | v3.0.0-beta.3

## 2. 安装坑 · 失败模式：installation: v3.0.0-beta.4

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: v3.0.0-beta.4
- 对用户的影响：Upgrade or migration may change expected behavior: v3.0.0-beta.4
- 证据：failure_mode_cluster:github_release | https://github.com/salishforge/memforge/releases/tag/v3.0.0-beta.4 | v3.0.0-beta.4

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

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

## 4. 配置坑 · 失败模式：configuration: MemForge v0.1.0-alpha

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

## 5. 配置坑 · 失败模式：configuration: v3.0.0-beta.2 — CI Green, Shared Memory, Full Test Coverage

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: v3.0.0-beta.2 — CI Green, Shared Memory, Full Test Coverage
- 对用户的影响：Upgrade or migration may change expected behavior: v3.0.0-beta.2 — CI Green, Shared Memory, Full Test Coverage
- 证据：failure_mode_cluster:github_release | https://github.com/salishforge/memforge/releases/tag/v3.0.0-beta.2 | v3.0.0-beta.2 — CI Green, Shared Memory, Full Test Coverage

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

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

## 7. 运行坑 · 来源证据：Python SDK: QueryResult dataclass rejects unknown response keys (breaks on v3.8+ fields)

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个运行相关的待验证问题：Python SDK: QueryResult dataclass rejects unknown response keys (breaks on v3.8+ fields)
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/salishforge/memforge/issues/161 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 8. 运行坑 · 来源证据：REST: /entities and /graph return 500 for invalid agent ids; OpenAPI query path missing epistemic param

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个运行相关的待验证问题：REST: /entities and /graph return 500 for invalid agent ids; OpenAPI query path missing epistemic param
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/salishforge/memforge/issues/162 | 来源类型 github_issue 暴露的待验证使用条件。

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

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

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

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

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

## 12. 运行坑 · 失败模式：performance: REST: /entities and /graph return 500 for invalid agent ids; OpenAPI query path missing epist...

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this performance risk before relying on the project: REST: /entities and /graph return 500 for invalid agent ids; OpenAPI query path missing epistemic param
- 对用户的影响：Developers may hit a documented source-backed failure mode: REST: /entities and /graph return 500 for invalid agent ids; OpenAPI query path missing epistemic param
- 证据：failure_mode_cluster:github_issue | https://github.com/salishforge/memforge/issues/162 | REST: /entities and /graph return 500 for invalid agent ids; OpenAPI query path missing epistemic param

## 13. 运行坑 · 失败模式：performance: v2.1.0-alpha — Architecture Complete

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this performance risk before relying on the project: v2.1.0-alpha — Architecture Complete
- 对用户的影响：Upgrade or migration may change expected behavior: v2.1.0-alpha — Architecture Complete
- 证据：failure_mode_cluster:github_release | https://github.com/salishforge/memforge/releases/tag/v2.1.0-alpha | v2.1.0-alpha — Architecture Complete

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

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

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

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