diff --git a/.github/workflows/deploy-docs-staging.yaml b/.github/workflows/deploy-docs-staging.yaml
index 38d88dbb4..872c378bf 100644
--- a/.github/workflows/deploy-docs-staging.yaml
+++ b/.github/workflows/deploy-docs-staging.yaml
@@ -1,5 +1,7 @@
 name: Deploy docs site to staging
 
+run-name: Deploy docs site to staging | ${{ github.event.workflow_run.id || github.sha }}
+
 on:
   push:
     branches:
diff --git a/.github/workflows/merge-main-into-staging.yaml b/.github/workflows/merge-main-into-staging.yaml
index fd825af4e..d132355b1 100644
--- a/.github/workflows/merge-main-into-staging.yaml
+++ b/.github/workflows/merge-main-into-staging.yaml
@@ -1,9 +1,13 @@
 name: Merge main into staging
 
+run-name: Merge main into staging | ${{ github.event.client_payload.correlation_id || github.sha }}
+
 on:
   push:
     branches:
       - main
+  repository_dispatch:
+    types: [release-notes-published]
 
 permissions:
   contents: write
@@ -77,4 +81,4 @@ jobs:
         if: ${{ success() && steps.pr-number.outputs.pull-request-number != '' }}
         run: gh api -X DELETE "repos/${{ github.repository }}/git/refs/heads/update-staging-${{ github.run_id }}"
         env:
-          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
\ No newline at end of file
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
diff --git a/AGENTS.md b/AGENTS.md
index 3a98ccb3d..dd7fa67ec 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -67,6 +67,13 @@ Documentation moves through `main` → `staging` → `prod`:
 3. The prospective production build runs the complete production-profile validation and uploads an immutable artifact keyed to the exact Git tree that a `staging` → `prod` merge will create.
 4. The production workflow deploys only that exact-tree artifact from a successful staging workflow run. If the artifact is missing, expired, or came from another workflow, production deployment must fail before loading AWS credentials or modifying production.
 
+Release-note content is sourced from `validmind/release-notes`, so merging a
+release-notes pull request does not create or merge a documentation pull request.
+Instead, the release-notes repository dispatches the existing **Merge main into
+staging** workflow. Its successful completion triggers the staging deployment,
+which builds the promoted documentation tree with the latest release-notes
+`main` revision.
+
 The merge-queue `validate` bridge does not render the site again. It records that the pull-request revision passed preview validation; the complete production safety boundary is the post-merge staging artifact.
 
 ## CI invariants