[Epic] Sub-Agent Question Propagation Fix (A→B→C→D)

[Cho-Geer]

Epic: Sub-Agent Question Propagation Fix

Source: docs/review/framework-refactor/sub-agent-question-propagation-issue.md
Severity: MEDIUM
Recommended sequence: A (Phase 0) → B (Phase 1) → C (Phase 2), with D tracked as upstream enhancement.

Problem

Subagents are configured with question: allow, but the question tool does not propagate from child Task() sessions to the parent/user session. This creates silent stalls and deadlocks in sub-agent workflows.

Phases

Phase 0 — Documentation and Prompt Safety (Option A)

• P0-1: Update subagent-preamble.md with Subagent Interaction Protocol #139 — Update subagent-preamble.md with Subagent Interaction Protocol
• P0-2: Update Knowledge-Curator.md — remove unconditional question tool usage #140 — Update Knowledge-Curator.md — remove unconditional question tool usage
• P0-3: Update Super-Admin.md — clarify destructive confirmation scope #141 — Update Super-Admin.md — clarify destructive confirmation scope
• P0-4: Update deliverables-templates.ts — add Questions for User / Assumptions #142 — Update deliverables-templates.ts — add Questions for User / Assumptions sections

Phase 1 — Runtime Guard and Logging (Option B)

• P1-1: Create question-policy-before.ts plugin #143 — Create question-policy-before.ts plugin
• P1-2: Emit Log Central events for question policy violations #144 — Emit Log Central events for question policy violations
• P1-3: Persist question payloads to questions.jsonl #145 — Persist question payloads to questions.jsonl

Phase 2 — Permission Cleanup (Option C)

• P2-1: Update opencode.json — deny question for pure subagents #146 — Update opencode.json — deny question for pure subagents
• P2-2: Update agent frontmatter — remove question from subagent configs #147 — Update agent frontmatter — remove question from subagent configs

Phase 3 — Harness and Regression Tests

• P3-1: Create test harness for question policy plugin #148 — Create test harness for question policy plugin
• P3-2: Verify HANDOVER protocol contract acceptance #149 — Verify HANDOVER protocol contract

Phase 4 — Upstream Enhancement (Option D, Tracked)

• D-1: Track upstream OpenCode child-to-parent question propagation #150 — Track upstream OpenCode child-to-parent question propagation support

Acceptance Criteria (from §10)

1. Generated dispatch prompts explicitly tell subagents not to call built-in question.
2. Pure subagent configs no longer present question as expected normal tool, or a runtime guard blocks it.
3. Knowledge-Curator and dispatched Super-Admin instructions no longer require direct question use in child sessions.
4. Subagent question attempts are visible in Log Central.
5. HANDOVER artifacts can carry deferred user questions.
6. Orchestrator remains the user-facing question relay.
7. Ordinary subagent sessions can still dispatch Knowledge-Curator for UC7KS.
8. Any future upstream propagation support replaces local guard only after E2E harness verification.