[HugoXK]

Fixes #1752

Owner: Dev2
Reviewer: Birfy
Written-by: Dev-2

What the bug was

Settings → Workflows drew the authored 960px plane at 1:1 inside a canvas that is far narrower, with the plane centred as a zero-width line, and it drew a parallel layer as one row whatever the stored y said. A workflow whose branch card was stored lower and near the right edge therefore reproduced all three reported symptoms:

• the 取证 / 真机取证 card was cut by the canvas's right edge, its status chip reduced to Q… (view) / Que… (Edit);
• the dashed "Parallel branch, then join" frame ran off the same edge;
• the Claim → 取证 wire ended with its arrowhead on the clip line, and the horizontal scrollbar was the only way to see the card.

Red first

Three tests in core/test/workflows-page.test.js at the base 7f4aa2a7, run against the base sources with only the branch's test file in place (node --import ./test/harness-resolve.mjs --test --test-name-pattern="1752" test/workflows-page.test.js): 3 tests, 0 pass, 3 fail.

not ok 1 - a parallel frame encloses a member stored lower than its partner (\#1752)
  error: 'the frame 90..182 leaves forensics (159..231) outside'

not ok 2 - the Settings graph fits its plane into the canvas width (\#1752)
  error: 'the canvas wraps the plane in a fit layer'

not ok 3 - a fitted graph keeps the right-hand card and the wire into it inside the canvas (\#1752)
  error: |-
    + actual - expected

    + 'undefined'
    - 'function'

After the fix the same pattern is 3/3, and the whole file is 14/14.

Fix

• fitScale(nodes, width) (exported pure helper): one scale() from the widest content reach (|x| + 108, so the dashed frame counts), capped at 1 and floored at 0.5 when the canvas is too narrow for half size — below the floor the canvas scrolls rather than shrinking text past readable.
• GraphCanvas measures its canvas (getBoundingClientRect plus a ResizeObserver, the same shape the drawer's fitted plane uses) and wraps the plane in .bt-wf-fit (transform: scale(...), transform-origin: 50% 0; .bt-wf-stage takes the scaled height). Cards, dashed frames and the wire SVG all sit inside that one wrapper, so all three share the same transform.
• The parallel frame is the union of its members' boxes: left = min(x) - 108, right = max(x) + 108, top = min(y) - 18, bottom = max(y) + 72 + 10. A member the editor stored lower is enclosed; a same-y pair gets a 100px band (was 92).
• Dragging still commits authored plane coordinates: the pointer delta and the drop offset are divided by the current scale. The display transform never becomes the stored value. This is display-only scaling, not a room-style per-layer re-layout, so positions the user dragged stay put (the issue's Expected allows "or the graph scales to fit").

Scope and lines

Real changes, excluding the generated core/client.js, the two patches/ds-bot/files/ mirrors and patches/ds-bot/0008 (all produced by the one generate step):

file	lines
core/src/client/workflows.js	+47/−12
core/src/client/styles.js	+3/−0
core/test/workflows-page.test.js	+72/−2
docs/subsystems/core-client.md	+1/−1
changelog.d/1752-settings-graph-fit.fixed.md	+1/−0

139 changed lines (136 code + 3 docs/changelog), under the 150 stop-line.

Generated at this base (not counted above): core/client.js +128/−89; patches/ds-bot/0008-client-bundle.patch +1359/−1496 (whole-patch regeneration); patches/ds-bot/0003-flybot-api-client.patch +27/−24 — of which 3 lines are the real styles.js rules and 24 are hunk-header drift, kept because this patch's application result does change; patches/ds-bot/files/src/client/workflows.js +47/−12; patches/ds-bot/files/test/workflows-page.test.js +72/−2.

Drift: generate is not byte-idempotent on this box (git 2.34.1 writes hunk headers with function context). It rewrote 0001-core-fixes.patch (44/44), 0003 and 0014-flybot-branding.patch (2/2) for header reasons alone. 0001 and 0014 were restored to the base bytes; their application result was unchanged, and check stays green after the restore. 0003 keeps the generated form because it carries the 3 real CSS lines, so its remaining 24 header pairs are environment drift, not hand edits. No hunk was hand-edited, and 0008 is the whole-chain regeneration.

check, twice on this tree, prints the same three lines:

ok   ds-bot/ = Fei2411/DeepSeek-Bot@2b10c70 (tree 5834c00, v0.1.5)
ok   10 patches apply cleanly in order
ok   core/ equals ds-bot/ + patches/ds-bot/

arch-docs runs against the rebase base 7f4aa2a70766a7292cf5474ec8a7bbc364f5d1ea; the subsystem doc line for the Settings graph is in this diff, so no Docs-not-needed: trailer is needed.

What I ran

node scripts/ds-bot-patches.mjs check            # twice, same three lines
node core/scripts/build-client.mjs --check       # silent, exit 0
TZ=UTC ARCH_DOCS_BASE=7f4aa2a7 npm run verify    # green at the tip

What I did not run

• No browser screenshot: jsdom cannot measure text, so the chip is pinned by geometry (the chip is inside the card, and the third test keeps the card's right edge inside the scaled half-width).
• No dev/bench.sh smoke: client-only change.
• No #1745, #1747, #1752 sibling branches touched; this diff carries no patches/ds-bot/0002-* and no patches/ds-bot/files/src/host/* (the parallel batch's generation is untouched).

Gates at this head

Head: 575774521864af328cd68e7dbe2557f83e2cbab3 (tree 8a3c9f43862ad36b1f82b0a43f165ddb2ec26cae), base 7f4aa2a70766a7292cf5474ec8a7bbc364f5d1ea.

enqueue-guard on this head, verbatim:

enqueue #1762: no `hold` and the gate passes

The check's own decision line is the same one (enqueue #1762: no hold and the gate passes), with no PASS needed: computed tier T1, and the fork exemption for the issue reference and agent-pr — this pull request lives on a fork.

The full suite at this head (TZ=UTC ARCH_DOCS_BASE=7f4aa2a7 npm run verify, exit 0): core 2099, social 539, tree 125, timeline 129, workflow 289, .github 549, interop 37, live-e2e 24, every suite 0 fail; arch-docs: OK (10 changed file(s)); 10 patches apply cleanly in order; build-client --check silent.

Checkpoint

{"pr": 1762, "claim": "Dev2", "issue": 1752, "summary": "The Settings Workflows canvas now fits the authored graph into the canvas with one scale on a wrapper, so cards, the dashed parallel frame and the wires share the transform and nothing is clipped at the right edge; the frame is the union of its members' boxes, so a member stored lower is enclosed. Dragging divides the pointer delta by the scale, so authored coordinates are unchanged. Tests: three new cases in core/test/workflows-page.test.js (red first), 14/14 in that file; full verify green at the tip.", "files": ["core/src/client/workflows.js", "core/src/client/styles.js", "core/test/workflows-page.test.js", "docs/subsystems/core-client.md", "changelog.d/1752-settings-graph-fit.fixed.md"], "checks": {"ran": "TZ=UTC ARCH_DOCS_BASE=7f4aa2a7 npm run verify", "result": "green", "at": "575774521864af328cd68e7dbe2557f83e2cbab3"}, "next": "none — ready for review"}