@battlegrid/mcp-server 31.2.77 → 31.2.79

package/README.md

@@ -24,6 +24,120 @@ 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 — v97 (a signal records the evidence it decided on)
+
+**Breaking at v97: an evaluated signal's evidence keys move, `BB_TOUCH` touches by %B, and a crossing is
+read on the bar that leaves zero.** v97 is the contract on top of v96.
+
+### Changed meaning — the same record, different keys
+
+- An evaluated signal's `indicatorValues` — on `get_signal_log`, `get_public_agent_signal_log_detail` and
+  `get_coin_signal_preview` — records the last price a live-priced signal evaluated under **`last_price`**.
+  Six signals recorded it under `price`: `MA_SMA200_ABOVE` / `_BELOW`, `SR_AT_SUPPORT` / `_RESISTANCE` and
+  `BOLLINGER_LOWER_TOUCH` / `_UPPER_TOUCH`; the three structure-approach signals now record it too.
+- **`price` means the last closed close** on every signal that records it.
+- The Bollinger touches add `bb_upper` and `bb_lower`, and their `bb_percent_b` is the live %B they
+  compared — never the closed-bar %B.
+- The EMA 5/13 crosses add `ema_cross` (`1` / `−1`), and the sector comparison signals add `ema5`, `ema13`
+  and `ema20`.
+- `MFI_SUSTAINED_*` and `CVD_BULLISH` / `CVD_BEARISH` record their prior-bar value when there is one, and
+  omit it when there is not.
+
+A signal records exactly the keys its declared vocabulary names. Records written before v97 keep the keys
+they were written with, so a reader of history meets both.
+
+### Changed values — the same fields, one rule each
+
+- **Crossings.** One zero-cross rule decides every crossing: a value that reaches zero has not crossed; one
+  that leaves zero has. Every `crossDetect` column (`MACD_cross`, `PPO_cross`, `ROC_cross` and authored
+  ones), the `EMA_CROSS` label, the MACD / PPO / stochastic cross signals and `FUNDING_RATE_FLIPPING` read
+  no crossing on a bar that lands exactly on zero. They read the crossing on the bar that leaves it.
+- **`BB_TOUCH` and `bandTouch`** classify a touch when %B is strictly below `0.05` or above `0.95` — the
+  touch signals' default thresholds. Before, a price within 2% of the band width of an edge, inclusive,
+  touched. A degenerate band reads `none`, and a `BBtouch` condition now agrees with the scorecard's touch
+  at defaults.
+- **RSI zone.** The projected RSI state is overbought strictly above 70 and oversold strictly below 30, as
+  the `RSI14_zone` columns already read it.
+- **Descriptions.** A served rule description states the thresholds that rule evaluates, and the ROC
+  descriptions read "positive and rising".
+
+### Widened output
+
+- `get_strategy_signal_definition`'s `indicators[].meta` gains `optional: true` on a key the signal records
+  only when its read is present — `prev_cvd_value` on `CVD_BULLISH` / `CVD_BEARISH`, `prev_mfi14_value` on
+  `MFI_SUSTAINED_*`. Every other key is always recorded when the signal has the data to evaluate.
+
+A key read at v96 is absent at v97 on the same signal, and a touch or a crossing read at v96 can read
+differently on the same bar — hence the MAJOR.
+
+## Contract history — v96 (a metric's meaning is declared once)
+
+**Breaking at v96: `efficiency` admits only a level or a price-fact series, and `nearestZoneDist` changes
+sign.** v96 is the contract on top of v95.
+
+### Rejected input — something you send is no longer accepted
+
+- `efficiency` over an increment or an oscillator metric — `CLOSE_CHANGE`, `VOLUME`, `RSI14`, `FUNDING_RATE`
+  and the like — is refused at construction, and so is `efficiency` as the outer of `distance` or `spread`
+  (`VALIDATION_ERROR`, authoring code `REPORT_COLUMN_CONSTRUCTION_FAILED` or `REPORT_COLUMN_CHAIN_UNSUPPORTED`),
+  by every tool that builds a report column. `distance` and `spread` chain `trajectory`, `aggregate` and
+  `rank`; the column contract and the vocabulary tools serve exactly those sets.
+- `BB_PCT_B` no longer composes `maxShare`: `%B` leaves `[0, 1]` when price closes outside a band.
+- A `rank` column with no `ordering` is gated as the default `hi` it ranks by, so it is refused wherever a
+  written `hi` is (`REPORT_COLUMN_PAIR_UNSUPPORTED`). Write the ordering you mean.
+- `transformId` is the closed enum of the seventeen transforms and `chainedTransformId` the enum of the five
+  chain outers, where each was any 1–40 character string. An id outside them is refused by schema.
+
+### Changed values — the same fields, a declared meaning
+
+- **`nearestZoneDist` is price's distance from the zone midpoint**, `((price − mid) / mid) × 100`: positive
+  when price is above the zone, negative below it. It was the midpoint's distance from price, with the
+  opposite sign. A range symmetric about zero reads the same window; a one-sided bound needs its sign
+  flipped.
+- `BB_PCT_B` offers all four rank orderings.
+- A `classifyZone` column declares and resolves its own metric's vocabulary in canonical labels — ADX's
+  strength bands, MFI's five bands — not a shared `overbought / oversold / neutral` set.
+- `highDev`, `lowDev` and `oiRegime` read live sources and declare the live clock, so a condition over them
+  is provisional on the live frame.
+- A chained column's formula binds its outer half to the inner column's header (`dist_VWAP`), and every
+  relative-change formula reads `((value − reference) / reference) × 100`.
+
+### Reshaped output
+
+- An authoring parameter's `defaultValue` on `get_metric_construction_hints` is typed per knob — `window`
+  and `offset` integers, `ordering` a rank ordering — and absent on `side`, `inputs` and `bars`.
+- A rendered section column's `role` is one enum of the same members, where it was a union of an enum and
+  five literals.
+
+An input v95 accepted is refused at v96, and a value read at v95 reads with the opposite sign — hence the
+MAJOR.
+
+## Contract history — v95 (a refusal names the verdict it applied)
+
+**Breaking at v95: a gate block's `conditionVerdict` is the verdict applied, not the one read.** v95 is the
+contract on top of v94.
+
+### Changed meaning — the same key, a different question
+
+- On `list_gate_blocks`, a conditions-stage `reasonDetail.conditionVerdict` is the verdict **applied** — the
+  one bound for the pair, which can be a held verdict this evaluation did not read — where it was the verdict
+  the conditions read. It is served only on a `CONDITION_VERDICT_OPPOSES_DIRECTION` or
+  `CONDITION_EXIT_RULE_CLOSES_DIRECTION` block recorded since v95; a `REQUIRED_CONDITION_FALSE` block, which
+  no verdict decided, and a block recorded before v95 no longer carry it. Read `observedVerdict` for what the
+  conditions read.
+
+### Widened output
+
+- The reason detail gains `observedVerdict`, served on every conditions-stage block, and `heldVerdict`,
+  `verdictDwellResolutions` and `verdictDwellRequired` — the dwell state the binding was resolved from,
+  served beside `conditionVerdict` and absent where it is. `get_signal_log` and
+  `get_public_agent_signal_log_detail` embed the same schema and never fill these keys: a block writes no
+  signal log.
+- `get_signal_log`'s `conditionEvaluation.verdict` and `get_agent_journal`'s `marketSnapshot.conditionVerdict`
+  keep meaning the verdict the evaluation observed.
+
+A key read at v94 answers a different question at v95 — hence the MAJOR.
+
 ## Contract history — v94 (every value you read names the bar it came from)
 
 **Breaking at v94: a timeless metric refuses an `offset`, and a value with no reading on its bar reads absent

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