Improve documentation coherence for sticky sessions

- Fix STICKY_SESSIONS.md to reference local terraform module (not sibling repo)
- Add enable_sticky_sessions variable and outputs to terraform/README.md
- Add sticky sessions section to terraform README explaining multi-replica usage
- Add sticky sessions to PRODUCTION_SETUP.md scaling section with instructions
- Add sticky sessions to security checklist

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: surinderunitone

docs/PRODUCTION_SETUP.md

@@ -395,6 +395,22 @@ View metrics in Azure Portal:
 
 ## Scaling
 
+### Important: Enable Sticky Sessions First
+
+When running multiple replicas, you **must** enable sticky sessions for MCP session affinity. MCP sessions are stored in-memory, so requests must be routed to the same replica.
+
+```bash
+# Enable sticky sessions (required for multi-replica)
+az containerapp ingress sticky-sessions set \
+  --name $APP_NAME \
+  --resource-group $RG_NAME \
+  --affinity sticky
+```
+
+If using Terraform, sticky sessions are enabled by default (`enable_sticky_sessions = true`).
+
+See [STICKY_SESSIONS.md](STICKY_SESSIONS.md) for details.
+
 ### Configure Auto-scaling
 
 ```bash
@@ -525,6 +541,7 @@ Tips:
 - [ ] Configure network restrictions if needed
 - [ ] Enable Azure Monitor for logging
 - [ ] Set up alerts for errors/failures
+- [ ] Enable sticky sessions if running multiple replicas
 
 ## Next Steps
 

docs/STICKY_SESSIONS.md

@@ -17,19 +17,19 @@ AgentGateway stores MCP sessions in-memory. When running multiple replicas, requ
 
 ### Terraform (Recommended)
 
-Sticky sessions are enabled by default in the Terraform module:
+Sticky sessions are enabled by default in the Terraform module (`terraform/`):
 
 ```hcl
-module "agentgateway" {
-  source = "../../../modules/azure/agentgateway"
+# In terraform/terraform.tfvars
+environment         = "prod"
+resource_group_name = "agentgateway-prod-rg"
 
-  # ... other configuration ...
-
-  # Enable sticky sessions for MCP session affinity (default: true)
-  enable_sticky_sessions = true
-}
+# Enable sticky sessions for MCP session affinity (default: true)
+enable_sticky_sessions = true
 ```
 
+The module automatically runs `az containerapp ingress sticky-sessions set` after creating the Container App.
+
 ### Azure CLI
 
 Enable manually with:

terraform/README.md

@@ -96,6 +96,7 @@ terraform output mcp_endpoint
 | `github_repo_url` | GitHub repo for CI/CD | `""` | No |
 | `github_pat` | GitHub PAT for CI/CD | `""` | No |
 | `client_certificate_mode` | mTLS mode: ignore/accept/require | `ignore` | No |
+| `enable_sticky_sessions` | Enable sticky sessions for MCP session affinity | `true` | No |
 
 ## Outputs
 
@@ -109,6 +110,20 @@ terraform output mcp_endpoint
 | `build_command` | Command to build image |
 | `deploy_command` | Command to deploy new image |
 | `logs_command` | Command to view logs |
+| `sticky_sessions_enabled` | Whether sticky sessions are enabled |
+| `sticky_sessions_verify_command` | Command to verify sticky sessions |
+
+## Sticky Sessions (Multi-Replica)
+
+When running multiple replicas, sticky sessions ensure MCP clients always connect to the same replica. This is critical because MCP sessions are stored in-memory.
+
+Sticky sessions are **enabled by default**. To disable:
+
+```hcl
+enable_sticky_sessions = false
+```
+
+See [docs/STICKY_SESSIONS.md](../docs/STICKY_SESSIONS.md) for details.
 
 ## CI/CD Automation