# Pitfall Log / 踩坑日志

项目：jomkz/second-brain-joplin

摘要：发现 32 个潜在踩坑项，其中 2 个为 high/blocking；最高优先级：安全/权限坑 - 失败模式：security_permissions: Add PR labeler workflow (actions/labeler)。

## 1. 安全/权限坑 · 失败模式：security_permissions: Add PR labeler workflow (actions/labeler)

- 严重度：high
- 证据强度：source_linked
- 发现：Developers should check this security_permissions risk before relying on the project: Add PR labeler workflow (actions/labeler)
- 对用户的影响：Developers may expose sensitive permissions or credentials: Add PR labeler workflow (actions/labeler)
- 证据：failure_mode_cluster:github_issue | https://github.com/jomkz/second-brain-joplin/issues/18 | Add PR labeler workflow (actions/labeler)

## 2. 安全/权限坑 · 失败模式：security_permissions: Set up CI pipeline (lint + test matrix)

- 严重度：high
- 证据强度：source_linked
- 发现：Developers should check this security_permissions risk before relying on the project: Set up CI pipeline (lint + test matrix)
- 对用户的影响：Developers may expose sensitive permissions or credentials: Set up CI pipeline (lint + test matrix)
- 证据：failure_mode_cluster:github_issue | https://github.com/jomkz/second-brain-joplin/issues/2 | Set up CI pipeline (lint + test matrix)

## 3. 安装坑 · 失败模式：installation: Bootstrap second-brain-joplin (v0.1)

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: Bootstrap second-brain-joplin (v0.1)
- 对用户的影响：Developers may fail before the first successful local run: Bootstrap second-brain-joplin (v0.1)
- 证据：failure_mode_cluster:github_issue | https://github.com/jomkz/second-brain-joplin/issues/1 | Bootstrap second-brain-joplin (v0.1)

## 4. 安装坑 · 来源证据：Bootstrap second-brain-joplin (v0.1)

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Bootstrap second-brain-joplin (v0.1)
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/jomkz/second-brain-joplin/issues/1 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 5. 安装坑 · 来源证据：Semantic search via embedding index (v0.3)

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Semantic search via embedding index (v0.3)
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/jomkz/second-brain-joplin/issues/9 | 来源类型 github_issue 暴露的待验证使用条件。

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

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

## 7. 配置坑 · 失败模式：configuration: Implement core read MCP tools (v0.2)

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: Implement core read MCP tools (v0.2)
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: Implement core read MCP tools (v0.2)
- 证据：failure_mode_cluster:github_issue | https://github.com/jomkz/second-brain-joplin/issues/4 | Implement core read MCP tools (v0.2)

## 8. 配置坑 · 失败模式：configuration: Implement package skeleton and stubbed MCP server

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: Implement package skeleton and stubbed MCP server
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: Implement package skeleton and stubbed MCP server
- 证据：failure_mode_cluster:github_issue | https://github.com/jomkz/second-brain-joplin/issues/3 | Implement package skeleton and stubbed MCP server

## 9. 配置坑 · 失败模式：configuration: PyPI publish, full docs, and Joplin templates (v1.0)

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: PyPI publish, full docs, and Joplin templates (v1.0)
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: PyPI publish, full docs, and Joplin templates (v1.0)
- 证据：failure_mode_cluster:github_issue | https://github.com/jomkz/second-brain-joplin/issues/11 | PyPI publish, full docs, and Joplin templates (v1.0)

## 10. 配置坑 · 来源证据：Tighten mypy toward strict and cover tests/

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个配置相关的待验证问题：Tighten mypy toward strict and cover tests/
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/jomkz/second-brain-joplin/issues/19 | 来源类型 github_issue 暴露的待验证使用条件。

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

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

## 12. 运行坑 · 来源证据：Implement joplin_read tool

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个运行相关的待验证问题：Implement joplin_read tool
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/jomkz/second-brain-joplin/issues/7 | 来源类型 github_issue 暴露的待验证使用条件。

## 13. 运行坑 · 来源证据：Implement joplin_search tool

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个运行相关的待验证问题：Implement joplin_search tool
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/jomkz/second-brain-joplin/issues/6 | 来源类型 github_issue 暴露的待验证使用条件。

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

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

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

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

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

## 17. 安全/权限坑 · 来源证据：Add PR labeler workflow (actions/labeler)

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Add PR labeler workflow (actions/labeler)
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/jomkz/second-brain-joplin/issues/18 | 来源类型 github_issue 暴露的待验证使用条件。

