[docs] Self-healing documentation fixes from issue analysis - 2026-06-28

docs/src/content/docs/reference/glossary.md

@@ -307,7 +307,7 @@ An extension mechanism for safe outputs that enables integration with third-part
 
 ### Dispatch Repository (`dispatch_repository`)
 
-An experimental safe output type that triggers `repository_dispatch` events in external repositories for cross-repository orchestration. Each key under `safe-outputs.dispatch_repository:` defines a named tool exposed to the agent. A tool requires a `workflow` identifier (forwarded in `client_payload` for routing), an `event_type`, and either a static `repository` slug or an `allowed_repositories` list. GitHub Actions expressions (`${{ ... }}`) are supported in repository fields and are passed through without format validation. At compile time the compiler emits a warning: `Using experimental feature: dispatch_repository`. See [Safe Outputs Reference](/gh-aw/reference/safe-outputs/#repository-dispatch-dispatch_repository).
+An experimental safe output type that triggers `repository_dispatch` events in external repositories for cross-repository orchestration. Each key under `safe-outputs.dispatch_repository:` defines a named tool exposed to the agent. The compiler also accepts `dispatch-repository` (dash) as an alias for the safe-output key. A tool requires a `workflow` identifier (forwarded in `client_payload` for routing), an `event_type`, and either a static `repository` slug or an `allowed_repositories` list. GitHub Actions expressions (`${{ ... }}`) are supported in repository fields and are passed through without format validation. At compile time the compiler emits a warning: `Using experimental feature: dispatch_repository`. See [Safe Outputs Reference](/gh-aw/reference/safe-outputs/#repository-dispatch-dispatch_repository).
 
 ### Safe Output Actions
 

docs/src/content/docs/reference/safe-outputs.md

@@ -1347,6 +1347,8 @@ Use `call-workflow` for deterministic fan-out where actor attribution and zero A
 
 Triggers [`repository_dispatch`](https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows#repository_dispatch) events in external repositories. Unlike `dispatch-workflow` (same-repo only), `dispatch_repository` is designed for cross-repository orchestration.
 
+The compiler accepts both `dispatch_repository` (underscore, preferred) and `dispatch-repository` (dash, alias) as the safe-output key. Either spelling produces the same behavior.
+
 Each key under `dispatch_repository:` defines a named tool exposed to the agent:
 
 ```yaml wrap