@battlegrid/mcp-server 31.2.10 → 31.2.12

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 → v52
+## Contract history — v37 → v53
 
 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 —
@@ -112,6 +112,21 @@ refuse is now stored. Listed because a client that special-cased the refusal can
 
 ### Rejected input — something you author is no longer accepted
 
+- **A condition naming a `swingHi` / `swingLo` header is refused — the indicator is a Donchian
+  channel** (53.0.0, `rename-donchian-channel`). The rolling-window extremes indicator computed the
+  highest high and lowest low of the trailing 20 closed bars — a Donchian channel — under a swing
+  point's name, and the name asserted a property the value does not have (a swing high survives being
+  broken; a channel edge re-anchors the instant it is). Every layer of the vocabulary moves at once,
+  with no alias: a clause on `compile_strategy_plan`, `apply_strategy_plan` or `fork_strategy` naming
+  a header on the old stems — `dist_swingLo`, `dist_swingHi_4h`, `dist_swingLo_rank_near`, any
+  timeframe- or rank-suffixed form — is refused as `CONDITION_COLUMN_UNKNOWN` where 52.0.0 accepted
+  it. The same shapes exist on the `donchianHi` / `donchianLo` stems, which
+  `get_strategy_column_contract` lists with the labels *20-bar high* / *20-bar low*. Every value is
+  the same number under its new name.
+
+  **Rename the stems** (`swingHi` → `donchianHi`, `swingLo` → `donchianLo`, suffixes unchanged) in
+  every condition and Market Read marker you author. That is the whole migration for what you send.
+
 - **`entry.levelSource` is refused — the level is derived, never authored** (52.0.0,
   `derive-entry-level`). The strict `entry` object on `compile_strategy_plan`, `apply_strategy_plan`
   and `fork_strategy` is six keys — `trigger`, `confirmTf`, `closes`, `bandAtrMultiple`,
@@ -258,6 +273,11 @@ refuse is now stored. Listed because a client that special-cased the refusal can
 
 ### Removed — no alias exists
 
+- **`SWING_LOW` / `SWING_HIGH` leave the stop and take-profit method enums, and the four S/R
+  indicator keys leave the signal vocabulary** (53.0.0, `rename-donchian-channel`). `DONCHIAN_LOWER`
+  / `DONCHIAN_UPPER` and `donchian_upper` / `donchian_lower` / `prev_donchian_upper` /
+  `prev_donchian_lower` carry the same values; nothing answers to the old names.
+
 - **`get_coin_market_context` is REMOVED** (40.0.0, `retire-get-coin-market-context`). Calling it
   returns an unknown-tool error. There is deliberately **no alias**: a silent redirect would hide a
   payload shape change from a client that never asked for one. Use `get_market_context`.
@@ -271,6 +291,19 @@ refuse is now stored. Listed because a client that special-cased the refusal can
 
 ### Reshaped output — the same call returns a different shape
 
