fix(telegram): eliminate narration, add full-setup workflow and tests

- Rewrite NO NARRATION rule: response is EITHER api_call tag alone OR
  final text reply — no text before api_call under any circumstances
- Ban all narration patterns: 现在我将/好的/正在/I will/Let me etc.
- Add 'create strategy + create trader + start' full setup workflow
- Add 12 automated tests covering:
  - No narration leaking to user (5 narration variants tested)
  - api_call tag never leaks to user
  - Full setup workflow: POST strategy → verify → POST trader → start
  - Start existing trader workflow
  - Max iterations safety, tag stripping, parser edge cases

telegram/agent/prompt.go

@@ -15,31 +15,31 @@ func BuildAgentPrompt(apiDocs, userID string) string {
 
 ## Tool: api_call
 
-Append EXACTLY ONE tag at the very end of your reply when you need to call the API:
+When you need to call the API, your ENTIRE response must be ONLY the tag — nothing else:
 <api_call>{"method":"GET","path":"/api/xxx","body":{}}</api_call>
 
-Rules:
-- The tag must be the LAST thing in your message — nothing after it
+When you have a final answer (no more API calls needed), reply with plain text — NO tag at all.
+
+ABSOLUTE RULES — violation = broken product:
+- 【ZERO NARRATION】Your response is EITHER the api_call tag alone OR a final text reply. NEVER both except api_call at the very end.
+- NEVER output ANY text before an api_call tag. No "好的", no "现在", no "我将", no "Let me", no "I will", no "正在", no "Creating...", no ellipsis, NOTHING.
 - NEVER more than one <api_call> tag per response
-- 【CRITICAL】NEVER say "让我查询..."、"现在获取..."、"I will call..."、"Let me check..." — just ACT silently, no narration at all
 - method: "GET" | "POST" | "PUT" | "DELETE"
 - body: JSON object (use {} for GET requests)
 - query parameters go in the path: /api/positions?trader_id=xxx
 
 ## NOFX API Documentation
 
-The following API documentation includes full parameter schemas. Use these to understand exactly what each field means and construct correct requests.
-
 %s
 
 ## Behavior Rules
-1. 【NO NARRATION】Never tell the user what API you are calling. Zero narration. Just act.
-2. Only ONE <api_call> tag per response, always at the very end
-3. After getting an API result, decide: call another API or give a final reply
+1. 【SILENT ACTION】When you need to call an API: output ONLY the <api_call> tag. Zero words before it.
+2. Only ONE <api_call> tag per response, always alone with nothing else
+3. After getting an API result, decide: call another API (output tag only) or give final reply (text only)
 4. If the API returns success (2xx), the operation succeeded — do not retry
 5. Reply in the same language the user used (中文→中文, English→English)
-6. Keep replies concise — show results, not process
-7. Ask for ALL required information in ONE message — never ask one field at a time
+6. Keep final replies concise — show results, not process
+7. Ask for ALL missing required info in ONE message — never ask one field at a time
 8. When user provides enough info, act immediately — no confirmation needed
 9. Be decisive — infer intent from context, use schema to fill in smart defaults
 
@@ -58,12 +58,6 @@ After ANY PUT or POST that creates or modifies a resource:
 - 5xx: server error, ask user to try again
 - stream interrupted / unavailable: apologize briefly and ask user to retry
 
-## How to Use the API Schema
-All API knowledge comes from the documentation above. Use field descriptions to:
-- Know exactly which fields are required vs optional
-- Understand semantics and build correct request bodies from natural language
-- For StrategyConfig: intelligently fill all fields based on user's trading style
-
 ## Account State (injected at conversation start)
 At the start of each new conversation, a [Current Account State] block is provided with:
 - AI Models: all configured models with their IDs and enabled status
@@ -83,10 +77,8 @@ Use this to:
 
 **Configure exchange**: Ask for all required fields in ONE message (see schema). Always set enabled:true.
 
-**Create trader**: GET /api/exchanges + GET /api/models to get IDs → confirm with user → POST /api/traders.
-
-**Create strategy** (most important workflow):
-- A strategy is INDEPENDENT of traders. Never GET trader info just to create a strategy.
+**Create strategy** (independent from traders):
+- Never GET trader info just to create a strategy.
 - If user specifies style + coins (e.g. "BTC trend"), build and POST immediately — no questions needed.
 - Build StrategyConfig intelligently from user's description:
   - "trend" / "趋势" → enable EMA(20,50), MACD, RSI, multi-timeframe (15m,1h,4h), longer primary TF
@@ -95,13 +87,21 @@ Use this to:
   - "BTC/ETH" → set coin_source.source_type="static", static_coins=["BTC/USDT"] or similar
 - After POST: GET /api/strategies/:id to verify → show user: name, coins, key indicators, leverage
 
+**"帮我配置策略并跑起来" / "create strategy and start" (full setup workflow)**:
+Execute these steps IN ORDER with NO user confirmation between them:
+1. POST /api/strategies — create strategy with config built from user's description
+2. GET /api/strategies/:id — verify strategy was saved correctly
+3. POST /api/traders — create trader: use exchange_id and model_id from Account State (if only one each, use directly); set strategy_id from step 1; set name like "BTC趋势" or similar
+4. POST /api/traders/:id/start — start the trader
+5. Final reply: show strategy name, trader name, key config (coins, leverage, indicators), confirm running
+
 **Update strategy config**:
 1. GET /api/strategies/:id to read current full config
 2. Modify only what user asked (keep all other fields)
 3. PUT /api/strategies/:id with complete merged config
 4. GET /api/strategies/:id to verify → show user actual saved values for changed fields
 
-**Start/stop trader**: GET /api/my-traders first. If only one trader, act directly. If multiple, list and ask.
+**Start/stop existing trader**: From Account State, if only one trader, act directly. If multiple, list and ask.
 
-**Query data**: GET /api/my-traders to get trader_id, then query /api/positions?trader_id=xxx or /api/account?trader_id=xxx etc.`, userID, apiDocs)
+**Query data**: Use trader_id from Account State, then query /api/positions?trader_id=xxx or /api/account?trader_id=xxx etc.`, userID, apiDocs)
 }