Skip to content

03_PITFALL_LOG.md

Latest commit

 

History

History
29 lines (21 loc) · 1.56 KB

03_PITFALL_LOG.md

File metadata and controls

29 lines (21 loc) · 1.56 KB
Raw

Pitfall Log

Pitfall 1: Documented install path needs real verification

  • Symptom: Internal discovery recorded pip install heventure-search-mcp, but Doramagic has not yet verified runtime success for HughesCuit/heventure-search-mcp.
  • Likely cause: bootstrap_runtime_verification
  • How to verify: Run or inspect the current upstream install path for HughesCuit/heventure-search-mcp before public release.
  • Recovery step: Stop, inspect the pitfall source, and rerun only after the boundary is clear.
  • When to stop: Stop when license, tool permission, or host compatibility is unclear.
  • Source/evidence: https://github.com/HughesCuit/heventure-search-mcp

Doramagic Source Extract

Heventure Search MCP Pitfall Log

1. Documented install path is not runtime proof

  • Symptom: the agent assumes pip install heventure-search-mcp is enough and claims the tool is ready.
  • Likely cause: install path came from repository metadata or internal discovery, not from a fresh execution trace.
  • Check first: rerun the upstream quickstart or install command in isolation.
  • Recovery: mark the install path as documented-but-unverified until a smoke check passes.
  • Evidence: https://github.com/HughesCuit/heventure-search-mcp

2. Upstream docs may drift faster than cached pack evidence

  • Symptom: commands or environment assumptions no longer match the latest README.
  • Likely cause: the bootstrap artifact was generated from a snapshot, not a live repo clone.
  • Check first: compare upstream README, release notes, and issues.
  • Recovery: refresh the source cache before public release.