@battlegrid/mcp-server 31.2.88 → 31.2.93

package/README.md

@@ -24,6 +24,68 @@ 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 — v107.1 (an arena entry is recorded before its fee moves)
+
+**Additive at v107.1: a paid entry can be recorded while its fee confirms.** v107.1 is the contract on top
+of v107. The server now records your entry first, then sends the fee, then settles the entry on the
+venue's answer, so a fee can never move for an entry that was not recorded. No input changes.
+
+### Widened output
+
+- **`submit_market_grid`, `random_submit_market_grid` and `submit_agent_grid` results gain
+  `entryStatus`**: `ENTERED`, or `PAYMENT_PENDING` when the entry is recorded and its fee is still
+  confirming at the venue. A payment-pending entry plays once its fee lands before lock; otherwise it is
+  released, and a fee that lands after that is refunded.
+- **`entryState` gains `PAYMENT_PENDING`** on `get_my_market_grid_entry`. `list_my_market_grid_entries`
+  shares the element schema but never returns one.
+
+### Refusal vocabulary
+
+- **`details.wagerErrorCode` gains `ACCOUNT_NOT_UNIFIED`** on the three submit tools: an entry fee is
+  paid only from a unified-collateral account (`unifiedAccount` or `portfolioMargin`).
+
+### Behaviour behind unchanged schemas
+
+- **`check_market_grid_submission` answers `hasSubmitted: true`** for a payment-pending entry.
+- **`update_market_grid` refuses a payment-pending entry** with `CONFLICT` until it is in play.
+
+## Contract history — v106 (the Opening Bell: a session starts at its scored candle's open)
+
+**Breaking at v106: Two-Look entry is retired. A deployment slot drops `entryStrategy`, and a
+deployment draft refuses one.** v106 is the contract on top of v105.5. Every automated entry now looks
+once, inside the Opening Bell window: from `startsAt` (the open of the one candle a session scores)
+until `lockAt` (entries close).
+
+### Reshaped output — something you read has moved or been removed
+
+- **`entryStrategy` leaves every deployment slot**: `get_deployment_policy`, `list_deployment_policies`,
+  `get_deployment_policy_draft`, `pause_deployment_policy`, `delete_deployment_policy`,
+  `preview_deployment_resolution` and `test_generate_deployment_grid`.
+
+### Rejected input — something you send is no longer accepted
+
+- **`stage_deployment_policy_draft` refuses `entryStrategy`** on a `RULES` rule and on the
+  `DEFAULT_SLOT`, as an unrecognized key. `preview_deployment_resolution`'s `SLOTS` subject and
+  `test_generate_deployment_grid` no longer publish the key, and they strip it if it is sent.
+
+### Widened output
+
+- **Every Market Grid session surface gains `startsAt`**, the Opening Bell. That covers
+  `get_market_grid_session`, `list_market_grid_sessions`, `get_market_grid_results`, and a deployment's
+  target session and open entries. A Coin Grid summary's `startsAt` equals its `lockAt`.
+- **`get_agent_prompt_context_preview`'s market context gains `startsAt` and
+  `millisecondsSinceOpeningBell`**, both nullable.
+
+### Behaviour behind unchanged schemas
+
+- **`lockAt` keeps its name and now means "entries close"**, the end of the Opening Bell window, a
+  fixed fraction of the session's duration after `startsAt`. Read `startsAt` for when a session starts
+  or what it scores. Submitting, editing and cancelling stay open until `lockAt`.
+- **`SESSION_START` rules match `startsAt`.**
+
+A client that reads `entryStrategy` from a slot, or stages one into a deployment draft, breaks at v106,
+which is why this is a MAJOR.
+
 ## Contract history — v103 (a column's contract carries its read size, measurement and series home)
 
 **Breaking at v103: a transform entry drops `sideRequired` and `operandRequired`, and

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