"oh-my-opencode uses which TWO subagent patterns, and where?"	Prometheus→Atlas = agents-as-tools (sync, structured summary returns). Atlas→Junior = worktree (parallel, git-mergeable). The MIX is the design decision — neither pure pattern would be correct.	harness-engineering::dd06::recall
"Name the 4 hierarchy levels and their roles."	Sisyphus (outer, entry) · Prometheus (planner, strong model) · Atlas (orchestrator, decomposes) · Junior × N (workers, cheap model, parallel git worktrees).	harness-engineering::dd06::recall
"Why does Prometheus use a strong model and Juniors use cheap models?"	Planning needs REASONING DEPTH (strong model). Execution is more MECHANICAL (cheap model suffices). This is cost-aware routing (Module 1.4, Fleet F03) at single-harness scale.	harness-engineering::dd06::analysis
"State the two-mode design (lazy vs precise)."	Lazy: one plan, one execution, loose verification — for simple tasks. Precise (ultrawork): plan→execute→verify→re-plan, tight verification — for complex tasks. Mode chosen by complexity assessment at intake.	harness-engineering::dd06::recall
"Why does the subagent hierarchy MULTIPLY the attack surface?"	Each Junior is an independent agent with its own context. A compromised Junior can use its scoped permissions to attack Atlas. Per-agent capability filtering (Module 2.4) is essential — a Junior should NEVER have Prometheus's permissions.	harness-engineering::dd06::analysis
"oh-my-opencode scores 38/55 — highest on which module?"	Module 10 (Subagent Orchestration): 5/5. It's the reference for subagent hierarchies. No other harness in the roster combines agents-as-tools + worktree in a studied way.	harness-engineering::dd06::analysis
"Name 3 things to fix if you forked oh-my-opencode."	(1) Add per-subagent tracing (Module 10) — debugging the hierarchy is hard. (2) Enforce per-Junior capability scoping (Module 2.4) — currently flat. (3) Bound Junior summaries to 1-2k (Module 1.3) — prevent Atlas context pollution.	harness-engineering::dd06::application
"oh-my-opencode does NOT replace OpenCode. What does it do instead?"	LAYERS on top — adds the planning/orchestration hierarchy (Sisyphus/Prometheus/Atlas/Junior). The loop is inherited from OpenCode. The contribution is the subagent taxonomy, not the loop.	harness-engineering::dd06::analysis