docs: document the current state of built-in and native

website/content/docs/connect/native/index.mdx

@@ -9,6 +9,11 @@ description: >-
 
 # Connect-Native App Integration
 
+~> **Note:** The Native App Integration does not support many of the Connect service
+mesh features, and is not under active development.
+The [Envoy proxy](/docs/connect/proxies/envoy) should be used for most production
+environments.
+
 Applications can natively integrate with the Connect API to support accepting
 and establishing connections to other Connect services without the overhead of a
 [proxy sidecar](/docs/connect/proxies). This option is especially useful

website/content/docs/connect/proxies/built-in.mdx

@@ -6,10 +6,13 @@ description: Consul Connect comes with a built-in proxy for testing and developm
 
 # Built-In Proxy Options
 
+~> **Note:** The built-in proxy is not supported for production deployments. It does not
+support many of the Connect service mesh features, and is not under active development.
+The [Envoy proxy](/docs/connect/proxies/envoy) should be used for production deployments.
+
 Consul comes with a built-in L4 proxy for testing and development with Consul
-Connect.
+Connect service mesh.
 
-~> **Note:** [Envoy](/docs/connect/proxies/envoy) should be used for production deployments, or when [layer 7 traffic management](/docs/connect/l7-traffic-management) features are needed.
 
 ## Getting Started