Is global confusing VS window?

As excited as I was in seeing this happening and working I haven't thought too much around the current naming convention ... if I need to explain that global field or export points to literally the only window out there (the browser page) I don't see why the whole thing shouldn't be named window instead:

coincident/window as exported utility
{proxy, window, isFromWindow} as fields instead of {proxy, global, isGlobal} and so on
const {document} = window feels way more natural to type too
all (deprecated) documentation out there uses window as global context for the Web
in NodeJS the global has a very well defined history / meaning and shame on me not thinking about that kind of clashing
nobody uses window in workers anyway, so this idea feels just about right

Any thoughts? It'd be a minor change as we're in 0.X semver convention, but the sooner I get this right the better to stop even thinking about it.

Hints on naming also welcomed, thanks!

WebReflection / coincident

Is global confusing VS window? #9