Issue #1910: Add status to Ansible proposal docs with relevant docs links. (#1920)

Author: geerlingguy

doc/proposals/ansible-operator-status.md

@@ -1,8 +1,8 @@
 # Ansible Operator Status Proposal
 
-
-## Current status
-The operator can currently surface basic information from the Ansible code in a generic fashion - it can set the conditions and it can surface a failure message if the run failed.
+> Status: **completed**
+> 
+> The operator can surface basic information from the Ansible code in a generic fashion - it can set the conditions and it can surface a failure message if the run failed. See documentation in the Developer Guide: [Custom Resource Status Management](../ansible/dev/developer_guide.md#custom-resource-status-management).
 
 ## Problem
 

doc/proposals/ansible-operator-testing.md

@@ -1,5 +1,9 @@
 # Ansible Operator Testing
 
+> Status: **completed**
+> 
+> Ansible-based operators can be tested with Molecule. Please see the testing documentation: [Testing Ansible Operators with Molecule](../ansible/dev/testing_guide.md).
+
 ## Background
 All operators should fit into the e2e testing framework used by operator-sdk, including Ansible Operator.
 

doc/proposals/ansible-operator.md

@@ -1,5 +1,9 @@
 ## Ansible Operator Proposal
 
+> Status: **completed**
+> 
+> This proposal has been completed, please see the [Ansible User Guide for Operator SDK](../ansible/user-guide.md) for current documentation.
+
 ### Background
 
 Not everyone is a golang developer, and therefore gaining adoption for the operator-sdk is capped by the number of golang developers. Also, tooling for Kubernetes in other languages is lacking support for things such as informers, caches, and listers.