Fix the desktop install shipping an empty node_modules

Reported from a real install:

  Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@diskpush/database'
  imported from ~/.local/share/diskpush/app/resources/cli/dist/bin.js

Two bugs compounding, neither visible in the artifact I checked.

Node's `fs.cpSync` resolves relative symlinks to absolute paths unless
`verbatimSymlinks` is set. Copying the staged CLI into the app therefore
rewrote pnpm's good `../.pnpm/...` links as absolute paths into this script's
temp directory - which the same script deletes in its finally block. The links
were dangling before packaging even started.

electron-builder's extraResources copy then silently produced nothing for
those broken links, so the shipped app had `resources/cli/node_modules`
present but empty. The CLI-only tarball was unaffected: tar preserved the
relative links, which is why that path installed and ran fine and this went
unnoticed.

Fixed at the root rather than by repairing the links: the deploy now uses
`--config.node-linker=hoisted`, so the bundle is plain directories with zero
symlinks - same 33MB - and survives any copy, including whatever
electron-builder does to it. `verbatimSymlinks: true` is set as well so the
copy cannot reintroduce the problem.

Author: ralyodio

apps/web/components/chrome.tsx

@@ -66,9 +66,9 @@ function Logo() {
         alt="DiskPush"
         width={2172}
         height={724}
-        className="logo-dark h-14 w-auto"
+        className="logo-dark w-60 h-auto"
       />
-      <img src="/logo.png" alt="DiskPush" width={2172} height={724} className="logo-light h-14 w-auto" />
+      <img src="/logo.png" alt="DiskPush" width={2172} height={724} className="logo-light w-60 h-auto" />
     </>
   )
 }

scripts/package-cli.mjs

@@ -77,7 +77,18 @@ try {
   const stage = join(work, 'cli')
   // --legacy because these are ordinary workspace links rather than injected
   // dependencies; --prod so devDependencies stay out of the artifact.
-  run('pnpm', ['deploy', '--filter', '@diskpush/cli', '--prod', '--legacy', stage], checkout)
+  //
+  // node-linker=hoisted is load-bearing. pnpm's default layout links each
+  // package from node_modules/.pnpm, and those symlinks do not survive the
+  // trip into an Electron bundle: electron-builder's extraResources copy drops
+  // them, and the app ships an empty node_modules that fails at first run with
+  // "Cannot find package '@diskpush/database'". A hoisted tree is plain
+  // directories, the same 33MB, and survives any copy.
+  run(
+    'pnpm',
+    ['deploy', '--filter', '@diskpush/cli', '--prod', '--legacy', '--config.node-linker=hoisted', stage],
+    checkout,
+  )
 
   writeFileSync(join(stage, 'diskpush'), LAUNCHER, { mode: 0o755 })
 
@@ -88,7 +99,10 @@ try {
   // The desktop build embeds this same tree, so both surfaces ship one build.
   const embedded = join(root, 'apps/desktop/resources/cli')
   rmSync(embedded, { recursive: true, force: true })
-  cpSync(stage, embedded, { recursive: true })
+  // verbatimSymlinks: without it Node's cp resolves relative symlinks to
+  // absolute paths, which would point into this script's temp directory - the
+  // one deleted in the finally block below.
+  cpSync(stage, embedded, { recursive: true, verbatimSymlinks: true })
   console.log(`embedded a copy at ${embedded}`)
 
   console.log(`\n${join(outDir, `${name}.tar.gz`)}`)