# Pitfall Log / 踩坑日志

项目：n0mad-ai/bastra-recall

摘要：发现 32 个潜在踩坑项，其中 1 个为 high/blocking；最高优先级：安全/权限坑 - 来源证据：Vault self-audit surfaced as Markdown in the vault (Obsidian as the viewer) — conflicts, demand-gaps, dangling。

## 1. 安全/权限坑 · 来源证据：Vault self-audit surfaced as Markdown in the vault (Obsidian as the viewer) — conflicts, demand-gaps, dangling

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Vault self-audit surfaced as Markdown in the vault (Obsidian as the viewer) — conflicts, demand-gaps, dangling
- 对用户的影响：可能阻塞安装或首次运行。
- 证据：community_evidence:github | https://github.com/n0mad-ai/bastra-recall/issues/140 | 来源讨论提到 node 相关条件，需在安装/试用前复核。

## 2. 安装坑 · 失败模式：installation: brew install fails on untrusted tap — docs and Install.command miss the new 'brew trust' step

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: brew install fails on untrusted tap — docs and Install.command miss the new 'brew trust' step
- 对用户的影响：Developers may fail before the first successful local run: brew install fails on untrusted tap — docs and Install.command miss the new 'brew trust' step
- 证据：failure_mode_cluster:github_issue | https://github.com/n0mad-ai/bastra-recall/issues/182 | brew install fails on untrusted tap — docs and Install.command miss the new 'brew trust' step

## 3. 安装坑 · 失败模式：installation: homebrew formula build fails — builds only the daemon workspace, core/statusline dist missing...

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: homebrew formula build fails — builds only the daemon workspace, core/statusline dist missing from the tarball
- 对用户的影响：Developers may fail before the first successful local run: homebrew formula build fails — builds only the daemon workspace, core/statusline dist missing from the tarball
- 证据：failure_mode_cluster:github_issue | https://github.com/n0mad-ai/bastra-recall/issues/184 | homebrew formula build fails — builds only the daemon workspace, core/statusline dist missing from the tarball

## 4. 安装坑 · 失败模式：installation: install via npx registers the forwarder path inside the ephemeral npx cache

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: install via npx registers the forwarder path inside the ephemeral npx cache
- 对用户的影响：Developers may fail before the first successful local run: install via npx registers the forwarder path inside the ephemeral npx cache
- 证据：failure_mode_cluster:github_issue | https://github.com/n0mad-ai/bastra-recall/issues/180 | install via npx registers the forwarder path inside the ephemeral npx cache

## 5. 安装坑 · 失败模式：installation: install: first-run wall — 'vault path required' error instead of a guided vault choice

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: install: first-run wall — 'vault path required' error instead of a guided vault choice
- 对用户的影响：Developers may fail before the first successful local run: install: first-run wall — 'vault path required' error instead of a guided vault choice
- 证据：failure_mode_cluster:github_issue | https://github.com/n0mad-ai/bastra-recall/issues/178 | install: first-run wall — 'vault path required' error instead of a guided vault choice

## 6. 安装坑 · 失败模式：installation: test: verify the Ollama fresh-install (brew) path on a clean macOS env

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: test: verify the Ollama fresh-install (brew) path on a clean macOS env
- 对用户的影响：Developers may fail before the first successful local run: test: verify the Ollama fresh-install (brew) path on a clean macOS env
- 证据：failure_mode_cluster:github_issue | https://github.com/n0mad-ai/bastra-recall/issues/90 | test: verify the Ollama fresh-install (brew) path on a clean macOS env

## 7. 安装坑 · 失败模式：installation: uninstall all: skill kept as 'shared with Claude Desktop' although Desktop was uninstalled in...

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: uninstall all: skill kept as 'shared with Claude Desktop' although Desktop was uninstalled in the same run
- 对用户的影响：Developers may fail before the first successful local run: uninstall all: skill kept as 'shared with Claude Desktop' although Desktop was uninstalled in the same run
- 证据：failure_mode_cluster:github_issue | https://github.com/n0mad-ai/bastra-recall/issues/181 | uninstall all: skill kept as 'shared with Claude Desktop' although Desktop was uninstalled in the same run

## 8. 安装坑 · 失败模式：installation: v0.6.0-beta.1

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

## 9. 安装坑 · 失败模式：installation: v0.6.5-beta.1

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

## 10. 安装坑 · 失败模式：installation: v0.6.6-beta.1

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

## 11. 安装坑 · 失败模式：installation: v0.7.0-beta.3

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

## 12. 安装坑 · 失败模式：installation: v0.7.0-beta.5 — guided install + lifecycle wave C

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: v0.7.0-beta.5 — guided install + lifecycle wave C
- 对用户的影响：Upgrade or migration may change expected behavior: v0.7.0-beta.5 — guided install + lifecycle wave C
- 证据：failure_mode_cluster:github_release | https://github.com/n0mad-ai/bastra-recall/releases/tag/v0.7.0-beta.5 | v0.7.0-beta.5 — guided install + lifecycle wave C

