@battlegrid/mcp-server 31.2.3 → 31.2.5

package/README.md

@@ -24,7 +24,7 @@ Seeing package `31.x` alongside handshake `battlegrid@33.x` — the package **be
 
 **What this changes for you:** nothing about how you call anything. Upgrading the package no longer waits on a server deploy, and a server deploy no longer strands you on a package that names the wrong contract — reconnect and the announcement follows. **Contract breaking-change notes are no longer keyed to package versions**, since a contract move is no longer a release here; the v11-and-earlier notes below are kept as history, and the live vocabulary is always discovery.
 
-## Contract history — v37 → v49.3
+## Contract history — v37 → v49.5
 
 Eleven majors reached authors while this section stopped at v36. That gap is the mechanism, not an
 oversight: since v31 a contract move needs no release here, so nothing forced a note to be written —
@@ -37,7 +37,7 @@ package.
 Nothing to migrate. This is the one direction that cannot break a client: a body the server used to
 refuse is now stored. Listed because a client that special-cased the refusal can delete that branch.
 
-- **An arming trigger no longer constrains its required conditions' clock** (49.2.0,
+- **An arming trigger no longer constrains its required conditions' clock** (49.4.0,
   `restore-arming-trigger-authoring`). `compile_strategy_plan`, `apply_strategy_plan` and
   `fork_strategy` accept a strategy whose entry trigger is `ON_CANDLE_CLOSE`, `STOP_THROUGH_LEVEL`
   or `ON_RETEST` **while a required condition reads the `LIVE` clock**. v48.1 announced that pairing
@@ -179,7 +179,7 @@ refuse is now stored. Listed because a client that special-cased the refusal can
 
 ### Reshaped output — the same call returns a different shape
 
-- **An entry void now names the gate that refused it** (49.3.0,
+- **An entry void now names the gate that refused it** (49.5.0,
   `fix-arming-trigger-clock-authority`), on `get_radar_activity_summary`. In the cause rollup, the
   `ENTRY_VOID` group's `gateCode` widens from always-`null` to `QualificationGateCode | null`: a
   conditions-side void carries the gate that blocked — `AGGREGATE_BELOW_MIN`,

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

package/skills/battlegrid-strategy-studio/references/tradingview-ports.md

@@ -145,7 +145,7 @@ the book out of single-name traps. Rules: `ma_sma200_above` 3 required, `ma_ema_
 **Source process.** In an uptrend (close > 200 SMA), buy panic dips (RSI(2) < 10); exit fast
 (cross of the 5-period average / a few bars).
 
-**Port — direct.** `RSI2` is native as of contract 49.1, so this ports exactly and no substitution
+**Port — direct.** `RSI2` is native as of contract 49.2, so this ports exactly and no substitution
 note is owed. `DIP_BUY` verdict UP = `dist_SMA200 gt 0` (ref a required `ABOVE_200`) AND
 `RSI2 lte 10`. Keep the literal `lte 10` as the gate: `RSI2 × classifyZone` exists and reads on the
 same Connors 10/90 bands, but a zone label is a fixed reading while the literal is a threshold the
@@ -217,7 +217,7 @@ Williams %R (`WILLR14`), Stochastic RSI (`STOCH_RSI14`), Bollinger boundaries
 (`BB_UPPER`/`BB_LOWER`), ADX components (`DI_PLUS`/`DI_MINUS`). All arrived with contract 46.1 —
 every one of them was listed as inexpressible in this file before it.
 
-Contract 49.1 did it again with seven more: Connors RSI-2 (`RSI2`, and `RSI2 × classifyZone` on its
+Contract 49.2 did it again with seven more: Connors RSI-2 (`RSI2`, and `RSI2 × classifyZone` on its
 own 10/90 bands), the TTM squeeze state (`KC_SQUEEZE`), the 9/21/50 EMAs (`EMA9`/`EMA21`/`EMA50`)
 and the prior-day levels (`PDH`/`PDL`). Two of those were standing absence claims in this file:
 RSI-2 was called a named substitute, and the prior-day levels were said to need a grammar form no