You're welcome.
Meanwhile there's an optional further step one could do, with stoplimit orders. When stop is reached, the order is converted to a limit order by removing the stop price. If stop_reached were set to True instead, then when filled it would be easy to log them as stoplimit orders rather than just as limit orders as you see above.
Imagine a strategy where any type of order might be used. It could be useful to see which fills were stoplimit distinguishable from those entered as purely limit orders.
The extra step would be to watch stoplimit orders every minute for when status remains 0 while stop price disappears (stop reached, can then also log that point), store that id, until their limit is reached and when complete, see if it is on the list of stored id's and log them as stoplimit instead of just limit, and then remove them from the stoplimit watch list. Just extra processing and code complexity.
This stoplimit order from open to filled happened to be selling 1 share ...