The point is that the CF profle should *always* be enabled by default, if the CF profile capability is *available*. That's the deal. If the CF profile is indeed available, then it should **never** be enabled for testing - **ever**. That's the purpose of this statement.

If the CF profile is **not** available i.e. "just cloned straight from GitHub" by Joe Public in the field, then this is a benign NOOP. No harm done. Nothing to see here, more along folks ...