@battlegrid/mcp-server 31.2.90 → 31.2.94

package/README.md

@@ -24,6 +24,78 @@ 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 — v108 (conditions are the only entry gate; signal rules are removed)
+
+**Breaking at v108: signal rules, the aggregate-score gate and the required-count gate are removed.**
+v108 is the contract on top of v107. A strategy's deterministic entry gate is its conditions: a
+required condition, or a condition that carries a verdict. A strategy that declares neither never
+trades, and its draft says so with the warning `NO_ENTRY_CONDITION`.
+
+### Removed tools
+
+- **`simulate_aggregate_score`, `list_strategy_signals`, `get_strategy_signal_definition`,
+  `derive_strategy_rule_view` and `get_coin_signal_preview`** leave discovery with no alias. A call
+  gets the standard unknown-tool refusal.
+
+### Rejected input — something you send is no longer accepted
+
+- **`stage_strategy_draft` refuses the `SIGNAL_RULES` and `SETUP_GATES` axes** as unrecognized keys.
+  The ATR floor `minAtrPct` is staged in the `TRADE_LEVEL_POLICY` axis, beside the stop-loss multiples
+  and the risk-reward minimum; a `TRADE_LEVEL_POLICY` stage without it is refused.
+- **`decide_trade` cites `entry.conditionChecklist`**: 1–8 items `{ conditionKey, verdict,
+  interpretation }` over the decision's evaluated entry conditions, each key at most once, `CONFIRM`
+  only on a condition that read TRUE. `signalChecklist` and `signalModulesUsed` are refused.
+- **The signal-log and agent-profile filters refuse `dominantBias`.**
+
+### Reshaped output — something you read has moved or been removed
+
+- **Strategies, agents and drafts** lose `signalRules`, `signalRuleTally`, `minAggregateScore` and
+  `minRequiredCount`; the trading-config catalog loses the gate dial steps.
+- **Qualification and scans** (`get_agent_coin_qualification`, `scan_agent_coins`, `scan_coin_agents`)
+  lose the score and required-count gates, the score shortfall and the signal readings. Scan rows rank
+  qualifying first, then by ticker or agent name.
+- **Radar reads** lose every score field: the activity events, the close decision, the curve samples
+  (`{ at, atrPct, qualified }`) and the curve digest.
+- **Entry decisions** carry `conditionChecklist` in place of `signalChecklist` and `signalModulesUsed`.
+  The public signal-log detail serves it as `{ name, outcome }` only.
+- **Signal logs and signal performance** lose the aggregate score, bias, conflict and count fields; a
+  signal-log detail loses its scorecard and serves `candidateLevels`. The agent explorer loses its
+  average score.
+
+### Narrowed enums
+
+- **The qualification and screen reasons lose `AGGREGATE_BELOW_MIN` and `REQUIRED_COUNT_BELOW_MIN`
+  and gain `NO_ENTRY_CONDITION`**, which is the first reason a strategy fails. The attempt reasons lose
+  `NO_ALLOCATED_SIGNALS`, and the error codes lose `REPAIR_REQUIRED`.
+
+A client that stages a signal rule or a gate, cites a signal in `decide_trade`, or reads a score field
+breaks at v108, which is why this is a MAJOR.
+
+## Contract history — v107.1 (an arena entry is recorded before its fee moves)
+
+**Additive at v107.1: a paid entry can be recorded while its fee confirms.** v107.1 is the contract on top
+of v107. The server now records your entry first, then sends the fee, then settles the entry on the
+venue's answer, so a fee can never move for an entry that was not recorded. No input changes.
+
+### Widened output
+
+- **`submit_market_grid`, `random_submit_market_grid` and `submit_agent_grid` results gain
+  `entryStatus`**: `ENTERED`, or `PAYMENT_PENDING` when the entry is recorded and its fee is still
+  confirming at the venue. A payment-pending entry plays once its fee lands before lock; otherwise it is
+  released, and a fee that lands after that is refunded.
+- **`entryState` gains `PAYMENT_PENDING`** on `get_my_market_grid_entry`. `list_my_market_grid_entries`
+  shares the element schema but never returns one.
+
+### Refusal vocabulary
+
+- **`details.wagerErrorCode` gains `ACCOUNT_NOT_UNIFIED`** on the three submit tools: an entry fee is
+  paid only from a unified-collateral account (`unifiedAccount` or `portfolioMargin`).
+
+### Behaviour behind unchanged schemas
+
+- **`check_market_grid_submission` answers `hasSubmitted: true`** for a payment-pending entry.
+- **`update_market_grid` refuses a payment-pending entry** with `CONFLICT` until it is in play.
+
 ## Contract history — v106 (the Opening Bell: a session starts at its scored candle's open)
 
 **Breaking at v106: Two-Look entry is retired. A deployment slot drops `entryStrategy`, and a

