- BUILD_PROXY now defaults to empty: the three GitHub fetches (llama.cpp zip x2,
pinned CPython tarball) go straight to GitHub, so the Dockerfile builds as-is on
unrestricted networks. Pass --build-arg BUILD_PROXY=socks5://<host>:<port> to
route them through a SOCKS5 proxy instead. The hard-coded cr1.mse:2000 address
is gone from every file.
- socks2http.py + proxyrun.sh are now committed: the Dockerfile always shells out
to proxyrun.sh (even in direct mode), so the bridge must be in the build context.
- proxyrun.sh resolves socks2http.py relative to its own location (was hard-coded
/src/socks2http.py), so the wrapper also works outside the image.
- socks2http.py: --upstream defaults to empty (was the hard-coded address); empty
upstream = plain TCP passthrough, still useful for testing.
