feat: Add KV storage facet

[jmoseley]

Summary

• implement new key-value storage API under gensx-storage
• support filesystem-backed KV with TTL handling
• provide KVClient and useKV helpers
• export KV facet in package index
• add basic tests for the KV filesystem implementation and usage helpers

Testing

• pnpm lint
• pnpm test (fails: create-gensx#test)
• pnpm format

---

https://chatgpt.com/codex/tasks/task_e_6841deb474f0832c81a09484e22d2581

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
gensx-docs	⬜️ Skipped (Inspect)			Jun 5, 2025 6:34pm
gensx-home	⬜️ Skipped (Inspect)			Jun 5, 2025 6:34pm

[cursor]

Bug: KVClient Ignores User-Provided RootDir

In the KVClient constructor, the logic for determining the filesystem rootDir incorrectly checks options.kind instead of the resolved kind variable. Consequently, a user-provided options.rootDir is ignored when options.kind is undefined but kind defaults to 'filesystem', resulting in the default path being used instead of the specified directory.

packages/gensx-storage/src/kv/kvClient.ts#L16-L20

gensx/packages/gensx-storage/src/kv/kvClient.ts

Lines 16 to 20 in 13145c6

	if (kind === "filesystem") {
	const rootDir =
	options.kind === "filesystem" && options.rootDir
	? options.rootDir
	: join(process.cwd(), ".gensx", "kv");

Fix in Cursor

---

BugBot free trial expires on June 9, 2025
Your team has used $0.00 of the $50.00 spend limit so far. Team admins can manage spend limit in the Cursor dashboard.

Was this report helpful? Give feedback by reacting with 👍 or 👎

[github-actions]

Hey mate 👋. Thank you for opening this Pull Request 🤘. It is really awesome to see this contribution 🚀

🔎 When working with this project we are requesting to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted 🥶.

👇 Bellow you can find details about what failed:

No release type found in pull request title "Add KV storage facet". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit