docs: slim verification-stack Layer 2 section to lightweight links

Full setup instructions now live in code-review.mdx and qa-changes.mdx.
Verification stack page links out to them instead of duplicating content.

Co-authored-by: openhands <openhands@all-hands.dev>

Author: all-hands-bot

openhands/usage/use-cases/verification-stack.mdx

@@ -48,76 +48,10 @@ For technical details on how the critic model works, see our paper: [A Rubric-Su
 
 The repo-level verifier consists of two components — a [code review agent](/openhands/usage/use-cases/code-review) and a [QA agent](/openhands/usage/use-cases/qa-changes) — both available as plugins in the [OpenHands/extensions](https://github.com/OpenHands/extensions) repository.
 
-### Option A: GitHub Actions
-
-Add the ReviewBot directly to your GitHub Actions workflow. This runs the code review (and optionally QA) as part of your CI pipeline on every PR.
-
-<Steps>
-  <Step title="Create a bot account">
-    Create a bot account under your GitHub organization (e.g., `your-org-bot`). This account will post review comments and approve/request changes on PRs. Grant it write access and the ability to approve PRs on your repository.
-  </Step>
-
-  <Step title="Configure secrets">
-    In your repository's **Settings → Secrets and variables → Actions**, add:
-    - **`LLM_API_KEY`**: Your LLM API key
-    - **`BOT_GITHUB_TOKEN`**: A GitHub token for the bot account (if you want reviews posted by the bot rather than the default `GITHUB_TOKEN`)
-  </Step>
-
-  <Step title="Add the workflow">
-    Create `.github/workflows/review-bot.yml`:
-
-    ```yaml
-    name: ReviewBot
-    on:
-      pull_request:
-        types: [opened, ready_for_review, synchronize]
-
-    jobs:
-      review:
-        runs-on: ubuntu-latest
-        if: github.event.pull_request.draft == false
-        steps:
-          - name: Run PR Review
-            uses: OpenHands/extensions/plugins/pr-review@main
-            with:
-              llm-model: anthropic/claude-sonnet-4-5-20250929
-              llm-api-key: ${{ secrets.LLM_API_KEY }}
-              github-token: ${{ secrets.BOT_GITHUB_TOKEN || secrets.GITHUB_TOKEN }}
-    ```
-  </Step>
-</Steps>
-
-**Trade-offs:** Full control over when and how the bot runs. However, it requires per-repository configuration — every new repo needs its own workflow file, and keeping them in sync requires maintenance.
-
-For the complete configuration reference (trigger customization, ACP mode, sub-agents, custom review guidelines), see the [Automated Code Review](/openhands/usage/use-cases/code-review) page.
-
-### Option B: OpenHands Automations (Beta)
+For full setup instructions, see:
 
-<Warning>
-OpenHands Automations is currently an experimental beta feature. The API and configuration format may change.
-</Warning>
-
-The alternative is using [OpenHands Automations](/openhands/usage/automations/overview), our event-triggered automation system. With Automations, you define the trigger once and it covers all repositories the bot account has access to — no per-repo workflow files needed.
-
-<Steps>
-  <Step title="Create a bot account on OpenHands Cloud">
-    Log in to [OpenHands Cloud](https://app.all-hands.dev) with your organization's bot GitHub account.
-  </Step>
-
-  <Step title="Connect GitHub">
-    Connect the bot account's GitHub to OpenHands Cloud via the [GitHub installation](/openhands/usage/cloud/github-installation) flow.
-  </Step>
-
-  <Step title="Create the automation">
-    Log in as the bot account and instruct the agent to set up the automation:
-
-    ```
-    Create an OpenHands Cloud automation using the Plugin Preset that automatically reviews pull requests. Use the pr-review plugin from github:OpenHands/extensions (repo_path: plugins/pr-review). Trigger it on pull_request.opened and pull_request.ready_for_review events for the repository YOUR_ORG/YOUR_REPO, excluding draft PRs. Set timeout to 3600 seconds. Use this exact prompt for the automation: "Review the pull request from the GitHub event payload using the pr-review plugin. Post a comprehensive code review on GitHub with inline comments on specific changed lines where appropriate, and a concise overall summary. Avoid duplicating existing unresolved review comments. Include a brief note that the review was generated by an AI agent (OpenHands) on behalf of the user through OpenHands Automation."
-    ```
-  </Step>
-</Steps>
-
-**Trade-offs:** Simpler to set up and maintain — define it once and it covers all repos. It also leverages the full OpenHands runtime (browser, tools, sandbox), which GitHub Actions cannot.
+- **[Automated Code Review](/openhands/usage/use-cases/code-review)** — GitHub Actions and OpenHands Automations setup for the ReviewBot
+- **[Automated QA Testing](/openhands/usage/use-cases/qa-changes)** — Setup for the QA agent
 
 ## Closing the Loop: The Iterate Skill