Revert "docs: add automated PR review gate setup guide (#43)"

This reverts commit 4466a02.

Author: isadeks

docs/astro.config.mjs

@@ -8,7 +8,7 @@ There are six ways to interact with the platform. You can use them independently
 
 1. **CLI** (recommended) - The `bgagent` CLI authenticates via Cognito and calls the Task API. Best for individual developers submitting tasks from the terminal. Handles login, token caching, and output formatting.
 2. **REST API** (direct) - Call the Task API endpoints directly with a JWT token. Best for building custom integrations, dashboards, or internal tools on top of the platform. Full validation, audit logging, and idempotency support.
-3. **Webhook** - External systems (CI pipelines, GitHub Actions) can create tasks via HMAC-authenticated HTTP requests. Best for automated workflows where tasks should be triggered by events (e.g., a new issue is labeled, a PR needs review). No Cognito credentials needed; uses a shared secret per integration. For the turnkey "auto-review every green PR" setup, see the [Automated PR review gate setup guide](./REVIEW_GATE_SETUP_GUIDE.md).
+3. **Webhook** - External systems (CI pipelines, GitHub Actions) can create tasks via HMAC-authenticated HTTP requests. Best for automated workflows where tasks should be triggered by events (e.g., a new issue is labeled, a PR needs review). No Cognito credentials needed; uses a shared secret per integration.
 4. **Slack** - Submit tasks by @mentioning the bot and receive threaded progress notifications with reaction-based status. See the [Slack setup guide](./SLACK_SETUP_GUIDE.md).
 5. **Linear** - Apply a label to a Linear issue to trigger a task; the agent posts progress comments back on the issue via Linear's MCP server. The label has variants — `bgagent` (do it), `bgagent:decompose` (plan a multi-part issue and wait for your approval), `bgagent:auto` (plan and start), and `bgagent:help` (explain the labels). See [Trigger labels](./LINEAR_SETUP_GUIDE.md#trigger-labels) in the Linear setup guide.
 6. **Jira** - Add a label to a Jira Cloud issue to trigger a task; the agent posts progress comments back on the issue via the Jira REST v3 API. See the [Jira setup guide](./JIRA_SETUP_GUIDE.md).

docs/guides/REVIEW_GATE_SETUP_GUIDE.md

@@ -47,7 +47,6 @@ function rewriteDocsLinkTarget(target) {
     LINEAR_PAK_MIGRATION_RUNBOOK: '/using/linear-pak-migration-runbook',
     JIRA_SETUP_GUIDE: '/using/jira-setup-guide',
     DEPLOY_PREVIEW_SCREENSHOTS_GUIDE: '/using/deploy-preview-screenshots-guide',
-    REVIEW_GATE_SETUP_GUIDE: '/using/review-gate-setup-guide',
     CEDAR_POLICY_GUIDE: '/customizing/cedar-policies',
     DEPLOYMENT_GUIDE: '/getting-started/deployment-guide',
   };
@@ -296,12 +295,6 @@ mirrorMarkdownFile(
   path.join('src', 'content', 'docs', 'using', 'Deploy-preview-screenshots-guide.md'),
 );
 
-// --- Automated PR review gate setup guide: mirror to using/ ---
-mirrorMarkdownFile(
-  path.join(docsRoot, 'guides', 'REVIEW_GATE_SETUP_GUIDE.md'),
-  path.join('src', 'content', 'docs', 'using', 'Review-gate-setup-guide.md'),
-);
-
 // --- Cedar Policy Guide: mirror to customizing/ (authoring reference for blueprint authors) ---
 mirrorMarkdownFile(
   path.join(docsRoot, 'guides', 'CEDAR_POLICY_GUIDE.md'),

docs/guides/USER_GUIDE.md

@@ -8,7 +8,7 @@ There are six ways to interact with the platform. You can use them independently
 
 1. **CLI** (recommended) - The `bgagent` CLI authenticates via Cognito and calls the Task API. Best for individual developers submitting tasks from the terminal. Handles login, token caching, and output formatting.
 2. **REST API** (direct) - Call the Task API endpoints directly with a JWT token. Best for building custom integrations, dashboards, or internal tools on top of the platform. Full validation, audit logging, and idempotency support.
-3. **Webhook** - External systems (CI pipelines, GitHub Actions) can create tasks via HMAC-authenticated HTTP requests. Best for automated workflows where tasks should be triggered by events (e.g., a new issue is labeled, a PR needs review). No Cognito credentials needed; uses a shared secret per integration. For the turnkey "auto-review every green PR" setup, see the [Automated PR review gate setup guide](/sample-autonomous-cloud-coding-agents/using/review-gate-setup-guide).
+3. **Webhook** - External systems (CI pipelines, GitHub Actions) can create tasks via HMAC-authenticated HTTP requests. Best for automated workflows where tasks should be triggered by events (e.g., a new issue is labeled, a PR needs review). No Cognito credentials needed; uses a shared secret per integration.
 4. **Slack** - Submit tasks by @mentioning the bot and receive threaded progress notifications with reaction-based status. See the [Slack setup guide](/sample-autonomous-cloud-coding-agents/using/slack-setup-guide).
 5. **Linear** - Apply a label to a Linear issue to trigger a task; the agent posts progress comments back on the issue via Linear's MCP server. The label has variants — `bgagent` (do it), `bgagent:decompose` (plan a multi-part issue and wait for your approval), `bgagent:auto` (plan and start), and `bgagent:help` (explain the labels). See [Trigger labels](/sample-autonomous-cloud-coding-agents/using/linear-setup-guide#trigger-labels) in the Linear setup guide.
 6. **Jira** - Add a label to a Jira Cloud issue to trigger a task; the agent posts progress comments back on the issue via the Jira REST v3 API. See the [Jira setup guide](/sample-autonomous-cloud-coding-agents/using/jira-setup-guide).