docs: make desktop and mobile platform priority explicit

Author: kdy1

docs/design.md

@@ -1,6 +1,6 @@
 # DexDex Design
 
-DexDex is a desktop-first orchestration UI for CLI-based coding agents.
+DexDex is a cross-platform orchestration UI for CLI-based coding agents.
 DexDex uses a Connect RPC-first architecture with Tauri clients and Rust servers.
 This document is the primary architecture reference.
 
@@ -26,7 +26,7 @@ Primary outcomes:
 4. Use UnitTask-centric workflows with nested SubTask and AgentSession history.
 5. Make PR management and PR review assist first-class workflows.
 6. Provide real-time event streaming for UI updates and automation.
-7. Support iOS and Android as first-wave platforms with phased capability rollout.
+7. Treat desktop, iOS, and Android as first-class platforms with phased capability rollout.
 
 ## Non-Goals
 
@@ -40,15 +40,16 @@ Primary outcomes:
 
 ### Desktop
 
-Desktop is the primary platform for full authoring and remediation workflows.
+Desktop and mobile are both product-priority platforms.
+Desktop is optimized for dense authoring workflows and keyboard-heavy interaction.
 
 ### Mobile
 
 Mobile uses the same API and data model as desktop.
-Capability rollout is phased:
+Capability rollout is phased by interaction constraints, not platform priority:
 
-1. baseline support: remote task monitoring, log viewing, approval and stop actions
-2. expanded support: broader remediation and review actions as UX matures
+1. baseline support: task monitoring, log viewing, approval and stop actions, and core remediation triggers
+2. expanded support: broader remediation, review interaction, and authoring parity as UX matures
 
 Mobile is not a separate business-logic path.
 

docs/tauri-app.md

@@ -17,11 +17,11 @@ The app does not use direct client-to-worker business APIs.
 
 ## Capability Rollout
 
-Desktop provides the full authoring workflow.
-Mobile uses phased rollout on the same contracts:
+Desktop and mobile are both first-class product targets on the same contracts.
+Capability rollout is phased by interaction constraints:
 
-1. baseline: task monitoring, log viewing, plan decisions, and stop actions
-2. expansion: broader remediation and review interaction flows
+1. baseline: task monitoring, log viewing, plan decisions, stop actions, and key remediation actions
+2. expansion: broader remediation, review interaction, and deeper authoring parity
 
 ## Client Architecture
 

docs/workspace-connectivity.md

@@ -48,6 +48,7 @@ A mobile app can connect to local endpoints (same network or tunneled) and remot
 
 Capability rollout is phased:
 
-1. baseline mobile flow focuses on remote monitoring, logs, plan actions, and stop actions
+1. baseline mobile flow supports monitoring, logs, plan actions, stop actions, and core remediation triggers
 2. expanded mobile flow adds broader remediation and review interactions
-3. connectivity contract stays identical across desktop and mobile
+3. rollout phase reflects interaction constraints, not lower product priority
+4. connectivity contract stays identical across desktop and mobile