fix: pin @altimateai/altimate-core to exact version to prevent stale binaries

Change `^0.2.5` → `0.2.5` so npm/pnpm/bun won't skip re-downloading
when a newer version is published. With the caret range, package managers
could serve a cached `0.2.5` binary even after `0.2.6` ships, causing
missing export errors at runtime.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: anandgupta42

bun.lock

@@ -78,7 +78,7 @@
     "@ai-sdk/togetherai": "1.0.34",
     "@ai-sdk/vercel": "1.0.33",
     "@ai-sdk/xai": "2.0.51",
-    "@altimateai/altimate-core": "^0.2.5",
+    "@altimateai/altimate-core": "0.2.5",
     "@altimateai/drivers": "workspace:*",
     "@aws-sdk/credential-providers": "3.993.0",
     "@clack/prompts": "1.0.0-alpha.1",