beads · Issues· 1208 open

bd init under $TMPDIR silently plants the embedded store at the OS temp root's own .beads instead of the target directory

is_blocked: a sub-epic close-gated under an exogenously blocked epic keeps its children visible (follow-up to #6506)

bd doctor: Phantom Databases check false-positives on shared-server mode's own beads_global database

dolt.user in config is ignored, so any caller without BEADS_DOLT_SERVER_USER authenticates as root

dolt_ignore'd tables with live dirty content have no loss-free recovery path when a pending ignored-source migration touches them (embedded and server mode)

init --reinit-local preflight: count errors silently skip the destroy confirmation, and the counted DB can differ from the gated DB

Proposal: Memory Beads

bd update --notes "" wipes the notes field at exit 0 with a success receipt; --allow-empty-description has no --allow-empty-notes counterpart

bd update --notes help reads as additive while the flag replaces the field

CompareVersions sorts a prerelease ABOVE its own stable release (1.3.1-rc.1 > 1.3.1), so rc users are never nudged back

bd config set deletes a same-named flat dotted key, and bd's own readers then disagree (bd-zj95 mirrored)

rename-prefix --repair replaces every id with a random hash; no way to consolidate prefixes while keeping suffixes, or to change the mint prefix alone

ready_issues / blocked_issues resolve blockers only via depends_on_issue_id, so external refs never block (measured on 1.2.2; believed already fixed by #4753 — filing to confirm)

Check migration hygiene is red on main since the 1.3.0 forward-port, and blames every pre-existing PR for main's own ignored-series rename

bd dolt push/pull cannot authenticate to a Dolt remote that requires HTTP basic auth