This looked to be fixed.

same here.

I've fixed that initial problem where a move was not returned.
The Master class handles the collisions between other bots and the boundaries, to make sure you're not cheating.
The bot knows the boundaries by the set map method where a map will be given showing the position of each bot and the goal.

console.log(Master.toString()) - unfortunately this approach only gave partial results for the sloth.

I started on this Kata because it looks like an awesome challenge. From the get go it's been a struggle. I did a clean reset and pressed "run tests" and it gets the error "bots[key].bot.move is not a function". I added a "move: function () {" to the returned object and it now gets errors from the sloth about index 0 being invalid. It'd be nice if the initial setup would run and give Test failed results.

You mentoined collisions but the instructions don't talk about that. What does that mean? collisions with other bots?

How does a bot know the boundaries in which it can randomly move if it doesn't yet have a map? does "return 's';" satisfy random movement? ;)

This is an awesome idea; I'd love to dig in to more of it.

map isn't a function, it's a setter and the setMap function on the Master does work correctly.

i'll have a look again and see what's happening but the implementation of the Master is not important, it just checks collisions and checks whether the bots are in their final state or not.

The original spec has the same ordering of LHS and RHS. The kata spec references ordering relative to popping the stack, while the original spec references ordering relative to pushing the stack. I can see how that can cause confusion.

The two additional stack manipulation commands were added by the orginal authors in Whitespace 0.3, as shown in this tutorial, to facilitate the implementation of recursive functions.

Having zero with a sign and no bit markers was based on my interpretation of the original specification that a number can have any width, and the fact that Haskell interpreter the original authors released accepts a sign without bit markers. There's additional ambiguity in the original spec that I tried to tighten in the kata spec, but that's certainly one of the more notable ones. Another ambiguity where the kata spec differs is that the original doesn't specify what to do when the argument to the slide command being less than zero or greater than the number of items on the stack.