docs: add Factory Computer Use verification recipe

[warp-agent-staging]

What this feature does

A Computer Use verification factory builds a user-facing change, exercises its rendered interface, and attaches focused screenshots or recordings that prove observable acceptance criteria. Shipped in v0.2026.10.07.08.29.stable_00 (2026-10-07).

Summary

Replaces the Computer Use scaffold with a verification recipe for the Warp Agent harness, including a dedicated verification role, label-triggered automation, capture policy, and evidence requirements.

Changes

src/content/docs/factories/use-cases/computer-use-verification.mdx

• Adds prerequisites and Warp Agent harness constraints.
• Adds VERIFY agent and pull request automation examples.
• Adds a six-step configuration procedure, example workflow, evidence standards, and related references.

Content design plan

Audience and JTBD: A team shipping user-facing changes that needs rendered-flow evidence in pull requests beyond code-level tests.

Problem: Computer Use and artifact documentation exists, but Factory users must infer how to add a dedicated verification stage and define acceptable proof.

Goals:

• The reader can configure a verification agent on the supported harness.
• The reader can trigger verification for a user-facing pull request.
• The reader can require evidence for specific observable states.

Purpose and value: The guide connects Factory orchestration to the existing Computer Use verification and artifact workflow.

Content type: Feature documentation (combined) — the reader needs capability boundaries and a configuration procedure.

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

High-impact scenarios:

• Covers: cloud-sandbox builds, browser interaction, screenshots or recordings, and pull request evidence.
• Excludes: third-party harness integration, production credentials, and inference from missing proof.

Unverified claims

• Harness support, computerUseModel, and artifact attachment modes were checked against current docs and configuration sources, but this draft did not run a live Factory verification.

Documentation risk

Risk: engineering-review-required
Rationale: Adds new public Factory workflow guidance, harness constraints, 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 Warp Agent-only support statement and model configuration.
• Confirm the recommended artifact attachment and proof requirements.

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 12:44am UTC

[warp-agent-staging]

This PR was generated with Warp.

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