# Cron Job: CryptoTradingBot Tournament 6h Check

**Job ID:** 29cd322cf187
**Run Time:** 2026-05-29 13:02:06
**Schedule:** once in 6h

## Prompt

[IMPORTANT: You are running as a scheduled cron job. DELIVERY: Your final response will be automatically delivered to the user — do NOT use send_message or try to deliver the output yourself. Just produce your report/output as your final response and the system handles the rest. SILENT: If there is genuinely nothing new to report, respond with exactly "[SILENT]" (nothing else) to suppress delivery. Never combine [SILENT] with content — either report your findings normally, or say [SILENT] and nothing more.]

Im Telegram-Topic Crypto Trading Bot einen kompakten Statusbericht zum CryptoTradingBot Strategy Tournament liefern. Arbeite im Repo /home/agent/projects/CryptoTradingBot/Crypto_Agent. Keine Secrets ausgeben. Prüfe: git branch/status/HEAD, laufende AutoTrader.py Paper-Prozesse unter ~/.local/state/CryptoTradingBot/experiments/*/bot.pid, Journal-Zeilen pro aktiver Strategie, aktuelles strategy_tournament.py Ranking für aktive Strategien, historischen Replay-Report ~/.local/state/CryptoTradingBot/reports/historical_replay_report.txt. Wenn Prozesse tot sind, nur melden; nicht automatisch live starten und keine Live-Orders. Sprache Deutsch, knapp, Sir ansprechen.

## Response

Sir, kompakter Status CryptoTradingBot Strategy Tournament — 2026-05-29 13:01 CEST

**Git**
- Branch: `chore/safety-optimizations`
- Status: clean, tracking `origin/chore/safety-optimizations`
- HEAD: `c5e3210` — `feat: add read-only tournament dashboard`

**Paper-Prozesse**
- Aktiv: 6 `AutoTrader.py` Paper-Prozesse, alle seit 07:52:40 CEST
  - `candidate_v62_loose_trend_rebound` PID 219888
  - `candidate_v62_scalp_fast_rebound` PID 219891
  - `candidate_v63_loose_fast_decay` PID 219887
  - `v59_1_frequency_boost` PID 219890
  - `v60_survival` PID 219889
  - `v61_tight_survival` PID 219892
- Tote/stale PID-Dateien:
  - `candidate_v62_anti_chop_context` PID 219019 tot
  - `candidate_v62_deep_capitulation` PID 218157 tot
- Keine Prozesse automatisch gestartet, keine Live-Orders.

**Journal-Zeilen aktive Strategien**
- Hinweis: `Tradeanalyse/trade_journal.jsonl` fehlt bei allen aktiven Strategien; gezählt wurde `Tradeanalyse/trading_log.txt`.
- `candidate_v62_loose_trend_rebound`: 366 Zeilen
- `candidate_v62_scalp_fast_rebound`: 118300 Zeilen
- `candidate_v63_loose_fast_decay`: 310 Zeilen
- `v59_1_frequency_boost`: 119918 Zeilen
- `v60_survival`: 119470 Zeilen
- `v61_tight_survival`: 121090 Zeilen

**Aktuelles `strategy_tournament.py` Ranking aktive Strategien**
Alle aktiven Strategien stehen aktuell bei `n=0`, `total=+0.0000`, `score=-2.0000`, `observation-only`:
1. `candidate_v62_loose_trend_rebound`
2. `candidate_v62_scalp_fast_rebound`
3. `candidate_v63_loose_fast_decay`
4. `v59_1_frequency_boost`
5. `v60_survival`
6. `v61_tight_survival`

**Historischer Replay-Report**
- Modus: walk-forward
- Top:
  1. `candidate_v63_loose_fast_decay`: score `+1.1418`, n=5, win=0.80, total `+1.5078`, PF 9.83
  2. `candidate_v62_loose_trend_rebound`: score `+1.0001`, n=5, win=0.80, total `+1.2133`, PF 4.72
  3. `v60_survival`: score `+0.3076`, n=5, win=0.60, total `+0.4868`, PF 1.66
- Gleichstand im Replay: `v59_1_frequency_boost` ebenfalls score `+0.3076`, total `+0.4868`.
- Schwächster aktiver Kandidat historisch: `v61_tight_survival`, score `-0.1029`, total `-0.3146`, PF 0.77.