Add limitations and premium notice

Author: rkoron007

content/terraform/v1.13.x/docs/language/stacks/deploy/conditions.mdx

@@ -7,6 +7,8 @@ description: Learn how to use deployment groups to create orchestration rules th
 
 Learn how to use deployment groups to create orchestration rules that automatically approve deployment runs, helping you manage your deployments at scale.
 
+@include 'premium-deployment-groups.mdx'
+
 ## Create deployment groups
 
 You can create deployment groups in your deployment configuration file to define rules that let you auto-approve deployment runs.

content/terraform/v1.13.x/docs/language/stacks/deploy/pass-data.mdx

@@ -15,11 +15,13 @@ To output information from a Stack, declare a `publish_output` block in the depl
 
 To consume the data exported by the upstream Stack, declare an `upstream_input` block in the deployment configuration of a different Stack in the same project. We refer to the Stack that declares an `upstream_input` block as the downstream Stack.
 
-## Requirements
+## Requirements and limitations
 
-The `publish_output` and `upstream_input` blocks require at least Terraform version `terraform_1.10.0-alpha20241009` or higher. Download the [latest version of Terraform](https://releases.hashicorp.com/terraform/) to use the most up-to-date functionality.
+Downstream Stacks must reside in the same project as their upstream Stacks.
 
-Downstream Stacks must also reside in the same project as their upstream Stacks.
+The following limitations apply to passing data between Stacks:
+- Stacks can link to up to 20 other upstream Stacks. [Learn more about passing data between Stacks](/terraform/language/stacks/deploy/pass-data).
+- Stacks can expose values to up to 25 downstream Stacks. [Learn more about passing data between Stacks](/terraform/language/stacks/deploy/pass-data).
 
 ## Expose outputs to another Stack
 

content/terraform/v1.13.x/docs/language/stacks/index.mdx

@@ -63,10 +63,14 @@ After fully configuring your Stack, use HCP Terraform to deploy your Stack’s i
 
 Stacks are useful when managing complex, multi-environment infrastructures where consistency and reusability are crucial. Refer to Stack [use cases](/terraform/language/stacks/use-cases) for inspiration on situations where Stacks are particularly well suited.
 
-## Constraints, limitations, and troubleshooting
+## Constraints and limitations
 
-While Stacks provide powerful capabilities, there are some limitations to be aware of during this beta phase:
+Stacks have the following constraints:
 
 - Each Stack currently supports a maximum of 20 deployments, which may limit scalability for large environments.
 - Stack deployment groups currently support only one deployment per group.
+- Each Stack supports up to 100 components.
+- Each Stack supports up to 10,000 resources.
+- Stacks can link to up to 20 other upstream Stacks. [Learn more about passing data between Stacks](/terraform/language/stacks/deploy/pass-data).
+- Stacks can expose values to up to 25 downstream Stacks. [Learn more about passing data between Stacks](/terraform/language/stacks/deploy/pass-data).
 - Stacks are not available for users on legacy HCP Terraform team plans. Learn more about [migrating to a current HCP Terraform plan](/terraform/cloud-docs/overview/migrate-teams-standard).

content/terraform/v1.13.x/docs/partials/premium-deployment-groups.mdx

@@ -0,0 +1,5 @@
+<Note title="Premium tier">
+
+Running orchestration rules for deployment groups isis available in the HCP Terraform **Plus** Edition. Refer to [HCP Terraform pricing](https://www.hashicorp.com/products/terraform/pricing) for details.
+
+</Note>