@idosgames/mcp 0.1.44 → 0.1.46

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@idosgames/mcp",
-  "version": "0.1.44",
+  "version": "0.1.46",
   "mcpName": "com.idosgames/sdk",
   "description": "MCP server that serves the iDosGames Module & Skills Registry to AI coding agents (Claude Code, Codex, Cursor…): list/pull composable game modules and the host scaffold, and load skills for @idosgames/core, the module contract, and composition.",
   "type": "module",

package/registry/host.json

@@ -15,7 +15,7 @@
     },
     {
       "path": "IDOS.md",
-      "content": "# IDOS.md — project guide\n\nEvery AI agent working on this game reads this file first: the platform's AI editor loads it into\ncontext on every run, and external agents reach it through `AGENTS.md` / `CLAUDE.md`. Keep it short\nand evergreen — what the game is, how the project is laid out, rules that hold for all of it. The\nhistory of individual features does NOT belong here (see \"Feature history\" at the end).\n\n## This game\n\n<!-- 2–4 lines, filled in once the direction is clear: genre, core loop, target platform, tone.\n     Update it when the concept changes — not with every feature. -->\n\n_Not described yet._\n\n## Installed modules\n\nMirror of the `modules` array in `src/modules.ts` (the source of truth), maintained by the\nplatform — do not edit by hand.\n\n<!-- idos:modules:start -->\n\n_None yet._\n<!-- idos:modules:end -->\n\n## How the project is built\n\n**The base + modules** on the iDosGames SDK. The base is sign-in and the lobby; everything else — the\nsystems (shop, heroes, leaderboards…) and the games — is a module. Two kinds of game:\n\n- a game whose route says `inLobby: true` (idle-rpg) lives INSIDE the lobby: after sign-in the player\n  lands in it, the lobby's balances and profile on top, its tabs at the bottom, \"Play\" is the game\n  itself, any other tab opens that system's screen (the base's game frame - the host's\n  `header`/`footer` panel slots lay the game out between them);\n- any other game (voxelcraft, board-game) takes the whole screen: sign-in → the lobby, \"Play\" launches\n  it, a small button over the game returns to the lobby.\n\n- `src/main.tsx` — creates ONE `IDosGamesClient` and calls `mountHost(...)` with the base first, then\n  the modules. The host signs the player in before any module runs; modules never create a client or\n  log in themselves.\n- **The base** — sign-in, the play-access screen and the lobby (tabs, balances, wallet, profile, \"Play\") —\n  is NOT project code: it lives in `@idosgames/app-shell` (`createBaseModule`, `DefaultLoginScreen`,\n  `DefaultPlayAccessScreen`) and `src/main.tsx` mounts it. You configure it: `src/app.config.ts`,\n  `src/ui.config.ts`, and the wallet stack in `src/walletLogin.tsx` / `src/walletButton.tsx`. It takes\n  the shared-UI roles `currency-bar`, `wallet`, `account`, `menu`, `modes`, so a game hides its own\n  balances and wallet by itself (`ctx.sharedUi.shouldDraw`) — don't edit games for that.\n- `src/app.config.ts` — what happens after sign-in (`start`: `\"game\"` — straight into the game, the\n  default; `\"lobby\"`; or a game's mode id) and the order of the lobby's tabs. The look, animations and sounds of the WHOLE app — sign-in included:\n  `src/ui.config.ts` (the only file a restyle edits; see the `idosgames-ui-kit` skill).\n- `src/modules.ts` — the composition list. **Regenerated by the platform** whenever modules are\n  installed or removed, so it holds only the imports and the `modules` array — nothing else. It is\n  also the list of what the app has: remove a system here and its tab is gone.\n- `src/modules/<id>/` — one folder per module: the catalog's systems and games and the game's own\n  modules alike. A system registers its screen with `ctx.features.register` (a lobby tab) and hides it\n  while the title has nothing for it (`available: false` + `ctx.features.setAvailable`); a game\n  registers a route (`ctx.registerRoute`) and gets a \"Play\" button.\n- `src/shared/` — created when needed: code two or more of this game's modules share.\n- `src/idos.title.ts` — **generated, do not edit.** The project's identity: which Title's data this\n  game reads and writes, baked in so a packaged mobile build or an iframe embed still knows it.\n- `src/config.ts` — **platform-owned, do not edit** (the build packs the platform's copy over it).\n  Resolves the effective title and environment: identity from `src/idos.title.ts`, DEV vs PROD from\n  the address (`{id}-dev.idos.games` vs `{id}.idos.games`) — never from the link's query. Never read\n  the title from the URL yourself: use `client.titleID`, or `ctx.titleId` inside a module's `setup()`.\n- `src/env.ts` — build-time values from `.env.local` (local development only).\n- `src/walletLogin.tsx` — the wallet sign-in button, generated for web3 titles; safe to edit.\n- `idos.modules.lock.json` — **platform-owned, do not edit.** Which modules came from the catalog,\n  their versions and file fingerprints — so updating a module never silently overwrites your edits.\n\n## Where new code goes\n\nFull standard: the `idosgames-project-structure` skill — load it before creating a module, touching\n`src/shared/`, or moving code around.\n\n- A catalog module already does it (a shop, heroes, leaderboards, rewards, …) → install that module\n  instead of rebuilding it.\n- It extends an existing module → change that module. The lobby, sign-in, balances, wallet and\n  profile are the SDK's base - configure it (`src/app.config.ts`, `src/ui.config.ts`), do not rebuild it.\n- It is its own mode, screen or system → a NEW module `src/modules/<feature-id>/` (kebab-case):\n  `index.ts` exporting `<camelCaseId>Module`, `module.ts`, `module.meta.json`, and as needed\n  `components/` (React UI), `game/` (engine & simulation), `data/` (static tables), `react/` (hooks,\n  context). Register it in `src/modules.ts`. A screen → `ctx.features.register` (it becomes a lobby\n  tab); a mode of its own → `ctx.registerRoute` (it gets a \"Play\" button).\n- To open another system's screen from your code: `ctx.features.open(\"store\")` — never import it. To\n  switch modes: `ctx.navigate(\"lobby\")` or a game's mode id. Other UI shown over every mode → a panel\n  with `activeOnly: false`.\n- Modules never reach into each other: a module imports only its own folder, `src/shared/` and npm\n  packages — never another module's files or host files. Durable shared state lives in the SDK\n  client; live signals go through `ctx.events` with typed topics\n  (`defineTopic(\"<module-id>:<event>@1\", shape({…}))`) declared in the module's `module.meta.json`;\n  to listen to another module, copy its topic, never import it.\n- `src/shared/` holds code TWO or more modules need (code one module needs stays inside it), by\n  purpose — `shared/ui/`, `shared/types/`, `shared/utils/`: types, constants, UI, pure helpers; no\n  game state or logic. It never imports a module.\n- When a change adds a new responsibility to a file past ~400 lines, put that part in its own file.\n\n## The SDK is npm packages — its source is NOT in this project\n\n`@idosgames/core`, `@idosgames/react`, `@idosgames/module-sdk`, `@idosgames/app-shell` are\ndependencies in `package.json`. There is no `node_modules` to read and no `.d.ts` to inspect here,\nso **you cannot discover the SDK's API by reading files in this project.**\n\n1. **Load the matching skill first.** Skills are the authoritative recipes for this SDK — one per\n   service (store, currency, item, quest, leaderboard, auth, blockchain, …).\n2. Then copy the patterns from the modules already in `src/modules/`.\n3. Never invent an SDK method, hook, or type name — it looks plausible and fails the build.\n\n`client.<service>.<action>()` returns `OperationResult<T>` (check `isOk` / `isFail`; it does not\nthrow). In React, reach the client with `useIDosGamesClient()` and player state with\n`useUserState()` from `@idosgames/react`.\n\n## Backend features live in the Title configuration, not in this repo\n\nCurrencies, items, characters, store offers, quests, lootboxes, leaderboards and seasons are\nconfigured per environment in the platform. There is **no config file in this project** — do not\ncreate `config/*.json`; it would be ignored. Write code against ids that exist in the title; if a\nfeature needs an entity that is not configured yet, name exactly what has to be added instead of\ninventing ids.\n\n## Stack & running\n\n- React 19 + TypeScript (strict) + Vite 8. Game engines (three.js, Phaser) arrive with the modules\n  that use them.\n- In the platform's AI editor there is no terminal and no package install: the project is built on\n  the server after each turn and shown in the live preview. Use only what `package.json` lists.\n- Locally (exported project or an external agent): `npm install`, then `npm run dev`,\n  `npm run build`, `npm run typecheck`.\n- Client code ships to players: never put secrets, keys or tokens in any file here.\n- Assets are not stored in the project — generated images/audio/3D are CDN URLs; reference those.\n\n## Feature history — how this project remembers\n\nThis file stays short on purpose: it is loaded on every run, so every paragraph here is paid for\nby all future work. When a game system or feature is done and something about it is worth\nremembering that the code does not show — why it is designed this way, a non-obvious constraint,\na decision the user made — write it to `docs/feature-history/<slug>.md` (one file per system;\nupdate that file when the system changes) and add ONE line to `docs/feature-history/README.md`:\n`- [Title](slug.md) — one-line gist`. Never append a feature write-up to this file. Those entries\nare not loaded automatically: open the relevant one before changing that system.\n"
+      "content": "# IDOS.md — project guide\n\nEvery AI agent working on this game reads this file first: the platform's AI editor loads it into\ncontext on every run, and external agents reach it through `AGENTS.md` / `CLAUDE.md`. Keep it short\nand evergreen — what the game is, how the project is laid out, rules that hold for all of it. The\nhistory of individual features does NOT belong here (see \"Feature history\" at the end).\n\n## This game\n\n<!-- 2–4 lines, filled in once the direction is clear: genre, core loop, target platform, tone.\n     Update it when the concept changes — not with every feature. -->\n\n_Not described yet._\n\n## Installed modules\n\nMirror of the `modules` array in `src/modules.ts` (the source of truth), maintained by the\nplatform — do not edit by hand.\n\n<!-- idos:modules:start -->\n\n_None yet._\n<!-- idos:modules:end -->\n\n## How the project is built\n\n**The base + modules** on the iDosGames SDK. The base is sign-in and the lobby; everything else — the\nsystems (shop, heroes, leaderboards…) and the games — is a module. Two kinds of game:\n\n- a game whose route says `inLobby: true` (idle-rpg) lives INSIDE the lobby: after sign-in the player\n  lands in it, the lobby's balances and profile on top, its tabs at the bottom, \"Play\" is the game\n  itself, any other tab opens that system's screen (the base's game frame - the host's\n  `header`/`footer` panel slots lay the game out between them);\n- any other game (voxelcraft) takes the whole screen: sign-in → straight into it too (when no game\n  lives inside the lobby), a small button over the game returns to the lobby.\n\nAfter sign-in the player is always IN the game, never on a \"Play\" button; the menus (lobby tabs) open\nfrom inside it.\n\n- `src/main.tsx` — creates ONE `IDosGamesClient` and calls `mountHost(...)` with the base first, then\n  the modules. The host signs the player in before any module runs; modules never create a client or\n  log in themselves.\n- **The base** — sign-in, the play-access screen and the lobby (tabs, balances, wallet, profile, \"Play\") —\n  is NOT project code: it lives in `@idosgames/app-shell` (`createBaseModule`, `DefaultLoginScreen`,\n  `DefaultPlayAccessScreen`) and `src/main.tsx` mounts it. You configure it: `src/app.config.ts`,\n  `src/ui.config.ts`, and the wallet stack in `src/walletLogin.tsx` / `src/walletButton.tsx`. It takes\n  the shared-UI roles `currency-bar`, `wallet`, `account`, `menu`, `modes`, so a game hides its own\n  balances and wallet by itself (`ctx.sharedUi.shouldDraw`) — don't edit games for that.\n- `src/app.config.ts` — what happens after sign-in (`start`: `\"game\"` — straight into the game, the\n  default; `\"lobby\"`; or a game's mode id) and the order of the lobby's tabs. The look, animations and sounds of the WHOLE app — sign-in included:\n  `src/ui.config.ts` (the only file a restyle edits; see the `idosgames-ui-kit` skill).\n- `src/modules.ts` — the composition list. **Regenerated by the platform** whenever modules are\n  installed or removed, so it holds only the imports and the `modules` array — nothing else. It is\n  also the list of what the app has: remove a system here and its tab is gone.\n- `src/modules/<id>/` — one folder per module: the catalog's systems and games and the game's own\n  modules alike. A system registers its screen with `ctx.features.register` (a lobby tab) and hides it\n  while the title has nothing for it (`available: false` + `ctx.features.setAvailable`); a game\n  registers a route (`ctx.registerRoute`) and gets a \"Play\" button.\n- `src/shared/` — created when needed: code two or more of this game's modules share.\n- `src/idos.title.ts` — **generated, do not edit.** The project's identity: which Title's data this\n  game reads and writes, baked in so a packaged mobile build or an iframe embed still knows it.\n- `src/config.ts` — **platform-owned, do not edit** (the build packs the platform's copy over it).\n  Resolves the effective title and environment: identity from `src/idos.title.ts`, DEV vs PROD from\n  the address (`{id}-dev.idos.games` vs `{id}.idos.games`) — never from the link's query. Never read\n  the title from the URL yourself: use `client.titleID`, or `ctx.titleId` inside a module's `setup()`.\n- `src/env.ts` — build-time values from `.env.local` (local development only).\n- `src/walletLogin.tsx` — the wallet sign-in button, generated for web3 titles; safe to edit.\n- `idos.modules.lock.json` — **platform-owned, do not edit.** Which modules came from the catalog,\n  their versions and file fingerprints — so updating a module never silently overwrites your edits.\n\n## Where new code goes\n\nFull standard: the `idosgames-project-structure` skill — load it before creating a module, touching\n`src/shared/`, or moving code around.\n\n- A catalog module already does it (a shop, heroes, leaderboards, rewards, …) → install that module\n  instead of rebuilding it.\n- It extends an existing module → change that module. The lobby, sign-in, balances, wallet and\n  profile are the SDK's base - configure it (`src/app.config.ts`, `src/ui.config.ts`), do not rebuild it.\n- It is its own mode, screen or system → a NEW module `src/modules/<feature-id>/` (kebab-case):\n  `index.ts` exporting `<camelCaseId>Module`, `module.ts`, `module.meta.json`, and as needed\n  `components/` (React UI), `game/` (engine & simulation), `data/` (static tables), `react/` (hooks,\n  context). Register it in `src/modules.ts`. A screen → `ctx.features.register` (it becomes a lobby\n  tab); a mode of its own → `ctx.registerRoute` (it gets a \"Play\" button).\n- To open another system's screen from your code: `ctx.features.open(\"store\")` — never import it. To\n  switch modes: `ctx.navigate(\"lobby\")` or a game's mode id. Other UI shown over every mode → a panel\n  with `activeOnly: false`.\n- Modules never reach into each other: a module imports only its own folder, `src/shared/` and npm\n  packages — never another module's files or host files. Durable shared state lives in the SDK\n  client; live signals go through `ctx.events` with typed topics\n  (`defineTopic(\"<module-id>:<event>@1\", shape({…}))`) declared in the module's `module.meta.json`;\n  to listen to another module, copy its topic, never import it.\n- `src/shared/` holds code TWO or more modules need (code one module needs stays inside it), by\n  purpose — `shared/ui/`, `shared/types/`, `shared/utils/`: types, constants, UI, pure helpers; no\n  game state or logic. It never imports a module.\n- When a change adds a new responsibility to a file past ~400 lines, put that part in its own file.\n\n## The SDK is npm packages — its source is NOT in this project\n\n`@idosgames/core`, `@idosgames/react`, `@idosgames/module-sdk`, `@idosgames/app-shell` are\ndependencies in `package.json`. There is no `node_modules` to read and no `.d.ts` to inspect here,\nso **you cannot discover the SDK's API by reading files in this project.**\n\n1. **Load the matching skill first.** Skills are the authoritative recipes for this SDK — one per\n   service (store, currency, item, quest, leaderboard, auth, blockchain, …).\n2. Then copy the patterns from the modules already in `src/modules/`.\n3. Never invent an SDK method, hook, or type name — it looks plausible and fails the build.\n\n`client.<service>.<action>()` returns `OperationResult<T>` (check `isOk` / `isFail`; it does not\nthrow). In React, reach the client with `useIDosGamesClient()` and player state with\n`useUserState()` from `@idosgames/react`.\n\n## Backend features live in the Title configuration, not in this repo\n\nCurrencies, items, characters, store offers, quests, lootboxes, leaderboards and seasons are\nconfigured per environment in the platform. There is **no config file in this project** — do not\ncreate `config/*.json`; it would be ignored. Write code against ids that exist in the title; if a\nfeature needs an entity that is not configured yet, name exactly what has to be added instead of\ninventing ids.\n\n## Stack & running\n\n- React 19 + TypeScript (strict) + Vite 8. Game engines (three.js, Phaser) arrive with the modules\n  that use them.\n- In the platform's AI editor there is no terminal and no package install: the project is built on\n  the server after each turn and shown in the live preview. Use only what `package.json` lists.\n- Locally (exported project or an external agent): `npm install`, then `npm run dev`,\n  `npm run build`, `npm run typecheck`.\n- Client code ships to players: never put secrets, keys or tokens in any file here.\n- Assets are not stored in the project — generated images/audio/3D are CDN URLs; reference those.\n\n## Feature history — how this project remembers\n\nThis file stays short on purpose: it is loaded on every run, so every paragraph here is paid for\nby all future work. When a game system or feature is done and something about it is worth\nremembering that the code does not show — why it is designed this way, a non-obvious constraint,\na decision the user made — write it to `docs/feature-history/<slug>.md` (one file per system;\nupdate that file when the system changes) and add ONE line to `docs/feature-history/README.md`:\n`- [Title](slug.md) — one-line gist`. Never append a feature write-up to this file. Those entries\nare not loaded automatically: open the relevant one before changing that system.\n"
     },
     {
       "path": "index.html",
@@ -23,7 +23,7 @@
     },
     {
       "path": "package.json",
-      "content": "{\n  \"name\": \"@idosgames/base-template\",\n  \"version\": \"0.0.0\",\n  \"private\": true,\n  \"type\": \"module\",\n  \"description\": \"The base every AI Coder project starts from: sign-in and the lobby (both from @idosgames/app-shell) on the host shell. The systems (shop, heroes, leaderboards…) and the games are modules plugged in via src/modules.ts.\",\n  \"scripts\": {\n    \"dev\": \"vite\",\n    \"build\": \"vite build\",\n    \"preview\": \"vite preview\",\n    \"typecheck\": \"tsc --noEmit -p tsconfig.json\"\n  },\n  \"//\": \"Versions are pinned exactly: this is a seed for AI Coder projects, which build offline against a dependency allowlist baked at these versions (see scripts/pack-builder.mjs). Modules bring their own engine deps (three/phaser) when added.\",\n  \"dependencies\": {\n    \"@idosgames/app-shell\": \"0.16.4\",\n    \"@idosgames/core\": \"0.25.0\",\n    \"@idosgames/module-sdk\": \"0.13.2\",\n    \"@idosgames/react\": \"0.6.3\",\n    \"@idosgames/wallet\": \"0.6.8\",\n    \"@reown/appkit\": \"1.8.23\",\n    \"@reown/appkit-adapter-wagmi\": \"1.8.23\",\n    \"@tanstack/react-query\": \"5.101.2\",\n    \"react\": \"19.2.7\",\n    \"react-dom\": \"19.2.7\",\n    \"wagmi\": \"3.7.2\"\n  },\n  \"devDependencies\": {\n    \"@types/react\": \"19.2.17\",\n    \"@types/react-dom\": \"19.2.3\",\n    \"@vitejs/plugin-react\": \"6.0.4\",\n    \"typescript\": \"5.9.3\",\n    \"vite\": \"8.1.5\"\n  }\n}\n"
+      "content": "{\n  \"name\": \"@idosgames/base-template\",\n  \"version\": \"0.0.0\",\n  \"private\": true,\n  \"type\": \"module\",\n  \"description\": \"The base every AI Coder project starts from: sign-in and the lobby (both from @idosgames/app-shell) on the host shell. The systems (shop, heroes, leaderboards…) and the games are modules plugged in via src/modules.ts.\",\n  \"scripts\": {\n    \"dev\": \"vite\",\n    \"build\": \"vite build\",\n    \"preview\": \"vite preview\",\n    \"typecheck\": \"tsc --noEmit -p tsconfig.json\"\n  },\n  \"//\": \"Versions are pinned exactly: this is a seed for AI Coder projects, which build offline against a dependency allowlist baked at these versions (see scripts/pack-builder.mjs). Modules bring their own engine deps (three/phaser) when added.\",\n  \"dependencies\": {\n    \"@idosgames/app-shell\": \"0.16.6\",\n    \"@idosgames/core\": \"0.26.1\",\n    \"@idosgames/module-sdk\": \"0.13.3\",\n    \"@idosgames/react\": \"0.7.1\",\n    \"@idosgames/wallet\": \"0.6.10\",\n    \"@reown/appkit\": \"1.8.23\",\n    \"@reown/appkit-adapter-wagmi\": \"1.8.23\",\n    \"@tanstack/react-query\": \"5.101.2\",\n    \"react\": \"19.2.7\",\n    \"react-dom\": \"19.2.7\",\n    \"wagmi\": \"3.7.2\"\n  },\n  \"devDependencies\": {\n    \"@types/react\": \"19.2.17\",\n    \"@types/react-dom\": \"19.2.3\",\n    \"@vitejs/plugin-react\": \"6.0.4\",\n    \"typescript\": \"5.9.3\",\n    \"vite\": \"8.1.5\"\n  }\n}\n"
     },
     {
       "path": "public/sw.js",
@@ -31,7 +31,7 @@
     },
     {
       "path": "src/app.config.ts",
-      "content": "import { defineAppConfig } from \"@idosgames/app-shell\";\n\n// What happens after sign-in and how the lobby is ordered. The look, animations and sounds are in\n// ./ui.config.ts. Which systems (shop, heroes, leaderboards…) and games the app has is\n// ./modules.ts: remove a module there and its tab is gone. A tab whose system has nothing configured\n// on the title yet (no store offers, no heroes…) stays hidden from players by itself.\n//\n// Everything is optional; uncomment and edit.\nexport default defineAppConfig({\n  // \"game\" — sign-in → straight into a game that lives inside the lobby (idle-rpg); an app whose\n  // games take the whole screen (voxelcraft, board-game) starts in the lobby. \"lobby\" — always\n  // sign-in → lobby → \"Play\". The mode id of a game (\"voxelcraft\") starts in that one.\n  start: \"game\",\n  lobby: {\n    // order: [\"play\", \"store\", \"character\"], // these tabs first, in this order\n    // primary: [\"season\"],                    // also a main tab rather than under \"More\"\n  },\n  auth: {\n    // The \"Play as guest\" button on the sign-in screen is OFF by default; uncomment to show it.\n    // guest: true,\n    // On the idosgames.com game page the player enters with their site account by itself (not signed\n    // in there — the site shows its sign-in window). On by default; uncomment to keep this screen.\n    // platformSignIn: false,\n  },\n});\n"
+      "content": "import { defineAppConfig } from \"@idosgames/app-shell\";\n\n// What happens after sign-in and how the lobby is ordered. The look, animations and sounds are in\n// ./ui.config.ts. Which systems (shop, heroes, leaderboards…) and games the app has is\n// ./modules.ts: remove a module there and its tab is gone. A tab whose system has nothing configured\n// on the title yet (no store offers, no heroes…) stays hidden from players by itself.\n//\n// Everything is optional; uncomment and edit.\nexport default defineAppConfig({\n  // \"game\" — sign-in → straight into the game, no \"Play\" click: the one that lives inside the lobby\n  // (idle-rpg) first, else the first full-screen game (voxelcraft). \"lobby\" — always\n  // sign-in → lobby → \"Play\". The mode id of a game (\"voxelcraft\") starts in that one.\n  start: \"game\",\n  lobby: {\n    // order: [\"play\", \"store\", \"character\"], // these tabs first, in this order\n    // primary: [\"season\"],                    // also a main tab rather than under \"More\"\n  },\n  auth: {\n    // The \"Play as guest\" button on the sign-in screen is OFF by default; uncomment to show it.\n    // guest: true,\n    // On the idosgames.com game page the player enters with their site account by itself (not signed\n    // in there — the site shows its sign-in window). On by default; uncomment to keep this screen.\n    // platformSignIn: false,\n  },\n});\n"
     },
     {
       "path": "src/config.ts",