You are reviewing a PR for the loreai project. The PR fixes a CI build failure where fossilize (a tool that creates standalone Node.js binaries) was receiving all platform names as a single comma-joined string instead of separate arguments.

The fix switches from CLI invocation to using fossilize's programmatic API directly.

Please review the changes critically. Look for:

1. Correctness issues
2. Hardcoded paths or fragile imports
3. Missing error handling
4. PR description accuracy
5. Any other concerns

Here is the diff:

File: packages/gateway/script/build-binary-sea.ts

The file adds these imports at the top (after line 46):

// Fossilize imports
import fs from "node:fs";
import os from "node:os";
import path from "node:path";
import { fileURLToPath as nodeFileURLToPath } from "node:url";
// @ts-ignore - fossilize doesn't have proper typedefs but works at runtime
import fossilize from "../../../node_modules/.pnpm/fossilize@0.8.1/node_modules/fossilize/dist/impl-7RS2FY5C.js";

And replaces the CLI invocation (lines ~582-629) with:

   // Use fossilize's programmatic API
   const fossilizeContext = {
     process,
     os,
     fs,
     path,
   };
   const fossilizeFlags = {
     nodeVersion: "lts",
     platforms: targets.map(fossilizeTarget),
     noBundle: true,
     holePunch: true,
     outputName: "lore",
     outDir: distBinDir,
     assetManifest: manifestPath,
     // Don't sign here - we'll handle signing/renaming manually like before
     sign: false,
     concurrencyLimit: 3,
   };

   console.log(
     `→ fossilize: ${targets.length} platform(s), ${Object.keys(manifest).length} asset(s)`,
   );
   await fossilize.default(fossilizeContext, fossilizeFlags, bundlePath);

Note: The old code used spawnSync (synchronous), the new code uses await (async). Check if the calling context supports async.

Also note: The import path ...