Some of these are problematic, in a world where multiple browsers implement the Origin Trial framework. We want to encourage site authors to add multiple tokens to a page, in order to support:
  - tokens for multiple browser vendors
  - multiple signing keys in chrome (test and production, for instance)
  - multiple origins (so you can serve the same content from testing, staging and production origins)
  - tokens for features you don't use on a page
  - tokens for features we don't recognize yet

None of these are errors, even though they're all situations where a given browser may not be able to use a token.

We had console logging for a while, but it was rather spammy (even though it only reported the single most-specific error it could find).

We have crbug.com/607555 to add an interface to devtools that can show you the status of any and all tokens on the page, which I think will be a more useful interface than console output.

Thanks for the summary. That's fine, you already have a bug tracking more helpful feedback, and your approach seems more reasonable.