I think the 'system' tests profile should be available -- if not merely to be a starting point for seeing the product work E2E.  Trying to execute the system tests will fire an error without configuration -- we only aim to have very specific, meaningful error messages so that they can be resolved quickly/efficiently.  Sound like a good plan?

True, all Sugar-specific language should be wiped/moved.

I filed an issue on your suggestion that all reserved keywords should be listed.  Perfectly valid.  I want to minimize research, so linked functionality that's adopted from tools (Maven, etc.) is certainly preferred.