Potential Bug?  After introducing `defaultHash`, runtime checks for hash value vs. `hashMode` might need revision

Since I introduced `defaultHash`, it is now possible to not specify a `hash` value on components and still opt in for a named hash routing universe.  However, I think the runtime checks don't account for the possibility of a default hash of type string while having `hashMode` set to `'single'`.