docs: add Factory code review recipe

[warp-agent-staging]

What this feature does

A code-review factory independently inspects ready pull requests, identifies actionable defects, and reports findings without editing, approving, or merging the code. Shipped in v0.2026.10.07.08.29.stable_00 (2026-10-07).

Summary

Replaces the code-review scaffold with a review-only recipe based on current pull request events, the default review role, and the public review-only factory example.

Changes

src/content/docs/factories/use-cases/code-review.mdx

• Adds prerequisites, provider-specific initial and update event mappings, agent settings, and definition-as-code examples.
• Adds a six-step setup and test procedure.
• Documents re-review, independent model or harness selection, duplicate-review prevention, and human merge authority.

Content design plan

Audience and JTBD: An engineering team that wants consistent independent review on ready pull requests without giving an agent merge authority.

Problem: Existing docs describe agents and automations but do not show a focused review-only configuration or its safety boundaries.

Goals:

• The reader can route ready pull requests to a review agent.
• The reader can constrain findings to actionable defects and unmet requirements.
• The reader can test that review does not mutate the branch.

Purpose and value: The recipe adapts a validated factory pattern and clarifies how automated review complements repository protection.

Content type: Feature documentation (combined) — the reader needs both decision guidance and setup steps.

Skill and template: draft_feature_doc / .agents/templates/feature-doc.md.

High-impact scenarios:

• Covers: initial review on ready pull requests and optional review after new commits.
• Excludes: automatic approval, branch mutation, and merging.

Unverified claims

• GitLab and Azure DevOps event mappings were checked against current Factory automation references but not exercised in live provider integrations.

Documentation risk

Risk: engineering-review-required
Rationale: Adds new public Factory workflow guidance and configuration examples that require product review.
Docs override: none

PR stack

• #895 — Navigation and structure
• #896 — Issue triage
• #897 — Code review
• #898 — Issue implementation
• #899 — Production incident resolution
• #900 — Computer Use verification
• #901 — End-to-end SDLC automation

Dependency: #895 is the shared base and targets main. PRs #896–#901 each independently target factory/factory-use-cases-structure; no guide PR depends on another guide PR.

Human review focus

• Confirm the recommended initial and re-review events.
• Confirm that the output and permission boundaries match the intended review-only product path.

Co-Authored-By: Oz oz-agent@warp.dev

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Oct 10, 2026 1:04am UTC

[warp-agent-staging]

This PR was generated with Warp.

Comment @warp-staging-factory on this PR to send it follow-up work.