Block a user
feat: use playbook allocation_pct in position sizing
feat: use playbook allocation_pct in position sizing (#172)
feat: add position-aware conditions to StockCondition (#171)
feat: add position-aware conditions to StockCondition
feat: include current holdings in pre-market AI prompt
feat: include current holdings in pre-market AI prompt (#170)
feat: include current holdings in realtime trading loop for exit evaluation
fix: SELL order quantity hardcoded to 1, ignores actual held position size
fix: use broker balance API as source of truth for SELL qty and holdings (#164 #165)
feat: include current holdings in realtime trading loop for exit evaluation (#165)
이것도 db만 봐도 될까? 매수할때 주문량과 체결량이 다를 수 있고, 매도 후 결과도 마찬가지로 다를 수 있어. db 기록이 잔량과 언제든지 다를 수 있는데 언제 싱크되는지도 모르지 않아?
fix: use actual held quantity for SELL orders instead of hardcoded 1 (#164)
db만 확인해도 될까? buy할때 주문량과 체결량이 다를 수 있는데, 그 부분도 고려해서 db에 기록하고 있나?
fix: take_profit_pct defined in schema but never enforced in trading loop
fix: enforce take_profit_pct in HOLD evaluation loop (#163)
feat: granular Telegram notification filters via .env