fix(ui): clear dice TARGET + result widget after narrator resolves the roll

[slabgorb]

Summary

• After a combat roll resolved, the TARGET banner (TARGET 18 · need 17 on d20) and result badge (Rolled 4 vs 18 Fail) stayed pinned to the screen through the narrator's next turn. When the next action buttons became clickable, players read the stale DC as the target for the next click — medium-priority UI ambiguity surfaced in playtest-pingpong 2026-04-24.
• Fix: clear diceRequest + diceResult inside the NARRATION_END branch in App.tsx. That is the same turn-boundary signal that already re-enables input and clears a resolved confrontation — no new protocol message, no component rewrite. InlineDiceTray / DiceOverlay are prop-driven, so both the banner and the result readout return to a neutral state (and the 3D die idles) until the next DICE_REQUEST triggers another throw.
• Added a wiring test in src/__tests__/dice-overlay-wiring-34-5.test.ts that pins setDiceRequest(null) + setDiceResult(null) inside the NARRATION_END branch, plus a regression guard on the overlay prop surface so the clear actually reaches the UI.

Test plan

• npx vitest run src/__tests__/dice-overlay-wiring-34-5.test.ts — both new tests pass.
• Full npx vitest run: 45 failed / 1112 passed. Baseline on develop was 46 failed / 1109 passed — no new regressions from this change (the ~45 pre-existing failures are in unrelated suites: Three.js Canvas asset loading, legacy confrontation-wiring refactor drift, etc.).
• Manual: enter Wasteland Brawl, pick a beat, let the roll resolve, wait for the narrator's next NARRATION_END — confirm the TARGET banner + "Rolled N vs M — Fail" badge disappear and the d20 sits idle until the next beat is clicked.

🤖 Generated with Claude Code