yea, keymaster.js introduces `key` into the global scope. `key` is the only mechanism for interacting with it's API. but yea, it's not ideal, which is why they included the noConflict method to mitigate the issue a bit.

This is actually the only part of this PR that I was worried about messing other parts of HQ. I did a search for `KEY` in our codebase and I couldn't find any js vars called `KEY` so I think this is safe.