chore: update AI governance docs for v2.30 release (#21870)

- remove beta labels
- clarify how AWB is measured
- reassurance of no downtimes when limit is reached

---------

Co-authored-by: Atif Ali <atif@coder.com>
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: Matt Vollmer <matthewjvollmer@outlook.com>

docs/ai-coder/ai-bridge/ai-bridge-proxy/setup.md

@@ -5,8 +5,7 @@ Once enabled, `coderd` runs the `aibridgeproxyd` in-memory and intercepts traffi
 
 **Required:**
 
-1. AI Bridge must be enabled and configured (requires a **premium** license). See [AI Bridge Setup](../setup.md) for further information.
-1. AI Bridge Proxy must be [enabled](#proxy-configuration) using the server flag.
+1. AI Bridge must be enabled and configured (requires a **Premium** license with the [AI Governance Add-On](../../ai-governance.md)). See [AI Bridge Setup](../setup.md) for further information.1. AI Bridge Proxy must be [enabled](#proxy-configuration) using the server flag.
 1. A [CA certificate](#ca-certificate) must be configured for MITM interception.
 1. Clients must be configured to trust the CA certificate and use the proxy.
 

docs/ai-coder/ai-bridge/setup.md

@@ -4,7 +4,7 @@ AI Bridge runs inside the Coder control plane (`coderd`), requiring no separate
 
 **Required**:
 
-1. A **premium** licensed Coder deployment
+1. A **Premium** license with the [AI Governance Add-On](../ai-governance.md).
 1. Feature must be [enabled](#activation) using the server flag
 1. One or more [providers](#configure-providers) API key(s) must be configured
 

docs/ai-coder/ai-governance.md

@@ -95,6 +95,11 @@ options, reach out to your
 
 ## How Coder Tasks usage is measured
 
+> [!NOTE]
+> There is a known issue with how Agent Workspace Builds are tallied in v2.28
+> and v2.29. We recommend updating to v2.28.9, v2.29.4, or v2.30 to resolve
+> this issue.
+
 The usage metric used to measure Coder Tasks consumption is called **Agent
 Workspace Builds** (prev. "managed agents").
 
@@ -133,8 +138,18 @@ workflows.
 Our [AI Governance Add-On](./ai-governance.md) includes a shared usage pool of
 Agent Workspace Builds for automated workflows, along with limits that scale
 proportionately with user count. Usage counts are measured and sent to Coder via
-[usage data reporting](./usage-data-reporting.md). Coder Tasks or other AI
-features do not break when you run over the limit.
+[usage data reporting](./usage-data-reporting.md). Coder Tasks and other AI
+features continue to function normally even if the limit is breached. Admins
+will receive a warning to [contact their account team](https://coder.com/contact)
+to remediate.
 
-If you are approaching your deployment-wide limits,
-[contact us](https://coder.com/contact) to discuss your use case with our team.
+### Tracking Agent Workspace Builds
+
+Admins can monitor Agent Workspace Build usage from the Coder dashboard.
+Navigate to **Deployment** > **Licenses** to view current usage against your
+entitlement limits.
+
+![Agent Workspace Build usage](../images/admin/ai-governance-awb-usage.png)
+
+<small>Agent Workspace Build usage showing current consumption against
+entitlement limits in the Licenses page.</small>

docs/ai-coder/index.md

@@ -31,7 +31,7 @@ terminal-based agent such as Claude Code or Codex's Open Source CLI.
 [Learn more about Coder Tasks](./tasks.md) for best practices and how to get
 started.
 
-## Secure Your Workflows with Agent Boundaries (Beta)
+## Secure Your Workflows with Agent Boundaries
 
 AI agents can be powerful teammates, but must be treated as untrusted and
 unpredictable interns as opposed to tools. Without the right controls, they can

docs/manifest.json

@@ -996,7 +996,7 @@
 							"title": "Agent Boundaries",
 							"description": "Understanding Agent Boundaries in Coder Tasks",
 							"path": "./ai-coder/agent-boundaries/index.md",
-							"state": ["premium", "beta"],
+							"state": ["premium"],
 							"children": [
 								{
 									"title": "NS Jail",