@stamprally/server 0.8.0 → 0.10.0

package/README.md

@@ -1,28 +1,20 @@
 # @stamprally/server
 
-Web Standard `Request` / `Response` handlers for server-authoritative stamp rally
-check-ins, reward claims, and offline synchronization.
+Web Standard `Request` / `Response` handlers for server-authoritative check-ins and reward claims.
 
 ```ts
 import { StampRallyServer } from "@stamprally/server";
 
-const server = new StampRallyServer(
-  {
-    id: "spring-rally",
-    secretKey: process.env.RALLY_SECRET ?? "replace-me",
-    stamps: [{ id: "gate", name: { en: "Gate" }, condition: { type: "instant" } }],
-  },
-  storage,
-);
-
+const server = new StampRallyServer(adminConfig, persistence, {
+  authenticate: (request) => request.headers.get("x-user-id"),
+});
 const response = await server.handle(request);
 ```
 
-Provide a Redis-backed `ServerStorageAdapter` in production. Its
-`decrementRewardStock` implementation should use a single atomic Redis
-operation (for example, a Lua script or `DECR` guarded by a non-negative check).
-The built-in `InMemoryServerStorage` is intended for tests and local demos.
+`ServerPersistenceAdapter` scopes locks, reward stock, idempotency records, user state, claim records, and audit logs by `rallyId`. Its `recordUserClaim` operation receives the rally, user, reward, issued ticket number, and timestamp. Use a transactional database or equivalent Redis primitives for multi-instance production deployments.
+
+Hono can mount the handler directly because it accepts the same Web Standard request and response types.
+
+## License
 
-If authentication is already handled by the host application, use
-`authenticate` to return the authenticated user ID. The handler rejects bodies
-that attempt to act for a different user.
+MIT