In itself this dependency isn't that bad, although Morphic-specific
tests should go into MorphicTests.

The dependency at the moment is simply caused by some tools not using
ToolBuilder. In particular, MCSnapshotBrowser has a bunch of tests
that assert that its UI is well-formed. If there's a way to express
these assertions without referring to Morphic classes, that would be
great.

For instance, MCSnapshotBrowserTest >> #testAnnotationPane counts the
number of TextMorphs when different preferences are set. Perhaps if
browser used ToolBuilder, one could query the _specs_ to see what you
would end up with?

Thoughts?