P1-2: Emit Log Central events for question policy violations

[Cho-Geer]

Parent Epic

#138 — Sub-Agent Question Propagation Fix

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

Task

Implement structured Log Central event emission for the question policy plugin.

Required Events (from §7 Phase 1)

• SUBAGENT-QUESTION-BLOCKED — when subagent question call is blocked
• SUBAGENT-QUESTION-RECORDED — when question payload is persisted
• PRIMARY-QUESTION-ALLOWED — when Orchestrator primary question is allowed
• QUESTION-POLICY-DETECTION-WARN — when subagent detection is ambiguous

Implementation

• Use writeLog() from log-manager.ts
• Each event must include: sessionID, agent, taskId, question payload (if available), timestamp, detection method

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.

Log Central events emitted:

• PRIMARY-QUESTION-ALLOWED — primary session question allowed
• SUBAGENT-QUESTION-BLOCKED — subagent question blocked (with level:WARN)
• SUBAGENT-QUESTION-RECORDED — question payload persisted to questions.jsonl
• QUESTION-POLICY-DETECTION-WARN — persist failure (non-fatal, level:WARN)