The package and its Java coordinate moved to intisy/bayonet, so every resolver
that named the old one moves with it: the dependency, the emit and build script
paths, the imports, the javac -Atsemit.keys argument and the Gradle coordinates.

Two things a search for the package name does not find, and one real defect:

 - the shared-library store matched one npm scope, so a plugin declaring the
   moved library would have had it left out of the home store and the deployed
   bundle would have failed to resolve it at run time
 - seven tests build the script path out of separate path segments, which no
   search for @intisy-ai/api reaches