@syntrologie/adapt-gamification 2.8.0-canary.152 → 2.8.0-canary.154

package/dist/cdn.d.ts

@@ -0,0 +1,47 @@
+/**
+ * CDN Entry Point for Adaptive Gamification
+ *
+ * Bundled for CDN delivery and loaded on-demand by the host runtime's
+ * AppLoader when a config references gamification actions/widgets.
+ *
+ * Mirrors the pattern in adaptive-mcp/src/cdn.ts: builds the manifest from
+ * the runtime export, then self-registers with the host's app registry on
+ * import. The host's AppLoader fetches this bundle, esbuild's IIFE wrapper
+ * runs the registration, and AppRegistry.activate() can then wire the
+ * executors into the runtime.
+ *
+ * Without this entry, the build script (build-adaptives-only.js) silently
+ * skips the package — gamification ends up "lazy in name only" with no
+ * bundle on disk, and any config using `gamification:awardBadge` /
+ * `gamification:addPoints` hits "Unknown action kind".
+ */
+export declare const manifest: {
+    id: string;
+    version: string;
+    name: string;
+    description: string;
+    runtime: {
+        actions: {
+            kind: "gamification:awardBadge" | "gamification:addPoints";
+            executor: import("packages/sdk-contracts/dist").ActionExecutor<import("./runtime").AwardBadgeAction> | import("packages/sdk-contracts/dist").ActionExecutor<import("./runtime").AddPointsAction>;
+        }[];
+        events: {
+            names: string[];
+            handler: (_event: unknown, _ctx: unknown) => void;
+        }[];
+    };
+    metadata: {
+        isBuiltIn: boolean;
+    };
+};
+declare global {
+    interface Window {
+        SynOS?: {
+            appRegistry?: {
+                register?: (m: unknown) => void;
+            };
+        };
+    }
+}
+export default manifest;
+//# sourceMappingURL=cdn.d.ts.map

package/dist/cdn.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"cdn.d.ts","sourceRoot":"","sources":["../src/cdn.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AAIH,eAAO,MAAM,QAAQ;;;;;;;;;;;;;;;;;;CAYpB,CAAC;AAEF,OAAO,CAAC,MAAM,CAAC;IACb,UAAU,MAAM;QACd,KAAK,CAAC,EAAE;YACN,WAAW,CAAC,EAAE;gBACZ,QAAQ,CAAC,EAAE,CAAC,CAAC,EAAE,OAAO,KAAK,IAAI,CAAC;aACjC,CAAC;SACH,CAAC;KACH;CACF;AASD,eAAe,QAAQ,CAAC"}

package/dist/cdn.js

@@ -0,0 +1,38 @@
+/**
+ * CDN Entry Point for Adaptive Gamification
+ *
+ * Bundled for CDN delivery and loaded on-demand by the host runtime's
+ * AppLoader when a config references gamification actions/widgets.
+ *
+ * Mirrors the pattern in adaptive-mcp/src/cdn.ts: builds the manifest from
+ * the runtime export, then self-registers with the host's app registry on
+ * import. The host's AppLoader fetches this bundle, esbuild's IIFE wrapper
+ * runs the registration, and AppRegistry.activate() can then wire the
+ * executors into the runtime.
+ *
+ * Without this entry, the build script (build-adaptives-only.js) silently
+ * skips the package — gamification ends up "lazy in name only" with no
+ * bundle on disk, and any config using `gamification:awardBadge` /
+ * `gamification:addPoints` hits "Unknown action kind".
+ */
+import { eventHandlers, executors, runtime } from './runtime';
+export const manifest = {
+    id: runtime.id,
+    version: runtime.version,
+    name: runtime.name,
+    description: runtime.description,
+    runtime: {
+        actions: executors.map(({ kind, executor }) => ({ kind, executor })),
+        events: eventHandlers,
+    },
+    metadata: {
+        isBuiltIn: false,
+    },
+};
+if (typeof window !== 'undefined') {
+    const registry = window.SynOS?.appRegistry;
+    if (registry && typeof registry.register === 'function') {
+        registry.register(manifest);
+    }
+}
+export default manifest;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@syntrologie/adapt-gamification",
-  "version": "2.8.0-canary.152",
+  "version": "2.8.0-canary.154",
   "description": "Adaptive Gamification app - Badges, rewards, points, and engagement mechanics",
   "license": "Proprietary",
   "private": false,