Make docs-review advisory-only.

Limit docs-review to non-blocking comment reviews, remove low-signal review-summary boilerplate, and document the current Vale dependency behavior in the workflow README.

Co-authored-by: GPT-5.4 <gpt-5.4@openai.com>
Made-with: Cursor

Author: theletterf

.github/workflows/gh-aw-docs-review.lock.yml

@@ -80,7 +80,7 @@ safe-outputs:
   submit-pull-request-review:
     max: 1
     target: "triggering"
-    allowed-events: [COMMENT, REQUEST_CHANGES]
+    allowed-events: [COMMENT]
 timeout-minutes: 30
 steps:
   - name: Repo-specific setup
@@ -253,7 +253,7 @@ If you found one or more high-confidence actionable issues:
 - create up to 20 focused inline review comments, and
 - submit one consolidated pull request review.
 
-Use `REQUEST_CHANGES` only when the issues are important enough that the PR should be revised before merge. Otherwise use `COMMENT`.
+Always use `COMMENT` for the final review. This workflow is advisory and must not block merging through a `REQUEST_CHANGES` review state.
 
 ## Review body format
 
@@ -262,11 +262,6 @@ Submit one final review body in this shape:
 ```markdown
 ## Docs review summary
 
-- Reviewed `<N>` changed markdown file(s) in scope.
-- Reviewed scope: `<docs-subtree | repo-wide-markdown>`.
-- Ignored `<N>` non-eligible changed file(s) outside the review scope.
-- Outcome: `<No actionable issues | Commented suggestions | Changes requested>`.
-
 ### Focus areas
 - Style and clarity: <short result>.
 - Jargon: <short result>.

.github/workflows/gh-aw-docs-review.md

@@ -34,7 +34,7 @@ Configure the `COPILOT_GITHUB_TOKEN` secret before running the workflow.
 |--------|-----|-------------|
 | `noop` | — | Used when the trigger is not a pull request, or the PR has no changed `docs/**/*.md` files |
 | `create-pull-request-review-comment` | 20 | Adds focused inline review comments on changed markdown lines |
-| `submit-pull-request-review` | 1 | Submits the overall pull request review summary as `COMMENT` or `REQUEST_CHANGES` |
+| `submit-pull-request-review` | 1 | Submits the overall pull request review summary as a non-blocking `COMMENT` |
 
 The inline review comment cap for this workflow is set to `20`, so the workflow prioritizes the highest-signal comments and keeps broader observations in the summary review. Lower-priority nits should only be reported when they are grounded in the Elastic style guide, and those nits should usually be summarized in the review body instead of consuming inline comment slots.
 
@@ -68,6 +68,8 @@ The review prompt instructs the Copilot agent to invoke these imported skills by
 
 When an inline comment can be expressed as a small, exact replacement for the reviewed line or hunk, the workflow should prefer an apply-ready GitHub suggestion block over prose-only guidance.
 
+Only `docs-check-style` explicitly references Vale. That skill tries the `vale_lint` MCP tool first and otherwise falls back to the `vale` CLI when available. The reusable workflow itself does not install Vale, so if the runtime environment lacks a `vale` binary and no Vale MCP tool is present, that skill falls back to manual style review.
+
 ## Example
 
 ```yaml