> This "feature" is misguided because a class can belong to multiple packages. So asking a class for its single package info is wrong.

(Why such strong words?)  A class can only be defined in one package,
just as in Monticello, and this method simply associates its MC
equivalent to PackageInfo domain objects.  Why do you say a class can
belong to multiple packages -- because of extensions?

> IMNSHO the #workingCopy method should be removed. It's not used in the system yet, fortunately.

It's used by external utilities for automating the building of .sar
packages which should be included in the system.