Perhaps, an alternative could be to use access properties instead of array
elements?

Additionally, this changes createIndexes() to no longer allow an empty array as input. The index management spec doesn't state that empty input must be accepted, so I'm not sure why we had that behavior.

Invalid arguments and options constitute a logic error, so InvalidArgumentTypeException may be used. For runtime errors (e.g. server returned something we didn't expect), UnexpectedValueTypeException may be used.

Syntax error typo

Let's also not assume that origin is the appropriate upstream remote (it may be a local fork).

This fixes an issue with 12c54575 where the error function was always being invoked.

Based on our "docs" build target, we will have already build the docs with a clean site/ directory. After that, we generate API documentation within it, which we'd like to stick around for the deploy.

This also adjusts some API doc settings and removes various options where we were supplying default values.

Update docs and code examples for 0.2