P0-3: Update Super-Admin.md — clarify destructive confirmation scope

[Cho-Geer]

Parent Epic

#138 — Sub-Agent Question Propagation Fix

Phase 0 — Option A: Prompt + HANDOVER Protocol

Task

Update .opencode/agents/Super-Admin.md to clarify that destructive confirmation via question is allowed only in a primary human session; dispatched Super-Admin must escalate to Orchestrator/user.

Rationale from §4.1 Finding 5

Super-Admin.md also requires question for destructive confirmation. These instructions are valid only in user-facing primary contexts, not in dispatched child sessions.

What to Change

• Find all instructions that require question for destructive confirmation
• Add context guard: only use question when running as primary user-facing session
• When dispatched as subagent: escalate destructive decisions to Orchestrator via HANDOVER

Reference

docs/review/framework-refactor/sub-agent-question-propagation-issue.md §4.1 (Finding 5), §6 Option A

[Cho-Geer]

✅ Completed — Implemented by @Super-Admin via ses_115f2ce18ffex1FS1ucrajpeAM.

Added ## ⚠️ Question Tool Scope section in .opencode/agents/Super-Admin.md (between dispatch table and UC7-009 ENFORCED section):

• question tool allowed ONLY in primary user-facing sessions (human invocation)
• When dispatched as subagent: use HANDOVER.md ## Blocked Actions Requiring User Approval + escalate to Orchestrator