* fix(test): pin DOCKER_HOST from the active docker context before TestMain swaps HOME (bd-84kos)
cmd/bd's testMainInner points HOME at a temp dir before any test runs,
which hides ~/.docker/config.json — the file holding the docker CLI's
active context. On machines where the daemon is reached via a context
(OrbStack, Docker Desktop's desktop-linux, remote daemons), 'docker
info' then falls back to unix:///var/run/docker.sock and fails, so
every container-gated test SKIPs 'Docker not available' even though
docker works fine in the invoking shell. Skips read as green, so the
proxied parity suites silently stopped running (bit bd-i8qx8).
Add testutil.PinDockerHostFromContext — resolve the active context's
endpoint ('docker context inspect -f {{.Endpoints.docker.Host}}') into
DOCKER_HOST, no-op when DOCKER_HOST is already set or docker is absent
— and call it in testMainInner just before the HOME swap.
Verified on macOS + OrbStack with no DOCKER_HOST in the environment:
TestProxiedServerExternalCreate skips 'Docker not available' on main,
and PASSes against a live container with this change.
* fix(test): harden PinDockerHostFromContext — 5s exec timeout + endpoint-shape check (bd-84kos)
Review hardenings: a pathological docker shim can no longer hang
TestMain (context inspect is local-metadata-only, so 5s is generous),
and a resolved value is only pinned when it is endpoint-shaped
(contains '://') — a shim printing something else degrades to no-op.