Clarify docs-review scope and suggestion handling (#145)

* Post docs-review summary as PR comment when no inline findings

When the docs-review workflow is triggered by an issue_comment event
(which is how the PR-menu /docs-review slash command fires), gh-aw's
submit_pull_request_review handler cannot resolve the PR — its
resolveTarget path treats only pull_request* events as PR context, so
body-only reviews silently drop with "No review context available".
The handler for create_pull_request_review_comment, by contrast, reads
context.payload.issue.pull_request and works fine on the same trigger.

Before #137 the agent always emitted at least one inline comment via
the docs skills, which set the review context as a side effect. The
autonomous Vale-only flow now produces zero inline comments on clean
PRs, exposing the latent gh-aw asymmetry. Tracked upstream at
github/gh-aw#30964.

Switch the no-findings path to add_comment, which correctly handles
issue_comment payloads, so the summary always posts. submit_pull_request_review
remains the path when there are inline review comments to attach.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* Clarify docs-review scope and suggestion handling.

Document repo-wide markdown review for repos like docs-content, keep Vale advisory instead of review-gating, and drop the obsolete gh-aw suggestion-block workaround for escaped curly braces.

Co-authored-by: GPT-5.4 <gpt-5.4@openai.com>
Co-authored-by: Cursor <cursoragent@cursor.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-authored-by: GPT-5.4 <gpt-5.4@openai.com>
Co-authored-by: Cursor <cursoragent@cursor.com>

Author: 4 people