once the database had any custom type, although create accepts them; in
proxied mode `bd config set storage-class.<type>` checked `config.yaml` alone
and refused custom types registered in the database; and the built-in system
types `message`, `molecule`, `gate` and `event` were never listed. Every
mode now composes custom types by one rule (the `custom_types` table, else
the `types.custom` config row, always unioned with `config.yaml`). `bd types`
gains a "System types" section, and `bd types --json` an additive
`system_types` field; `core_types` and `custom_types` are unchanged. A
failure to read the custom types now fails `bd types`, `bd create --graph`
and `bd config set storage-class.*` instead of being silently treated as "no
custom types".
- **`bd sql` no longer drops the rows of CTE queries or CALL result sets**
([#6932](https://github.com/gastownhall/beads/pull/6932)). In proxied-server
mode, `WITH name(cols) AS (...) SELECT ...` and `WITH RECURSIVE ...` queries
were misread as writes and printed `OK, 0 rows affected` with no error; they
now return their rows. Statements are now classified with the Dolt SQL
parser (shared by the proxied and direct paths): reads return rows, plain
writes (including CTE-prefixed `UPDATE`/`DELETE`) commit and report
`rows_affected`, and anything that may both write and return rows (`CALL`,
`EXPLAIN ANALYZE` of a write, `RETURNING`) or that the parser cannot
classify is committed and prints whatever rows it returns, so
`CALL DOLT_BRANCH(...)`-style result sets are rendered instead of discarded.
Visible changes for scripts: in direct server mode a multi-statement write,
or a single write statement the parser cannot classify, now prints `OK` /
`{"status":"ok"}` (as proxied mode already did) instead of
`OK, N rows affected` / `{"rows_affected":N}`; and `--readonly` now refuses
statements it cannot parse (for example `PRAGMA`) instead of treating them
as reads.
- **Unblocking two blockers of one dependent at the same time no longer leaves
the dependent stuck as blocked** ([#6716](https://github.com/gastownhall/beads/issues/6716); [#6719](https://github.com/gastownhall/beads/pull/6719), [#6942](https://github.com/gastownhall/beads/pull/6942)).
Closing both blockers in parallel (formula fan-in with parallel workers), or
a close racing a `bd dep remove` or a delete of the other, could leave the
dependent `is_blocked=1` and missing from `bd ready` until
`bd recompute-blocked`. A write that takes a blocker away (a close, an update
to an inactive status, a dependency removal, a delete) now rechecks the
dependents it recomputed once its transaction has committed. This covers the
Dolt store write transactions, every write the proxied-server (uow/domain-db)
route serves — under `--proxied-server`, the default topology, that is
`bd close` (single and batch), `bd update --status`, `bd dep remove`,
direct, `bd cook`, `bd mol squash`/`burn`, and SDK callers that close or
update inside a transaction), the wisp close, update and delete writers, and
the legacy dependency removal behind `bd duplicates --merge`. Demote-to-wisp
moves a row between planes without taking a blocker away and is unchanged.
- **`bd close` now exits non-zero when any issue in a batch fails to close**
([#6648](https://github.com/gastownhall/beads/issues/6648); [#6740](https://github.com/gastownhall/beads/pull/6740), [#6771](https://github.com/gastownhall/beads/pull/6771)). A batch with one
refused id used to exit 0 as long as another id closed, so scripts could not
tell that part of the batch was left open. The closable ids still close, the
refusals are still printed, and a final `Error: N of M issues failed to close`
line is added; ids that were already closed still count as success. Both the
direct and proxied-server routes behave this way for ids the close policy or
the engine refuses. (An id that cannot be *resolved* at all is unchanged and
still differs by route: the direct route aborts the whole command before any
close runs, while the proxied route refuses that argument and closes the
rest.) In `--json` mode the summary is instead a compact JSON line on stderr
naming the failed ids, matching `bd update`'s partial-failure report, while
stdout keeps the usual closed-issues array. Each `failed[]` entry carries the
refusal as the engine worded it, identically on both routes; the `--force`
hint and the route's own framing stay on the human-readable stderr line, which
is unchanged. `--claim-next` still claims when
part of the batch closed — the claim commits inside the batch's own
transaction and a sibling's refusal does not roll it back — so the summary
names the claimed id rather than leaving it silently assigned.
- **`bd query` no longer silently stops at 50 rows when its output is piped**
([#6229](https://github.com/gastownhall/beads/issues/6229), [#6744](https://github.com/gastownhall/beads/pull/6744)). `bd list` has
treated piped stdout as unlimited since GH#4094, but `bd query` read its
`--limit` default of 50 straight through, so `bd query '...' | consumer`
dropped every row past 50 with no hint. An unflagged `bd query` now resolves
through the same policy as `bd list`: an explicit `--limit` wins, piped
stdout is unlimited, agent mode on a terminal gets 20, and a terminal gets 50.
- **Deleting or purging a wisp no longer leaves orphan rows behind on stores
without the wisp foreign keys** ([#6563](https://github.com/gastownhall/beads/pull/6563), [#6627](https://github.com/gastownhall/beads/pull/6627), [#6487](https://github.com/gastownhall/beads/issues/6487)).
On a store whose `wisp_dependencies` and wisp auxiliary tables lack the
migration-0047 FK constraints, every wisp delete (including `bd purge`,
`bd mol burn` and wisp GC) left its `wisp_dependencies` edges on both sides
and its `wisp_labels`, `wisp_events`, `wisp_comments` and
`wisp_child_counters` rows in place, which showed up as dangling parent
references and store bloat. The delete paths now remove them. This is a
forward fix: orphans already in a store are not cleaned up.
- **A clone missing its local `events`, `bd_events_journal` or `bd_events_seq`
table recreates it on open** ([#6547](https://github.com/gastownhall/beads/pull/6547)). Those tables are dolt-ignored, so
a fresh clone can arrive at the latest schema version without them, and bd
then treated the schema as complete and never created them. Their absence
now makes the migration runner replay the migrations that create them, from
each table's own floor rather than from zero.
- **The smart migrate gate no longer auto-migrates a clone whose data is behind
the remote** ([#6575](https://github.com/gastownhall/beads/issues/6575)). The
@ -529,23 +534,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
--force` / `BD_ALLOW_REMOTE_MIGRATE=1` are still consulted before the gate and
still override it.
- **A dotted config key now round-trips: what `bd config set` writes,
`bd config get` and bd's own readers find**
([#6578](https://github.com/gastownhall/beads/pull/6578), bd-zj95). Setting a
key like `sync.remote` or `dolt.host` into a `config.yaml` with no matching
section appended a key whose *name* contained the dot — a top-level
`sync.remote: "..."` — instead of nesting it under `sync:`. Viper finds a key
spelled that way; the direct reader `GetStringFromDir` splits on the dot and
walks nested mappings, so it does not. The value was set and invisible at the
same time depending on which reader asked, and `bd init --remote` in a fresh
workspace was the ordinary way in: the remote was recorded and then not found.
Dotted keys are written nested now, and `bd config unset` removes the nested
form — it only ever matched the flat spelling, so unsetting
`sync.remote` silently left the remote live. Keys the write does not own,
including dotted ones somebody else put there, are left exactly as they are.
Two consequences of the nested write — the flat-key migration and two new
failure exits — are under **Changed** above.
- **`bd list --status <s> --ready` honors `--status`**
// versionChanges contains agent-actionable changes for recent versions
varversionChanges=[]VersionChange{
{
Version:"1.3.1-rc.2",
Date:"2026-09-29",
Changes:[]string{
"RC: second candidate for the 1.3.1 patch line. Still no schema migration, so upgrading from 1.3.0 or 1.3.1-rc.1 is a binary swap. The 1.3.1-rc.1 entry below still applies.",
"NEW: on a proxied-server workspace whose Dolt server bd runs (managed-local, the default), 'bd backup init/sync/status/restore/remove' now work, and 'backup.enabled=true' turns on auto-backup (default stays OFF). On an external or team-server proxied topology the family stays refused with 'proxy.backup.unsupported' and \"reason\": \"design\". Proxied refusals now carry a 'reason' field ('design' or 'unimplemented'). A per-workspace '.beads/backup.lock' serializes backups: 'bd backup sync' fails after 5s if another backup is running.",
"NEW: 'bd purge --wisps-plane --older-than <age> --force [--limit N] --json' can replace a raw DELETE FROM wisps retention step. With --limit it purges oldest-closed first and reports 'remaining' and 'has_more'; loop while has_more is true.",
"CHANGE: 'bd purge' ALWAYS keeps a closed bead that a not-done bead depends on through parent-child, tracks or blocks, and reports the count as 'live_dependent_skipped'. There is no flag to disable it.",
"CHANGE: '--older-than' on 'bd purge' and 'bd prune' takes hour values exactly: '12h' no longer rounds up to a day and '36h' no longer floors to one, so 'bd prune --older-than 12h' now deletes rows closed 12-24 hours ago. Day values (7, 7d, 2w) are unchanged; a value too large to represent is refused.",
"CHANGE: 'bd show --watch <id>' works under --proxied-server, and on both routes a watch whose id cannot be found exits 1 instead of 0.",
"CHANGE: 'bd sql' classifies statements with the SQL parser. Proxied CTE queries ('WITH ... AS (...) SELECT') return their rows instead of 'OK, 0 rows affected', and CALL result sets are printed. In direct server mode a multi-statement write, or a write the parser cannot classify, prints 'OK' / {\"status\":\"ok\"} instead of 'OK, N rows affected' / {\"rows_affected\":N}. 'bd sql --readonly' refuses statements it cannot parse (e.g. PRAGMA).",
"CHANGE: 'bd types' lists exactly what 'bd create --type' accepts, with a new 'System types' section and an additive 'system_types' JSON field. A failure to read custom types now fails 'bd types', 'bd create --graph' and 'bd config set storage-class.*' instead of meaning 'no custom types'.",
"CHANGE: an explicit BEADS_DIR is authoritative. Point it at the .beads directory itself: a BEADS_DIR naming a project root, or a .beads that does not exist yet, now fails with 'no beads database found' instead of resolving to the nearest workspace above the current directory. 'bd init' initializes the named directory.",
"CHANGE: 'bd close' with several ids exits non-zero when any id fails to close (the rest still close). With --json, a summary naming the failed ids goes to stderr.",
"CHANGE: an unflagged piped 'bd query' is no longer capped at 50 rows; it follows the 'bd list' limit policy.",
"CHANGE: on a proxied workspace, dolt.auto-commit=batch/off now defers Dolt history commits and 'bd dolt commit' is supported as the flush point. Explicit commit points ('bd batch', 'bd mol bond/pour/squash', 'bd mol wisp create') still commit. The default 'on' is unchanged.",
"CHANGE: 'bd ready' and 'bd list --ready' include issues whose custom status is in the 'active' category; 'bd list --status <s> --ready' honors --status; bare 'bd list --wisp-type' is refused (use --include-ephemeral); 'bd doctor' warns about a missing .beads/dolt-server-config.yaml gitignore pattern until 'bd doctor --fix'.",
"CHANGE: on a proxied-server workspace or under 'bd serve', opening a store against an unreachable Dolt server retries for up to ~40s before failing, instead of failing at once.",
"FIX: two blockers of one dependent removed at the same time (parallel closes, a close racing 'bd dep remove' or a delete) no longer leave the dependent stuck blocked and hidden from 'bd ready' (#6716), on every store route including --proxied-server.",
"FIX: a proxy whose Dolt backend exits cleanly now retires, so the next command starts a fresh one; 'bd dolt status' reports it as not serving.",
"FIX: a server workspace with an empty .beads/dolt is no longer refused as a legacy workspace; 'bd init' writes the version marker.",
"FIX: the smart migrate gate no longer auto-migrates a clone whose data is behind its remote. It stops with 'run bd dolt pull, then retry', and 'bd dolt pull' works from that state.",
"FIX: deleting or purging a wisp no longer orphans wisp_dependencies, wisp_labels, wisp_events, wisp_comments or wisp_child_counters rows on stores without the wisp foreign keys (existing orphans are not cleaned). A clone missing its dolt-ignored events tables recreates them on open.",