@battlegrid/mcp-server 31.2.29 → 31.2.31

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.29";
+export declare const PACKAGE_VERSION = "31.2.31";
 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.29';
+export const PACKAGE_VERSION = '31.2.31';
 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.29",
+  "version": "31.2.31",
   "description": "BattleGrid MCP server — play crypto prediction games from AI agents",
   "type": "module",
   "main": "dist/index.js",

package/skills/EXPORT.json

@@ -1,18 +1,18 @@
 {
   "generator": "battlegrid-app/server/scripts/export-mcp-skills.mjs",
-  "contractVersion": "61.1.0",
+  "contractVersion": "61.2.0",
   "files": {
-    "battlegrid-agent-management/SKILL.md": "b6ea75b3d838c1dbaaf3984d7e99a11c81686de2c1a1910c35699ee7e70dafa5",
-    "battlegrid-arena-play/SKILL.md": "03fa153bf82be18bf5ed01e3ba12e2cd9f99a81b08d903a77b52169e7519a182",
+    "battlegrid-agent-management/SKILL.md": "8c7ed25e61e013c69694ada82e5893e7af8d12d0c0a6dccdaaaedea868efa47e",
+    "battlegrid-arena-play/SKILL.md": "67375816c1b5a40f55fcd4616386eb5afd97f3d91ea6fb94aeb6a56c7d0948a5",
     "battlegrid-market-analysis/SKILL.md": "22fde9c4eac0261c89a8056ab8b20b66fcbe1fd58447fa0ac84fd410b4d134d7",
     "battlegrid-radar-deployment/SKILL.md": "d2a012b154e1e529db19529bd7c3d75d069f4e410d5804add51165f0f0902b2e",
-    "battlegrid-strategy-authoring/SKILL.md": "93e1c9709079a4e9c968597ac572b4b62f5b0e68c01f9e9947db7e2ba304dcdf",
-    "battlegrid-strategy-doctor/SKILL.md": "9ab3f79128ec81d3e90167c3f1ea4bd6f6b570290e5ebe2bf855195263c58239",
+    "battlegrid-strategy-authoring/SKILL.md": "66ed78d8e83401586b6d0ec33ce59b0fdc8b22b04a3db0ab529cc77779bfe1c9",
+    "battlegrid-strategy-doctor/SKILL.md": "d0b9e9e07648246d5a23b0c17183278b70b5bcbb5f472ac7da13d03e42a6c6c6",
     "battlegrid-strategy-examples/SKILL.md": "17e8cf8040813622bd5b82165c7af82e03287fee1f6aac974e0b6c584580dd27",
     "battlegrid-strategy-examples/references/playbooks.md": "35c543c090d00ba19e4bcf0a80502afac7a4954643fc535de0b24381c91ecbf4",
     "battlegrid-strategy-examples/references/recipes.md": "53887daece17995543e7d3fe1bf2577fc41a6254c291acacde48d7de63853641",
     "battlegrid-strategy-examples/references/tradingview-ports.md": "2b13adbc137178955edcca31b6ab40c01c745a932a0750b91db8820c736700bb",
-    "battlegrid-trade-analysis/SKILL.md": "32573a67e55d735e6ee4e36b3b48c815694102704bc453c4d1c13db39551b3da",
+    "battlegrid-trade-analysis/SKILL.md": "f49482702f17d7fc44db00c31a19fc6e9350668fe76e8948d22faaa9c7e9d6bf",
     "battlegrid-trade-proposal/SKILL.md": "0d8ffecd493f7916d352cee3d22aee5812c3790592b100d3f9802c75ca1180c0"
   }
 }

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

@@ -96,8 +96,9 @@ State the blast radius **from server fields, as numbers**, before the confirm fo
   Agent-owned settings are untouched.
 - **Update** — the concrete diff: each field, from what, to what.
 
-Then one confirmation. Act only on an explicit pick. Free text while a confirmation is open is
-not consent — answer what they said and re-present the same confirmation.
+Then one confirmation. Act only on an explicit pick — one of the options you offered. Free text
+while a confirmation is open is not consent, whether it arrives in chat or in the form's own
+answer-in-your-own-words box — answer what they said and re-present the same confirmation.
 
 **`expectedRevision` comes from the latest read.** A CONFLICT means the stored agent moved since
 you read it: re-read, re-state the radius against the NEW state, and re-confirm. Never retry with a

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

@@ -120,7 +120,8 @@ Each is typed and distinguishable. Read the code, do not paraphrase:
   you to think.
 - **Your confirmation with the player is interaction, never authorization.** Do not describe it as
   a permission check, do not add a wager gate of your own, and do not treat free text typed while a
