"Opt in" does not work; must turn on content-type "New revision in draft" as DEFAULT, for Revisioning moderation to work

Issue Summary

According to the documentation (Opt in/Opt out section), you should NOT need to set "New revision in draft" as the default option for a content-type, you should be able to "opt in" to creating a new revision on the fly from the content edit form:

you can now confidently give selected roles the permission to opt-in or opt-out of content moderation on a per-edit basis. So, for instance, if at Structure >> Content types >> edit the content type Article has not been configured to be subject to moderation by default, then the roles with the "Administer content" permission may, at any point, decide to switch moderation on, simply by pushing a radio button on the Article content edit form.

This does not seem to work in practice. If we do NOT set "New revision in draft, pending moderation" as the DEFAULT option for a content-type, then new revisions are always published immediately and visible to anonymous users, even if "New revision in draft, pending moderation" is selected during the edit process.

We want to create a site where the default behaviour is for edits to be published immediately, the editor must manually select "New revision in draft, pending moderation" if they want to delay publishing. This doesn't seem to be possible; the only way to get it working is to set "New revision in draft, pending moderation" as the default option. Unless I am doing something wrong.

Steps to reproduce:

1) Do a fresh install of Drupal 7.10 and Revisioning (7.x-1.2, I have tried latest dev version too, same results)
2) Enable Revisioning module
3) Create a new Basic page
4) Edit this new Basic page, select "Create new revision and moderate" option, and save.
5) The newly edited Basic page revision is immediately published and visible to everyone. Additionally, the Revisions list page incorrectly identifies the new revision as "in draft/pending publication [status=0]" even though in actuality it is the current viewable revision. There is also no way of publishing/reverting revisions, as these tabs are not present when viewing a revision.
6) Turning on the "New revision in draft, pending moderation" DEFAULT option for the Basic page content-type immediately fixes all problems and everything works as expected; the original revision is displayed as the current one, and the new revision is not visible until explicitly published.

So it does not seem that the documentation quoted above is accurate, "opt in" does not seem to work... the "New revision in draft" must be set as a default for everything to work.

Thus, this doesn't really seem to be behaving like simply a "default" option; it appears to have a fundamental effect on how this content type handles revisions entirely.

I intend to try setting "New revision in draft" as the default for all of our content-types, then adjust the radio button on the node edit form to "Modify current revision, no moderation" as the default with hook_form_alter(), to see if that is a viable workaround for our use case.