Remove the "not supported in proxied-server mode" gates from bd kv
(set/get/clear/list) and the memory surface (remember/memories/forget/
recall). Both are thin prefix layers (kv.* / kv.memory.*) over the config
table, so the handlers mirror config_proxied_server.go: one RunTx per
write invocation with a real commit message ("bd: kv set <key>",
"bd: kv clear <key>", "bd: remember <key>", "bd: forget <key>"), reads
via RunTxRead. The proxied path never touches ensureDirectMode; the
classic path keeps it.
Presentation and namespace filtering are extracted into helpers shared
by both paths (printKV*, kvPairsFromConfig, printRemember*/printForget*/
printRecall*, memoriesFromConfig, rememberBareKeyPath), so output —
including the kv list --json shape that the wyvern wheelhouse mail
transport parses — cannot drift between modes. Key validation and the
remember desire-path/command-word guards run before dispatch and behave
identically in both modes. Storage errors pass through %v unmodified so
callers can keep retrying on the 'Merge conflict detected' /
'constraint violation, transaction rolled back' substrings.
Journey tests: TestProxiedServerKV (byte-preserving multi-line/JSON
envelope round-trip, list --json shape + classic-vs-proxied comparison,
idempotent clear, invalid-key refusal, one-Dolt-commit-per-write) and
TestProxiedServerMemory (remember → memories → recall → forget journey,
kv.memory.<key> storage-key check, bare-key desire path, command-word
guard, one-commit-per-remember). Manifest entries added at the shards
the hash fallback already assigns (13/14), so nothing reshuffles.
Refs bd-dnzjy, program bd-vxavz.