kami
e95d2633f8
Live QA showed two problems with paused-approval narration: - The narrator was told to "name the stage, outcome, and reason" but the pause trigger only carried "APPROVAL_PENDING" with no detail — on a first-stage pause there's no L2 history either, so it had nothing to ground on. NarrationSubscriber now captures the latest ApprovalRequestedEvent per session (tool name, tier, preview) and folds it into the pause instruction (preview truncated to 800 chars). - Narration reused the 512-token chat generation config; a reasoning model spent the whole budget "thinking" and returned empty content (finishReason=length). Add a separate narrationGenerationConfig (maxTokens=1024) so thinking can complete and still leave room for the one or two sentences. Adds a subscriber test asserting the pause narration names the tool and includes the preview.