docs: prepare Warp Factories docs for launch - #748
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
![warp-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Overview
This PR reorganizes Factory, Automation Platform, Agent API/SDK, and legacy Oz CLI documentation, with sidebar updates and redirects for moved pages. The overall structure is directionally clear, but several changed lines introduce broken or corrupted public documentation.
Concerns
src/content/docs/factories/developer-tools.mdxcontains duplicated/corrupted prose in the new API and SDK section.- Two external documentation URLs were accidentally rewritten to non-existent paths.
- The redirect list omits
/platform/deployment-patternseven though that page moved to/factories/deployment-patterns/. - Comment audit: no new explanatory code comments were added; existing comments were removed or retained in sidebar context only.
- Test audit: no tests were added or changed.
- Spec/security audit: no approved spec context was attached; the docs/security pass found no secret exposure or unsafe examples beyond the broken documentation links called out inline.
Verdict
Found: 3 critical, 1 important, 0 suggestions
Request changes
Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Review summary
The independent agent completed its review for this commit.
Findings
PR body ## Documentation risk section— [IMPORTANT] Risk is correctly declared 'engineering-review-required' for this 114-file restructure, but the block omits 'Source files consulted' and 'Requested engineering reviewers', even though new/rewritten pages (e.g. src/content/docs/factories/self-hosting/index.mdx, src/content/docs/factories/deployment-patterns.mdx) restate Enterprise-plan gating, ZDR/network, and self-hosting behavior claims. Without cited sources the independent review pass in .agents/references/doc-quality-policy.md step 2 cannot verify claims against source, and source-owner review-request resolution has nothing to key off. Requested change: add a 'Source files consulted' line (or an explicit 'N/A — reorganization of previously published content, no new technical claims' note naming the pages it was cross-checked against) so the engineering-review-required declaration is actionable.src/content/docs/platform/skills-as-agents.mdx:15— [SUGGESTION] Newly added sentence 'This page describes skills that run independently of a factory.' is a meta-opener that narrates the page instead of stating the distinction directly (AGENTS.md → Voice & tone → No meta-openers). Requested change: rewrite to state the scope directly, e.g. 'Skills that run independently of a factory are covered here; for skills scoped to a factory or its agents, see factory skills.'src/content/docs/platform/integrations/github-actions.mdx:51— [NIT] The touched line (link target updated to /agents/cli/oz-cli/api-keys/) still bolds 'Warp API Key' with a capital K, the only such casing in the repo; every other instance (e.g. src/content/docs/platform/integrations/quickstart-github-actions.mdx:17) uses 'Warp API key'. Requested change: lowercase to 'Warp API key' for consistency.
Verdict
Request changes
Contributor
There was a problem hiding this comment.
Review summary
The independent agent completed its review for this commit.
Findings
PR body:39— [CRITICAL] The## Documentation risksection hasEngineering review status: pending.(with a trailing period).check_pr_contract.py's field parser captures the raw remainder of the line as the value, so it readspending.instead of the valid enum valuepending, and the required 'Docs technical references' CI check fails withinvalid engineering review status 'pending.'; must be one of ('not-applicable', 'pending', 'approved'). Verified by runningcheck_pr_contract.py --bodyagainst this PR body and the 108 changed docs files at head 9162794: it failed with exactly this error, and passed once the trailing period was removed. Requested resolution: edit the PR body so the line reads exactlyEngineering review status: pending(no trailing period).
Verdict
Request changes
Contributor
Author
|
/warp-agent-review |
Contributor
|
I'm re-reviewing this pull request in response to a review request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
Contributor
There was a problem hiding this comment.
Overview
This PR restructures the Factory, API/SDK, legacy CLI, deployment, self-hosting, sidebar, and redirect documentation. I reviewed the attached PR description, annotated diff, empty spec context, docs guidance, and supplemental security guidance.
Concerns
- The new managed self-hosting overview drops the cross-surface routing examples that the migrated backend pages still link to for CLI, schedule, integration, API, and web UI routing guidance.
- No security findings were identified in the docs and workflow changes. The spec context was empty, so there was no implementation-spec drift to check.
Verdict
Found: 0 critical, 1 important, 0 suggestions
Request changes
Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
rachaelrenk
force-pushed
the
rrenk/grow-6127-factories-ga
branch
from
September 16, 2026 17:40
2af3dc8 to
687a2f7
Compare
Contributor
There was a problem hiding this comment.
Review summary
The independent agent completed its review for this commit.
Findings
src/pages/api.astro:39-265— [SUGGESTION] The page hardcodes the literal string "Warp Platform API" nine times (the <title>, OG/Twitter meta tags, the WarpTopbar crumb, the visually-hidden h1, the endpoint-index aria-label, and the Scalar metaData block) instead of importing{ VARS } from '@data/vars'and using{VARS.WARP_PLATFORM_API}the way the .mdx content correctly does, even though the PR's own '## Unverified claims' section marks this exact product name as pending confirmation from the requested engineering reviewer (hongyi-chen). Requested resolution: import VARS in api.astro (or reuse the already-computedspecInfo.title/specInfo.description, which the page already derives from the same synced spec) and replace the hardcoded occurrences, so a reviewer-driven rename or reversion stays a one-line vars.ts change instead of a manual multi-spot fix.src/content/docs/platform/quickstart.mdx— [SUGGESTION]check_compression_contract.pyreports the page at 1,174 words with 3 callouts, exceeding the quickstart contract's 800-word/2-callout ceiling. Verified this is not a new violation from this PR — the diff on this file only updates internal link paths (e.g./reference/cli/quickstart/→/agents/cli/oz-cli/quickstart/), matching the PR body's claim that this is a pre-existing, pre-restructure exception. Requested resolution: file (or link) a tracking issue for the deferred callout-consolidation/cut pass called out in the PR body, so the exception doesn't get silently re-deferred through the next navigation restructure.
Verdict
Approve with nits
Co-Authored-By: Warp <agent@warp.dev>
Contributor
There was a problem hiding this comment.
Review summary
The independent agent completed its review for this commit.
Findings
src/content/docs/platform/unmanaged-execution.mdx:110-116— [SUGGESTION] Two callouts (:::cautionpinning the Docker image digest, immediately followed by:::noteon pod sandboxing) sit back-to-back; this predates the PR (carried over unchanged fromplatform/self-hosting/unmanaged.mdx) but the file is already being touched for this rename. AGENTS.md → Callouts and hints disallows consecutive callouts. Requested resolution: merge the two callouts or move one into body prose in this PR or a fast-follow, since the file is already open.
Verdict
Approve
Contributor
There was a problem hiding this comment.
Review summary
The independent agent completed its review for this commit.
Findings
src/content/docs/platform/unmanaged-execution.mdx:138— [IMPORTANT] The Related pages entry says 'The Standalone CLI-only agents section describes the unmanaged model conceptually,' but the restructuredsrc/content/docs/factories/deployment-patterns.mdxno longer has a 'Standalone CLI-only agents' (or any CLI-only) section — it now only covers 'Warp-hosted execution' and 'Managed self-hosting', with unmanaged/CLI execution referenced solely via one row in the model-choice comparison table. Update this line to accurately describe the restructured target page (e.g. point to the comparison table or link directly to/platform/unmanaged-execution/context) instead of a section that no longer exists.src/content/docs/guides/agent-workflows/run-a-software-factory-in-the-cloud.mdx:34— [SUGGESTION] States that Deployment patterns gives 'a full comparison of {WARP_AUTOMATION_PLATFORM}-hosted, CLI-based, and self-hosted execution patterns,' but the restructuredfactories/deployment-patterns.mdxno longer treats CLI-based/unmanaged execution as a first-class pattern with its own section — it appears only as one row in the model-choice table linking out to/platform/unmanaged-execution/. Reword to reflect the current page structure, e.g. 'a comparison of Warp-hosted and managed self-hosted execution, plus where to find unmanaged/CLI-based execution.'src/content/docs/platform/quickstart.mdx— [SUGGESTION] Independently confirmed viacheck_compression_contract.py: this page is 1,174 words with 3 callouts, over the quickstart maximum (800 words / 2 callouts). The diff here only updates redirected link paths and the {VARS.WARP_PLATFORM_API} rename — no prose was added — so this PR does not expand the pre-existing violation, matching the PR body's justification (tracked by #782). No action required here; keep #782 open for the dedicated cut pass.
Verdict
Request changes
Co-Authored-By: Warp <agent@warp.dev>
Contributor
There was a problem hiding this comment.
Review summary
The independent agent completed its review for this commit.
Findings
src/sidebar.ts:412-413— [NIT] In the new 'Factory configuration' group,label: 'Factory configuration',anditems: [are indented one level shallower (4 tabs) than the surrounding object's opening brace and its leading comments (5 tabs), unlike every sibling group in the file. Requested resolution: re-indent lines 412-413 to 5 tabs (or run the project formatter) to match the rest of the file.
Verdict
Approve with nits
Contributor
|
This PR was generated with Warp. Comment    |
Resolve the launch information architecture against current platform behavior, including self-hosted worker authentication and nondeprecated run endpoints. Co-Authored-By: Warp <agent@warp.dev>
Co-Authored-By: Warp <agent@warp.dev>
Co-Authored-By: Warp <agent@warp.dev>
Contributor
There was a problem hiding this comment.
Review summary
The independent agent completed its review for this commit.
Findings
src/content/docs/factories/integrations/azure-devops.mdx:13— [CRITICAL] The page, which this PR changes, contains the marker{/* VERIFY: Confirm first-class Azure DevOps Services support is enabled in production before merging this documentation. */}. It is not listed under## Unverified claims, socheck_pr_contract.py --bodyfails with an unlisted VERIFY marker. Requested change: add one bullet for this marker to## Unverified claims, or resolve the claim and remove the marker. The declaredengineering-review-requiredrisk is correct and stays.src/content/docs/platform/transitioning-from-oz.mdx:14-19— [IMPORTANT] TheFuture directioncolumn makes unconfirmed forward-looking product claims:ozfunctionalitymoves towardthe Warp CLI, thewarpCLI isthe preferred direction, SDK packagesmay be renamed or repackaged under Warp, and Warp Factoriesremains the primary product experience. The PR body and content design plan say the page excludes unconfirmed migration dates, destinations, and replacement surfaces, and no cited source supports these statements. Requested change: remove theFuture directioncolumn or limit it to claims backed by a cited source, such asExisting workflows continue to work. Otherwise add the sources toSource files consultedand list each claim under## Unverified claims.src/content/docs/factories/integrations/azure-devops.mdx:74— [IMPORTANT] The new text saysAzure DevOps doesn't add a default automation, which reverses the previous statement that new Azure DevOps factories include a default automation. Lines 102 and 104 add that definition files accept the Azure DevOpspushevent andsource_reposfor pull request events. TheSource files consultedlist covers onlyworker_hostrouting and self-hosted dispatch, so no cited source supports these behavior and schema claims. Requested change: cite the warp-server or client source files that define the default automations, the supported Azure DevOps events, andsource_repos, or revert these additions. If they stay unverified, list each under## Unverified claims.src/content/docs/platform/quickstart.mdx:105— [SUGGESTION] The PR edits this quickstart, which is 1,174 words with 3 callouts. The compression contract allows at most 800 words and 2 callouts, andcheck_compression_contract.pyexits 1. The PR body justifies the overage as pre-existing and tracks the cut pass in #782, so this does not block. Requested change: keep the #782 reference and schedule the cut pass, or reclassify the page as a tutorial.developers/agent-api-openapi.yaml:4— [SUGGESTION]info.titleis changed toWarp Platform APIand the description now says factories are supported. The PR body says the public name is still pending engineering confirmation, and this file powers the published API reference. Requested change: hold the title and description override until the reviewer confirms the name, or record the confirmation in## Documentation riskbefore merge.
Verdict
Request changes
Co-Authored-By: Warp <agent@warp.dev>
Co-Authored-By: Warp <agent@warp.dev>
Contributor
There was a problem hiding this comment.
Review summary
The independent agent completed its review for this commit.
Findings
src/content/docs/platform/transitioning-from-oz.mdx:17— [IMPORTANT] The table says the Oz web app's "Existing workflows remain supported" and line 21 says "no endpoint migration is required", but the PR's own cited source (GROW-6127) records the Oz web-app retirement in the weeks after the October 6 GA. These are public support and compatibility commitments that the## Unverified claimssection does not list. Requested change: have the engineering reviewer confirm each commitment (lines 17, 18, 20, 21, 36), then either soften the wording to what is confirmed or list the commitments under## Unverified claims.vercel.json:6566— [SUGGESTION] The new/platform/*to/factories/*redirects sit behind the existing/agent-platform/cloud-agents/:path*rule (lines 6526 and 6531), which sends moved pages such asdeployment-patterns,warp-hosting,runners, andself-hosting/*to/platform/...first. Those URLs now take two hops. Requested change: add direct/agent-platform/cloud-agents/...redirects to the final/factories/...destinations, placed before the wildcard rules.PR body ## Documentation risk, Source files consulted— [SUGGESTION] The entry cites a ticket (GROW-6127) and a prose description of earlier sources. Thewarp-serverfiles have no@<sha>pin, so a reviewer cannot verify the claims against a fixed revision. Requested change: replace the ticket and prose withpath@<sha>entries for each source file, and add the head SHA of the former Platform pages that were moved..agents/references/terminology.md:275— [SUGGESTION] The glossary entry "Agent API" is replaced by "Warp Platform API", but theAGENTS.mdlist of proper-noun feature names still includesAgent API. Requested change: updateAGENTS.mdto match, or note in the glossary that "Agent API keys" remains the name of the credential type.
Verdict
Request changes
Co-Authored-By: Warp <agent@warp.dev>
Co-Authored-By: Warp <agent@warp.dev>
Contributor
There was a problem hiding this comment.
Review summary
The independent agent completed its review for this commit.
Findings
AGENTS.md:591— [IMPORTANT] The PR body and its## Documentation riskrationale never mention that this PR also raises the quickstart limit from 600 to 800 words (AGENTS.md,.agents/references/doc-quality-policy.md,check_compression_contract.py, the quickstart and guide skills and templates) and replaceswarpdotdev/oz-agent-actionwith an apt-installedozin.github/workflows/agent-docs-review.yml(about line 40). The loosened limit is the same exception this PR relies on for the 723-word factory quickstart, so the gate is changed in the PR it is applied to. Requested change: move the policy, review-workflow, and verify_review_signal changes to a separate PR, or list them in Summary and Changes and extend the risk Rationale to cover them. If the policy change stays in this PR, add a note that the quickstart exception does not depend on it.src/content/docs/factories/connect-your-factory.mdx:78— [SUGGESTION] The heading## factory endpointsis lowercase, and line 80 starts a sentence with[factory endpoints](also the table cell at line 32). Headings use sentence case, and a sentence-initial word is capitalized. This looks like a find-and-replace side effect. Requested change: write the heading as## Factory endpointsand begin the sentence on line 80 withFactory endpoints.src/content/docs/factories/quickstart.mdx:15— [SUGGESTION] The opening paragraph still explains the concept and uses marketing phrasing (a fleet of agents wired to your software development lifecycle,while people stay in control of key decisions). Line 17 then opens with the meta-openerIn this quickstart, you will.... A quickstart should skip explanation and state the outcome. Requested change: cut the concept paragraph to one or two plain sentences, link tohow-factories-workfor the model, and replace line 17 with the outcome and time budget.src/content/docs/factories/quickstart.mdx:40— [SUGGESTION] The figcaptionClick + next to Factories to open the setup wizard.is procedural, and the caption on line 70 (Toggle which default agents the foreman can dispatch.) is too. Captions should orient the reader, not instruct, and the step text already gives the action. Requested change: rewrite as orienting sentences, for exampleThe Factories section of the sidebar.andThe Pick your factory agents screen.src/content/docs/factories/quickstart.mdx:5— [SUGGESTION] The description promisesin less than 10 minutes, but the quickstart convention is about five minutes. The page labels two sections at about 5 minutes each and runs 723 words. Requested change: either cut the page toward the 600-word, five-minute target or state the 10-minute budget consistently in the opening paragraph and record that in the PR rationale.src/content/docs/factories/index.mdx:16— [SUGGESTION] The new definitionA factory is a cloud automation loop around your software development lifecycleis abstract and is repeated inindex.mdx:72andquickstart.mdx:15. It replaces a plainer description (requests become pull requests). Requested change: restore a concrete definition (what comes in, what the agents do, what comes out) and keep it in one place, linking from the other pages.src/content/docs/index.mdx:2— [SUGGESTION] The homepage rewrite is not described in the PR body. It renames the page toWarp products and getting startedand removes the Privacy and security section (SOC 2, Zero Data Retention, disabling AI features), the Open source section, the multi-model section, and the video. Requested change: add the homepage change to the PR summary, confirm that dropping the privacy and open-source content is intended, and check whether the title change affects the page's search entry.src/content/docs/platform/transitioning-from-oz.mdx:2— [SUGGESTION] The title and sidebar labelAbout the transition from the {{WEB_APP}}promise transition information about the Oz web app. The body is only a table of current documentation and never says what is changing or when. Requested change: either add the actual transition information (what moves, what stays, timing) or retitle the page as a documentation map. Also decide whether it belongs in both the Factories and Automation Platform tabs (src/sidebar.ts:526andsrc/sidebar.ts:554).src/sidebar.ts:496— [SUGGESTION] Onmain, the API quickstart, the Sentry monitoring example, and each individual error page were sidebar entries. Now only the Overview, endpoint pages, and Errors index are listed.factories/api-and-sdk/quickstartandfactories/api-and-sdk/demo-sentry-monitoring-with-sdkare reachable only through links ondeveloper-tools.mdx. Requested change: add the quickstart and Sentry example back under API & SDKs, or note in the PR that dropping them from the sidebar is intentional.src/data/vars.ts:10— [SUGGESTION] The comment now calls theozbinary and the Oz web app supported legacy surfaces with no end date.AGENTS.md(Automation Platform terminology) and.agents/references/terminology.mdstill say these names hold only until 2026-10-06. Requested change: update those two files to match the new comment, or restore the date invars.ts, so contributors get one consistent rule.src/content/docs/factories/self-hosting/managed-kubernetes.mdx:1— [SUGGESTION]check_compression_contract.pyreports 2071 words (maximum 1500) and 4 callouts (budget 2). The PR body justifies this as inherited content, so it is non-blocking. Requested change: record a follow-up issue or cut-pass owner for this page, as the contract asks for an over-maximum exception, and avoid moving more content into it..agents/references/doc-quality-policy.md:41— [SUGGESTION] The## Documentation risksection listsSource files consultedas default branches, generated schemas, and published docs. The file paths and SHAs are in a separate Authoritative sources section, not in the field the policy defines (path@sha). Security-sensitive Azure DevOps claims, such as the Manager's Project Collection Administrators membership and the Microsoft GraphApplication.ReadWrite.OwnedBypermission insrc/content/docs/factories/integrations/azure-devops.mdx:26and:45, could not be checked against source from this review checkout. Requested change: list the specific warp-server files at the pinned SHA inSource files consulted, and leave the engineering review for hongyi-chen as pending until that owner confirms these claims.
Verdict
Request changes
Remove unrelated documentation-policy and review-workflow changes, tighten the Factory quickstart to the existing compression contract, and restore moved API pages to navigation.\n\nCo-Authored-By: Warp <agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
Contributor
There was a problem hiding this comment.
Review summary
The independent agent completed its review for this commit.
Findings
src/content/docs/factories/self-hosting/managed-kubernetes.mdx:13— [SUGGESTION] Page is about 2,071 words with 4 callouts, over the 1500-word and 2-callout compression budget (the PR body justifies this as inherited content). Requested change: run a deletion-only "Cut again" pass, fold the top-of-page cross-link:::noteinto prose or Related pages, and move the later:::cautioninto the step it applies to.src/content/docs/platform/transitioning-from-oz.mdx:2— [SUGGESTION] The title is "Cloud agent documentation map" but the new URL slug is/platform/transitioning-from-oz, which describes a past rename and does not match the title or sidebar label. Requested change: rename the file to something likeplatform/documentation-map.mdx, update the twosrc/sidebar.tsreferences, and add avercel.jsonredirect for the old slug if it has been published.AGENTS.md:820— [SUGGESTION] RemovingAgent APIfrom the proper-noun list is part of the rename to Warp Platform API, butAGENTS.md:1135still says "Warp Agent API",src/pages/api.astro:5still says "upstream Agent API source", and.agents/references/docs-worthiness-criteria.md:44still says "public Agent API". Requested change: update those references so the terminology source of truth, glossary, and comments agree, leaving the separate "Agent API keys" term alone.
Verdict
Approve
Preserve the Factory information architecture while incorporating current self-hosting, entitlement, model router, benchmark, and Teams behavior.\n\nCo-Authored-By: Oz <oz-agent@warp.dev>
Sync benchmark schema and UI guidance with warp-server develop at 3b4638b5.\n\nCo-Authored-By: Oz <oz-agent@warp.dev>
Restore current self-hosting, federation, and workspace guidance while preserving the Factory information architecture. Align plan eligibility, harness support, canonical links, and redirects with the launch sources. Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
Co-Authored-By: Oz <oz-agent@warp.dev>
hongyi-chen
approved these changes
Oct 6, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Prepares the Warp Factories documentation for launch by reconciling the existing restructure with current product behavior in
warpandwarp-server. The update resolves conflicts with currentmain, moves current self-hosting guidance into the Factory information architecture, adds native Azure DevOps guidance, expands the factory-definition reference, restores missing navigation, repairs cross-links, and flattens redirect chains.Changes
Content design plan
Authoritative sources
warpdotdev/warp@88afc88fe2251e77c66a80e80518affeafcbf7e8(master)warpdotdev/warp-server@3b4638b56ae2b9e926fc1f7d59b2062deb4e2110(develop)warpdotdev/docs@46935ea5b192a8145f8eff46243726fea97ec2f0(main), merged without force-pushing.3826de732815d9cf967f6563ec155d4837efd298.billing/config/tiers/build_business.yamlandbilling/config/tiers/_base_enterprise.yaml, where Business and Enterprise grantMANAGED_BYOK_BYOE.config/prod.yaml,config/features/features.go, andclient/packages/factory/.env.production; trigger and filter behavior was verified frommodel/types/triggers/triggers.goandlogic/factoryfile/schema/v1alpha1/automation.schema.json; the editor limitation was verified fromclient/packages/factory/src/pages/FactoryAutomations/azure-devops.ts.logic/factoryfile/schema/v1alpha1/.Validation
git diff --check- passed.python3 scripts/test_check_redirects.py- passed, 3 tests.python3 scripts/check_redirects.py- passed, 1,336 redirects loaded, 536 statically checked, 0 broken.python3 .agents/skills/check_for_broken_links/check_links.py --internal-only- passed, 394 files and 4,291 internal links checked, 0 broken.warpandwarp-servercheckouts - passed with 0 gaps.python3 .agents/skills/validate_ui_refs/validate_ui_refs.py --changed --require-provenance- passed across 131 changed files with 0 Settings-path, Command Palette, or formatting issues.npm run typecheck- passed with 0 errors and 7 existing hints.npm run build- passed; generatedpublic/openapi.jsonat 197.1 KB and produced 395 HTML files and 393 Markdown documents.npm run test:homepage-json-ld- passed.python3 -m unittest discover -s .agents/skills/doc_quality_policy -p 'test_*.py'- passed, 110 tests.python3 .agents/skills/missing_docs/scripts/test_audit_docs.py- passed, 29 tests.python3 .agents/skills/docs_consistency_audit/scripts/test_audit_consistency.py- passed, 41 tests.python3 .agents/skills/sync-openapi-spec/scripts/sync_openapi.py --mode self-test- passed.Validation caveats
python3 .agents/skills/style_lint/style_lint.py --changedreports 332 branch-wide warnings across 132 changed files. None intersect lines added by the review-finding revisions.trunk checkwas unavailable because Trunk is not installed in this environment.networkingtag and path. The stale generated error-documentation URL is fixed; this PR does not silently fold the remaining separate OpenAPI sync into the launch audit.Rollout caveats
factory_reply_no_reply_ackis enabled in staging and disabled in production, so the public docs do not claim the reply acknowledgment before rollout.integration_setup_delegationis enabled in staging and disabled in production, so the Microsoft Teams docs cover the production disconnected state and recovery rather than the delegated setup flow.oz agent run-cloud --attach; no content change was needed.Unverified claims
None. In particular, the pinned production server and client configuration enables Azure DevOps environments, factory identities, and automations, and the pinned canonical OpenAPI spec names the API "Warp Platform API."
Documentation risk
Risk: engineering-review-required
Rationale: This PR restructures launch documentation, changes navigation and redirects, and documents current integration defaults and infrastructure behavior across multiple product surfaces.
Source files consulted: the pinned
warp-serverrevision's billing tier configs; production and staging feature configs; Factory production environment; public OpenAPI; Azure DevOps trigger, generated schema, and automation editor sources; router catalog; incremental benchmark scoring; and Teams handler. The current docs source was consulted for deployment patterns, self-hosting, cloud-provider federation, and Admin Panel workspace behavior. Exact paths are listed in Authoritative sources.Requested engineering reviewers: hongyi-chen
Engineering review status: pending
Docs override: none
Co-Authored-By: Warp agent@warp.dev
Plans: