Summary

Fixes #112 by updating local .flyde file imports when VS Code reports a file or folder rename/move.

When an imported flow moves, the extension now scans workspace .flyde files, deserializes them, rewrites file-backed source.data paths (and legacy imports entries), and saves the updated flow with the new relative path.

/claim #112

Demo

The behavior is covered by the focused test cases in vscode/src/update-flyde-import-paths.test.ts:

• imported flow file move: ./Child.flyde -> ../shared/Child.flyde
• containing folder move: ./nested/Child.flyde -> ../shared/nested/Child.flyde
• parent flow move: child imports stay pointed at their original files from the new parent location
• package/custom sources are left untouched

Verification

• npx --yes pnpm@10.12.4 --dir vscode run compile-tests
• npx --yes pnpm@10.12.4 --dir vscode exec mocha out/update-flyde-import-paths.test.js --ui tdd --timeout 60000