🐞 Fix stack overflow crash on window-move actions

[bit-saver]

Summary

Window-move actions (moveUp / moveDown / moveLeft / moveRight) crash Loop with EXC_BAD_ACCESS (stack overflow) as soon as they're triggered — via a keybind, the radial-menu preview, or a loop://direction/Move… URL.

Root cause

WindowFrameResolver.calculateTargetFrame(...) resolves the willMove branch by reading context.getTargetFrame(). ResizeContext.getTargetFrame() lazily calls recomputeTargetFrame(), which calls WindowFrameResolver.getFrame(resizeContext: self) on the same context — re-entering the willMove branch and calling getTargetFrame() again. Since needsRecompute is only cleared at the end of recomputeTargetFrame(), the re-entrant call recomputes again → infinite mutual recursion → stack overflow.

Crash backtrace (abridged):

0  libswiftCore  swift_beginAccess
2  Loop  static WindowFrameResolver.getFrame(resizeContext:)
3  Loop  ResizeContext.recomputeTargetFrame()
4  Loop  static WindowFrameResolver.calculateTargetFrame(sidesToAdjust:context:)
5  Loop  static WindowFrameResolver.getFrame(resizeContext:)
…  (repeats until KERN_PROTECTION_FAILURE at the stack guard page)

Fix

• WindowFrameResolver.swift — the willMove branch now reads lastAppliedFrame ?? cachedTargetFrame.raw (matching the grow/shrink branches) instead of getTargetFrame(). This removes the self-recursion at its source, and anchors moves to the window's actual position rather than a theoretical, possibly clamped-away target frame (also fixing move drift on size-constrained windows).
• ResizeContext.swift (defensive) — recomputeTargetFrame() clears needsRecompute before resolving, so any future re-entrant getTargetFrame() returns the cached frame instead of recursing. Not strictly required after the resolver change; happy to drop it if you'd prefer a minimal one-file diff.

Testing

Before: open "loop://direction/MoveLeft" on a focused window → immediate EXC_BAD_ACCESS crash with the recursion backtrace above.

After: same trigger (MoveLeft + MoveRight) → resolver computes the frame, the window moves, action recorded, no crash:

[URLCommandHandler] Executing direction: MoveLeft
[URLCommandHandler] Found 14 eligible windows
[ResizeContext] Computed target frame … for action: WindowAction(direction: MoveLeft)
[WindowEngine] Resizing Window(…) to (4061.0, 867.0, 399.0, 455.0)

swiftformat --lint is clean; built with the Loop scheme (Release).

[mrkai77]

I was able to reproduce the issue locally, and this PR fixes it. Thanks :)