Collectible Card Game Headquarters

Describe the Bug:
1- EDIT: 1 Shackles can be activated by AI more than once to send multiple copies back to hand.
2- AI tends to spend most or all mana playing and activating Shackles to creatures and even worse to the same creature.
Which card did behave improperly ?
Shackles

Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
Manalink 2014/11/14: Khans of Tarkir,duel

What exactly should be the correct behavior/interaction ?
1- Shackles if activated more than once only the last activation first to resolve finds a target to return.
2- AI doesn't spend mana to play and activate the card on the same creature over and over or to all creatures untill all mana is spend.Preferably it plays it to the creature that can heart AI most and only activate it if another creature whcih can do more damage enters or if the enchanted creature is going to die so AI will rescue Shackles.(How easy is to say something that is ("impossible" to code at least with our engine and no source code)
EDIT also AI if it has more than 1 Shackles to play it plays them on the same creature.
Are any other cards possibly affected by this bug ?
-

1st is not a bug, activated for 2 different shackles (check the card IDs).

2nd is more of an AI issue, but is confirmed.

I have read the cards text very carefully and I still think I am right.Of course you can activate it and then on the stack activate the same Shackles as many times you can afford to BUT you can't have as many activations so many Shackles return to hand from your 1 and only original Shackle.

I think we are talking past each other. When I tried your savegame (from another post) 1 creature had 3 Shackles on it. The AI activated 2 different Shackles (by card ID) and returned them both to his hand, 1 in response to the other. As I understand things, that is legal. I haven't seen AI activate 1 Shackles to return multiple copies of Shackles or activate 1 copy of Shackles more than once.

And just after I finish writing that I go back and try again and what you described happened. This is why I hate testing AI actions. Consider both confirmed.

The second bug is caused by the first one, which is fixed in 453dd33