fix: use hard copy instead of symlink for altimate-code binary alias

The build script created `altimate-code` as a symlink to `altimate`.
npm publish strips symlinks during packing, so the Verdaccio sanity
test couldn't find the binary after install ("Binary not found at
.../bin/altimate-code"). Using `cp` instead of `ln -sf` ensures the
binary is a real file that survives npm pack/publish cycles.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: anandgupta42

packages/opencode/script/build.ts

@@ -270,10 +270,12 @@ for (const item of targets) {
   })
 
   // Create backward-compatible altimate-code alias
+  // Use hard copy instead of symlink — npm publish and Docker COPY can strip symlinks,
+  // causing "Binary not found" in Verdaccio sanity tests.
   if (item.os === "win32") {
     await $`cp dist/${name}/bin/altimate.exe dist/${name}/bin/altimate-code.exe`.nothrow()
   } else {
-    await $`ln -sf altimate dist/${name}/bin/altimate-code`.nothrow()
+    await $`cp dist/${name}/bin/altimate dist/${name}/bin/altimate-code`.nothrow()
   }
 
   await $`rm -rf ./dist/${name}/bin/tui`