beads: ignore the JSONL exports
The Dolt companion is the sync layer for issues and their audit trail, so a
second copy riding in git buys nothing and costs a dirty status after every bd
write. The config half (config.yaml, metadata.json, hooks/) stays tracked, or
there is nothing for bd hooks install to install in a fresh clone.
bd: point the Dolt remote at dolt.srht.bigb.es and enable auto-push
bd init wrote the git URL into sync.remote, which Dolt cannot push to. Point
it at the companion database instead and turn on auto-push (30s debounce, 60s
timeout) so a bead created in a session does not sit only in the local store.