first steps for Issue #19
Fix superclass, add postload doit for tests
checkpoint: all script tests passing...
  renamed/commented script notification classes
  getting into serious rework of the load: command flow ...
checkpoint: all script tests pass
  the registration block for MetacelloProjectSpecLoadedNotification is now correct.
    signaled after load
    project spec unconditionally merged
    registration unconditionally updated
initial fix for Issue #19
  correct registration post version load in initial Load: block
  correct registration upon MetacelloProjectSpecLoadedNotification (previously)
  correct behavior in absence of "load conflicts"
  need to add test cases to introduce "load conflicts"
checkpoint: conflict logic complete
  consolidate to a single lookup method
  add configuration conflict tests
  need a bit more test coverage (downgrade and baseline conflicts)
added two new tests (renamed 2 tests) for downgrade testing of configurations
  still need baseline conflict tests

  commit 2af1cc0a61223f281050771be5b6eeeb13e2439a fixed Issue #29
add $.
tweaks
projectSpecClass shouldn't change with the type of project being used .... the classes differ primarly in that a BaselineProject has only one version
fix a bug in MetacelloMCProjectSpec>>copyForScriptingInto:
add two new tests for Issue #19:

  one for testing copyFrom:with:
  one for testing printString of a versionSpec ... which lead to needing
    to address Issue #28
cherry-pick b2a1e7a38cdb67c25875ffb81265c370b9e4a636 : pick up the versionSpec test

add two new tests for Issue #19:

  one for testing copyFrom:with:
  one for testing printString of a versionSpec ... which lead to needing
    to address Issue #28
className: printed as part of #project:with: construct

  tests and printing done...
  still have to require #className: for #project:with: constructs
Issue #28: #className: expected with #project:With:

542 run, 534 passes, 8 expected failures, 0 failures, 0 errors, 0 unexpected passes
now need to enforce use of #className: in #project:With: specs
Issue #28: add validation error for #className:

  add tests
  remaining task: catch missing className: in scripting api
final tasks for Issue #28 complete:

  validation for projectSpec used in load
  set of tests verifying that the validator throws the correct error
Merge branch 'issue_28' into issue_19

Conflicts:
	repository/Metacello-TestsMC.package/MetacelloBaselineConfigurationTestCase.class/instance/tearDownPackages..st
	repository/Metacello-TestsMC.package/MetacelloBaselineConfigurationTestCase.class/instance/testGithubRefXI.st
	repository/Metacello-TestsMC.package/MetacelloScriptingResource.class/instance/configurationGithubReferenceV..st
	repository/Metacello-TestsMC.package/monticello.meta/version
checkpoint Issue #19:

  fix for 'duplicate projectSpecs' which showed
    up in first configuration that used #project:copyFrom:with:
  need to work through additional #project:copyFrom:with: scenarios
checkpoint Issue #19:

  #project:copyFrom:with: using baseline tests...resolving
    issue discovered when trying to load Seaside through
    scripting api
  time to try to load Seaside again...
checkpoint Issue #19:

  restructure script test hierarchy
  start poaching tests from MetacelloCurrentVersionTest for scripts