Skip to content

docs: restructure factories documentation - #748

Open
rachaelrenk wants to merge 17 commits into
mainfrom
rrenk/grow-6127-factories-ga
Open

rachaelrenk wants to merge 17 commits into
mainfrom
rrenk/grow-6127-factories-ga

Conversation

@rachaelrenk

@rachaelrenk rachaelrenk commented Sep 15, 2026

Copy link
Copy Markdown
Contributor

Summary

Completes the revised pre-GA Phase 1 documentation restructure around Warp Factories while preserving the current top-level order, Factory topic link, and Early Access treatment.

Changes

  • Moves managed self-hosting, deployment, hosting, runners, API/SDK, and related troubleshooting docs into Factory-owned navigation.
  • Rehomes the legacy Oz CLI reference under Agents and removes the standalone API & Reference tab.
  • Adds Factory Developer tools and Infrastructure & security sidebar groups, with Factory API, Factory MCP, and webhooks grouped only under Developer tools.
  • Adds a high-level transition page that confirms existing workflows remain available and links readers to the Automation Platform and Warp Factories without claiming unconfirmed exact migration dates or replacement surfaces.
  • Reframes Factory hosting, runner, API/SDK, and managed-worker guidance around Factory setup and operations, linking back to the shared Automation Platform and Enterprise references.
  • Adds Factory-context links from retained Platform management, harness, skills, MCP, secrets, environments, triggers, and integrations references.
  • Preserves published paths with redirects and updates internal links to the new canonical pages.
  • Renames the root landing page to Warp products while keeping its pre-GA Terminal and Agent emphasis.
  • Captures the independent review agent's CLI output directly in a file so review publication does not exceed GitHub Actions process-environment limits.

Content design plan

  • Target audience and their JTBD - A developer with existing legacy cloud-agent workflows who needs to know whether the Factory-first docs restructure changes their setup and where to find the right documentation.
  • Problem statement - Moved documentation could make readers assume they must migrate immediately or that a Factory-specific page replaces every standalone cloud-agent workflow.
  • Goals - Let readers choose the Automation Platform or Warp Factories entry point; confirm that existing workflows remain available; route them to relocated API/SDK, CLI, and managed-self-hosting documentation.
  • Purpose and value added - This is the cross-cutting transition surface. Neither the Automation Platform overview nor the Factory overview can accurately own the relationship between the two documentation paths.
  • Content type and model - Conceptual. Readers need scope and decision guidance, not migration steps that depend on unconfirmed product mapping.
  • Skills and templates to use - draft_conceptual and .agents/templates/conceptual.md.
  • High-impact scenarios - Covers readers choosing standalone Automation Platform workflows versus Factory workflows and finding moved references. Excludes exact dates, legacy web-app routes, replacement destinations, and migration actions until product mapping is confirmed.

Validation

  • python3 .agents/skills/style_lint/style_lint.py --changed - completed; the Phase 1 delta has no actionable structural or terminology findings. Existing report-only warnings remain elsewhere in moved source.
  • python3 .agents/skills/check_for_broken_links/check_links.py --internal-only - passed with 0 broken links across 4,126 internal links.
  • git diff --check - passed.
  • Direct review-output capture, review publication, workflow structure, and verification tests - passed.
  • Representative redirect families for moved Platform, API/SDK, legacy CLI, unmanaged execution, and execution-security paths - verified in vercel.json.
  • npm run build - compiled the updated MDX, variables, and sidebar, then failed on the existing /_llms-txt/support.txt prerender with RangeError: Maximum call stack size exceeded in hast-util-to-text.

Unverified claims

  • Factory Dashboard controls and managed self-hosting behavior were restructured from existing documentation. They were not revalidated against a live Factory Dashboard during this documentation-only change.
  • The transition page deliberately excludes unconfirmed exact migration dates, destination surfaces, and legacy web-app behavior pending the product mapping.

Documentation risk

