build.sh requires outbound network for full browse build (vendor:xterm / gen:skill-docs)

[Spooks444]

Follow-up: scripts/build.sh requires outbound network for a full browse build

Summary

browse/scripts/build-node-server.sh only produces server-node.mjs (the Node.js
server bundle). The runnable browse executable is a compiled artifact produced by
the root scripts/build.sh via bun build --compile. That script also runs
prep steps that need outbound network access:

• vendor:xterm (npm install of the xterm dependency)
• gen:skill-docs (generates skill documentation, fetches remote sources)

Impact

On a machine with no outbound network (or a flaky registry), a bare
rm -rf browse/dist && bash browse/scripts/build-node-server.sh regenerates the
server bundle but leaves no browse CLI binary. Running ./browse/dist/browse
then fails with a cryptic ENOENT instead of an actionable message.

PR #2260 added a Step-5 guard to build-node-server.sh that detects the missing
binary and prints remediation. This issue tracks the root cause — making the
network-dependent steps resilient or clearly documented.

Suggested fixes

1. Document the network requirement in scripts/build.sh header / README.
2. Make vendor:xterm and gen:skill-docs skippable via an env var
   (e.g. GSTACK_OFFLINE=1) so the compiled binary can still be produced from a
   cached vendor tree.
3. Have build-node-server.sh optionally invoke the compile step itself when the
   binary is absent and a suitable toolchain is present.

Verification note

The full pipeline (server start + Chromium navigation) was confirmed working via a
loopback http://127.0.0.1:8099/ test; external-URL navigation is only blocked by
sandbox DNS policy, not by this issue.

[time-attack]

@16francej — recommend closing this issue because the reported build-time network requirement does not occur in the cited current build paths. The valid remaining concern is already handled by #2260 through a clear missing-binary diagnostic and remediation. Credit #2271 for that diagnostic requirement, but do not carry forward the unsupported offline-build mode.