docs: add Helicone + Valkey vector store cookbook

[rileydes-improving]

Summary

Adds a new cookbook demonstrating how Helicone's Jawn API server uses Valkey for caching,
rate limiting, and encrypted key storage through 5 distinct subsystems, all via core Valkey
commands (GET, SET EX, SET PX, INCR, PTTL, PEXPIRE, SCRIPT LOAD, EVALSHA)
with zero modules required. The cookbook includes two skill-level guides, a plain JavaScript
sample with a simulate script and integration tests, and a CI workflow.

Cookbook Pages

Page	Level	Description
01-getting-started.md	Beginner	Local setup with Docker Compose and basic KV cache and rate limiting operations
02-production.md	Intermediate	TLS configuration, Lua scripting, monitoring, and encrypted storage

What's Included

cookbooks/framework-integrations/helicone/
├── README.md
├── 01-getting-started.md
├── 02-production.md
└── sample/
    ├── docker-compose.yml
    ├── .env.example
    ├── .gitignore
    ├── README.md
    ├── package.json
    ├── scripts/
     │   ├── health_check.mjs
     │   └── simulate_helicone.mjs
    └── tests/
        └── test_helicone_patterns.mjs

.github/workflows/cookbook-helicone.yml

Testing

• Integration tests run with Node.js built-in node:test runner
• Scenarios tested:
  • GET/SET PX — KV cache with millisecond TTL and expiry verification
  • GET/SET EX — Sliding window rate limiting with second-precision TTL
  • INCR/PTTL/PEXPIRE — Atomic counter operations with millisecond TTL
  • SCRIPT LOAD/EVALSHA — Lua script registration and execution, including NOSCRIPT
  • GET/SET EX — Cache-aside usage limit pattern
  • GET/SET EX — SHA-256 hashed key storage for encrypted values
• All tests run against valkey/valkey:8.1-alpine

Upstream Status

Related upstream PR for Valkey support in Helicone: helicone/helicone — Valkey integration

Notes

• The encrypted key cache section shows the Valkey pattern (hashed key + SET EX) with a comment that the app handles AES-GCM; crypto is not in scope for the sample
• Cookbook is vendor-neutral: no specific cloud provider, managed service, or proprietary tooling is recommended
• Only core Valkey commands are used, no modules or extensions required
• All dependencies in package.json use pinned (exact) versions
• All localhost URLs in Markdown are inside fenced code blocks or inline code spans
• The client library matches Helicone's actual production implementation

[jbrinkman]

Closing this draft PR as part of a cookbook program cleanup.