fix(dashboard): measure V8 heap against its limit, not its current size

The Health Score's heap component divided heapUsed by heapTotal, which is
only what V8 has grown the heap to so far, so a healthy server read 70-90%
and dragged the score down. GET /api/settings/info now also reports
server.memory.heapLimit (v8 heap_size_limit, the ceiling the process dies
at); the V8 Heap bar and the Health Score divide by it, falling back to
heapTotal against an older server.

server/routes/settings.js

@@ -7,6 +7,7 @@ const { Router } = require("express");
 const fs = require("fs");
 const path = require("path");
 const os = require("os");
+const v8 = require("v8");
 const { db, stmts, DB_PATH, DEFAULT_PRICING, applyIntroPricing } = require("../db");
 const { getConnectionCount } = require("../websocket");
 const { transcriptCache } = require("./hooks");
@@ -121,7 +122,10 @@ router.get("/info", (req, res) => {
       node_version: process.version,
       platform: process.platform,
       ws_connections: getConnectionCount(),
-      memory: process.memoryUsage(),
+      // heapTotal is only what V8 has grown the heap to SO FAR, so used/total
+      // sits at 70-90% on a perfectly healthy process. heapLimit is the ceiling
+      // the process actually dies at — the denominator a "heap used %" needs.
+      memory: { ...process.memoryUsage(), heapLimit: v8.getHeapStatistics().heap_size_limit },
       cpu_load: os.loadavg(),
       arch: os.arch(),
       total_mem: os.totalmem(),