@mpgd/cli 0.52.0 → 0.53.0

package/templates/phaser-game/apps/target-ait/src/main.ts

@@ -12,6 +12,7 @@ installAitHostBridge({
   adGroupIds: runtimeConfig.adGroupIds,
   adPlacementTypes: runtimeConfig.adPlacementTypes,
   ...iapBridgeOptions(),
+  ...notificationBridgeOptions(),
   ...identityBridgeOptions(),
 });
 
@@ -38,6 +39,20 @@ function iapBridgeOptions(): Pick<
   return runtimeConfig.iapProducts.length === 0 ? {} : { iapProducts: runtimeConfig.iapProducts };
 }
 
+/**
+ * Notifications v2 topics come from the notification topic catalog's
+ * `targets.ait` mappings at build time. Without one the host bridge offers no
+ * notifications event channel, so the game exposes no `notificationsV2`; with
+ * them the bridge asks for each topic's agreement through
+ * `Notification.requestAgreement` and routes notification landings. Agreements
+ * are recorded by the game backend, never trusted from the wrapper.
+ */
+function notificationBridgeOptions(): Pick<InstallAitHostBridgeOptions, 'notificationTopics'> {
+  return Object.keys(runtimeConfig.notificationTopics).length === 0
+    ? {}
+    : { notificationTopics: runtimeConfig.notificationTopics };
+}
+
 function identityBridgeOptions(): Pick<InstallAitHostBridgeOptions, 'dependencies'> {
   return import.meta.env.VITE_MPGD_AIT_MOCK_IDENTITY === '1'
     ? {

package/templates/phaser-game/apps/target-ait/src/runtime-config.types.ts

@@ -8,6 +8,11 @@ declare module 'virtual:mpgd-ait-runtime-config' {
     >>;
     /** Catalog products sold on Apps in Toss (`platformProductIds.ait`), read at build time. */
     readonly iapProducts: readonly import('@mpgd/adapter-ait').AitIapProductConfig[];
+    /** Notifications v2 topics mapped for Apps in Toss (`targets.ait`), read at build time. */
+    readonly notificationTopics: Readonly<Record<
+      string,
+      import('@mpgd/adapter-ait/notification-config').AitNotificationTopicMapping
+    >>;
   }>;
 
   export default runtimeConfig;

package/templates/phaser-game/apps/target-ait/vite.config.ts

@@ -1,14 +1,33 @@
-import { readFileSync } from 'node:fs';
+import { existsSync, readFileSync } from 'node:fs';
+import { resolve } from 'node:path';
+import { fileURLToPath } from 'node:url';
 
 import type { AitIapProductConfig } from '@mpgd/adapter-ait';
 import { extractAitAdBridgeConfig, type AitAdBridgeConfig } from '@mpgd/adapter-ait/ad-config';
 import { extractAitIapProductConfig } from '@mpgd/adapter-ait/iap-config';
+import {
+  readAitNotificationTopicsFile,
+  type AitNotificationTopicMapping,
+} from '@mpgd/adapter-ait/notification-config';
 import ttsc from '@ttsc/unplugin/vite';
 import { defineConfig, type Plugin } from 'vite';
 
 const aitAppName = process.env.MPGD_AIT_APP_NAME?.trim() || '__GAME_NAME__';
 const aitAdConfig = readAitAdConfig(process.env.MPGD_AD_PLACEMENTS_FILE);
 const aitIapProducts = readAitIapProducts(process.env.MPGD_PRODUCT_CATALOG_FILE);
+// Notifications v2 topics come from the notification topic catalog
+// (`targets.ait`), so the wrapper and the backend share one source:
+// MPGD_NOTIFICATION_TOPICS_FILE (a relative path names a file of the game),
+// else notifications/topics.json when it exists. Without a catalog, or with
+// no topic mapped for Apps in Toss, the host bridge exposes no notifications.
+const aitNotificationTopics = readAitNotificationTopicsFile(
+  {
+    configured: process.env.MPGD_NOTIFICATION_TOPICS_FILE,
+    rootDir: fileURLToPath(new URL('../..', import.meta.url)),
+    defaultFile: 'notifications/topics.json',
+  },
+  { existsSync, readFileSync, resolve },
+);
 
 export default defineConfig(({ command, isPreview }) => {
   const enableLocalAitMock = command === 'serve'
@@ -33,6 +52,7 @@ export default defineConfig(({ command, isPreview }) => {
         adGroupIds: aitAdConfig.adGroupIds,
         adPlacementTypes: aitAdConfig.adPlacementTypes,
         iapProducts: aitIapProducts,
+        notificationTopics: aitNotificationTopics,
       }),
       ...(command === 'build'
         ? [ttsc({ project: 'tsconfig.json', plugins: false })]
@@ -51,6 +71,7 @@ function createAitRuntimeConfigPlugin(input: Readonly<{
   readonly adGroupIds: Readonly<Record<string, string>>;
   readonly adPlacementTypes: AitAdBridgeConfig['adPlacementTypes'];
   readonly iapProducts: readonly AitIapProductConfig[];
+  readonly notificationTopics: Readonly<Record<string, AitNotificationTopicMapping>>;
 }>): Plugin {
   const publicId = 'virtual:mpgd-ait-runtime-config';
   const resolvedId = `\0${publicId}`;

package/templates/phaser-game/docs/MPGD_KIT_WORKFLOWS.md

@@ -165,3 +165,17 @@ game-owned production credentials, deployment, signing, or store evidence.
 Use `@mpgd/adapter-browser/oneplay` through `PlatformGateway`. Build and smoke the `oneplay` target with the configured kit path. The adapter initializes the H5 SDK before gameplay; `completeLoading()` awaits host acknowledgement. Exit checkpoints must be synchronous through `storage.saveSync`. Use game-owned issued placement IDs and server verification before enabling ads or purchases. Check final HTTPS hosting headers for both ONE store domain families. See the [ONE play guide](https://github.com/imjlk/mpgd-kit/blob/main/docs/ONEPLAY.md) and [official SDK guide](https://onestore-dev.gitbook.io/dev/tools/web-sdk).
 
 Wire `rewardRequests` and `commerceServer` in `src/platform/buildGateways/oneplay.ts`. Server-only `@mpgd/game-services/oneplay-reward`, `oneplay-purchase-client`, `oneplay-purchase` and `oneplay-pns` provide signed SSV, authenticated checkout intents, API V7 verification, post-ledger consume/acknowledge and signed notification recovery. The game owns durable stores, routes, an encrypted client journal and atomic cancellation fencing. A completed PNS requires completed finalization. Missing ports keep capabilities unavailable; subscriptions are unsupported. See `commerce.checkout.verified-intent` in the game manifest and the ONE play acceptance notes before enabling policies.
+
+## ONEplay official SDK skill
+
+From this game's repository root, install or explicitly refresh the official instructions:
+
+```sh
+npx skills add ONE-store/onestore_web_sdk_skills --agent codex --yes
+```
+
+Review the resulting `.agents/skills/onestore-web-sdk` and `skills-lock.json` diff before committing.
+Use the skill's doctor and pre-release checklist alongside Kit's `docs/ONEPLAY.md`.
+Keep SDK imports in composition, game-services credentials on the server, and rewards behind
+purchase verification / signed SSV. The official standalone HTML template is reference material,
+not a replacement for the generated gateway. Do not refresh skills inside production builds.