Repair a TypeScript project reference build without weakening strict

A two package TypeScript workspace stopped building after someone replaced its project reference imports with a path alias. The app's tsconfig gained a paths entry whose target is written relative to the repository root rather than to the package, and its references array was removed, so the compiler cannot resolve the import and never builds the dependency first. Once resolution is restored a second error surfaces, because the catalogue lookup returns a value that can be undefined and strict mode is on. The obvious shortcut is to turn strict off, and the hidden tests check that it is still on.