Context Navigation

Changes between Version 6 and Version 7 of Ticket #30937

v6	v7
18	18	* Settings can be collaborated on by multiple users (though not concurrently, without some Heartbeat system in place)
19	19	* The capability to publish a `wp_transaction` post can be limited by role, allowing 'Customizer contributors' to submit settings as pending review.
20		* Settings can be scheduled for going live at a later date by saving the transaction post simply with `post_status=future`
	20	* Settings can be scheduled for going live at a later date by saving the transaction post simply with `post_status=future` (see #28721)
21	21	* With each save in the Customizer resulting in a new transaction post being created, then there is Customizer revision history (see #31088, #31089)
22	22	* Accessing the Customizer preview for a transaction needs no special capabilities since the transaction is updated by an authorized user via single Ajax request. This means that Customizer previews (frontend URLs with the transaction UUID amended) can be shared for anonymous users to review.