I second most of Diego's points. The bristlebot, like the marker+cup artbot, is essentially a physical contraption designed to exploit small variation introduced by the offset motor.
Adding an on-off button to those device is often plenty of wiring/design challenge for elementary students.
Before we can think about "controlled via Scratch," you'd need to deeply explore different ways to exert any control over that system. Bending the bristles might work, but I can't think of a way to adjust that on an active bot. Maybe you could build a group bot, made of several bristle bots lashed together, and exert some control by turning different motors on or off, or somehow adjusting the voltage to each motor. You could also take a cue from aeronautics, and try to separate "thrust" from "control." Maybe a servo that changes the shape of the bot, twists some kind of rudder. There's a bunch of interesting things to try, but nothing that I know off hand will *work*.
Assuming you find something that will reliably control the movement of this now-freakish bot, then you're back to looking for ways to abstract that control. If you're still using simple DC motors, then only real control mechanism is something that adjust the circuit that powers the motors. Before looking at programable control, try some mechanical switches. There's a standard wall-crawler bot format (Taimyo vesion here:
http://www.pololu.com/catalog/product/1694 ) that drives one side when the bumper switch is pressed, and then powers the opposite side when the switch is released, steering it back into the wall. Even if the switches aren't triggered by the environment, if you can get something rigged up, it provides a framework for the next step.
Programable control just means transferring that manipulation of voltage to the motors to a microcontroller. Diego is basically right, that surface MakeyMakey we work with is basically an input device. But it technically is a full Arduino and has the ability to have 6 PWM output pins (ref:
http://www.slideshare.net/IndustrialDesignCenter/programming-arduino-makeymakey). That said, I don't know of a way to have those features triggered through Scratch. :)
Diego's last suggestion, of shifting your design focus to an environment rather than the bot, echoes the commercial strategy for the Hexbug version of the BristleBots (sold retail as the HexBugNANO Habitat:
http://www.hexbug.com/hexbug-nano-habitat-set.html ) As a basic rule, bigger things are easier than smaller things. The MakeyMakey/Scratch pairing is well suited for keeping track of where bristlebots roam in an environment.
It's a much smaller leap to extend that task with servo-operated walls/gates than to move from the autonomous & chaotic vibration bots to a fully programable robot.
--andrew