It Sort of Works

1. I fixed the crashing by making "runtime contiguity enforcement" an experimental feature. This was caused by memory overflow on any game with > 50 houses. This really did 2 things: check for a break in contiguity, and autofill a region if it is smaller than minimum district size. I am working on more efficient algorithm in C++. 

My plans to implement this are to first efficiently check contiguity. Without "runtime enforcement" the ui will indicate when a district is not contiguous. (The district "palate button" turning into a broken puzzle piece would be cute.) With runtime enforcement, the player decides which half of the district to delete, rather than just nothing happening. Auto-fill will be a separate thing.

2. I implemented pan and zoom. The game has a mobile focus so the user has to toggle between draw mode and camera mode, as there is no right click.

3. Settings can be saved and loaded, although this won't work in the browser without third-party cookies.