examples/integrations: unpin @relayfile/mount-* (use workspace/* range) to prevent future lockfile drift

[khaliqgant]

Problem

The examples/integrations/* projects (shipped via #309) commit package-lock.json files that pin @relayfile/mount-* to a fixed version (6–12 refs each across langchain-, openai-agents-, vercel-ai-sdk-* examples).

These example lockfiles are not in publish.yml's version-bump list, so the lockfile-regen automation added in #308 / PR #314 does not cover them. Today this is harmless (no example is wired into an npm ci CI job), but the day one is, it becomes the next recurring npm ci drift surface — the same class of break #308 just fixed for the root + SDK lockfiles.

Fix

Have the example projects reference @relayfile/mount-* (and other @relayfile/* deps) via a non-pinned range — */latest or a workspace/file: reference — so their lockfiles never pin a specific published version and can't drift on release.

Notes

• Surfaced by the issue-sweep verification gate during chore(release): version-bump must regenerate package-lock.json files (recurring npm ci CI break) #308 review (documented as out-of-scope in PR fix(release): regenerate lockfiles before tagging (#308) #314).
• Preventive hardening; no current bug.
• Effort: S.