Core should have a test case to catch potentially false mappings

What needs to be modeled?

There should be a test case that makes sure non-exported interfaces in different files don't have the same name.

Why is a new model necessary?

This issue is not caught by the TypeScript compiler and is an easy thing to miss when making changes or additions, and can have weird effects on the functionality search.

This stems from an issue in TypeDoc that can cause the mapping to be wrong without any indication by current test cases. #48 (core-tools)