@battlegrid/mcp-server 31.2.69 → 31.2.71

package/README.md

@@ -24,6 +24,61 @@ 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 — v89 (a new strategy is held to today's operator bounds)
+
+**Breaking at v89: acceptance narrows behind unchanged schemas.** v89 is the contract on top of v88.1.
+
+### Narrowed acceptance — `commit_strategy_draft`, `preview_strategy_report` (`DRAFT` source)
+
+- **A create judges every dial of the new strategy at the operator bounds configured now.** That includes a dial
+  the author typed, one a fork copied from its source, and one left at the creation default. The operator bounds
+  are the platform's ATR %, stop-loss ATR-multiple and risk:reward limits.
+- At v88.1 a create judged only the dials that differed from the fork's source or the creation default. So a copied
+  dial outside a bound tightened since the source stored it was committed.
+- At v89 `commit_strategy_draft` (`expectedRevision: null`) refuses that create with `VALIDATION_ERROR`, naming the
+  dial and the bound, for example `minAtrPct (0.1) must be >= 0.15`. Nothing is created and the draft is unchanged:
+  stage the dial inside the bound and commit again.
+- `preview_strategy_report` with `source: { kind: "DRAFT", … }` composes the draft exactly as the commit does, so it
+  refuses the same draft with the same error where v88.1 rendered it.
+- `stage_strategy_draft` and `get_strategy_draft` report the error in their diagnostics before the commit.
+- `fork_strategy`'s description now says this, so its description hash moves.
+
+### Behaviour behind unchanged schemas
+
+- **An edit still judges only what it moves.** An update or a restore carries a dial it leaves unchanged, so a stored
+  value outside a since-tightened bound stays readable and saveable on its own strategy.
+- **The platform keeps its defaults creatable.** An operator cannot set a bound that would put a creation default
+  outside it, so a create that leaves a dial untouched is never refused for a value the platform seeded.
+
+Something accepted at v88.1 is refused at v89 — hence the MAJOR.
+
+## Contract history — v88.1 (an open position keeps the exit rules it opened under)
+
+**Additive at v88.1: acceptance widens and one served value narrows; no input or output schema
+changes.** v88.1 is the contract on top of v88.
+
+### Widened acceptance — `commit_strategy_draft`, `restore_strategy`, `commit_agent_draft`
+
+- **An open position no longer refuses a strategy commit, a restore or a rebind.** At v88 a write that
+  would leave an exit rule unreadable on a coin a bound agent held an open position on was refused with
+  `CONDITION_UNREADABLE_BY_RADAR_SCAN` or `CONDITION_OPERAND_UNSERVED_IN_LANE`. At v88.1 it commits. A radar
+  slot's coin and a pending manual request's coin are still checked, and refused exactly as before.
+- The three tools' descriptions now say this, so their description hashes move.
+
+### Narrowed served value — the readability refusal's `coinRole`
+
+- The refusal's error context serves `coinRole` as `SLOT` or `MANUAL_REQUEST` only. `OPEN_POSITION` is no
+  longer emitted. A client switching on it loses a member it can no longer receive.
+
+### Behaviour behind unchanged schemas
+
+- **An open position keeps what it opened with.** An agent position records the exit rules it opened
+  under, with the report and timeframes they read, and its exit rules are evaluated from that record for
+  the life of the trade. An exit-rule, exit-policy or level edit reaches only positions opened after it;
+  a revision, rebind, SYSTEM update or timeframe change after the open never reaches an open trade.
+
+Nothing accepted at v88 is refused at v88.1.
+
 ## Contract history — v88 (an exit rule names the side it closes)
 
 **Breaking at v88: a condition body accepted at v87 is refused, and condition and chart output is

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

package/skills/EXPORT.json

@@ -1,6 +1,6 @@
 {
   "generator": "battlegrid-app/server/scripts/export-mcp-skills.mjs",
-  "contractVersion": "88.0.0",
+  "contractVersion": "88.1.0",
   "files": {
     "battlegrid-agent-management/SKILL.md": "b2f04d76480de2f9fdbd00f8cb25610d2b72fcaa4f87ca57a09bd9ffc78fdbba",
     "battlegrid-arena-play/SKILL.md": "4cfaa92a8d0dcaf477b227abd774e7aa8642c185d72108dfd401be0cf8aecd7f",
@@ -8,7 +8,7 @@
     "battlegrid-radar-deployment/SKILL.md": "a624807c9d1f0e1fa650592bfbbdab228d75098d66a9c2d4d3cd3f85e5d3796c",
     "battlegrid-strategy-authoring/SKILL.md": "a5066740d7d57f095545fd812b0228a8eef6e3b08c87047596a0e1639ae4971d",
     "battlegrid-strategy-doctor/SKILL.md": "14f20bff9e2b5a59d11634fe3615b1298d672d5e2eba06d3dc8698b571b3bee3",
-    "battlegrid-strategy-examples/SKILL.md": "5c3d9b484569c62f0c340620ca1ec2b1dfb9b950662558d07b7ae9c40d682979",
+    "battlegrid-strategy-examples/SKILL.md": "7ec80099efe3a923e1a701703eba5edbbe3ce044628273c806dfd688f2fd715c",
     "battlegrid-strategy-examples/references/playbooks.md": "63aa07f3d55f97e53b2bf6401528807ab23bd093a4bbc37e598158249db24a59",
     "battlegrid-strategy-examples/references/recipes.md": "61382acdd295fa159f055b787ba501f1c015f383f59a6714a973057f10de611f",
     "battlegrid-strategy-examples/references/tradingview-ports.md": "2b13adbc137178955edcca31b6ab40c01c745a932a0750b91db8820c736700bb",

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

@@ -222,7 +222,7 @@ scan has on that coin, or free the coin.
 
 **The refusal lands where an agent meets a coin**: at the radar deploy (its preview, the builder's
 Save and the draft commit); at a manual entry request, as `CONDITION_UNREADABLE_ON_COIN`;
-and, for an agent already deployed or holding an open position or a pending manual request, at a
+and, for an agent already deployed or holding a pending manual request, at a
 strategy commit (`commit_strategy_draft`, the builder's Save, `restore_strategy`) or a rebind (the
 agent draft's STRATEGY_BINDING commit). A commit is checked only on behalf of those agents: a
 strategy carries no lane of its own, so one with no agent the radar acts on is never checked, and
@@ -242,7 +242,10 @@ an exit rule may reference anything, so "exit when the entry setup stops holding
 whose definition is `NOT` a `conditionRef` to the entry condition. An exit rule is legal only over a
 closure every operand of which a completed bar MOVES (`CONDITION_EXIT_READ_ILLEGAL`), which rules out
 a developing read — a bar in progress is the forming bar, and an exit fired on one is an intrabar
-exit — and rules out a frame-inert operand, which could never fire.
+exit — and rules out a frame-inert operand, which could never fire. A position stamps the exit rules
+it opened under, with the report and timeframes they read: an exit-rule edit applies to positions
+opened after it, and an open position keeps the exit rules it opened with, so an open position never
+refuses a commit or a rebind.
 
 **A state column is not a flip event.** `ST_DIR` reads the same on every bar of a trend, so
 `ST_DIR is "bullish"` is a regime filter and never an entry signal. The flip needs an event column