boost report shows "No tracking data yet" despite active writes to history.db-wal

[zivziv123]

Environment

• boost v0.8.4
• Windows 11, Git Bash (MSYS)
• Claude Code, hooks wired via boost init (PreToolUse rewrite + Stop sync)

Bug

boost report --days 0 always prints "No tracking data yet. Run some boost commands to start." — even after confirming the tracking pipeline is active.

Steps to reproduce

1. boost init wires PreToolUse hook that pipes commands through | boost.
2. Ran several commands through the wrapped pipeline; confirmed via manual hook invocation that boost rewrite <cmd> correctly wraps commands with BOOST_HOOK_META and pipes through boost.
3. Confirmed ~/AppData/Local/boost/history.db-wal mtime updates live with each wrapped command (writes are happening).
4. boost report (and boost report --days 0, and with BOOST_DB_PATH explicitly pointed at the same db file) still reports no data.

Also found

Separately, our hook install had a silent failure mode worth flagging: boost-rewrite.sh requires jq; if jq isn't found on PATH (checked only in hardcoded chocolatey/git-bash paths), it prints one stderr warning and exits 0 — silently disabling all rewriting for the whole session with no persistent/visible indication. Might be worth a louder one-time warning or boost report/boost update health check flagging "hooks not active."

Expected

boost report should reflect the WAL data being written.

[menachemm-byte]

Hi @zivziv123,
Thanks for reporting the issue