This happened in game #54322 I played.

The order of event involving the manticore in that round is as follows:
1) The manticore began the round being controlled by me (it stood close to my beast master)
2) The manticore become aloft with the temple of zorn.
3) Then it went to attack a building and became uncontrolled.
4) My slore which is close to the manticore can't heal it.

I think this is a bug because slore should be able to heal any creature.

It was showing attack by default. You should've choose ability(click on ability icon or Ctrl+A) and only then click on manticore.

I've run into the opposite interface issue. How do you force the game to *not* use an ability? In particular, I've had trouble moving treeherds to spaces with seedlings. The game always wants to turn the seeding into a forest rather than moving there.

Usually when you click on Hex that have more than one possible action popup-window appears and you choose action.

Just tried this (downloaded client, maximized). I got no popup-window. Here are the various things I tried.

1) Click on treent. A star icon appears over him. Mousing over the map gives the foot icon.

2) Click on the star icon. The icon disappears and the message "select a seedling to herd" appears. The mouse is the ability icon and only hexes with seedlings are hinted.

3) Instead, don't click on the star icon. Click on a square containing a seedling (foot icon is displayed before clicking). No popup appears, hexes that would be legal targets for a forest are hinted. Clicking on a hex consumes seedling and generates forest. Interestingly, if the square you are trying to move to contains two seedlings, clicking on the hex brings up a popup window asking you to select a target. Both options are the current hex (presumably it is actually having you select which seedling to consume).

Still can't figure out how to move to the hex without popping the seedlings.

Treeherd was fixed.

so Carrion Feeder is next?
I still don't know how to move him on adjacent space which contains corpse..

It was same bug, so it is fixed too.