package/SKILL.md

@@ -17,7 +17,7 @@ from BattleGrid's own server so they name exactly the tools you reach here:
 |---|---|
 | Playing Market Grid sessions | `battlegrid-arena-play` |
 | Building or changing a strategy | `battlegrid-strategy-authoring` |
-| Composing beyond a bare template — conditions, weights, gates, trade levels, playbooks | `battlegrid-strategy-examples` |
+| Composing beyond a bare template — report sections, conditions, trade levels, playbooks | `battlegrid-strategy-examples` |
 | Creating and governing intelligence agents | `battlegrid-agent-management` |
 | Putting an agent on standing duty (Radar, Arena presets) | `battlegrid-radar-deployment` |
 | Reading the market — regime, funding, leaders, a coin deep-dive | `battlegrid-market-analysis` |
@@ -43,7 +43,7 @@ Never put `account` inside `request`, and never flatten request fields beside it
 
 ## Scopes
 
-- `mcp:read` — strategy discovery **and** non-financial configuration writes (stage and commit strategy and agent drafts, customize signals). Treat it as configuration authority, not view-only.
+- `mcp:read` — strategy discovery **and** non-financial configuration writes (stage and commit strategy and agent drafts). Treat it as configuration authority, not view-only.
 - `mcp:wager` — financial actions (submit paid entries, accept/cancel entry decisions, deployment policies). Enable **Server-Signed Wagers** in Profile → MCP to grant it. Pending entry decisions come from the conversational surface, which waits for approval; an agent deployed to a radar coin or a trading-enabled arena slot executes without one.
 
 ## Author a strategy or an agent, and bind them
@@ -93,7 +93,7 @@ The `play-market-grid` prompt (discover via `prompts/list`) provides a guided en
 
 ## Retired operations
 
-`create_strategy`, the plan tools (`compile_strategy_plan`, `stage_strategy_plan`, `apply_strategy_plan`), `update_strategy_signal_rule`, and the direct agent writers (`create_intelligence_agent`, `update_intelligence_agent`, `rebind_intelligence_agent`) are **retired** — they are absent from discovery and cannot be invoked. Stage into the entity's draft, read it back, and commit the version you read; a signal rule is a row of the strategy draft's `SIGNAL_RULES` axis, and a strategy binding is the agent draft's `STRATEGY_BINDING` axis. A deployment preview's `previewToken`, and the `confirm` on a deployment commit, resume, delete or draft discard, are retired the same way: a strict input refuses either key. Do not attempt flat legacy payloads; the server enforces a closed-world request root and the proxy never reconstructs them.
+`create_strategy`, the plan tools (`compile_strategy_plan`, `stage_strategy_plan`, `apply_strategy_plan`), `update_strategy_signal_rule`, the signal-rule tools (`simulate_aggregate_score`, `list_strategy_signals`, `get_strategy_signal_definition`, `derive_strategy_rule_view`, `get_coin_signal_preview`), and the direct agent writers (`create_intelligence_agent`, `update_intelligence_agent`, `rebind_intelligence_agent`) are **retired** — they are absent from discovery and cannot be invoked. Stage into the entity's draft, read it back, and commit the version you read; a strategy's entry gate is its conditions (a required or verdict-carrying condition — a strategy with none never trades, and its draft warns `NO_ENTRY_CONDITION`), its ATR floor `minAtrPct` is part of the `TRADE_LEVEL_POLICY` axis, and a strategy binding is the agent draft's `STRATEGY_BINDING` axis. A deployment preview's `previewToken`, and the `confirm` on a deployment commit, resume, delete or draft discard, are retired the same way: a strict input refuses either key. Do not attempt flat legacy payloads; the server enforces a closed-world request root and the proxy never reconstructs them.
 
 ## Common errors
 
@@ -106,6 +106,5 @@ The `play-market-grid` prompt (discover via `prompts/list`) provides a guided en
 | `DRAFT_VERSION_MOVED` | The draft changed after you read it, or no draft is held (`details.draftVersion` null) | Call `get_<kind>_draft` again, show the player what it now holds, and commit only on their word |
 | `DRAFT_AXIS_CONTESTED` | The player changed `details.contestedAxes` in their open form after the version you staged against | Read the draft again and propose against what they now have |
 | `CONFLICT` on a commit | The live revision moved after the draft read | Read the draft again, show the player the new diff and impact, and commit at the new `committedRevision` only on their word |
-| Required at allocation Off | A rule flags `required` on a signal weighted `0` (contract 34) | Read `details.inertRequiredSignalIds`; per signal either raise `allocation` or set `required: false` |
 | Method not found | Calling a retired/unknown tool | Re-run `tools/list`; stage, read and commit through the entity's draft |
 | `Wager scope required` | `mcp:wager` not enabled | Enable Server-Signed Wagers in Profile → MCP |

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