docs(factories): document that factories and the Oz web app coexist

src/content/docs/factories/index.mdx

@@ -46,6 +46,8 @@ Warp Factories is designed for engineering teams with repeatable work that exten
 | **{VARS.WARP_CLI}** | Runs the Warp Agent in any terminal and exchanges work with a factory through the Factory MCP. |
 | **{VARS.WARP_AUTOMATION_PLATFORM}** | Provides the cloud runs, environments, runners, integrations, secrets, orchestration, and APIs that a factory assembles into one workflow. |
 
+Warp Factories runs alongside the {VARS.WEB_APP} rather than replacing it. Each has its own home: the <a href={VARS.FACTORY_WEB_APP_URL}>{VARS.FACTORY_WEB_APP}</a> for factories, and the <a href={VARS.WEB_APP_URL}>{VARS.WEB_APP}</a> for everything you run there today. Creating a factory changes nothing about your existing environments, schedules, and Slack and Linear integrations, which keep working.
+
 ## Next steps
 
 * [**Set up a factory**](/factories/quickstart/) - Create a factory and send its first work item.

src/content/docs/factories/integrations/linear.mdx

@@ -50,7 +50,7 @@ Both paths end in the same state: Linear is connected to your factory, and a def
 
 ## Route agent sessions
 
-When someone mentions, assigns, or delegates the Warp app on an issue, Linear starts an agent session. The default automation created when you connected Linear routes new sessions from your selected teams to the factory, so assigning an issue or tagging the factory in a comment is enough to start work. If a session doesn't match any automation, the [Linear integration](/platform/integrations/linear/) handles it with its default behavior.
+When someone mentions, assigns, or delegates the Warp app on an issue, Linear starts an agent session. The default automation created when you connected Linear routes new sessions from your selected teams to the factory, so assigning an issue or tagging the factory in a comment is enough to start work. The factory takes precedence for the teams its automations cover: a matching session routes to the factory rather than to the [Linear integration](/platform/integrations/linear/), which still handles any session that matches no automation.
 
 Agent sessions don't appear as a trigger in the [automation editor](#configure-linear-triggers). To change how sessions route, for example by creator or keyword, edit the `agent_session_created` event in the factory's [version-controlled definition](/factories/factory-as-code/). Replies in an existing session continue that run; they aren't separate triggers.
 

src/content/docs/platform/integrations/linear.mdx

@@ -66,6 +66,14 @@ Because PRs are created as _you_, this makes code review, auditing, and team col
 
 ---
 
+### Factories and this integration
+
+If your team also runs a [software factory](/factories/), both keep working. This integration continues to handle the Linear teams that no factory covers, so an existing setup needs no changes.
+
+Where the two overlap, the factory takes precedence: when a factory automation matches an agent session, that session routes to the factory instead of starting a run here. A session that matches no factory automation falls back to the behavior described above. For how that routing is configured, see [Connect Linear to your factory](/factories/integrations/linear/).
+
+---
+
 ### Requirements
 
 * **Team membership** - The Linear integration requires you to be part of a [Warp team](/knowledge-and-collaboration/teams/). Teams can be created on any plan, including Free.

src/content/docs/platform/integrations/slack.mdx

@@ -96,6 +96,12 @@ Because PRs are created as you, the workflow slots seamlessly into your team’s
 
 ---
 
+### Factories and this integration
+
+If your team also runs a [software factory](/factories/), both keep working. A factory connected to Slack installs its own app carrying that factory's name, so the two never compete for the same mention: **@Warp** starts a cloud agent run through this integration, and mentioning a factory's app sends the request to that factory. See [Connect Slack to your factory](/factories/integrations/slack/).
+
+---
+
 ### Configuration
 
 #### 1. Create an environment