## 18. 安全/权限坑 · 来源证据：Implement core read MCP tools (v0.2)

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Implement core read MCP tools (v0.2)
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/jomkz/second-brain-joplin/issues/4 | 来源类型 github_issue 暴露的待验证使用条件。

## 19. 安全/权限坑 · 来源证据：Implement joplin_overview tool

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Implement joplin_overview tool
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/jomkz/second-brain-joplin/issues/5 | 来源类型 github_issue 暴露的待验证使用条件。

## 20. 安全/权限坑 · 来源证据：Implement package skeleton and stubbed MCP server

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Implement package skeleton and stubbed MCP server
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/jomkz/second-brain-joplin/issues/3 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 21. 安全/权限坑 · 来源证据：Publish package to PyPI (trusted publisher)

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Publish package to PyPI (trusted publisher)
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/jomkz/second-brain-joplin/issues/12 | 来源类型 github_issue 暴露的待验证使用条件。

## 22. 安全/权限坑 · 来源证据：Set up CI pipeline (lint + test matrix)

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Set up CI pipeline (lint + test matrix)
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/jomkz/second-brain-joplin/issues/2 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 23. 能力坑 · 失败模式：capability: Human-gated note creation (v0.4)

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: Human-gated note creation (v0.4)
- 对用户的影响：Developers may hit a documented source-backed failure mode: Human-gated note creation (v0.4)
- 证据：failure_mode_cluster:github_issue | https://github.com/jomkz/second-brain-joplin/issues/10 | Human-gated note creation (v0.4)

## 24. 能力坑 · 失败模式：capability: Implement joplin_overview tool

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: Implement joplin_overview tool
- 对用户的影响：Developers may hit a documented source-backed failure mode: Implement joplin_overview tool
- 证据：failure_mode_cluster:github_issue | https://github.com/jomkz/second-brain-joplin/issues/5 | Implement joplin_overview tool

## 25. 能力坑 · 失败模式：capability: Implement joplin_read tool

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: Implement joplin_read tool
- 对用户的影响：Developers may hit a documented source-backed failure mode: Implement joplin_read tool
- 证据：failure_mode_cluster:github_issue | https://github.com/jomkz/second-brain-joplin/issues/7 | Implement joplin_read tool

## 26. 能力坑 · 失败模式：capability: Implement joplin_recent tool

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: Implement joplin_recent tool
- 对用户的影响：Developers may hit a documented source-backed failure mode: Implement joplin_recent tool
- 证据：failure_mode_cluster:github_issue | https://github.com/jomkz/second-brain-joplin/issues/8 | Implement joplin_recent tool

## 27. 能力坑 · 失败模式：capability: Implement joplin_search tool

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: Implement joplin_search tool
- 对用户的影响：Developers may hit a documented source-backed failure mode: Implement joplin_search tool
- 证据：failure_mode_cluster:github_issue | https://github.com/jomkz/second-brain-joplin/issues/6 | Implement joplin_search tool

## 28. 能力坑 · 失败模式：capability: Semantic search via embedding index (v0.3)

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: Semantic search via embedding index (v0.3)
- 对用户的影响：Developers may hit a documented source-backed failure mode: Semantic search via embedding index (v0.3)
- 证据：failure_mode_cluster:github_issue | https://github.com/jomkz/second-brain-joplin/issues/9 | Semantic search via embedding index (v0.3)

## 29. 能力坑 · 失败模式：capability: Tighten mypy toward strict and cover tests/

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this capability risk before relying on the project: Tighten mypy toward strict and cover tests/
- 对用户的影响：Developers may hit a documented source-backed failure mode: Tighten mypy toward strict and cover tests/
- 证据：failure_mode_cluster:github_issue | https://github.com/jomkz/second-brain-joplin/issues/19 | Tighten mypy toward strict and cover tests/

## 30. 能力坑 · 失败模式：conceptual: Publish package to PyPI (trusted publisher)

- 严重度：low
- 证据强度：source_linked
- 发现：Developers should check this conceptual risk before relying on the project: Publish package to PyPI (trusted publisher)
- 对用户的影响：Developers may hit a documented source-backed failure mode: Publish package to PyPI (trusted publisher)
- 证据：failure_mode_cluster:github_issue | https://github.com/jomkz/second-brain-joplin/issues/12 | Publish package to PyPI (trusted publisher)

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

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

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

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