New nodes not held for moderation with trigger enabled

When using the action/trigger defined in the patch I submitted earlier (see #345964: Publish node when its first "revision" is approved), the first revision of a node -- i.e., the brand-new node that hasn't been published yet -- isn't marked as published. Also, two revisions appear for each change -- whether a new node or a change of an existing node -- though this may be a separate issue.

Steps to reproduce:

1. Add "Enable revision moderation on node" action to the trigger "When either saving a new post or updating an existing post."
2. Log in as a user who is not allow to publish a node.
3. Create a new node. (The node type should not be configured to be published by default. See note (1) below.)
4. Log in as an admin and go to the "Pending revisions" page at admin/content/node/revisions.
5. Click on the pending revision for the new node. You will see two revisions listed.
6. Click on the first revision.
7. Publish this revision.
8. Go back to the new node. It has not been published.

Notes:

(1) Setting the node type to be published by default results in a published node with two revisions. In other words, the new node has not been held for moderation, yet two revisions have been created.

(2) The "New revisions in moderation" node type setting does not affect this issue. Checked or not, the behavior described above occurs.