castle-web-sdk 0.4.9 → 0.4.10

package/README.md

@@ -20,6 +20,7 @@ import { setup, initCard, Storage, Leaderboard } from "castle-web-sdk";
 - [User](#user)
 - [Pass](#pass)
 - [Portal](#portal)
+- [Haptics](#haptics)
 - [Lifecycle](#lifecycle)
 - [Setup](#setup)
 - [CastleError](#castleerror)
@@ -269,6 +270,41 @@ link.addEventListener("pointerenter", () => {
 });
 ```
 
+## Haptics
+
+`Haptics` plays a short device vibration ("buzz") for tactile feedback —
+a tap confirmation, a success chime, an error shake. The host owns the
+effect: the Castle mobile app plays a native haptic, the website uses the
+browser's vibration API where available, and the dev server or an
+unsupported device does nothing.
+
+### `Haptics.play(style): Promise<HapticsResult>`
+
+Plays a haptic in one of seven styles:
+
+- `'light'`, `'medium'`, `'heavy'` — impact taps of increasing strength.
+- `'selection'` — a light tick, e.g. moving through options.
+- `'success'`, `'warning'`, `'error'` — notification patterns.
+
+Usually you don't await it — fire it and move on:
+
+```js
+button.onclick = () => {
+  Haptics.play("light");
+  doTheThing();
+};
+```
+
+The returned `HapticsResult` has a `status`, if you want to branch on it:
+
+- `'triggered'` — the host played (or accepted) the haptic.
+- `'unavailable'` — this host or device can't play haptics (e.g. the dev
+  server, or a browser with no vibration support). Nothing was played.
+
+Haptics respect the player's settings — if a player has muted haptics,
+`play` does nothing and resolves `'unavailable'`. Rapid repeated calls may
+be coalesced, so it's safe to call on frequent events.
+
 ## Lifecycle
 
 `Lifecycle` tells the host when the deck has painted its first frame, so

package/dist/castle.d.ts

@@ -1,5 +1,7 @@
 export { isEdit } from "./context";
 export { CastleError } from "./errors";
+export { Haptics } from "./haptics";
+export type { CastleHapticsApi, HapticsResult, HapticsStatus, HapticStyle } from "./haptics";
 export { Leaderboard } from "./leaderboard";
 export type { LeaderboardData, LeaderboardEntry, LeaderboardOptions, LeaderboardScope, LeaderboardSort, } from "./leaderboard";
 export { Lifecycle } from "./lifecycle";

package/dist/castle.js

@@ -1,6 +1,7 @@
 // Castle Web SDK
 export { isEdit } from "./context";
 export { CastleError } from "./errors";
+export { Haptics } from "./haptics";
 export { Leaderboard } from "./leaderboard";
 export { Lifecycle } from "./lifecycle";
 export { Pass } from "./passes";

package/dist/commands.d.ts

@@ -32,6 +32,11 @@ export type PortalPrefetchStatus = "prefetching" | "rejected" | "unavailable";
 export interface PortalPrefetchResult {
     status: PortalPrefetchStatus;
 }
+export type HapticStyle = "light" | "medium" | "heavy" | "selection" | "success" | "warning" | "error";
+export type HapticsStatus = "triggered" | "unavailable";
+export interface HapticsResult {
+    status: HapticsStatus;
+}
 export interface CommandParams {
     "deckStorage.load": Record<string, never>;
     "deckStorage.update": {
@@ -71,6 +76,9 @@ export interface CommandParams {
     "portal.prefetch": {
         targetDeckId: string;
     };
+    "haptics.play": {
+        style: HapticStyle;
+    };
 }
 export interface CommandResult {
     "deckStorage.load": {
@@ -109,6 +117,7 @@ export interface CommandResult {
     "pass.offer": PassOfferResult;
     "portal.open": PortalOpenResult;
     "portal.prefetch": PortalPrefetchResult;
+    "haptics.play": HapticsResult;
 }
 export type CommandName = keyof CommandParams;
 export interface SerializedCommandError {

package/dist/haptics.d.ts

@@ -0,0 +1,6 @@
+import type { HapticStyle, HapticsResult } from "./commands";
+export type { HapticStyle, HapticsResult, HapticsStatus } from "./commands";
+export interface CastleHapticsApi {
+    play(style: HapticStyle): Promise<HapticsResult>;
+}
+export declare const Haptics: CastleHapticsApi;

package/dist/haptics.js

@@ -0,0 +1,36 @@
+// Haptics — a deck-facing capability for playing a device haptic (a "buzz").
+// Like pass and portal, the deck stays capability-AGNOSTIC: it asks for a
+// haptic and gets back one normalized outcome regardless of platform. The host
+// owns the effect:
+//   - mobile app : plays a native haptic (Taptic Engine / VibrationEffect),
+//                  subject to the host's own rate-limiting and device support
+//   - web player : best-effort navigator.vibrate; `unavailable` where the
+//                  browser has no vibration API (e.g. iOS Safari)
+//   - dev CLI    : no host handler, so `unavailable`
+// A haptic is a fleeting device effect, not deck-scoped state, so unlike
+// pass/portal the host requires no deckId. Decks usually fire-and-forget (don't
+// await); the returned status just says whether the host could play it.
+import { CastleError } from "./errors";
+import { hostRequest } from "./transport";
+const HAPTIC_STYLES = [
+    "light",
+    "medium",
+    "heavy",
+    "selection",
+    "success",
+    "warning",
+    "error",
+];
+export const Haptics = {
+    play,
+};
+async function play(style) {
+    if (!HAPTIC_STYLES.includes(style)) {
+        throw new CastleError({
+            code: "INVALID_ARGUMENT",
+            message: `Haptics.play style must be one of: ${HAPTIC_STYLES.join(", ")}.`,
+            operation: "Haptics.play",
+        });
+    }
+    return hostRequest("haptics.play", { style });
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "castle-web-sdk",
-  "version": "0.4.9",
+  "version": "0.4.10",
   "type": "module",
   "main": "dist/castle.js",
   "types": "dist/castle.d.ts",