@battlegrid/mcp-server 31.2.83 → 31.2.86

package/README.md

@@ -24,6 +24,69 @@ 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 — v102 (your entry history's facets come with the first page)
+
+**Breaking at v102: `list_my_market_grid_entries` moves its counts, summary and agent options under one
+`facets` object, sent with the first page only, and every entry gains a payout state.** v102 is the
+contract on top of v101.1.
+
+### Reshaped output — something you read has moved or been added
+
+- **`outcomeCounts`, `summary` and `agentOptions` move under `facets`**, unchanged inside it:
+  `facets.outcomeCounts`, `facets.summary`, `facets.agentOptions`.
+- **`facets` comes with the first page only.** A page you read with a `cursor` carries `facets: null`.
+  Keep the first page's facets for the whole scroll: every page of one read shares the same filters, so
+  the first page's counts, summary and agent options describe all of them.
+- **Every entry gains `payoutState`**, in `list_my_market_grid_entries` and `get_my_market_grid_entry`:
+  `RECORDED` once settlement has recorded both of the entry's payouts, `UNDER_REVIEW` if it left one
+  unrecorded, and `null` while the entry is in play or cancelled.
+- **`facets.summary` gains `payoutsUnderReviewCount`**: how many settled entries the money figures leave
+  out because their payout is under review.
+
+### Behaviour behind unchanged schemas
+
+- **An entry under review has `netPnl: null`.** It is listed under `PLAYED` only, never under `PAID` or
+  `NOT_PAID`, and the summary leaves both its fee and its payout out of every money figure, so the totals
+  stay consistent. Today no entry is under review: the entries settled before settlement recorded both
+  payouts now record `0` for the payout they never received, so their net reads the same as before.
+- The five filters (`window`, `outcome`, `source`, `agentId`, `cursor`) accept exactly what they
+  accepted before. Only the `agentId` description changes: it now points at `facets.agentOptions`.
+
+A client that reads `outcomeCounts`, `summary` or `agentOptions` at the top level, expects them on every
+page, or rejects unknown entry fields, breaks at v102 — hence the MAJOR.
+
+## 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

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