# Pitfall Log / 踩坑日志

项目：amitpatole/verel

摘要：发现 25 个潜在踩坑项，其中 1 个为 high/blocking；最高优先级：安全/权限坑 - 失败模式：security_permissions: verel doctor: report installed extras and key presence。

## 1. 安全/权限坑 · 失败模式：security_permissions: verel doctor: report installed extras and key presence

- 严重度：high
- 证据强度：source_linked
- 发现：Developers should check this security_permissions risk before relying on the project: verel doctor: report installed extras and key presence
- 对用户的影响：Developers may expose sensitive permissions or credentials: verel doctor: report installed extras and key presence
- 证据：failure_mode_cluster:github_issue | https://github.com/amitpatole/verel/issues/2 | verel doctor: report installed extras and key presence

## 2. 安装坑 · 失败模式：installation: Add a Rust toolchain (cargo test + clippy) to the CI graders

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: Add a Rust toolchain (cargo test + clippy) to the CI graders
- 对用户的影响：Developers may fail before the first successful local run: Add a Rust toolchain (cargo test + clippy) to the CI graders
- 证据：failure_mode_cluster:github_issue | https://github.com/amitpatole/verel/issues/1 | Add a Rust toolchain (cargo test + clippy) to the CI graders

## 3. 安装坑 · 失败模式：installation: v0.28.0 — quorum reads: a point read survives the leader being down

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: v0.28.0 — quorum reads: a point read survives the leader being down
- 对用户的影响：Upgrade or migration may change expected behavior: v0.28.0 — quorum reads: a point read survives the leader being down
- 证据：failure_mode_cluster:github_release | https://github.com/amitpatole/verel/releases/tag/v0.28.0 | v0.28.0 — quorum reads: a point read survives the leader being down

## 4. 安装坑 · 失败模式：installation: v0.29.0 — security hardening: full attack-surface audit + red-team

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: v0.29.0 — security hardening: full attack-surface audit + red-team
- 对用户的影响：Upgrade or migration may change expected behavior: v0.29.0 — security hardening: full attack-surface audit + red-team
- 证据：failure_mode_cluster:github_release | https://github.com/amitpatole/verel/releases/tag/v0.29.0 | v0.29.0 — security hardening: full attack-surface audit + red-team

## 5. 安装坑 · 失败模式：installation: v0.29.1 — security: 3-round adversarial red-team

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: v0.29.1 — security: 3-round adversarial red-team
- 对用户的影响：Upgrade or migration may change expected behavior: v0.29.1 — security: 3-round adversarial red-team
- 证据：failure_mode_cluster:github_release | https://github.com/amitpatole/verel/releases/tag/v0.29.1 | v0.29.1 — security: 3-round adversarial red-team

## 6. 安装坑 · 失败模式：installation: v0.29.2 — CI fix for the v0.29.1 security release

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: v0.29.2 — CI fix for the v0.29.1 security release
- 对用户的影响：Upgrade or migration may change expected behavior: v0.29.2 — CI fix for the v0.29.1 security release
- 证据：failure_mode_cluster:github_release | https://github.com/amitpatole/verel/releases/tag/v0.29.2 | v0.29.2 — CI fix for the v0.29.1 security release

## 7. 安装坑 · 失败模式：installation: v0.30.0 — the verification substrate

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

## 8. 安装坑 · 失败模式：installation: v0.31.0 — the shared verified brain

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

## 9. 安装坑 · 失败模式：installation: v0.32.0 — the authenticated multi-principal brain

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: v0.32.0 — the authenticated multi-principal brain
- 对用户的影响：Upgrade or migration may change expected behavior: v0.32.0 — the authenticated multi-principal brain
- 证据：failure_mode_cluster:github_release | https://github.com/amitpatole/verel/releases/tag/v0.32.0 | v0.32.0 — the authenticated multi-principal brain

## 10. 安装坑 · 失败模式：installation: v0.34.0 — cross-principal verified tier (fact-bound attestation)

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: v0.34.0 — cross-principal verified tier (fact-bound attestation)
- 对用户的影响：Upgrade or migration may change expected behavior: v0.34.0 — cross-principal verified tier (fact-bound attestation)
- 证据：failure_mode_cluster:github_release | https://github.com/amitpatole/verel/releases/tag/v0.34.0 | v0.34.0 — cross-principal verified tier (fact-bound attestation)

## 11. 安装坑 · 失败模式：installation: v0.35.0 — MCP recall/remember over a remote authenticated brain

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: v0.35.0 — MCP recall/remember over a remote authenticated brain
- 对用户的影响：Upgrade or migration may change expected behavior: v0.35.0 — MCP recall/remember over a remote authenticated brain
- 证据：failure_mode_cluster:github_release | https://github.com/amitpatole/verel/releases/tag/v0.35.0 | v0.35.0 — MCP recall/remember over a remote authenticated brain

## 12. 安装坑 · 来源证据：Add a Rust toolchain (cargo test + clippy) to the CI graders

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Add a Rust toolchain (cargo test + clippy) to the CI graders
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/amitpatole/verel/issues/1 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 13. 安装坑 · 来源证据：Broaden grader-parser test coverage with more real tool-output samples

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Broaden grader-parser test coverage with more real tool-output samples
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/amitpatole/verel/issues/3 | 来源讨论提到 npm 相关条件，需在安装/试用前复核。

## 14. 安装坑 · 来源证据：verel doctor: report installed extras and key presence

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：verel doctor: report installed extras and key presence
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/amitpatole/verel/issues/2 | 来源类型 github_issue 暴露的待验证使用条件。

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

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

## 16. 配置坑 · 失败模式：configuration: v0.36.0 — TLS for routable brain/lease/registry binds

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: v0.36.0 — TLS for routable brain/lease/registry binds
- 对用户的影响：Upgrade or migration may change expected behavior: v0.36.0 — TLS for routable brain/lease/registry binds
- 证据：failure_mode_cluster:github_release | https://github.com/amitpatole/verel/releases/tag/v0.36.0 | v0.36.0 — TLS for routable brain/lease/registry binds

## 17. 能力坑 · 来源证据：Docs: add a 'gate a monorepo with per-package stages' recipe

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个能力理解相关的待验证问题：Docs: add a 'gate a monorepo with per-package stages' recipe
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/amitpatole/verel/issues/4 | 来源类型 github_issue 暴露的待验证使用条件。

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

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

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

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

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

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

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

## 22. 能力坑 · 失败模式：conceptual: Broaden grader-parser test coverage with more real tool-output samples

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this conceptual risk before relying on the project: Broaden grader-parser test coverage with more real tool-output samples
- 对用户的影响：Developers may hit a documented source-backed failure mode: Broaden grader-parser test coverage with more real tool-output samples
- 证据：failure_mode_cluster:github_issue | https://github.com/amitpatole/verel/issues/3 | Broaden grader-parser test coverage with more real tool-output samples

## 23. 能力坑 · 失败模式：conceptual: Docs: add a 'gate a monorepo with per-package stages' recipe

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this conceptual risk before relying on the project: Docs: add a 'gate a monorepo with per-package stages' recipe
- 对用户的影响：Developers may hit a documented source-backed failure mode: Docs: add a 'gate a monorepo with per-package stages' recipe
- 证据：failure_mode_cluster:github_issue | https://github.com/amitpatole/verel/issues/4 | Docs: add a 'gate a monorepo with per-package stages' recipe

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

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

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

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