looked at bundler.js
audit compiler.js
update linker.js
package-loader and package-source
project and selftest
tropohouse and unipackage

done???
work around pre1 builds (ie, rebuild works now)

we changed the effective format without changing the name a while ago
anyway. Technically we didn't need this before because we also changed
the .build dir name to .build.foo but this is still reasonable.
rename build -> unibuild in constraint solver too
initial checkpoint for "buildArchitectures"

this is a string like "browser+os"
some other stuff that goes together
fix for removing fields from Builds
oops! actually use specific arch!
fix wrong arch in plugin package search

the "We pass" comment was stolen back from devel

basically, whenever doing eachUsedBuild, you really want to pass in the
arch of the overall compilation (or for plugins, the host arch), not the
arch of the unibuild you happen to be sitting in right now.  because if
you're sitting in a generic "os" unibuild, it won't know whether to use
os.mac or os.linux or whatever if you pass in "os"!
Merge branch 'build-arch-rename' into packaging

This makes a few changes:

- renames the thing inside a unipackage to 'unibuild' from
  'build' (previously 'slice'); 'build' continues to refer to a specific
  instance of a version of a package (ie a tarball)

- renames the 'architecture' field of a build (which is a plus-separated
  string of arches) to 'buildArchitectures'

- oops! we were not actually making any packages binary-specific (ie
  they were all browser+os!)  fixed this, and another bug that it
  revealed

- updates the unipackage format to unipackage-pre2, and allow us
  to recognize (but not load, just ignore) unipackage-pre1

- some fixes for the recent schema change that removes packageName and
  version from Build records