Two P1-1 residual proxied-mode seams from the bd-6dnrw.44 re-verification,
both PORTED (each was genuinely small):
- bd dep relate/unrelate: no usesProxiedServer() branch meant an opaque
"cannot resolve issue ID: storage is nil" death. Now routed through new
runRelate/UnrelateProxiedServer duals: one RunTx with a real commit
message per invocation (both directed relates-to edges in one Dolt
commit for relate; both removals in one for unrelate, empty-message
no-op when neither edge existed), classic "issue not found" /
self-relate refusals preserved. Exact canonical ids only, like every
other proxied dep verb.
- bd human list/respond/dismiss/stats: each called ensureStoreActive(),
which in proxied mode lazily opened a DIRECT store, silently bypassing
the proxy. Root cause: "human" sits in noDbCommands for its bare help
screen, so its DB-backed subcommands skipped store init entirely and
direct mode papered over it lazily. The subcommands now fall through to
store init (needsStoreHumanSubcommands, dolt-subcommand pattern) and
branch to proxied duals before the direct-store path: reads on one
read-only UOW, respond/dismiss each ONE RunTxResult (existence +
already-closed preflight, comment + close in the same transaction)
under "bd: human respond/dismiss <id>" commit messages. human moves to
the forbidigo proxied-twin family in .golangci.yml (same filter built
on both routes).
Tests: TestProxiedServerRelate + TestProxiedServerHuman journey suites on
the shared testcontainers harness, incl. dolt_log assertions that each
write invocation lands exactly one commit with its own message, and that
the "storage is nil" death is gone; shard manifest entries added at the
hash-fallback shards (7, 11).
Claude-Session: https://claude.ai/code/session_01JtAkNTf8DGzP1AF3FMuGmm
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>