> What is it that you're using ares for in your code if you're not keeping track of permissions and scope through the decision process?

Probably nothing.  `ares` is entirely based on how the app chooses to present dialogs to the user (this is left completely undefined by OAuth).  Tracing it through, its just routed out to the grant `issue` callbacks so they can handle it how they need it.  Likewise, this info construct being introduced is just an opaque place to for the application to store arbitrary stuff in the transaction, probably as an optimization when later when figuring out what the response should be.

That info can be *exactly* what you want for `ares`, and that may be the best thing to use it for.  But, that implies an assumption by this module on what application-specific opaque data contains.  I don't like making assumptions inside of modules, and the point of the `parse` function is to delegate to the application.  So I'd just prefer that to remain assumption-less as before.