@battlegrid/mcp-server 32.0.10 → 32.0.11

package/dist/index.d.ts

@@ -47,7 +47,7 @@ import { Client, StreamableHTTPClientTransport } from '@modelcontextprotocol/cli
  * 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 = "32.0.10";
+export declare const PACKAGE_VERSION = "32.0.11";
 export declare const DEFAULT_URL = "https://mcp.battlegrid.trade/mcp";
 export interface EnvConfig {
     apiKeys: string[];

package/dist/index.js

@@ -49,7 +49,7 @@ import { Client, SdkHttpError, StreamableHTTPClientTransport } from '@modelconte
  * 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 = '32.0.10';
+export const PACKAGE_VERSION = '32.0.11';
 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": "32.0.10",
+  "version": "32.0.11",
   "description": "BattleGrid MCP server — play crypto prediction games from AI agents",
   "type": "module",
   "main": "dist/index.js",

package/skills/EXPORT.json

@@ -1,20 +1,20 @@
 {
   "generator": "battlegrid-app/server/scripts/export-mcp-skills.mjs",
-  "contractVersion": "120.2.0",
+  "contractVersion": "113.0.0",
   "files": {
     "battlegrid-agent-management/SKILL.md": "9dc151c32c3578d06e8895c6752d7a64959bff6a6681a01d62ab65e1ea1590d1",
     "battlegrid-agent-management/references/agent-stage-examples.md": "dffcc353d61dfc7b5bb6a2b3077fc6bf8c760a34c287cafb3b59b99306f24195",
     "battlegrid-arena-play/SKILL.md": "2e37970a66b8738ffbc445a23da90651c1f41b56ce4eef551582ab123517ef74",
     "battlegrid-arena-play/references/entry-stage-examples.md": "0223f3743171ff213e943789d27590b2f65648398e85e10cd24938d5eb6af665",
     "battlegrid-market-analysis/SKILL.md": "fcbe98e30e1edce39bb170c224cdf20181934f62b5f3a26b293787c70eeb6229",
-    "battlegrid-radar-deployment/SKILL.md": "cf6664f51f92d40acce21a46f4fb078d9afe46c99c4f4b603bf002e73d4c5a23",
+    "battlegrid-radar-deployment/SKILL.md": "dfe8f354ac3dd426eedeac1ec080ac518e9c8cbfefdd26036afa61f80c08295c",
     "battlegrid-radar-deployment/references/arena-stage-examples.md": "d27cfed1f4663f267c4a7ecebe4a6e65a450fc74bd14ce8987fb61af5bbf2ca5",
-    "battlegrid-radar-deployment/references/radar-stage-examples.md": "13fc3f55d91d3da9754e1ed7fb27493b7b7ba4d40a6a7e8d1ee0365f90ea10de",
+    "battlegrid-radar-deployment/references/radar-stage-examples.md": "e3805f5c1b243135a7f25fb3a8cc6093dd242f8ad67b7e6b242bbdefa58a0735",
     "battlegrid-strategy-authoring/SKILL.md": "39cfa46b1f640e6800edb7e85a8f2c4b6b8786cddf71bb8244d172a44fc11d75",
     "battlegrid-strategy-authoring/references/strategy-stage-examples.md": "f10ecdc91f3660a708eee7a7bacefce2acbb46c9cf7e0ac1454bd54f839f39fd",
     "battlegrid-strategy-doctor/SKILL.md": "e34e055b0cc9b355bc1adeb5d49d464eaa0756ca3f48dc89ca2ccdda94e1311f",
-    "battlegrid-strategy-examples/SKILL.md": "82df6781b8dbb222407cc58f622f5fadb6f933aeb7efb855c26a9ae13620cca3",
-    "battlegrid-strategy-examples/references/playbooks.md": "275352be43652ca0fd36a35981ea7ffcfabdc4f9b33293826656ee500d3795e9",
+    "battlegrid-strategy-examples/SKILL.md": "597ddacdfc00955fcfd5a1afcc40b5ea72a0f658acbbebc8264afeecc46d2306",
+    "battlegrid-strategy-examples/references/playbooks.md": "2309eb7e8324f563c5b1b51e05da931b37c542484135a2be749eff6ef78aa40f",
     "battlegrid-strategy-examples/references/recipes.md": "635e03d163100f6de37cda1f6cc12928d5d36aa0ea883bf44fc72f17cbf3e98e",
     "battlegrid-strategy-examples/references/tradingview-ports.md": "9eaa926cbe8606c6a09f91007a0606042afbfdc50173a5b13ae9336d2e9e9b08",
     "battlegrid-trade-analysis/SKILL.md": "3f927b4f9796178526fa1673a2043c5f14358c39aa955de33192ea58641f18fb",

package/skills/battlegrid-radar-deployment/SKILL.md

@@ -107,12 +107,7 @@ is test-routing a regime. Never carry a fact from a radar conversation into it,
    Do not confirm a draft whose diagnostics carry an error: stage a fix.
 3. `preview_radar_resolution({ coinId, request: { kind: "DRAFT", draftVersion } })` at the version that
    read returned. It composes the draft over the deployed policy **exactly as the commit will write it**,
-   and refuses a draft no longer at that version with `DRAFT_VERSION_MOVED`. Its `ruleCloseCoverage`
-   counts, for each hours rule, the closes of its agent's `strategyTimeframe` bar the rule's hours let
-   it decide through `windowEndAt`. Before asking the player to commit, name every rule whose
-   `decidableCloses` is 0: its agent's timeframe, the served `windowEndAt`, and that it is this rule's
-   hours alone that hold no close — not the agent, which still decides closes it is on duty for through
-   another rule or the default. Never tell the player the agent will not trade.
+   and refuses a draft no longer at that version with `DRAFT_VERSION_MOVED`.
 
 To try a slot set without touching the draft, preview `{ kind: "SLOTS", slots }` — it resolves
 explicit slots and nothing can commit it.
@@ -127,19 +122,6 @@ from what the player asked for:
 | only in named hours and days | a rule with an hours condition |
 | in named regimes during named hours | a rule with one hours condition and one regime condition |
 
-When the player names an exchange session — New York, the New York open, London, the London open,
-the London–New York overlap, Tokyo, the Tokyo open — call `get_radar_market_hours` and stage that session's `hours`
-exactly as served, merged with any other session they name; never work session hours out yourself,
-because New York and London shift with daylight saving on their own dates and the overlap changes
-shape on each of those dates. The three opens are one hour wide, so they suit agents on 1h bars or
-faster. The days stay the player's choice. Tell the player the staged hours are UTC, that an hour is
-on duty from :00 through :59, and, when the session carries a `nextShift`, the date its hours change
-and that the rule keeps the hours it was given.
-
-Session closes are not presets. Asked for "the New York close" or any other session close, stage only
-the hours the player names, or raise flattening before the session ends as a separate idea — never
-work a close window out yourself.
-
 When the ask maps to no single row, or a refusal rules out the construction the player asked for,
 ask the player which construction they mean, naming the rows that fit — never stage one they did not
 choose. Complete stage payloads for every row are in `references/radar-stage-examples.md`.
@@ -370,9 +352,8 @@ Four reads, cheapest first. Stop as soon as the player's question is answered.
    refused it and nothing was traded. It is the only history of not-qualifying closes: the journal
    writes no row for one, and `resolvesNow` keeps only each agent's last decision — the one
    `reading.lastClose` (step 1) carries; this read holds every decision before it. Narrow with
-   `agentId`. Each record carries its whole evidence, so keep `limit` small; page back by passing
-   the response's `nextCursor` as `cursor`, and stop when `nextCursor` is null — that is the end of
-   the history. A bar still
+   `agentId`; page back by passing the response's `nextBefore` as `before`, and stop when
+   `nextBefore` is null — that is the end of the history. A bar still
    waiting inside its window has no record yet (`resolvesNow` shows its `closeDecision.state` as
    `DEFERRED`), and records are kept 90 days.
 4. **`get_radar_activity`** only for what steps 2 and 3 cannot do: more rows than its ten, a

package/skills/battlegrid-radar-deployment/references/radar-stage-examples.md

@@ -56,10 +56,7 @@ regime condition is the regime-reading floor, and must be a level one of the sel
 
 ## On duty only in named hours and days
 
-Hours are UTC, 0–23. Days run 0 (Sunday) to 6. Each is listed once. For a named exchange session —
-including the London and Tokyo opens and the London–New York overlap — stage the `hours` `get_radar_market_hours`
-serves for it rather than a set of your own; the example below is a shape, not a session. No session
-close is served: a close is staged only as hours the player names.
+Hours are UTC, 0–23. Days run 0 (Sunday) to 6. Each is listed once.
 
 ```json stage_radar_deployment_draft
 {

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

@@ -228,12 +228,9 @@ column selecting Developing above the strategy timeframe (`CONDITION_VERDICT_REA
 closure is what the condition reads directly plus everything reached through `conditionRef`,
 transitively: a referenced condition contributes what IT reads, so moving the clause into a building
 block does not launder it. A closure whose candle columns all read Confirmed — or whose operands no
-bar moves at all, such as a published regime label or a funding rate — admits a verdict at every
-decision, because a decision reads the completed strategy bar and a level is compared against that
-bar's close. A change over a horizon above the strategy timeframe — `chg4h` or `chg24h` on a `1h`
-strategy, and `oiRegime`, which reads the `1h` change, below `1h` — is a developing read whatever its
-selector: its bar is still in progress at the close, so it carries no verdict. Read a horizon at or
-below the strategy timeframe instead, or a Confirmed `CLOSE_CHANGE` on the higher timeframe.
+bar moves at all, such as a published regime label, an open-interest regime or a published rolling
+change — admits a verdict at every decision, because a decision reads the completed strategy bar and
+a level is compared against that bar's close.
 
 Evaluation is three-valued: UNRESOLVED never collapses to FALSE; a developing read is provisional,
 and so is any reading taken on the display lane's forming bar.
@@ -269,11 +266,10 @@ the served domain is refused (`CONDITION_HOLD_ILLEGAL`, the domain in `allowedDo
 a header admits only Once:
 
 - `NOT_REWINDABLE` — the value is stored for the current bar only (session and universe scalars,
-  ranks, zone entities, enrichment metrics, a change at or below the strategy timeframe). **Worked liquidity floor:**
+  ranks, zone entities, enrichment metrics, published rolling changes). **Worked liquidity floor:**
   `LIQUID_FLOOR` holds Once because `vol24hUsd` is a bundle scalar.
-- `DEVELOPING` — the column reads a bar still forming: a Developing candle column above the strategy
-  timeframe, or a change over a horizon above it. **Developing columns cannot be held**; set a candle
-  column Confirmed to count closes, or read a change at or below the strategy timeframe.
+- `DEVELOPING` — the column reads the bar still forming. **Developing columns cannot be held**; set
+  the column Confirmed to count closes.
 - `OFFSET` — the column already reads an earlier bar; remove the offset to count closes.
 - `BAR_STATE` — the header describes only the bar being decided.
 - `HISTORY` — not enough history is stored on that timeframe to count more than one close.
@@ -304,10 +300,8 @@ anchor's own close — so Developing there is legal and changes no decision. A c
 developing bar is single-frame: its clause holds Once (a Developing column cannot be held), it
 carries no verdict and it cannot be an exit rule. One exception overrides both the stored value and the default: a column reading a metric with
 no live value (itself, or a `spread` operand) reads completed bars at every rung, because the forming
-bar publishes nothing for it. A change (`chg5m` … `chg24h`, and `oiRegime`'s `1h` change) carries its
-horizon in the metric, so above the strategy timeframe it is Developing at every rung and under every
-selector. The resolved answer for a column is served on `effectiveParameters.bars`, and it states both
-exceptions.
+bar publishes nothing for it. The resolved answer for a column is served on
+`effectiveParameters.bars`, and it states that exception.
 
 **A higher-timeframe level is measured from the current strategy-bar price.** The distance to a `4h`
 Donchian band, and every candle label classifier (`MA_ALIGN`, `PRICE_ZONE`, `BB_TOUCH`), compares

package/skills/battlegrid-strategy-examples/references/playbooks.md

@@ -36,14 +36,11 @@ anything failing {LIQUID_FLOOR}."
 Custom `Positioning`: `FUNDING_RATE value`→`rate`, `aggregate w24`→`rate_mean24`,
 `FUNDING_ANN value`→`ann`, `OI_CHG value`→`oiChg`, `OI_PX_REGIME value`→`oiRegime` (vocab:
 new longs / new shorts / short covering / long liquidation), `MARK spread ORACLE`→
-`mark_oracle_spread`, `RSI14 value`, `CLOSE_CHANGE value @ {abs: 1d}`→`closeChg_1d` (Confirmed, the
-default above the strategy timeframe); plus `includeCvd`. Conditions:
+`mark_oracle_spread`, `RSI14 value`, `CHG_24H value`→`chg24h`; plus `includeCvd`. Conditions:
 `NO_LIQUIDATION_TAPE` required NOT-veto (`NOT [oiRegime is "long liquidation"]`);
 `CROWDED_LONGS` building block (`ann gte 25` + `oiChg gte 3` + `oiRegime is "new longs"`);
-`FADE_SHORT` verdict DOWN (ref + `RSI14 gte 65` + `closeChg_1d gte 5`); mirrored `SQUEEZED_SHORTS`
-/ `SQUEEZE_LONG` verdict UP (`closeChg_1d lte -5`). The confirmation is the prior completed UTC day's
-move, not today's: today's (`chg24h`) is a 1d bar still in progress at every 1h close, a developing
-read no verdict may carry. Levels 1.0–2.5 ATR, RR 1.5, ATR floor 0.5%. PM: BE 0.8R, no trail, timeDecay ON (120/60, 10→40, stale 25).
+`FADE_SHORT` verdict DOWN (ref + `RSI14 gte 65` + `chg24h gte 5`); mirrored `SQUEEZED_SHORTS`
+/ `SQUEEZE_LONG` verdict UP. Levels 1.0–2.5 ATR, RR 1.5, ATR floor 0.5%. PM: BE 0.8R, no trail, timeDecay ON (120/60, 10→40, stale 25).
 
 ### 3 · Relative-Strength Rotation with a Benchmark Gate — 4h cross-sectional