P1-3: Persist question payloads to questions.jsonl

[Cho-Geer]

Parent Epic

#138 — Sub-Agent Question Propagation Fix

Phase 1 — Option B: Runtime Guard (Sub-task of P1-1)

Task

Add question payload persistence to the question-policy-before.ts plugin.

Implementation

• When a subagent question call is blocked, save the question payload to .task_temp/{taskId}/questions.jsonl
• Each line is a JSON object with: sessionID, agent, taskId, timestamp, output.args.questions shape (from plugin-hook-reference docs)
• This provides durable audit trail for parent/Orchestrator to reconstruct

Data Shape

{
  "event": "SUBAGENT-QUESTION-BLOCKED",
  "timestamp": "ISO8601",
  "sessionID": "cg_ses_xxx",
  "agent": "Coder-BE",
  "taskId": "T-xxx",
  "question_payload": {
    "questions": [
      {
        "id": "q1",
        "question": "Which approach should I use?",
        "options": ["Option A", "Option B"]
      }
    ]
  }
}

Reference

docs/review/framework-refactor/sub-agent-question-propagation-issue.md §7 Phase 1

[Cho-Geer]

✅ Completed — Implemented as part of question-policy-before.ts plugin.

Blocked question payloads are persisted to .task_temp/{taskId}/questions.jsonl as JSONL entries with:

• event type, timestamp, sessionID, callID, agent, taskId
• Full question_payload (questions array with options)
• Directory auto-created with mkdirSync recursive if missing
• Write failures non-fatal (logged as QUESTION-POLICY-DETECTION-WARN)