+- **Report headers, glosses and signal indicator keys are renamed for the Donchian channel**
+  (53.0.0, `rename-donchian-channel`). Every report surface — `preview_strategy_report`,
+  `get_strategy_section_template`, the agent prompt previews — renders `donchianHi` / `donchianLo`
+  and their `dist_…` / `…_rank_near` forms where it rendered `swingHi` / `swingLo`, with the labels
+  *20-bar high* / *20-bar low* and glosses that say what the number is (the highest high / lowest low
+  of the last 20 closed bars — the channel's edges). Signal definitions
+  (`get_strategy_signal_definition`, `list_strategy_signals`) and signal-log `indicatorValues`
+  carry `donchian_upper` / `donchian_lower` / `prev_donchian_upper` / `prev_donchian_lower` for the
+  four S/R signals. Signal ids, the `SUPPORT_RESISTANCE` module and its display names are unchanged.
+
+  **Read the new keys.** A reader keyed on `swing_high` / `swing_low` finds nothing; the values are
+  the same numbers under the new keys.
+
 - **The stored entry discipline no longer names a level source** (52.0.0, `derive-entry-level`).
   `StrategyDTO.entry` (`get_strategy`, `list_strategies`, the `fork_strategy` / `archive_strategy` /
   `restore_strategy` envelopes) and the apply envelope's `postState.entry` lose `levelSource`.
@@ -340,6 +373,11 @@ refuse is now stored. Listed because a client that special-cased the refusal can
 
 ### Widened enum — new members your own copy rejects
 
+- **The stop and take-profit method enums gain `DONCHIAN_LOWER` / `DONCHIAN_UPPER`** (53.0.0,
+  `rename-donchian-channel`), replacing `SWING_LOW` / `SWING_HIGH` on the signal-pipeline detail
+  schemas — trade-setup options, R:R-rejected pairs and candidate levels. A copy of either enum that
+  rejects unknown members must add the two new ones; the two old ones never appear again.
+
 - **`TradeExecutionFailureReason` gains `LEVEL_NOT_RESTABLE`** (52.0.0, `derive-entry-level`): a
   level entry refused at placement because its resting price sat on the wrong side of the exchange
   mid — a buy stop at or below it, a buy limit at or above it, and the mirror for a sell. It appears

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.10";
+export declare const PACKAGE_VERSION = "31.2.12";
 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.10';
+export const PACKAGE_VERSION = '31.2.12';
 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.10",
+  "version": "31.2.12",
   "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": "52.0.0",
+  "contractVersion": "53.0.0",
   "files": {
     "battlegrid-agent-management/SKILL.md": "b6ea75b3d838c1dbaaf3984d7e99a11c81686de2c1a1910c35699ee7e70dafa5",
     "battlegrid-arena-play/SKILL.md": "03fa153bf82be18bf5ed01e3ba12e2cd9f99a81b08d903a77b52169e7519a182",
@@ -8,10 +8,11 @@
     "battlegrid-radar-deployment/SKILL.md": "d2a012b154e1e529db19529bd7c3d75d069f4e410d5804add51165f0f0902b2e",
     "battlegrid-strategy-authoring/SKILL.md": "2a973a9e52832ab1e0d9bf1b6d21b8bf898899bc3a455fde223646a01e914242",
     "battlegrid-strategy-doctor/SKILL.md": "9ab3f79128ec81d3e90167c3f1ea4bd6f6b570290e5ebe2bf855195263c58239",
-    "battlegrid-strategy-examples/SKILL.md": "c986b9dfbf1a3dba083bd7f4fd0d06e187935d9c7e8bde175fafe592136b2f1d",
+    "battlegrid-strategy-examples/SKILL.md": "316c9635219c9a732e9c4bce9918a442be8b3ad9abac16c613224951e12887a1",
     "battlegrid-strategy-examples/references/playbooks.md": "35c543c090d00ba19e4bcf0a80502afac7a4954643fc535de0b24381c91ecbf4",
     "battlegrid-strategy-examples/references/recipes.md": "53887daece17995543e7d3fe1bf2577fc41a6254c291acacde48d7de63853641",
-    "battlegrid-strategy-examples/references/tradingview-ports.md": "2f84758ba6ec015c7db3cf996f663971a7017eddbebe42d6ecba6386c7b78362",
-    "battlegrid-trade-analysis/SKILL.md": "32573a67e55d735e6ee4e36b3b48c815694102704bc453c4d1c13db39551b3da"
+    "battlegrid-strategy-examples/references/tradingview-ports.md": "1ff63367de1f9a9fbbcd7ecd5367137800373df47aaeb1d61fb1298d3a1924f4",
+    "battlegrid-trade-analysis/SKILL.md": "32573a67e55d735e6ee4e36b3b48c815694102704bc453c4d1c13db39551b3da",
+    "battlegrid-trade-proposal/SKILL.md": "0a4586f660f605281c7775523c9e41422c6e52646ce52bf0688254af4619e46c"
   }
 }

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

@@ -145,7 +145,7 @@ level a level trigger rests at is DERIVED from the trigger and the trade's direc
   the tape, keeping the platform's flat wall-clock entry window. Today's behaviour.
 - `ON_CANDLE_CLOSE` — the flip ARMS the pair; the entry is taken only after a close on
   `confirmTf` that still reads the conditions true and has not displaced beyond the band.
-- `STOP_THROUGH_LEVEL` — a TRIGGER order rests past the swing channel's CURRENT edge in the
+- `STOP_THROUGH_LEVEL` — a TRIGGER order rests past the Donchian channel's CURRENT edge in the
   trade's direction (the 20-bar high for a long, the 20-bar low for a short) by the offset, and
   the exchange book is the watcher; the entry is taken when price trades through, not when the
   platform notices.

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

@@ -60,10 +60,10 @@ rules about the columns themselves, not about porting — they live in the skill
 - **VWAP reversion** → `dist_VWAP` band + `dist_VWAP_rank_far lte 5` for board-relative
   stretch; required `NOT [ADX_state in ["trending","extreme"]]` veto; scalp geometry +
   aggressive timeDecay (VWAP anchors daily at 00:00 UTC).
