feat(cache): add per-tool cache key prefixing and improve API clarity

[Yuripetusko]

Summary

This PR adds per-tool cache key prefixing to prevent cache collisions between different tools using the same parameters, and improves Redis key organization with clearer hierarchy.

Fixes #91

Problem

Cache keys could clash between different tools when using the same parameters. For example, a weather tool and news tool both receiving { location: "NYC" } would generate the same cache key, causing incorrect cached results.

Key Changes

New Features:

• Per-tool prefixing: Add toolName option to namespace cache keys per tool
• Configurable separator: Add keySeparator option (default ":")
• Clearer naming: cacheKeyContext replaces cacheKey (better reflects it's a suffix)

Breaking Changes:

• keyPrefix → storeName in RedisCacheStore and CacheBackendConfig
• Default changed from "ai-tools-cache:" to "ai-tools-cache" (separator added automatically)
• keyGenerator signature changed from positional to object parameters

Deprecations:

• cacheKey deprecated in favor of cacheKeyContext (backward compatible)

Migration Examples

keyGenerator

// Before
const keyGenerator = (params: any, context?: any): string => {
  return `custom-${JSON.stringify(params)}`;
};

// After
const keyGenerator = ({ params, context, toolName, keySeparator }: {
  params: any;
  context?: any;
  toolName?: string;
  keySeparator?: string;
}): string => {
  return `custom-${JSON.stringify(params)}`;
};

Usage Example

const weatherTool = createCached(tool({ /* ... */ }), {
  toolName: "weather",
  ttl: 3600
});

const newsTool = createCached(tool({ /* ... */ }), {
  toolName: "news",
  ttl: 1800
});

Keys structure: storeName:toolName:params:context

Note: there are breaking changes, not sure if contributors are suppose to run changeset?

[vercel]

@Yuripetusko is attempting to deploy a commit to the Pontus Abrahamsson's projects Team on Vercel.

A member of the Team first needs to authorize it.