Warp open-sources docs, agent workflows

Warp is using docs-as-code as an agent platform, not just a publishing format. That matters because the docs now double as product context for Warp Agent, so documentation quality becomes part of the product’s intelligence loop.

• –The move shifts docs from a vendor UI to inspectable Markdown, which makes changes, diffs, and community PRs much easier
• –Warp is explicitly treating docs as agent-consumable context via RAG and `llms.txt`, which is a practical pattern for AI-native developer tools
• –The migration scale is the story: 285 cloud-agent runs for a docs rewrite shows Warp is dogfooding Oz for real operational work, not demos
• –Open-sourcing the maintenance skills is more interesting than the repo itself, because the repeatable workflows are what make the system scalable
• –This also strengthens Warp’s positioning against closed agent IDEs by tying openness, automation, and maintainability into one narrative