feat: add unstorage state adapter

[Schniz]

Summary

• add a new @chat-adapter/state-unstorage package implementing the full StateAdapter surface on top of unstorage, with JSDoc for in-IDE docs
• include a comprehensive test suite mirroring state adapter compatibility scenarios (locks, cache, lists, queue, connection behavior) and switch subscriptions to per-key storage (sub:<threadId>) to avoid list RMW
• wire the new package into workspace/integration checks and update docs/catalog references across README, docs pages, adapters catalog, and chat skill table

Validation

• pnpm --filter @chat-adapter/state-unstorage test
• pnpm --filter @chat-adapter/state-unstorage build
• pnpm --filter @chat-adapter/integration-tests test
• pnpm validate

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
chat	Ready	Preview, Comment, Open in v0	Apr 8, 2026 2:59am
chat-sdk-nextjs-chat	Ready	Preview, Comment, Open in v0	Apr 8, 2026 2:59am

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	unstorage@​1.17.5

View full report

[Schniz]

this might not be good enough to ship because any read-manipulate-write code path will require distributed locking, which is not really possible with unstorage's api

at least until we will have unlock

could've been nice if we could ship that somehow though. maybe someone else has an idea?