What problem does it solve? When the Rust core emits a blocking-prompt event (ask, approval, or intercom), the Go TUI must render a modal flyout and capture user input until the core unblocks. Missing any of the three integration points (event handler, key dispatch, render overlay) leaves the feature as dead code, and subtle pitfalls like the rawKey-vs-get unmarshalling bug silently break it. ## Core Features & Use Cases - Three-point wiring checklist: Add the event case in handleCoreEvent, intercept keys in handleKey, and apply the overlay at the end of View() so the flyout actually receives input. - Gotcha prevention: Covers the rawKey-vs-get JSON unmarshalling failure, keybind action-name mismatches, hardcoded arrow-key fallbacks, and inline validation errors instead of transcript spam. - Use Case: The core adds a new approval-style event that blocks on a Notify until the user replies. Use this Skill to add the TUI case, key handler, and render overlay, then verify with go build, go vet, and event-path tests. ## Quick Start Wire the new core blocking event into the Go TUI as a modal flyout following the three integration points and add a handleCoreEvent test.