## 13. 安装坑 · 来源证据：brew install fails on untrusted tap — docs and Install.command miss the new 'brew trust' step

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：brew install fails on untrusted tap — docs and Install.command miss the new 'brew trust' step
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/n0mad-ai/bastra-recall/issues/182 | 来源类型 github_issue 暴露的待验证使用条件。

## 14. 安装坑 · 来源证据：homebrew formula build fails — builds only the daemon workspace, core/statusline dist missing from the tarball

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：homebrew formula build fails — builds only the daemon workspace, core/statusline dist missing from the tarball
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/n0mad-ai/bastra-recall/issues/184 | 来源讨论提到 node 相关条件，需在安装/试用前复核。

## 15. 安装坑 · 来源证据：install via npx registers the forwarder path inside the ephemeral npx cache

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：install via npx registers the forwarder path inside the ephemeral npx cache
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/n0mad-ai/bastra-recall/issues/180 | 来源讨论提到 node 相关条件，需在安装/试用前复核。

## 16. 安装坑 · 来源证据：install: first-run wall — 'vault path required' error instead of a guided vault choice

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：install: first-run wall — 'vault path required' error instead of a guided vault choice
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/n0mad-ai/bastra-recall/issues/178 | 来源讨论提到 npm 相关条件，需在安装/试用前复核。

## 17. 安装坑 · 来源证据：test: verify the Ollama fresh-install (brew) path on a clean macOS env

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：test: verify the Ollama fresh-install (brew) path on a clean macOS env
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/n0mad-ai/bastra-recall/issues/90 | 来源讨论提到 npm 相关条件，需在安装/试用前复核。

## 18. 安装坑 · 来源证据：uninstall all: skill kept as 'shared with Claude Desktop' although Desktop was uninstalled in the same run

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：uninstall all: skill kept as 'shared with Claude Desktop' although Desktop was uninstalled in the same run
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/n0mad-ai/bastra-recall/issues/181 | 来源类型 github_issue 暴露的待验证使用条件。

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

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

## 20. 配置坑 · 失败模式：configuration: Vault self-audit surfaced as Markdown in the vault (Obsidian as the viewer) — conflicts, dema...

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: Vault self-audit surfaced as Markdown in the vault (Obsidian as the viewer) — conflicts, demand-gaps, dangling
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: Vault self-audit surfaced as Markdown in the vault (Obsidian as the viewer) — conflicts, demand-gaps, dangling
- 证据：failure_mode_cluster:github_issue | https://github.com/n0mad-ai/bastra-recall/issues/140 | Vault self-audit surfaced as Markdown in the vault (Obsidian as the viewer) — conflicts, demand-gaps, dangling

## 21. 配置坑 · 失败模式：configuration: curator phase A: deterministic usage-driven staleness pass (score-only, idle-gated)

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: curator phase A: deterministic usage-driven staleness pass (score-only, idle-gated)
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: curator phase A: deterministic usage-driven staleness pass (score-only, idle-gated)
- 证据：failure_mode_cluster:github_issue | https://github.com/n0mad-ai/bastra-recall/issues/155 | curator phase A: deterministic usage-driven staleness pass (score-only, idle-gated)

## 22. 配置坑 · 失败模式：configuration: telemetry: per-memory usage sidecar — append-only aggregate of surfaced/loaded/acted_on

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: telemetry: per-memory usage sidecar — append-only aggregate of surfaced/loaded/acted_on
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: telemetry: per-memory usage sidecar — append-only aggregate of surfaced/loaded/acted_on
- 证据：failure_mode_cluster:github_issue | https://github.com/n0mad-ai/bastra-recall/issues/154 | telemetry: per-memory usage sidecar — append-only aggregate of surfaced/loaded/acted_on

## 23. 配置坑 · 失败模式：configuration: v0.7.0-beta.1 — Recall that proves itself

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: v0.7.0-beta.1 — Recall that proves itself
- 对用户的影响：Upgrade or migration may change expected behavior: v0.7.0-beta.1 — Recall that proves itself
- 证据：failure_mode_cluster:github_release | https://github.com/n0mad-ai/bastra-recall/releases/tag/v0.7.0-beta.1 | v0.7.0-beta.1 — Recall that proves itself

## 24. 配置坑 · 失败模式：configuration: v0.7.0-beta.4

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

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

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

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

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

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

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

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

## 29. 安全/权限坑 · 来源证据：curator phase A: deterministic usage-driven staleness pass (score-only, idle-gated)

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：curator phase A: deterministic usage-driven staleness pass (score-only, idle-gated)
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/n0mad-ai/bastra-recall/issues/155 | 来源类型 github_issue 暴露的待验证使用条件。

## 30. 安全/权限坑 · 来源证据：telemetry: per-memory usage sidecar — append-only aggregate of surfaced/loaded/acted_on

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：telemetry: per-memory usage sidecar — append-only aggregate of surfaced/loaded/acted_on
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/n0mad-ai/bastra-recall/issues/154 | 来源类型 github_issue 暴露的待验证使用条件。

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

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

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

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