* docs(troubleshooting): document the two native-Windows integration traps
bd.exe is a native Windows binary, and two consequences of that are
undocumented. Both cost real debugging time because neither fails loudly.
- npm installs bd as a generated bd.cmd shim, so Node's execFile/spawn --
which run their target directly, without a shell -- never resolve it and
die with "spawn bd ENOENT" while bd works in the same terminal.
- Git Bash resolves /tmp to its own temp directory; bd, being native,
resolves it against the current drive root. `bd export -o /tmp/x.jsonl`
reports success and writes C:\tmp\x.jsonl.
Adds a subsection for each under Platform-Specific Issues, following the
symptom/solution shape already used there, plus cross-links from the FAQ
Windows entry and the installation Windows notes.
Agent-Signature: claude-code-claude-opus-5[1m]-unknown-reasoning on behalf of CuongBPV
* Update troubleshooting for Windows `/tmp` path issues
Clarify behavior of `/tmp` paths in Git Bash and provide solutions for Windows path handling.
* Update FAQ for Windows integration details
Clarify integration details regarding `bd.exe` and `/tmp` paths in Windows.
---------
Co-authored-by: CuongBPV <cuongbpv@fpt.com>