Use “plugin resolution service” instead of “plugin portal”.
Add a little detail to the forward/backward compatibility section, and schedule some more stories for these concerns.
Focus test on communication aspects of using the plugin resolution service.
Rework the PluginResolver API to support more complex outcomes.
Suitable message when declaring non core plugin dependency without version number.
Remove answered open question.
Moved test coverage case to more appropriate story.
JSON should be sent back as utf8 and with no encoding param in the content type.
Handle responses from the plugin resolution service that are actually from something else.

This could occur if a proxy gets in the way and returns HTML instead of the JSON the client is expecting.
If the response from the plugin resolution service is completely unexpected content, log it at info level.

This is to help people debug inevitable proxy issues.
Fix varargs problem.
Add note to plugin search UI story to include search UI URL in relevant error messages.
Expose the error response details from the resolution service client.
Tighten up the response status code handling.
If the plugin is known to the resolution service, but not by the specified version, say so in the not found message.
Make dynamic and snapshot versions non fatal.

Resolvers down the line may support them.
Remove unnecessary test coverage note.
Test for reasonable error message when http request to plugin resolution service fails.
Better error message when dependency resolution fails.
Shorter name.