Unfortunately, the `wire!` resolver is poorly documented, but [we're working on it](https://github.com/cujojs/wire/blob/dev/docs/wire.md#injecting-wire).  It is provided as a part of wire's core functionality, so no additional plugin is required in order to use it.  In 0.9.x, the code [lives here](https://github.com/cujojs/wire/blob/master/lib/context.js#L772), and in dev it was extracted [to its own plugin](https://github.com/cujojs/wire/blob/dev/lib/plugin/wirePlugin.js#L88)(a plugin that is *always* loaded, so again, the functionality is always present).

The way this particular usage works is that we're injecting a function as `controller.createView`.  That function is the composition of 2 other functions: `nodeToViewSpec` and the contextual `wire`.  `nodeToViewSpec` takes a DOM Node and returns an array.  That array is passed *as the first parameter* to the contextual `wire`.  In other words, it's as if we're doing `wire(resultOfNodeToViewSpec)` and *not* `wire.apply(null, resultOfNodeToViewSpec)`.  Thus, there is no second parameter (`options`) being passed in this case.

I may have tried to be too clever here at the expense of making the code harder to understand :( Sorry about that.

So, we're basically passing an array to `wire`, which will merge the 2 specs (the items in the array) together, then wire the result.  The reason for the merge is to provide a way to do simple overrides.  There are lots of nice use cases for `wire([mainSpec, overrides]);`, such as overriding some components with test/mock alternatives, customer-specific or application-specific overrides, etc.

Did that all make sense?  Happy to continue to discuss if not!