fix(microvm): the relay URL must survive the login profile; deploy.sh must not ship a target symlink

- The first relayed kimi mission (01a0cfc3) bound the node relay, yet the guest
  dialled api.kimi.com through egress with the proxy token: the turn runs in a
  login shell that sources /etc/profile.d/00-image-env.sh (the image's ENV),
  which re-exports the glm/kimi images' baked ANTHROPIC_BASE_URL over ours. The
  turn command now re-exports the base URL after the profile. No key leaked —
  the guest had only the token — but relayed kimi/glm missions could not run.
- deploy.sh excluded `target/`, which matches only a directory; a workstation
  whose target is a symlink copied it to the build host, breaking its builds.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

scripts/deploy.sh

@@ -90,7 +90,11 @@ load_if_changed() {
 }
 
 echo "→ sync to $BUILD_HOST"
-rsync -az --delete --exclude target/ --exclude node_modules/ --exclude .git/ \
+# `target`, not `target/`: a trailing slash matches only a DIRECTORY, and a
+# workstation whose target is a symlink (to an external drive) copied that
+# symlink over the build host's, leaving it pointing at a path that does not
+# exist there — every build since 2026-08-15 failed with "Not a directory".
+rsync -az --delete --exclude target --exclude node_modules/ --exclude .git/ \
   --exclude '.next/' --exclude 'frontend/public/dl/' --exclude '**/.DS_Store' \
   ./ "$BUILD_HOST":~/clawmates/