[Edit] In the I.D. the AI does this correctly. But the problem is caused by the way the latest user move is passed to the AI. This derives the move from the origin and destination highlights, so it completely misses any locust capture.
I did test the position I gave you by having the AI capture the Lions instead of the user, but this too seems to not properly invoke the counter-strike rule, though I suppose you still have to update the source file. I'm guessing the problem is that the way the AI gets the last move in general is through the origin and destination squares.
I can see the way you interpret "non-lion" in the counter-strike rule becoming a point of contention. The rule does not explicitly say "non-Lion piece" when it says "a non-Lion cannot capture a Lion...", which is the source of this confusion.
I did test the position I gave you by having the AI capture the Lions instead of the user, but this too seems to not properly invoke the counter-strike rule, though I suppose you still have to update the source file. I'm guessing the problem is that the way the AI gets the last move in general is through the origin and destination squares.
I can see the way you interpret "non-lion" in the counter-strike rule becoming a point of contention. The rule does not explicitly say "non-Lion piece" when it says "a non-Lion cannot capture a Lion...", which is the source of this confusion.