We sparred earlier in the session...

<1037hp 440m 917mv 26053tnl - 8 PM>
Depoetsende's punch misses a stone golem.
Your shocking bite MASSACRES a stone golem!
A stone golem parries your suction.
Your shocking bite MANGLES a stone golem!
Your shocking bite MASSACRES a stone golem!
A stone golem's crush EVISCERATES Depoetsende!
You anticipate Depoetsende turning to flee, and quickly move to block his escape!
A stone golem has some small but disgusting cuts.

<1037hp 440m 917mv 26053tnl - 8 PM> aa

What part of that seems like a bug to you?

You fought, you learned his movements, and that means you can (and will) do certain things, such as in this log. The MUD code isn't smart enough to know that the guy you spent an asspile of time fighting isn't really your enemy, and it really can't be. If you don't want to do that to people, don't spend a lot of time fighting them.

They're both fighting the golem and it looks like he blocked his groupmates attempt to flee from that golem.

I'd consider changing that in the case of specifically groupmates, but the general trend is, if you spar with someone and get your legacy rolling on them, this is a consequence for a while.

That's all I was getting at. If we're not fighting as a team, it doesn't make much game play sense that the warrior with Striking would try and get his groupmate killed.