* feat(gate): port create/add-waiter/resolve/show to proxied-server mode (bd-v50ru)
Four gate subcommands stop refusing proxied-server mode and route through
the UOW provider, following the conventions gate check/list already set in
cmd/bd/gate_proxied_server.go:
- gate create: ONE RunTxResult doing target lookup + CreateIssue +
AddDependency under a single commit message ("bd: create gate <id>
blocking <target>") — the direct route's create + add-dep + explicit
store.Commit collapse into one Dolt commit per invocation.
- gate add-waiter: one transaction; an already-registered waiter returns an
empty commit message (deliberate no-commit no-op). Fires the on_update
hook post-commit.
- gate resolve: one transaction (type check + CloseIssue), then audit
LogFieldChange + close hooks post-commit, mirroring gate check's closes.
- gate show: read-only UOW; not-found and read-failure exit nonzero with
distinct messages (fail-closed: an unreachable server is not "no gate").
Output parity is enforced structurally: the direct route's renderers and
gate-create input/issue construction are extracted (renderGateShow,
renderGateCreated, renderGateResolved, renderGateWaiterAdded/Already,
gatherGateCreateInput, buildGateIssue) and both routes call the same code,
so the text downstream scripts parse cannot drift.
gate discover keeps its proxied-mode refusal: it interleaves GitHub CLI
queries with per-gate writes and incremental output, so it is not the pure
routing this port covers.
Also fixes the latent domain/db bug the new journey test caught: the
proxied repository's normalizeUpdateValue never serialized "waiters", so
any waiters update through the proxied backend failed at the SQL driver
("unsupported type []string"). It now JSON-marshals the value exactly as
the embedded path (issueops.updateIssueInTx) always has, with a unit test
pinning the behavior.
New journey test TestProxiedServerGateLifecycle covers the wheelhouse
consumer shapes (gate-id parsing from create output, wh-park bead-gate
create, show markers, list --all --json fields, rc-only resolve,
fail-closed error paths) and is listed in the proxied shard manifest.
Part of bd-vxavz (proxied-server capability parity).
* fix(ci): drop stray duplicate TestProxiedServerDelete shard line (bd-v50ru)
Review blocker on #5346: the duplicate tripped proxied-test-shard.sh's
duplicate check and failed all 15 Proxied Dolt Cmd shards, so
TestProxiedServerGateLifecycle never ran in CI.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NvU6bUda8oQjvG3zoa4uyX
---------
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>