-- **Donchian / Turtle breakout** → `zone is "breakout high"` + `dist_swingHi gte 0` +
+- **Donchian / Turtle breakout** → `zone is "breakout high"` + `dist_donchianHi gte 0` +
   `RVOL gte 1.5`; `sr_resistance_break` 3 required; turtle exits = trend preset (trail from
   1R, giveback 50). Mirror with `"breakdown low"`. **Daily-breakout variant on any anchor:**
-  pin the structure at 1d — `zone_1d is "breakout high"`, `dist_swingHi_1d gte 0` (validated).
+  pin the structure at 1d — `zone_1d is "breakout high"`, `dist_donchianHi_1d gte 0` (validated).
   **Literal previous-day levels are native**: `dist_PDH gte 0` composes directly. Their `{abs: '1d'}`
   binding is stated in `## Header grammar` in the skill body.
 - **ICT / SMC (FVG + order blocks)** → `STRUCT_ZONES` is the native zone engine:

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

@@ -0,0 +1,58 @@
+---
+name: battlegrid-trade-proposal
+description: Find and stage a trade for one of the player's agents, for the player to approve. Activate whenever the player asks which coins fit an agent right now, wants a trade found or proposed for an agent, asks the agent to evaluate a coin, or wants to approve or decline a proposal it made. The scan is the agent's own gates over every active coin; the proposal is the agent's own conversational turn; approval is always the player's word.
+---
+
+# Trade Proposal
+
+You are finding and staging a trade for an agent the player configured — never placing one. Every
+step below reads what the server decided and puts it to the player in their terms; nothing here
+re-sorts a list, re-derives a verdict, or approves on the player's behalf.
+
+## 0. What is already held — before anything else
+
+- `list_pending_approvals` and `list_user_active_positions` first, every time.
+- A proposal holds the player's live-position slot for that coin across **all** their agents until
+  it is accepted, cancelled or expires. **Never propose on a coin the player already holds a pending
+  or live position on** — say why, and name the decision or position that holds it.
+
+## 1. Which coins fit the agent right now
+
+- `scan_agent_coins` for the agent. The rows arrive server-ranked: qualifying coins first by score,
+  then the rest with their first failing gate, then coins that could not be scored with the reason.
+- Read the rows **as written**: the rank, the verdict, the first failing gate, the unscorable
+  label. Never re-sort them and never re-derive a verdict from its numbers — the server's ranking
+  is the answer.
+- A refused scan (`RATE_LIMITED`) is a refusal: say the scan was refused and when it can be retried
+  (`retryAfterSeconds`). Never say "nothing fits".
+
+## 2. Propose
+
+- `propose_entry_decision` **only** on the coins the player named, or on the top qualifying row
+  when they asked for the best fit. One coin per call.
+- `userMessage` is the player's own words for the turn. Mint a **fresh UUID** `idempotencyKey` per
+  proposal; a retry with the same key replays the recorded result and never runs a second turn.
+- The call is synchronous and may take the turn's full LLM latency. Do not retry while it is in
+  flight; a same-key call during that time is refused with `CONFLICT`.
+
+## 3. Report the outcome in the player's terms
+
+- `type: "recommendation"` — the PROPOSED decision, awaiting approval. State the direction, the
+  entry, stop and take-profit levels, the position size, the **`convictionPercent`**, and the
+  expiry (`expiresAt`). No conviction floor was applied on this surface: the conviction is the
+  agent's own reading, and the player judges it.
+- `type: "no_trade"` — the reason (`reasonCode`) and the next coins worth asking about.
+- `type: "error"` — the engine's block or a post-billing failure, with its remedy:
+  `OPEN_POSITION_CONFLICT` means a position already holds the slot (see step 0);
+  `LLM_CREDITS_EXHAUSTED` means top up when `topupAvailable` is true; a `SURFACE` / `LLM_FAILURE`
+  means the model was billed and produced nothing usable — retry **with a new key**, since the
+  same key replays this failure.
+- A refused proposal (`RATE_LIMITED`) is a refusal with its retry-after. Never "nothing to do".
+
+## 4. Approve or decline — only on the player's word
+
+- Present the decision and **ask**. `accept_entry_decision` only after the player explicitly
+  approves; `cancel_entry_decision` only after they explicitly decline.
+- Never accept because the conviction reads high, because the scan ranked the coin first, or
+  because the player asked you to "find a trade" — finding is not approving. `get_entry_decision`
+  re-reads the row if the conversation moved on before they answered.