Broken imports after moving files (#112)

[velnory]

Addresses #112.

Summary

Update local flow references when imported files or folders move, and rebase imports when their importing flow moves. Preserve unsaved document changes and report rejected VS Code edits. Full pnpm build and all 17 VS Code host tests passed, including the reproduced-and-fixed applyEdit(false) failure. Stored visual baselines fail identically on the unmodified base and this patch; all 4 actual screenshots are byte-identical, so no patch visual regression was detected. Stored-baseline visual tests remain failed.

Acceptance coverage

AI-reviewed mapping to the source and executed checks:

• AC1 Importing a simple code flow into another flow continues to work as existing behavior.: PASS — T2; vscode/src/test/updateFlowReferencesOnRename.test.ts
• AC2 After an imported file is moved to a different folder, the import must continue to work.: PASS — T2; vscode/src/test/updateFlowReferencesOnRename.test.ts

Scope

5 files, +400/-0 lines; 1 test files; moderate diff

Changed files

• loader/src/serdes/index.ts
• loader/src/serdes/updateFlowReferencesOnRename.ts
• vscode/src/extension.ts
• vscode/src/test/updateFlowReferencesOnRename.test.ts
• vscode/src/updateFlowReferencesOnRename.ts

Verification

• T1 pnpm --filter flyde-vscode... build: PASS
• T2 pnpm test: PASS

Tests ran in a credential-free, network-isolated Linux sandbox. A separate AI review session accepted the tested diff.

AI-assisted contribution under a human-operated account; this is not a claim that a person has manually reviewed every line.

/claim #112