Risk: engineering-review-required
Rationale: Moves published documentation across top-level sections, revises navigation, changes the product-context framing for infrastructure and developer interfaces, and hardens the independent review workflow.
Source files consulted: GROW-6127 for the currently scheduled October 6 Factories GA and the Oz web-app retirement in the following weeks; previously published Platform sources for managed self-hosting, execution security, runners, deployment patterns, and Warp-hosted execution; the former API & SDK and legacy Oz CLI references; and src/content/docs/factories/factory-dashboard.mdx.
Requested engineering reviewers: none — no single source owner resolved for this cross-cutting documentation restructure.
Engineering review status: pending
Docs override: none

Co-Authored-By: Warp agent@warp.dev

rachaelrenk and others added 2 commits September 15, 2026 11:18
Co-Authored-By: Warp <agent@warp.dev>
…ries-ga

# Conflicts:
#	src/sidebar.ts
#	vercel.json
@cla-bot cla-bot Bot added the cla-signed label Sep 15, 2026
@vercel

vercel Bot commented Sep 15, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated
docs Ready Ready Preview Sep 16, 2026 12:56am UTC

Request Review

@warp-for-oss

warp-for-oss Bot commented Sep 15, 2026

Copy link
Copy Markdown
Contributor

@rachaelrenk

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 /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

@rachaelrenk rachaelrenk added the warpy-factory Opened by the Warp factory agents label Sep 15, 2026

@warp-for-oss warp-for-oss Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.mdx contains 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-patterns even 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

Comment thread src/content/docs/factories/developer-tools.mdx Outdated
Comment thread src/content/docs/agents/cli/oz-cli/federate.mdx Outdated
Comment thread vercel.json
@rachaelrenk
rachaelrenk removed the request for review from hongyi-chen September 15, 2026 17:33
Co-Authored-By: Warp <agent@warp.dev>
Co-Authored-By: Warp <agent@warp.dev>
Co-Authored-By: Warp <agent@warp.dev>
Co-Authored-By: Warp <agent@warp.dev>
Co-Authored-By: Warp <agent@warp.dev>
Co-Authored-By: Warp <agent@warp.dev>

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Co-Authored-By: Warp <agent@warp.dev>
Co-Authored-By: Warp <agent@warp.dev>
Co-Authored-By: Warp <agent@warp.dev>

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review summary

The independent agent completed its review for this commit.

Findings

  • PR body:39 — [CRITICAL] The ## Documentation risk section has Engineering 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 reads pending. instead of the valid enum value pending, and the required 'Docs technical references' CI check fails with invalid engineering review status 'pending.'; must be one of ('not-applicable', 'pending', 'approved'). Verified by running check_pr_contract.py --body against 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 exactly Engineering review status: pending (no trailing period).

Verdict

Request changes

@rachaelrenk

Copy link
Copy Markdown
Contributor Author

/warp-agent-review

@warp-for-oss

warp-for-oss Bot commented Sep 15, 2026

Copy link
Copy Markdown
Contributor

@rachaelrenk

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 /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

@warp-for-oss warp-for-oss Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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


## Configure a factory to use a worker

Define the worker host and a compatible runner in your [factory definition](/factories/factory-as-code/). The factory dashboard shows each configured runner and the worker that executes its work. Use the [worker reference](/factories/self-hosting/reference/) to configure the worker process and the [factory dashboard](/factories/factory-dashboard/) to inspect its runs.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [IMPORTANT] This new section only explains routing factory work through the factory definition, but the migrated backend pages still link to this anchor for CLI, schedules, integrations, API, and web UI routing examples. That removes the operational guidance that used to live on the self-hosting overview while leaving inbound links that promise it; restore those routing examples or update the inbound link text and targets so readers aren't sent here for missing instructions.

Co-Authored-By: Warp <agent@warp.dev>
Co-Authored-By: Warp <agent@warp.dev>
Co-Authored-By: Warp <agent@warp.dev>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed warpy-factory Opened by the Warp factory agents

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant