@battlegrid/mcp-server 31.2.21 → 31.2.23

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

package/skills/EXPORT.json

@@ -1,14 +1,14 @@
 {
   "generator": "battlegrid-app/server/scripts/export-mcp-skills.mjs",
-  "contractVersion": "55.2.0",
+  "contractVersion": "56.2.0",
   "files": {
     "battlegrid-agent-management/SKILL.md": "b6ea75b3d838c1dbaaf3984d7e99a11c81686de2c1a1910c35699ee7e70dafa5",
     "battlegrid-arena-play/SKILL.md": "03fa153bf82be18bf5ed01e3ba12e2cd9f99a81b08d903a77b52169e7519a182",
     "battlegrid-market-analysis/SKILL.md": "22fde9c4eac0261c89a8056ab8b20b66fcbe1fd58447fa0ac84fd410b4d134d7",
     "battlegrid-radar-deployment/SKILL.md": "d2a012b154e1e529db19529bd7c3d75d069f4e410d5804add51165f0f0902b2e",
-    "battlegrid-strategy-authoring/SKILL.md": "2a973a9e52832ab1e0d9bf1b6d21b8bf898899bc3a455fde223646a01e914242",
+    "battlegrid-strategy-authoring/SKILL.md": "1f1bf1ecfbf1a20d585a53e8f1ba8e9fbdeaa329cad9ebdc16ce6cac2b213358",
     "battlegrid-strategy-doctor/SKILL.md": "9ab3f79128ec81d3e90167c3f1ea4bd6f6b570290e5ebe2bf855195263c58239",
-    "battlegrid-strategy-examples/SKILL.md": "5343cb1ec76a1b1f1b3caface886ee87526ecd0da159abf98f34cf2de1392c3e",
+    "battlegrid-strategy-examples/SKILL.md": "6f15da8b29a8aff15f6829d7ae87cbe74904bfe5372e37fe17d578cc0c289577",
     "battlegrid-strategy-examples/references/playbooks.md": "35c543c090d00ba19e4bcf0a80502afac7a4954643fc535de0b24381c91ecbf4",
     "battlegrid-strategy-examples/references/recipes.md": "53887daece17995543e7d3fe1bf2577fc41a6254c291acacde48d7de63853641",
     "battlegrid-strategy-examples/references/tradingview-ports.md": "2b13adbc137178955edcca31b6ab40c01c745a932a0750b91db8820c736700bb",

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

@@ -187,6 +187,12 @@ point-in-time reading, and you say so.
 
 ### 6. Confirm, then apply
 
+**In a conversation the Strategy Builder hosts, this section does not apply: compile and stop.**
+The compiled plan lands on the player's rail as unsaved changes and their Review & save is the one
+consent. Report that it is staged, name the axes, and present no apply confirmation — the server
+refuses `apply_strategy_plan` from such a conversation as a tool error, so calling it spends an op
+of your budget and commits nothing.
+
 One confirmation carrying the plan's own `confirmationSummary`, offering Apply / Revise / Cancel.
 
 On **Apply**, call `apply_strategy_plan` with two values and nothing else:
@@ -215,6 +221,12 @@ only authority on all of them; your job is to react to what it returns.
 `fork_strategy`, `update_strategy_signal_rule`, `restore_strategy`, `archive_strategy` and
 `preview_strategy_report` are part of this flow.
 
+**In a builder-hosted conversation, three of those are refused at execution** —
+`update_strategy_signal_rule`, `restore_strategy` and `archive_strategy`, alongside
+`apply_strategy_plan` — because each commits a revision of the open strategy around the player's
+save. `fork_strategy` stays available: it writes a DIFFERENT strategy, which is not the one the
+builder owns. `preview_strategy_report` and every read stay available.
+
 Before any destructive one, state the blast radius from the server's own fields and confirm it
 with the player:
 

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

@@ -104,9 +104,12 @@ setups block and from the `decide_trade` contract, not merely discouraged in the
 declares no verdict-carrying condition resolves `null` and constrains nothing.
 
 A verdict carrier must read a SETTLED bar wherever one is available to it — `clock: "CLOSE"`
-whenever every column it reads accepts a closed frame and every condition it references is itself
-`CLOSE`. Where no closed frame moves its operands (a published regime label, an open-interest
-regime), `LIVE` stays legal: there is no settled bar to take.
+whenever every column in its CLOSURE accepts a closed frame. The closure is what it reads directly
+plus everything reached through `conditionRef`, transitively: a referenced condition contributes what
+IT reads, never the clock it happens to declare, so moving a clause into a building block and leaving
+that block `LIVE` does not make a settled bar unavailable to the carrier. Where no closed frame moves
+some operand in the closure (a published regime label, an open-interest regime, a published rolling
+change), `LIVE` stays legal at any depth: there is no settled bar to take.
 
 Evaluation is three-valued: UNRESOLVED never collapses to FALSE; forming-bar reads are provisional.
 
@@ -117,10 +120,13 @@ this coin's own candle series at offset 0. Frame-inert operands are refused
 (`CONDITION_CLOCK_OPERAND_ILLEGAL`): perp-payload scalars, published rolling changes, ranks, zone
 entities, MDS regime labels, enrichment metrics, session scalars, and any clause authored at a
 non-zero offset. A closed frame cannot move them, so "held for N closes" would describe reads
-that never happened. The remedy is a split, not a re-clock: move that clause into its own LIVE
-condition and `conditionRef` it. **Worked liquidity floor:** `LIQUID_FLOOR` is LIVE because
-`vol24hUsd` is a bundle scalar; the carrier that refs it may be CLOSE over its own candle-series
-clauses.
+that never happened. A frame-inert operand anywhere in a condition's closure simply keeps that
+condition on `LIVE`, and that is legal — splitting the clause into its own condition and
+`conditionRef`-ing it does NOT buy the referencing condition a CLOSE clock, because a `CLOSE`
+condition may not reference a `LIVE` one (`CONDITION_CLOCK_REFERENCE_ILLEGAL`) and availability walks
+into the referenced closure anyway. **Worked liquidity floor:** `LIQUID_FLOOR` is `LIVE` because
+`vol24hUsd` is a bundle scalar, and a condition that references it is `LIVE` too. Reach for a split to
+keep a condition's MEANING separable, not to change its clock.
 
 **The lane a strategy is deployed to.** Report-level scalars split by LANE, and the split is not a
 quality of the header — it is which reader runs. Market breadth and the reference pairs are ordinary