@battlegrid/mcp-server 31.2.32 → 31.2.33

package/dist/index.d.ts

@@ -49,7 +49,7 @@ import { type Implementation, type Prompt, type Resource } from '@modelcontextpr
  * being asked. Move it for a change to THIS package — a proxy fix, a dependency bump, a docs
  * correction. Never move it to track the server.
  */
-export declare const PACKAGE_VERSION = "31.2.32";
+export declare const PACKAGE_VERSION = "31.2.33";
 export declare const DEFAULT_URL = "https://mcp.battlegrid.trade/mcp";
 export interface EnvConfig {
     apiKeys: string[];

package/dist/index.js

@@ -52,7 +52,7 @@ import { ListToolsRequestSchema, CallToolRequestSchema, ListPromptsRequestSchema
  * being asked. Move it for a change to THIS package — a proxy fix, a dependency bump, a docs
  * correction. Never move it to track the server.
  */
-export const PACKAGE_VERSION = '31.2.32';
+export const PACKAGE_VERSION = '31.2.33';
 export const DEFAULT_URL = 'https://mcp.battlegrid.trade/mcp';
 const MAX_RETRIES = 3;
 const RETRY_DELAYS_MS = [2000, 4000, 8000];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@battlegrid/mcp-server",
-  "version": "31.2.32",
+  "version": "31.2.33",
   "description": "BattleGrid MCP server — play crypto prediction games from AI agents",
   "type": "module",
   "main": "dist/index.js",

package/skills/EXPORT.json

@@ -1,9 +1,9 @@
 {
   "generator": "battlegrid-app/server/scripts/export-mcp-skills.mjs",
-  "contractVersion": "61.3.0",
+  "contractVersion": "62.1.0",
   "files": {
-    "battlegrid-agent-management/SKILL.md": "8c7ed25e61e013c69694ada82e5893e7af8d12d0c0a6dccdaaaedea868efa47e",
-    "battlegrid-arena-play/SKILL.md": "67375816c1b5a40f55fcd4616386eb5afd97f3d91ea6fb94aeb6a56c7d0948a5",
+    "battlegrid-agent-management/SKILL.md": "d56834fa2016ec9371994999fa13a3dbb69906efc54db522e10fd2eb0ebb6044",
+    "battlegrid-arena-play/SKILL.md": "4cfaa92a8d0dcaf477b227abd774e7aa8642c185d72108dfd401be0cf8aecd7f",
     "battlegrid-market-analysis/SKILL.md": "22fde9c4eac0261c89a8056ab8b20b66fcbe1fd58447fa0ac84fd410b4d134d7",
     "battlegrid-radar-deployment/SKILL.md": "d2a012b154e1e529db19529bd7c3d75d069f4e410d5804add51165f0f0902b2e",
     "battlegrid-strategy-authoring/SKILL.md": "66ed78d8e83401586b6d0ec33ce59b0fdc8b22b04a3db0ab529cc77779bfe1c9",
@@ -13,6 +13,6 @@
     "battlegrid-strategy-examples/references/recipes.md": "53887daece17995543e7d3fe1bf2577fc41a6254c291acacde48d7de63853641",
     "battlegrid-strategy-examples/references/tradingview-ports.md": "2b13adbc137178955edcca31b6ab40c01c745a932a0750b91db8820c736700bb",
     "battlegrid-trade-analysis/SKILL.md": "f49482702f17d7fc44db00c31a19fc6e9350668fe76e8948d22faaa9c7e9d6bf",
-    "battlegrid-trade-proposal/SKILL.md": "0d8ffecd493f7916d352cee3d22aee5812c3790592b100d3f9802c75ca1180c0"
+    "battlegrid-trade-proposal/SKILL.md": "a198dd360bd7a1de5f00237b544a3535fc7c373612c09cf9a9dae4f2607c489a"
   }
 }

package/skills/battlegrid-agent-management/SKILL.md

@@ -78,6 +78,14 @@ this confirm turn. A create spends an agent slot against the player's rank quota
 dropped response would spend a second one. With the key, an ambiguous retry replays the original
 result instead.
 
+**When the mandate names the arena, read `get_account_state` in the same breath.** The arena needs
+Agent Wagers: `mcpWagerEnabled: false` means every entry will be refused at the fee, so say the
+arena needs it and offer the switch — **in a conversation a web Commander surface hosts, the switch
+renders beneath the account card just shown, so offer it there**, and in every other host name the
+Profile → Wallet tab path instead, because no control renders there. **Create the agent either
+way**: the consent gates entering a game, never commissioning one. A `true` flag is consent alone
+and not readiness — the pipeline's own refusal at the fee is the authority.
+
 ### 3. Lifecycle verbs: read first, state the radius, then confirm
 
 Every one of update, rebind, halt, resume, activate and archive runs this shape. The reads

package/skills/battlegrid-arena-play/SKILL.md

@@ -27,12 +27,20 @@ the grid you submit is the one that gets scored. There is no draft state and no
 `get_account_state`. It carries the balance, the rank, and **`mcpWagerEnabled`** — a served
 projection of the player's Server-Signed Wagers signer consent.
 
-- **False** ⇒ say so up front, name the enablement path (Profile → Wallet tab → enable Agent
-  Wagers), and continue **read-only**: sessions, market context, results and journals are all still
-  useful. Do not pretend a submit will work.
-- **True** ⇒ proceed. It is a routing signal for what you tell them, never an authorization: the
-  wager pipeline re-checks consent at the fee itself, and its refusal is the authority in either
-  direction.
+- **False** ⇒ a **definite refusal**, before any submission. Say so up front, name the enablement
+  path (Profile → Wallet tab → enable Agent Wagers), and continue **read-only**: sessions, market
+  context, results and journals are all still useful. Never call a submission tool the flag says
+  will be refused.
+- **True** ⇒ proceed, but it is **consent alone and never readiness**. It projects the signer
+  consent and nothing else, so an account whose server signer is unregistered reads true here and
+  is still refused at the fee. The wager pipeline re-checks at the fee itself and its refusal is
+  the authority in either direction.
+
+**In a conversation a web Commander surface hosts, the switch renders beneath the account card just
+shown, or beneath the refusal — offer it there.** Say the arena needs Agent Wagers and point at the
+control rather than at a settings path they would have to leave the conversation for. Every other
+host — an external MCP client, Telegram — renders no such control, so the Wallet-tab path above is
+the enablement path there.
 
 ### 2. Workflow A reads, in order
 

package/skills/battlegrid-trade-proposal/SKILL.md

@@ -56,8 +56,13 @@ flow stays available.
   (`barStart`), when the answer is due (`decidesBy`), and the deadline past which that bar can no
   longer be decided (`windowEndsAt`). `decidesBy` and `windowEndsAt` are different instants — a bar
   that has already settled is decided at the next sweep, seconds away.
-- Say where the answer will appear: in the agent's conversation, and — if it proposes a trade — in
-  `list_pending_approvals`. Nothing further is needed from the player until then.
+- Say where the answer will appear: on the delegation card in this conversation, and — if it
+  proposes a trade — in `list_pending_approvals`. Nothing further is needed from the player until
+  then; the card carries the answer to them when the bar closes.
+- When the player asks what the agent decided, read the request's conversation with
+  `get_trade_conversation({ conversationId })`, using the id the `queued` result carried. It serves
+  the whole transcript in stored order — the queued card, the agent's reasoning, its thesis and
+  setups, the recommendation, a no-trade with its reason and next coins, or a close answer.
 - `get_entry_request` re-reads a request still pending; `cancel_entry_request` withdraws it. Both
   are `NOT_FOUND` once it has been answered, cancelled or expired, and that is the honest record:
   the answer is in the conversation.
@@ -71,12 +76,17 @@ flow stays available.
 
 ## 4. When the answer arrives — approve or decline only on the player's word
 
-**In a conversation the Agent Toolbox hosts, the approval is not yours to send.** The decided close
-lands on the trade card in the lane beside you, carrying the player's own Accept and Decline;
+**On a web Commander surface the approval is the card's own.** The decided close lands on the
+delegation card in this conversation, carrying the player's Accept and Decline. `accept_entry_decision`
+and `cancel_entry_decision` remain yours for the external and Telegram doors, and on the web only on
+the player's explicit typed word — never inferred from interest, agreement, or a question about the
+trade.
+
+**In a conversation the Agent Toolbox hosts, the approval is not yours to send at all.** The decided
+close lands on the trade card in the lane beside you, carrying the player's own Accept and Decline;
 `accept_entry_decision` and `cancel_entry_decision` are refused there as tool errors, so calling one
 spends an op and moves nothing. Read the card back to them — the direction, the levels, the
-conviction, the expiry — and say what you would do, which is the whole of your part. What you have
-to work from is whatever the player attaches from a card: its rendered readings, nothing more.
+conviction, the expiry — and say what you would do, which is the whole of your part.
 
 - A decided close produces one of: a PROPOSED decision awaiting approval; a no-trade with the
   reason and the next coins worth asking about; a close that did not qualify; a window that passed