/**
 * Regression tests for US-001 (hq-sync-windows-skill-symlink-collision):
 * Windows-safe, idempotent symlink materialization in downloadFile.
 *
 * Background: the .claude/skills/<ns>:<skill> link farm is materialized from
 * `hq-symlink:<target>` records. Pre-fix, downloadFile always did
 * symlinkSync(temp) + renameSync(temp, dest). On Windows that is doubly
 * broken: (1) rename() can never replace an existing directory — and a
 * directory symlink counts as one — so every pull over the farm EPERM'd,
 * never journaled, and re-downloaded forever; (2) a bare symlinkSync mints a
 * FILE-type link, which is broken for directory targets on Windows.
 *
 * Windows semantics are exercised via the injectable `win32` option (the
 * local-path-codec.ts convention) plus scripted fs fakes, so these tests are
 * deterministic on POSIX CI and on a real Windows host alike.
 */
export {};
//# sourceMappingURL=s3.symlink-materialize.test.d.ts.map