@battlegrid/mcp-server 31.2.82 → 31.2.85

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 — v101.1 (swing highs, swing lows and the structure label)
+
+**Additive at v101.1: the catalog gains three swing-structure metrics.** v101.1 is the contract on top of
+v101; nothing you send today is refused and nothing you read is reshaped.
+
+### Widened input — something new you can send
+
+- **`SWING_FRACTAL_HIGH` and `SWING_FRACTAL_LOW`** — the most recent swing high and swing low: a bar
+  whose high is at or above the two highs before it and strictly above the two after it (Pine's
+  `ta.pivothigh(2, 2)` tie rule), and the mirror on the lows. A swing is published from the bar that
+  completes its right side — never under its own bar, never from a forming bar — and held until the
+  next swing on its side. They are candle price levels: every transform a candle level takes,
+  `levelInteraction` included, and they rank across the board as `dist_fractalHi` / `dist_fractalLo`.
+- **`SWING_FRACTAL_LABEL`** — the most recent swing against the previous one on its side: `HH` / `LH` for
+  a high (an equal high is `LH`), `HL` / `LL` for a low (an equal low is `HL`), `none` when no comparable
+  pair is in reach. A held state, value-only; on too short a history it reads nothing.
+- **Break of structure** is `dist_fractalHi crossesAbove 0` / `dist_fractalLo crossesBelow 0`; a step of
+  the level onto a newly confirmed swing never fires it.
+
+### Widened output
+
+- The catalog and vocabulary surfaces list the three keys, and the authoring digest's `metricKeys` gains
+  them.
+
+### Still refused
+
+- The headers are `fractalHi` / `fractalLo` / `fractalLabel`. The `swingHi` / `swingLo` stems retired at
+  v53 (the Donchian channel's old names) stay refused: `dist_swingHi` is still `CONDITION_COLUMN_UNKNOWN`.
+
+A client that treats the metric vocabulary as a closed set re-reads it; no request is refused — hence
+the MINOR.
+
+## Contract history — v101 (an agent on a radar cannot be archived)
+
+**Breaking at v101: `archive_intelligence_agent` refuses an agent held in any radar deployment, and its
+refusal names a fourth blocker.** v101 is the contract on top of v100.
+
+### Narrowed acceptance — the same request, refused where it was accepted
+
+- **`archive_intelligence_agent` refuses an agent that holds a slot in any radar deployment, paused ones
+  included.** The input schema is unchanged: a call that archived such an agent before now gets the
+  existing `CONFLICT`. A paused radar still holds its slots, so pausing does not clear it. Find the coins
+  with `list_radar_deployments`, then commit a radar draft without the agent or call
+  `delete_radar_deployment`, and archive again.
+
+### Widened enum
+
+- **`details.archiveBlockers[].reason` gains `RADAR_DEPLOYED`**, after `DEPLOYED`, `OPEN_TRADES` and
+  `ACTIVE_SESSION`. Its `detail` reads `in N radar deployment(s)`, counting every radar deployment that
+  holds the agent.
+
+### Behaviour behind unchanged schemas
+
+- An archived agent holds no deployment slot in either venue, so `activate_intelligence_agent` arms
+  nothing: the agent trades again only once you deploy it.
+- A `commit_radar_deployment_draft` or `commit_deployment_policy_draft` that races an archive of one of its
+  agents is refused with the existing `CONFLICT`. Read the draft again; its diagnostics name the archived
+  agent.
+
+A client that reads `archiveBlockers[].reason` as a closed set, or expects an archive of a radar-deployed
+agent to succeed, breaks at v101 — hence the MAJOR.
+
 ## Contract history — v100 (what one bar did: level interaction, candle patterns, gaps, runs)
 
 **Breaking at v100: the `bandTouch` transform is retired and `levelInteraction` takes its place; a column

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