docs(workspace): document omo workspace paths

docs/guide/orchestration.md

@@ -55,7 +55,7 @@ flowchart TB
     User -->|"Describe work"| Prometheus
     Prometheus -->|"Consult"| Metis
     Prometheus -->|"Interview"| User
-    Prometheus -->|"Generate plan"| Plan[".sisyphus/plans/*.md"]
+    Prometheus -->|"Generate plan"| Plan[".omo/plans/*.md"]
     Plan -->|"High accuracy?"| Momus
     Momus -->|"OKAY / REJECT"| Prometheus
 
@@ -105,7 +105,7 @@ Mode distinction:
 
 ### Prometheus: Your Strategic Consultant
 
-Prometheus is not just a planner, it's an intelligent interviewer that helps you think through what you actually need. It is **READ-ONLY** - can only create or modify markdown files within `.sisyphus/` directory.
+Prometheus is not just a planner, it's an intelligent interviewer that helps you think through what you actually need. It is **READ-ONLY** - can only create or modify markdown files within `.omo/` directory.
 
 **The Interview Process:**
 
@@ -244,7 +244,7 @@ This prevents repeating mistakes and ensures consistent patterns.
 **Notepad System:**
 
 ```
-.sisyphus/notepads/{plan-name}/
+.omo/notepads/{plan-name}/
 ├── learnings.md      # Patterns, conventions, successful approaches
 ├── decisions.md      # Architectural choices and rationales
 ├── issues.md         # Problems, blockers, gotchas encountered
@@ -379,7 +379,7 @@ For `subagent_type` team members, current eligibility is:
 Why `oracle`/`prometheus` are rejected in team members:
 
 - Oracle is read-only (cannot write/edit/patch/delegate)
-- Prometheus is constrained to `.sisyphus/*.md` writes by the `prometheus-md-only` hook
+- Prometheus is constrained to `.omo/*.md` writes by the `prometheus-md-only` hook
 
 ---
 
@@ -394,7 +394,7 @@ Why `oracle`/`prometheus` are rejected in team members:
 2. Select "Prometheus" from the agent list
 3. Describe your work: "I want to refactor the auth system"
 4. Answer interview questions
-5. Prometheus creates plan in .sisyphus/plans/{name}.md
+5. Prometheus creates plan in .omo/plans/{name}.md
 ```
 
 **Method 2: Use @plan Command (in Sisyphus)**
@@ -404,7 +404,7 @@ Why `oracle`/`prometheus` are rejected in team members:
 2. Type: @plan "I want to refactor the auth system"
 3. The @plan command automatically switches to Prometheus
 4. Answer interview questions
-5. Prometheus creates plan in .sisyphus/plans/{name}.md
+5. Prometheus creates plan in .omo/plans/{name}.md
 ```
 
 **Which Should You Use?**
@@ -427,7 +427,7 @@ User: /start-work
     ↓
 [start-work hook activates]
     ↓
-Check: Does .sisyphus/boulder.json exist?
+Check: Does .omo/boulder.json exist?
     ↓
     ├─ YES (existing work) → RESUME MODE
     │   - Read the existing boulder state
@@ -436,7 +436,7 @@ Check: Does .sisyphus/boulder.json exist?
     │   - Atlas continues where you left off
     │
     └─ NO (fresh start) → INIT MODE
-        - Find the most recent plan in .sisyphus/plans/
+        - Find the most recent plan in .omo/plans/
         - Create new boulder.json tracking this plan
         - Switch session agent to Atlas
         - Begin execution from task 1
@@ -563,8 +563,8 @@ Prometheus enters interview mode by default. It will ask you questions about you
 
 Either:
 
-- No plans exist in `.sisyphus/plans/` → Create one with Prometheus first
-- Plans exist but boulder.json points elsewhere → Delete `.sisyphus/boulder.json` and retry
+- No plans exist in `.omo/plans/` → Create one with Prometheus first
+- Plans exist but boulder.json points elsewhere → Delete `.omo/boulder.json` and retry
 
 ### "I'm in Atlas but I want to switch back to normal mode"
 

docs/guide/team-mode.md

@@ -146,4 +146,4 @@ When enabled, each member gets a dedicated tmux pane attached to that member's s
 
 ## Reference
 
-Full design: `.sisyphus/plans/team-mode.md`.
+Full design: `.omo/plans/team-mode.md`.