test(graph-engine): update flow-speed expectation after the 2x bypass

The P2 codex fix on PR #180 (commit 76424c5) bypasses the 2x
response mapping for `graph-flow-speed` so the slider's visible
endpoints are linear and the new `flowSpeed=0` stop guard fires
only at user-selected zero, not throughout the lower quarter of
the visible range. The e2e test in
`tests/e2e/graph-engine.spec.js::served Ledger handles overflows,
label overlays, and orbit pause` set the visible slider to 65
and asserted the engine received 85 (= 45 + (65-45)*2, the old 2x
response). With the bypass the engine now receives the raw value
(65), so the expected `flowSpeed` in `rangeResponse.settings` is
65 instead of 85.

The other test in `tests/e2e/ledger.spec.js` (visible value `'45'`
default, set-then-expect `'67'`) is not affected because that test
sets the slider to 67 directly and reads the resulting HTML
attribute, neither of which goes through
`graphSliderResponseValue` (the function only mutates the
`settings` object passed to the engine). The new linear flow-speed
slider still shows 67 on the dashboard when the user moves it to
67 and the engine receives 67.

Author: Coding-Dev-Tools

tests/e2e/graph-engine.spec.js

@@ -1937,7 +1937,7 @@ test('served Ledger wires normalized spacetime controls, overlay, and orbit paus
       };
     });
     expect(rangeResponse.settings).toMatchObject({
-      flowSpeed: 85, repel: 200, link: 32, gravity: 144, size: 5, font: 20,
+      flowSpeed: 65, repel: 200, link: 32, gravity: 144, size: 5, font: 20,
       linkw: 1.28, labelDensity: 56,
     });
     expect(rangeResponse.scope).toEqual({ minDegree: 2, depth: 3 });