@battlegrid/mcp-server 32.0.61 → 32.0.62

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.d.ts CHANGED
@@ -47,7 +47,7 @@ import { Client, StreamableHTTPClientTransport } from '@modelcontextprotocol/cli
47
47
  * being asked. Move it for a change to THIS package — a proxy fix, a dependency bump, a docs
48
48
  * correction. Never move it to track the server.
49
49
  */
50
- export declare const PACKAGE_VERSION = "32.0.61";
50
+ export declare const PACKAGE_VERSION = "32.0.62";
51
51
  export declare const DEFAULT_URL = "https://mcp.battlegrid.trade/mcp";
52
52
  export interface EnvConfig {
53
53
  apiKeys: string[];
package/dist/index.js CHANGED
@@ -49,7 +49,7 @@ import { Client, SdkHttpError, StreamableHTTPClientTransport } from '@modelconte
49
49
  * being asked. Move it for a change to THIS package — a proxy fix, a dependency bump, a docs
50
50
  * correction. Never move it to track the server.
51
51
  */
52
- export const PACKAGE_VERSION = '32.0.61';
52
+ export const PACKAGE_VERSION = '32.0.62';
53
53
  export const DEFAULT_URL = 'https://mcp.battlegrid.trade/mcp';
54
54
  const MAX_RETRIES = 3;
55
55
  const RETRY_DELAYS_MS = [2000, 4000, 8000];
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@battlegrid/mcp-server",
3
- "version": "32.0.61",
3
+ "version": "32.0.62",
4
4
  "description": "BattleGrid MCP server — play crypto prediction games from AI agents",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -1,25 +1,25 @@
1
1
  {
2
2
  "generator": "battlegrid-app/server/scripts/export-mcp-skills.mjs",
3
- "contractVersion": "142.3.0",
3
+ "contractVersion": "143.0.0",
4
4
  "files": {
5
5
  "battlegrid-agent-management/SKILL.md": "324ef8181bfcfc99b955d9644ed543c6ab91071153d43f77ccf0a4979b896b09",
6
6
  "battlegrid-agent-management/references/agent-stage-examples.md": "dffcc353d61dfc7b5bb6a2b3077fc6bf8c760a34c287cafb3b59b99306f24195",
7
7
  "battlegrid-arena-play/SKILL.md": "fdaabcd2e5ce3946ee96e553ce2e1931a822b84f91b0c94ce86a8bde0cc1d50f",
8
8
  "battlegrid-arena-play/references/entry-stage-examples.md": "0223f3743171ff213e943789d27590b2f65648398e85e10cd24938d5eb6af665",
9
9
  "battlegrid-market-analysis/SKILL.md": "e50a63492c635af9e8748561148efd7e1d9aafdfb843acc657e557670b2f55e4",
10
- "battlegrid-officers/SKILL.md": "0e5b4fd7a11fc1b6643eecd0008dfe1528b915ee00d0a99be9aca1e3934d57f7",
10
+ "battlegrid-officers/SKILL.md": "0ac2173d0026b7329171fe24d38185e7717196340778d402c7af1aa74ea34bc8",
11
11
  "battlegrid-officers/references/officer-stage-examples.md": "ef46ba26f4b36c9964b5bde95fdf98e5952c3786b77be5f136056cac792f0aec",
12
- "battlegrid-radar-deployment/SKILL.md": "cd058d887e1342f42ce855708178d5f746400835a204e92238b63ec1fe57bf30",
12
+ "battlegrid-radar-deployment/SKILL.md": "5a72ee1aede27adbbb398ee99883ce36579c01352a0543782451af5d9a91d5f9",
13
13
  "battlegrid-radar-deployment/references/arena-stage-examples.md": "d27cfed1f4663f267c4a7ecebe4a6e65a450fc74bd14ce8987fb61af5bbf2ca5",
14
- "battlegrid-radar-deployment/references/radar-stage-examples.md": "13fc3f55d91d3da9754e1ed7fb27493b7b7ba4d40a6a7e8d1ee0365f90ea10de",
14
+ "battlegrid-radar-deployment/references/radar-stage-examples.md": "a07a6f1c525a5c4d60b5ba3ec9d896c6e4a0f8fb9968b9fd539c738956babc47",
15
15
  "battlegrid-strategy-authoring/SKILL.md": "e2422b0e02de6d240bbab261ed1181b32d175bf877f499d7df556eca31ce5133",
16
16
  "battlegrid-strategy-authoring/references/strategy-stage-examples.md": "f10ecdc91f3660a708eee7a7bacefce2acbb46c9cf7e0ac1454bd54f839f39fd",
17
- "battlegrid-strategy-doctor/SKILL.md": "24c2208cf6832f1fc34e1b1c52acd8dae10f56b9860aaf27b450a62a9fb74634",
17
+ "battlegrid-strategy-doctor/SKILL.md": "4be392e51f3b5e76ff4aa22f61700236e8b1e19dfe286aeda8ed98e48a8457ba",
18
18
  "battlegrid-strategy-examples/SKILL.md": "cbbc7a7271aaa9f530a11d91511f4bf35a9632aa3ab67ecd996975c65ae72625",
19
19
  "battlegrid-strategy-examples/references/playbooks.md": "59996c37eea08e7ce398e49304171939e55c968400a1603597d6737faf9e1771",
20
20
  "battlegrid-strategy-examples/references/recipes.md": "4136ff306f32d1e3aa612ac13a116d58df2177f619464ab2481a84f608e56cfc",
21
21
  "battlegrid-strategy-examples/references/tradingview-ports.md": "bc63e26b16458fd17b7bc567541fc9889ee857b444ccb2d3f011545635758d8f",
22
- "battlegrid-trade-analysis/SKILL.md": "140d847f24e98845736d4f0c2e72b318a4d235413f72f072d2fe6d0daa5f64db",
23
- "battlegrid-trade-proposal/SKILL.md": "bf8f3794478cdecc989020bd775c3c91744f72b440b1a90f88f6700c9a61ca24"
22
+ "battlegrid-trade-analysis/SKILL.md": "ec0b543bc62fe66d629833b10e4bc58548be1fee57f29c04f41f036e860af1ca",
23
+ "battlegrid-trade-proposal/SKILL.md": "8d833022f753dfc5a765eca2fcd272c4f29d22b8444bc00c14ce63571646ba71"
24
24
  }
25
25
  }
@@ -45,9 +45,11 @@ confirmed before it is called.
45
45
  refuses either.
46
46
  - **Show, then commit on the player's word.** Read `get_officer_draft` and show the diff, the diagnostics and the
47
47
  impact — `nextRunAt` is when it first runs, and a create's `admission` says how many officers the player holds
48
- against the limit and how many more it admits (`officersRemaining`). Commit with `commit_officer_draft` naming
49
- exactly the `draftVersion` and `committedRevision` the read returned, and only when the player says so. A cadence
50
- of `OFF` keeps the setup and runs nothing on a schedule.
48
+ against their account plan's officer limit and how many more it admits (`officersRemaining`). Every unarchived
49
+ officer counts, paused ones included; a create past the limit is refused as `PLAN_LIMIT_REACHED`, and archiving
50
+ an officer frees its place. Commit with `commit_officer_draft` naming exactly the `draftVersion` and
51
+ `committedRevision` the read returned, and only when the player says so. A cadence of `OFF` keeps the setup and
52
+ runs nothing on a schedule.
51
53
  - **Archive** with `archive_officer` only on the player's word: an archived officer runs no more, and its open
52
54
  reviews stay in the inbox.
53
55
  - In the app, the player sets an officer up in its own console, where this conversation may be docked beside the
@@ -1,18 +1,18 @@
1
1
  ---
2
2
  name: battlegrid-radar-deployment
3
- description: Deploy the player's agents to standing duty — per-coin Radar policies that put every matching rule's agent on duty and fire real trades at confirmed closes, and per-preset Arena deployment policies that enter sessions automatically. Reads what is deployed now, stages a change into the player's draft, previews what it would actually resolve to, commits it only after the player has seen that preview, and un-deploys with the blast radius stated. Activate whenever the player wants an agent put on duty, wants to change or pause a deployment, asks what would fire right now or why nothing is firing, or wants to stop a coin or a preset being traded automatically.
3
+ description: Deploy the player's agents to standing duty — Radar deployments, each one team's watch on one coin, that put every matching rule's agent on duty and fire real trades at confirmed closes, and per-preset Arena deployment policies that enter sessions automatically. Reads what is deployed now, stages a change into the player's draft, previews what it would actually resolve to, commits it only after the player has seen that preview, and un-deploys with the blast radius stated. Activate whenever the player wants an agent put on duty, wants to change or pause a deployment, asks what would fire right now or why nothing is firing, or wants to stop a coin or a preset being traded automatically.
4
4
  ---
5
5
 
6
6
  # Radar & Deployment
7
7
 
8
8
  You are handing agents **standing authority**. A Radar policy puts EVERY rule whose conditions match
9
9
  on duty at once — each rule's regime read at its own agent's regime timeframe — and fires real trades
10
- at their confirmed closes with no further human action, at most one per coin per pass, offered in rule
11
- priority; a deployment policy enters real sessions the same way.
10
+ at their confirmed closes with no further human action, at most one per deployment per pass, offered
11
+ in rule priority; a deployment policy enters real sessions the same way.
12
12
  Nobody is watching when it happens — which is why the player has to see what a policy resolves to
13
13
  *before* it exists, not after.
14
14
 
15
- Radar (per coin) and Arena deployment (per preset) are **separate bounded contexts**. They share
15
+ Radar (per team and coin) and Arena deployment (per preset) are **separate bounded contexts**. They share
16
16
  no slot shape, no condition union and no resolution type. Never carry a fact from one to the other,
17
17
  and never describe them as one thing with two modes.
18
18
 
@@ -21,6 +21,13 @@ trades a coin on its own only where a Radar policy puts it on duty, and an entry
21
21
  needs no deployment. An Arena deployment enters an agent into a preset's sessions and grants
22
22
  **no** trade permission — to have an agent trade a coin on its own, deploy it on Radar.
23
23
 
24
+ **A Radar deployment is one team's watch on one coin.** Each team trades on its own wallet, so a coin
25
+ may be deployed once per team: Main's BTC and Swing's BTC are two deployments that sweep, fire, cool
26
+ down and hold positions independently — one position per team per coin. Every Radar tool names the
27
+ deployment with `coinId` **and** `teamId`; a `teamId` you omit addresses the player's **Main** team, so
28
+ on a coin deployed for another team always pass that team. `list_radar_deployments` rows carry each
29
+ deployment's `teamId` and `teamName`. The draft commit always names its team.
30
+
24
31
  ## The five failures this flow exists to prevent
25
32
 
26
33
  1. **A write with no fresh preview.** *Cue: any `commit_radar_deployment_draft`,
@@ -53,14 +60,15 @@ Arena deployment is keyed on `presetId` (a UUID) — from `list_game_presets`.
53
60
 
54
61
  Then read what exists:
55
62
 
56
- - `get_radar_deployment` (one coin) or `list_radar_deployments` (the fleet, plus the platform
63
+ - `get_radar_deployment` (one deployment: `coinId` and `teamId`) or `list_radar_deployments` (the fleet, plus the platform
57
64
  `radarPaused` kill-switch — if that is set, say so up front: nothing will fire whatever you
58
65
  write). A `SCANNING` card whose reason is `ENTRIES_PAUSED` is the platform's **entry pause**: new
59
66
  entries are paused platform-wide while market data is missing across many coins. Say that up front
60
67
  too — the radar takes no new entry on any coin until it lifts, which it does by itself once the
61
68
  data is back, and nothing the player changes on a deployment clears it.
62
- - **For Radar, also read the player's draft of the coin** with `get_radar_deployment_draft` — or
63
- `list_radar_deployment_drafts` when no coin is named yet. The player may be part-way through a
69
+ - **For Radar, also read the player's draft of the deployment** with `get_radar_deployment_draft`
70
+ (`coinId` and `teamId`) — or `list_radar_deployment_drafts` when no deployment is named yet; each of
71
+ its rows names its `teamId` and `coinId`. The player may be part-way through a
64
72
  change in their radar builder. **If a draft exists, say so** — what it holds, and when and from
65
73
  where it was last written — and propose against it rather than starting over beside it.
66
74
  - `get_deployment_policy` / `list_deployment_policies` for Arena, and **the player's draft of the
@@ -73,9 +81,10 @@ Then read what exists:
73
81
  If the question is *why did my radar agent not fire*, do not start from the journal — **go to step
74
82
  5**, which reads state first and pattern second.
75
83
 
76
- **In a conversation the radar builder hosts** — your context names the radar builder and a coin id —
77
- the player's builder is open on that coin whether or not a draft exists yet. Stage every change into
78
- that coin's draft, naming that `coinId`; it lands in their builder as a proposal. Their own Save
84
+ **In a conversation the radar builder hosts** — your context names the radar builder, a team and a coin
85
+ id — the player's builder is open on that team's deployment of the coin whether or not a draft exists
86
+ yet. Stage every change into that deployment's draft, naming that `coinId` and that `teamId`; it lands
87
+ in their builder as a proposal. Their own Save
79
88
  commits it; commit it yourself only when they explicitly confirm through `ask_user`, after the
80
89
  preview this flow requires. The builder's state — its rules, the default agent, who is on duty now —
81
90
  arrives as the turn's attached scope. An axis their form rewrote after your proposal is their answer:
@@ -88,24 +97,26 @@ is test-routing a regime. Never carry a fact from a radar conversation into it,
88
97
 
89
98
  ### 2. Stage the change, then preview exactly what would be written
90
99
 
91
- **Radar** — the change goes into the player's draft of the coin, never straight to the policy:
100
+ **Radar** — the change goes into the player's draft of the deployment, never straight to the policy.
101
+ Name the `coinId` and the `teamId` on every call below:
92
102
 
93
103
  1. `stage_radar_deployment_draft` with `draftVersion` = the `version` you read (0 when there was
94
104
  no draft) and only the axes you are changing, each WHOLE: `RULES` (the complete ordered rule list
95
105
  — first is highest priority; every rule that matches is on duty, so priority decides only which
96
- agent is offered the coin's one fire on a pass) and `DEFAULT_SLOT` (the catch-all, on duty only
106
+ agent is offered the deployment's one fire on a pass) and `DEFAULT_SLOT` (the catch-all, on duty only
97
107
  when no rule is, or null for none). A Radar policy has **no timeframe**: each rule's regime
98
108
  condition is read at its agent's own regime timeframe, which every slot reports as
99
109
  `agentRegimeTimeframe`. Staging writes nothing live and shows the change in the player's builder as
100
110
  a proposal. A refusal naming axes means the player changed them after your read: read again and
101
111
  propose against what they now have.
102
112
  2. `get_radar_deployment_draft` — the draft as it now stands: its `draftVersion`, the
103
- `committedRevision` it would be published over (null for a coin with no policy yet), the diff
113
+ `committedRevision` it would be published over (null for a team with no policy on the coin yet), the diff
104
114
  against the deployed policy, the `diagnostics` a commit would refuse, and the `impact` — who goes
105
115
  on duty, whether it trades once committed, and for a first deployment the coin cap
106
- (`admission.coinCapReached` true means the commit will be refused until a coin is un-deployed).
116
+ (`admission.coinCapReached` true means the commit will be refused until a deployment is un-deployed;
117
+ a coin deployed for two teams counts twice).
107
118
  Do not confirm a draft whose diagnostics carry an error: stage a fix.
108
- 3. `preview_radar_resolution({ coinId, request: { kind: "DRAFT", draftVersion } })` at the version that
119
+ 3. `preview_radar_resolution({ coinId, teamId, request: { kind: "DRAFT", draftVersion } })` at the version that
109
120
  read returned. It composes the draft over the deployed policy **exactly as the commit will write it**,
110
121
  and refuses a draft no longer at that version with `DRAFT_VERSION_MOVED`. Its `ruleCloseCoverage`
111
122
  counts, for each hours rule, the closes of its agent's `strategyTimeframe` bar the rule's hours let
@@ -261,18 +272,18 @@ the reason — and **names what the change does to the stored policy**, read fro
261
272
 
262
273
  Then:
263
274
 
264
- - **Radar** → `commit_radar_deployment_draft({ coinId, draftVersion, expectedRevision, teamId })`,
265
- naming exactly the `draftVersion` and `committedRevision` your draft read returned — the version
266
- your preview resolved. Ask with `ask_user` first and commit only after an explicit confirming pick.
267
- The axes it published leave the draft.
268
- `teamId` is the team the deployment trades on, and a team is never drafted. For a deployed coin,
269
- pass the `teamId` its `list_radar_deployments` (or `get_radar_deployment`) row carries: a
270
- deployment keeps its team for life, and another team is a CONFLICT naming the stored one. For a
271
- first deployment, choose one of the player's teams from `get_account_state.teams` (ask when there
272
- is more than one) and name it in the confirmation. Every slot agent must trade on that team. A
273
- platform agent trades on Main, so it fits only a Main deployment. A slot agent of another team is a
274
- VALIDATION_ERROR naming the agent and its team. The draft read reports it beforehand for a deployed
275
- coin, and for a first deployment it reports slot agents that trade on different teams.
275
+ - **Radar** → `commit_radar_deployment_draft({ coinId, teamId, draftVersion, expectedRevision })`,
276
+ naming exactly the `teamId`, `draftVersion` and `committedRevision` your draft read returned — the
277
+ version your preview resolved. Ask with `ask_user` first and commit only after an explicit confirming
278
+ pick. The axes it published leave the draft.
279
+ `teamId` is **required** and never inferred: the commit writes that team's deployment of the coin
280
+ and nothing else. For a deployed one, pass the `teamId` its `list_radar_deployments` (or
281
+ `get_radar_deployment`) row carries. For a first deployment, choose one of the player's teams from
282
+ `get_account_state.teams` (ask when there is more than one), stage and read the draft under it, and
283
+ name it in the confirmation; a coin another team holds stays deployable for this one. Every slot
284
+ agent must trade on that team. A platform agent trades on Main, so it fits only a Main deployment. A
285
+ slot agent of another team is a VALIDATION_ERROR naming the agent and its team, which the draft read
286
+ reports beforehand.
276
287
  - **Arena** → `commit_deployment_policy_draft({ presetId, draftVersion, expectedRevision })`,
277
288
  the same way.
278
289
 
@@ -284,11 +295,12 @@ ask for again.
284
295
 
285
296
  ### 4. Pause, resume, discard, delete
286
297
 
287
- **Pause a coin's Radar** → `pause_radar_deployment({ coinId })`. No preview and no revision: stopping
288
- never waits on a read. The player's draft keeps its content and is re-based onto the paused revision.
289
- **Resume** → preview the deployed policy with `preview_radar_resolution({ coinId, request: { kind: "COMMITTED" } })`, tell the player which
298
+ **Pause a deployment** → `pause_radar_deployment({ coinId, teamId })`. No preview and no revision:
299
+ stopping never waits on a read. Another team's deployment of the coin keeps trading. The player's draft
300
+ keeps its content and is re-based onto the paused revision.
301
+ **Resume** → preview the deployed policy with `preview_radar_resolution({ coinId, teamId, request: { kind: "COMMITTED" } })`, tell the player which
290
302
  agents will go on duty again, and on their word
291
- `resume_radar_deployment({ coinId, expectedPolicyId, expectedRevision })` naming the `policyId` and
303
+ `resume_radar_deployment({ coinId, teamId, expectedPolicyId, expectedRevision })` naming the `policyId` and
292
304
  `revision` that preview returned — so it re-arms the policy the player was shown, or nothing.
293
305
 
294
306
  **Pause an arena** → `pause_deployment_policy({ presetId })`, and **resume** it the Radar way: preview
@@ -304,14 +316,14 @@ same cancellation and refund as their own Cancel button. Say nothing is cancelle
304
316
 
305
317
  **Discard a draft** only on the player's word. Read it first and tell the player what it holds and
306
318
  when and from where it was last written; then
307
- `discard_radar_deployment_draft({ coinId, draftVersion })` or
319
+ `discard_radar_deployment_draft({ coinId, teamId, draftVersion })` or
308
320
  `discard_deployment_policy_draft({ presetId, draftVersion })` at **the version you read**.
309
321
  If the draft moved since, it is refused with `DRAFT_VERSION_MOVED` and nothing is removed — read it
310
322
  again and show them.
311
323
 
312
324
  **Deletes** — `delete_radar_deployment` / `delete_deployment_policy` remove the **entire** policy —
313
325
  every slot and condition — and revoke the standing authority. Un-deploying **also ends the player's
314
- draft** of the coin or the arena. There is no preview here, and correctly so: there is no resolution
326
+ draft** of the deployment or the arena; another team's deployment of the coin, and its draft, stand. There is no preview here, and correctly so: there is no resolution
315
327
  to preview once the policy is gone. The evidence is **the deployment's own read**, which supplies the
316
328
  `expectedPolicyId` and `expectedRevision` both deletes carry — a policy removed and redeployed since
317
329
  your read is refused rather than removed.
@@ -331,13 +343,13 @@ Four reads, cheapest first. Stop as soon as the player's question is answered.
331
343
  1. **`get_radar_deployment` → `resolvesNow`** for what is true **right now**: the coin's section and
332
344
  reason, and one `onDuty` row per agent — its blocked reason and since when, its qualification
333
345
  block, its cooldown, whether its edge is spent, its last fire and its close clock. A row whose last
334
- close reads `CLAIMED` qualified but lost the coin's one fire that pass to a higher-priority agent;
346
+ close reads `CLAIMED` qualified but lost the deployment's one fire that pass to a higher-priority agent;
335
347
  its edge is preserved and it fires at a later close only if it still qualifies there. A `SCANNING`
336
348
  coin whose reason is `ENTRIES_PAUSED` is under the entry pause (step 1): its agents still decide and
337
349
  record every close, and a close that qualifies is held — its fire refused, its edge preserved,
338
350
  journaled and recorded as `EDGE_PRESERVED_ENTRIES_PAUSED` with `scanBlockReason` `ENTRIES_PAUSED` —
339
351
  so it fires at a later close only if that close qualifies on its own data after the pause lifts. A
340
- lower-priority agent behind that fire reads `CLAIMED` on the same bar: the coin's one fire went to
352
+ lower-priority agent behind that fire reads `CLAIMED` on the same bar: the deployment's one fire went to
341
353
  the agent the pause refused, not to a trade. That is the whole answer while the pause lasts; never
342
354
  send the player to change an agent or a policy for it. Most "is it working?" questions end here.
343
355
  When the question is what ONE on-duty agent of a scanning coin needs to fire — which condition
@@ -347,8 +359,9 @@ Four reads, cheapest first. Stop as soon as the player's question is answered.
347
359
  agent reads now, and `lastClose` is the decision its row names as its last close, with the reading
348
360
  that bar was decided on.
349
361
  2. **`get_radar_activity_summary`** for everything else about "why is it quiet", in ONE call. Pass
350
- `agentId` when the question is about one agent — "why isn't Hawk firing on SOL?" — and the read is
351
- that agent's history on the coin. Without it the read is the **coin feed**: the deployment's
362
+ `agentId` when the question is about one agent — "why isn't Hawk firing on SOL?" — with the `teamId`
363
+ Hawk trades on, and the read is that agent's history on that team's deployment. Without it the read
364
+ is the **coin feed**: the deployment's
352
365
  lifecycle, status changes, duty changes and fires, with no agent's gates, an empty `curveDigest`
353
366
  and no curve agent. An `agentId` the player cannot access is answered as not found. It carries
354
367
  three parts and they answer three different questions, each on its own scope:
@@ -10,8 +10,11 @@ Every `<UPPER_SNAKE>` value is a placeholder. Replace it with the id a read retu
10
10
  - `<AGENT_ID>` comes from your agent list.
11
11
  - `<OTHER_AGENT_ID>` is a second agent from your agent list, where an example deploys two.
12
12
 
13
+ Every example addresses the player's Main team's deployment of the coin. For another team's deployment,
14
+ add its `teamId` (from `list_radar_deployments` or `get_account_state.teams`) beside `coinId`.
15
+
13
16
  Never send a placeholder as written, and never invent an id. `draftVersion` is the version
14
- `get_radar_deployment_draft` returned: 0 when the coin has no draft. Each axis you send is written whole, and an axis
17
+ `get_radar_deployment_draft` returned: 0 when the deployment has no draft. Each axis you send is written whole, and an axis
15
18
  you omit keeps the value the draft already has.
16
19
 
17
20
  ## On duty whenever no rule matches — the default slot
@@ -64,7 +64,8 @@ Three reads, and they are not interchangeable:
64
64
  agent's `tradingTeamId` on `get_agents_hub`, or a `list_radar_deployments` row's `teamId`. For "why did nothing happen on SOL", read
65
65
  `list_gate_blocks` for the pre-model refusals on that coin, and for a Radar coin
66
66
  `get_radar_activity_summary` for its causes, then `get_radar_close_decisions` for the bars it
67
- decided.
67
+ decided — both on the team the agent trades on, as `teamId` (a `list_radar_deployments` row's
68
+ `teamId`); without one they read Main's deployment.
68
69
  - **`get_agent_coin_qualification` answers the forward-looking half.** The reason codes above say
69
70
  why an agent did NOT trade in the past; this says whether a coin would route for it RIGHT NOW,
70
71
  and which gate stops it — the strategy's entry condition, candidate levels, the ATR% volatility
@@ -117,7 +117,8 @@ reading a clean report about a messy account learns nothing.
117
117
  One trade's fills are `get_trade_outcome_by_decision`'s, on the trade's `decisionId` from
118
118
  `list_agent_trades`; never assign an account fill to an agent by its coin and time.
119
119
  - `get_deployment_policy` / `get_radar_deployment` when the protection state comes from standing
120
- policy rather than the position itself. `list_gate_blocks` when something looks like it should
120
+ policy rather than the position itself — `get_radar_deployment` with the position's `teamId`, since
121
+ each team's deployment of a coin is its own. `list_gate_blocks` when something looks like it should
121
122
  have fired and did not.
122
123
 
123
124
  ## 4. Automation health — unprompted
@@ -25,8 +25,9 @@ close executes.
25
25
  reason, then `ineligible` with the refusal `propose_entry_decision` would give (`AGENT_NOT_ACTIVE`,
26
26
  `MODEL_INACTIVE`, `AGENT_HALTED`). Read them **as written** — never re-sort or re-derive a verdict.
27
27
  - **Ask the top-ranked qualifying agent**, and name the other agents that qualified so the player can
28
- choose one of them instead. One request per coin: the platform holds one pending request per coin
29
- across all of the player's agents, so ask one agent, not each of them.
28
+ choose one of them instead. One request per team and coin: the platform holds one pending request per
29
+ coin for each team, across all of that team's agents — an agent trades on its team's wallet — so ask one
30
+ agent of a team, not each of them.
30
31
  - **When none qualifies, say so plainly.** Name each agent's blocking gate or ineligibility, and offer
31
32
  the strategy doctor for the one whose blocking gate is the one to work on. Never propose through an agent the scan
32
33
  reports rejected, unscorable or ineligible.
@@ -65,7 +66,8 @@ close executes.
65
66
  - `userMessage` is the player's own words for the turn; it is recorded in the conversation and read
66
67
  by no model. Mint a **fresh UUID** `idempotencyKey` per request; a retry with the same key replays
67
68
  the recorded result and never registers a second one.
68
- - **One pending request per coin.** A second is refused with `CONFLICT` / `REQUEST_PENDING` — read
69
+ - **One pending request per team and coin.** A second on the same team is refused with `CONFLICT` /
70
+ `REQUEST_PENDING` — read
69
71
  the one that exists with `get_entry_request` rather than asking again.
70
72
 
71
73
  ## 4. Tell the player what they are waiting for