ZhouYongyou 0fddd2731d fix(prompts): rename actions to match backend implementation ...

## Problem

Backend code expects these action names:
- `open_long`, `open_short`, `close_long`, `close_short`

But prompts use outdated names:
- `buy_to_enter`, `sell_to_enter`, `close`

This causes all trading decisions to fail with unknown action errors.

## Solution

Minimal changes to fix action name compatibility:

### prompts/nof1.txt
- ✅ `buy_to_enter` → `open_long`
- ✅ `sell_to_enter` → `open_short`
- ✅ `close` → `close_long` / `close_short`
- ✅ Explicitly list `wait` action
- +18 lines, -6 lines (only action definitions section)

### prompts/adaptive.txt
- ✅ `buy_to_enter` → `open_long`
- ✅ `sell_to_enter` → `open_short`
- ✅ `close` → `close_long` / `close_short`
- +15 lines, -6 lines (only action definitions section)

## Impact

- ✅ Trading decisions now execute successfully
- ✅ Maintains all existing functionality
- ✅ No new features added (minimal diff)

## Verification

```bash
# Backend expects these actions:
grep 'Action string' decision/engine.go
# "open_long", "open_short", "close_long", "close_short", ...

# Old names removed:
grep -r "buy_to_enter\|sell_to_enter" prompts/
# (no results)
```

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-11-04 19:41:23 +08:00

..

adaptive.txt

fix(prompts): rename actions to match backend implementation

2025-11-04 19:41:23 +08:00

default.txt

Supports custom system prompts and custom models.

2025-11-01 19:45:54 +08:00

nof1.txt

fix(prompts): rename actions to match backend implementation

2025-11-04 19:41:23 +08:00

taro_long_prompts.txt

文件命名空格问题

2025-11-03 00:16:28 +08:00