stgeorge:
I assume you don't need to call out any baud rate on either the bridge or the console, right?
Correct.
Bridge.begin() can accept an optional baud rate, because it is actually a serial port connection to the Linux processor. They give you the option of changing that baud rate if you have a special need.
Console.begin() expects no parameters. There is no concept of a baud rate for a network connection. While a network connection does have a physical data signalling speed, that is a function of the physical hardware interface and not something that can be changed in software. (Or at least not by the Console class.)
Does it matter the order in which you list the 'include' libraries (?) - I'm guessing not.
Sometimes it matters, usually it doesn't. There may be a case where an include file needs to use information from another include file, and therefore must be included after the other one. But usually, that include file will just include the specific file it needs, eliminating the need to include them in a specific order. (Wow, talk about some convoluted logic, any chance you can follow that?)
In the case of these include files, it doesn't really matter. I like to include Bridge.h first, as it is the main include file of the Bridge library, and everything else depends on it. However, because everything else depends on it, it is automatically included by the other include files. So, if you happen to include Console.h first, it will include Bridge.h internally to it. Then, when you get to the point where you are including it in your sketch, the compiler will realize that it's already been included and not include it a second time.
But the short answer is no, it usually doesn't matter. In general, I tend to include files in alphabetical order: sometimes there is a long list of includes in a source file, and having them in order makes it easier to find a file in the list when reading the code.
Finally...since I've run across 'boolean' I'm curious if you can shed light on what that does and/or what the proper use is for it?
A boolean is usually another name for an unsigned char (byte.)
It represents a logical value: either true or false. The results of the comparison operators (==, >, <, <=, >=, etc) is a logical value. There are logical operators that take logical values and return logical results like and (&) or (|) exclusive-or (^) and not (!). There are statements that expect logical expressions, like if and while.
C++ uses the numeric value 0 to represent false, and any non-zero numeric value is considered true. The result of a comparison or logical operator is usually 1 when it wants to signal true.
A logical value can be stored in just about any integral numeric variable type, although a single byte value is usually used for efficiency. "boolean" is just another form of unsigned character value (just like "byte") that can be used to store any 8-bit value, but by using the type "boolean" you are giving the reader a hint that you intend to use it for true/false values. (Although the compiler really doesn't care, it treats "byte", "boolean", and "unsigned char" as the same thing: an unsigned 8-bit value.)