Currently, if a Shape is Rotate Transformed in Studio, it will automatically set an Origin of 0.5,0.5 in the Shape's Properties Panel.

However, this Origin value can become out of-sync via the Undo/Redo stack, and either:
a) Display an Origin of 0.5,0.5, when the actual Origin is 0,0
b) Not show a Blue dot on the Origin Property, even when the Origin is modified from the default.

Repro Steps:

1) Create a Studio Project featuring a MainPage.xaml

2) Introduce a Button to the Stage.

3) Create a new Button Template from the Button on-Stage.
This will enter the Template in the Template Dummy Editor.

4) Expand the RootBorder, and delete the default ContentPresenter.

5) Introduce a Star Element into the RootBorder.

6) Navigate to the Animation Panel, and under the VisualStates Tab, select any VisualState

7) Select the Star Shape, navigate to its Properties, and open the RenderTransform 'Origin' sub-tab.

Observe how the Origin is set to 0,0.

8) Navigate to the RenderTransform Rotate sub-tab, and change the Angle value 180.

Observe how the 'Origin' sub-tab in the RenderTransform Section is not displaying a Blue dot, displaying that a value has been changed.

9) Click on the 'Origin' sub-tab, and observe how the value has actually changed from 0,0 to 0.5,0.5

10) Press 'Undo' once to remove the Rotation from the Star.

Observe how the Rotation has been successfully removed, but the auto-Origin change has not been changed alongside it, in the same way it was added alongside the Rotation.

11) Press 'Undo' once more to remove the Star from the Page.

12) Press 'Redo' once to add the Star back to the Page.

Observe how the Origin is now back to 0,0.

Observe how it appears that Origin changes are not included in the Undo/Redo Stack.

Expected Results: Origin Changes are included in the Undo/Redo Stack.
Expected Results: Rotations that cause Origin changes are flagged as value changes as they do when the operation is performed outside of the context of a VisualState.