fix: make schema-sync directory renames EXDEV-safe for docker builds

[mikemeier]

Problem

npm run sync-schemas (and therefore schemas:ensure / build:lib) fails inside any docker build where the schema cache is not pre-populated.

During an image build, the working tree is overlayfs. renameSync on a directory that came from a lower image layer (e.g. via COPY . .) fails with EXDEV: cross-device link not permitted even though src and dest are on the same mount — overlayfs cannot rename lower-layer directories. This hits copySkillTree when it snapshots an existing skill dir (skills/adcp-brand -> skills/adcp-brand.previous) and can equally hit replaceTree.

The failure is then misreported: the catch in sync() swallows the error and prints AdCP <version> was not reachable from adcontextprotocol.org, and the GitHub-dist fallback 404s (no dist/ on main), so the build dies with a misleading network error. Bind mounts and normal checkouts are unaffected, which makes this look flaky/environment-specific.

Fix

• Add moveTreeSync: try renameSync, and on EXDEV fall back to cpSync(recursive) + rmSync — overlayfs handles copy+delete fine. Used at all three directory-rename sites (replaceTree x2, copySkillTree).
• Include the original error message in the GitHub-dist fallback warning so extraction failures are no longer misreported as network failures.

Notes

• scripts/-only change (dev tooling, not published in files), so no changeset per CONTRIBUTING policy — happy to add one if you want it anyway.
• Repro: docker build a context containing the repo, run npm run sync-schemas with an empty schemas/cache/. Verified fixed in node:22-alpine builds.

🤖 Generated with Claude Code

[aao-secretariat]

⚠️ Argus review could not complete (no verdict or review body was produced). A human reviewer should take this PR. View workflow run