-  confirmation is open as consent.
+  confirmation is open as consent — in chat or in the form's own answer-in-your-own-words box. Only
+  an explicit pick from the options you offered confirms.
 - **Never re-submit over an unknown outcome.** An interrupted submit may have committed the fee.
   Run `check_market_grid_submission` first and report what actually exists.
 

package/skills/battlegrid-strategy-authoring/SKILL.md

@@ -213,7 +213,9 @@ On **Revise**, return to step 4. On **Cancel**, stop and let the token lapse.
 
 If the player types free text while the confirm form is open, that is **not** consent and not a
 cancellation. Answer what they said, then present the same plan's confirmation again, unchanged.
-Prose never triggers an apply.
+Prose never triggers an apply. The same holds for an answer typed into the form's own
+answer-in-your-own-words box: it is the player's words in an answer slot, not a confirming pick,
+so treat it exactly as you would free text in the chat.
 
 Do not pre-check expiry, digests, ownership, viability or quota before calling. The server is the
 only authority on all of them; your job is to react to what it returns.
@@ -241,7 +243,9 @@ with the player:
 independently requires `confirm:true` whenever the strategy has bound agents, so stating the radius
 and calling anyway is refused, not committed. Send `confirm:true` only on a turn where the player
 made an explicit confirming pick — never because you judged the edit safe. Free text typed while a
-confirmation is open is not consent: answer it, then present the same confirmation again.
+confirmation is open is not consent: answer it, then present the same confirmation again. That
+covers words typed into the form's own answer box as well as words sent in chat — a confirming pick
+is one of the options you offered, and nothing else is.
 
 **Send only the fields you were asked to change.** `allocation`, `required` and `params` are each
 optional and each preserves on omission. "Raise volume_surge to Critical" is

package/skills/battlegrid-strategy-doctor/SKILL.md

@@ -61,6 +61,16 @@ Three reads, and they are not interchangeable:
   four-member verdict as written: `NOT_ENFORCED` means the agent's own threshold switches the gate
   off, `UNMEASURABLE` means the input was missing and the gate fail-opened. Neither is a pass, and
   reporting either as "cleared" is the conflation the verdict vocabulary exists to prevent.
+- **A failing condition comes back as a KEY — resolve it.** `requiredConditions.failedKeys` names
+  gates like `LOCATION_OK`: an identifier, not an explanation. Read the agent's bound strategy with
+  `get_strategy` (the `strategyId` is on `get_intelligence_agent`), find the matching
+  `conditions[].conditionKey`, and say what that condition actually tests in the player's terms.
+  Quoting the key back at the player is the same defect as a raw enum on screen.
+- **Check `bindingState` before you present that definition as live.** `get_intelligence_agent`
+  carries it. At `BOUND`, the strategy's current revision is what the agent evaluates. At `SYNCING`
+  or `ORPHANED` it is not — the agent runs a materialized copy at its own `strategyRevision` — so
+  name the binding state beside the definition rather than letting current rules read as running
+  ones.
 - **Gate blocks link to their thought log** through `sourceThoughtLogId` — follow it with
   `get_agent_thought_log` when the block's reason needs the evaluation behind it.
 - `get_signal_performance` / `list_signal_logs` when the question is whether the signals fired, as
@@ -132,6 +142,10 @@ it is undetermined.
   player's intelligence credits and writes thought and activity records. It is the deployment
   flow's composition aid for tuning a draft — it is not a diagnostic read, and running it as one
   charges the player to answer a question the journals already answer.
+- **Never name a strategy write tool, even to forbid it.** Reading a rule is not authority to change
+  one: route a rule change by naming the `strategy-authoring` skill, as step 4 does. The authoring
+  tools are in a family this skill does not declare, and a skill body that names an unreachable tool
+  — including in a negative — fails the registry's reachability check.
 - Never diagnose from the agent's own prose or overlay text where a typed field exists.
 - Never present a gate-block count as a rate, a trend, or a percentage — report it as served.
 

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

@@ -27,6 +27,11 @@ Not "what were its returns" — whether it did *the thing it was told to do*.
 
 - `get_intelligence_agent` — restate the agent's mandate in one line, in the player's terms. This
   is the yardstick; without it "up 4%" means nothing.
+- `get_strategy` on the `strategyId` that read returns — the mandate is the bound strategy, so the
+  yardstick is its admission gates, required conditions and trade levels, not the agent's overlay
+  prose. Read `bindingState` too: at `SYNCING` or `ORPHANED` the agent evaluates a materialized copy
+  at its own `strategyRevision`, and judging it against the strategy's current revision measures it
+  by rules it is not running.
 - `get_agent_performance` and `list_trade_outcomes` — judge against that mandate.
 - `get_trade_outcome_by_decision` / `get_trade_chart` when a specific trade needs explaining.
 - `get_signal_performance` when the question is whether the agent's signals are working, as