fix(boot): identity-match run re-adoption, not length-only (Test-#11 class)

At boot, when state.activeRunNumber wasn't restored from snapshot, the working
set (results.json) was adopted onto a candidate saved run `cand` whenever
candData.length === results.length — LENGTH ONLY. Two different full audits of
the same ~1052-node chain have identical length, so an interrupted/unsaved
working set aliased a saved run's number and a later save overwrote that saved
run (the "Test #11" corruption).

Fix: require an order-independent content match too — an address|timestamp|mbps
key over all rows (each result carries a unique-per-run timestamp). Err STRICT:
when the key differs, mint a fresh number (getNextRunNumber, always > max, never
collides/overwrites) instead of adopting `cand`. A false-negative is harmless
(cosmetic new number); only the old false-positive caused data loss.

Adversarially reviewed: timestamps survive the JSON save/load round-trip and
genuinely differ between audits; legit restart-after-complete still reuses the
right number (saveResults writes identical data to both files); composes
correctly with the reserved-number saveCurrentRun fix. Test suite green
(188/31/45/35).

Author: Sentinel-Bluebuilder

server.js

@@ -1133,7 +1133,16 @@ function rehydrateState(results) {
       const cand = index.activeRun != null ? index.activeRun
                  : (index.runs.length > 0 ? index.runs[index.runs.length - 1].number : null);
       const candData = cand != null ? loadRun(cand) : null;
-      const reused = candData && candData.length === results.length;
+      // Strengthen "is the working set the SAME run as `cand`?" beyond length:
+      // two DIFFERENT audits of the same chain set have identical length but
+      // different per-node timestamps/speeds. Matching on length alone aliased
+      // them, so a later save overwrote a real saved run (the "Test #11"
+      // corruption). Compare an order-independent content key; err STRICT (fresh
+      // number when unsure) — a fresh number can never overwrite a saved run.
+      const _runKey = rows => rows.map(r => `${r.address}|${r.timestamp || ''}|${r.actualMbps == null ? 'x' : r.actualMbps}`).sort().join('\n');
+      const reused = candData
+        && candData.length === results.length
+        && _runKey(candData) === _runKey(results);
       state.activeRunNumber = reused ? cand : getNextRunNumber();
       // When we assigned a FRESH number (not reusing a saved run), reserve it by
       // persisting it into the snapshot immediately. getNextRunNumber() only