TUI Hover Polish

Modal mouse dispatch is still centralized through Gantry's modal integration and the frontmost overlay router. Prompt, confirm, read-only, pager, process, git activity, stats, info, help, and stage-log overlays all route through the same frontmost decision before application actions are handled. Underlying pane hover state is cleared while an overlay owns the pointer, so modal interaction remains visually and behaviorally exclusive.

The current theme module still builds modal colors and modal button styles from Gantry's palette. Modal configuration is derived from menu colors, and button states have separate normal, hovered, and focused styles. Rendered modal code now consumes those styles through the shared modal layout path instead of leaving Gantry dialogs on unrelated widget defaults.

GantryHoverTarget is still the application-side hover model for Gantry-owned controls. The mouse router maps divider regions, run controls, the sidebar gutter, the chat input row, and inline blocker footprints into that enum, then clears stale targets when menus or overlays take ownership. Dynamic blocker targets still carry prompt identity, action index, and action token so rendering and clicks can revalidate against live state.

The chat renderer still checks GantryHoverTarget before painting the assistant title, size controls, drag band, and composer row. Hovered chat title text and compact controls use the bright accent, the drag band lifts its surface, and the unfocused composer row gets a distinct hover style. Focused composer rendering remains separate, so a mouse pass over the row does not masquerade as keyboard focus.

Inline blocker rows still publish button footprints from the draw pass and render button spans with hover-aware styles. The current style resolver distinguishes plain hover, action-row keyboard focus, composer-return focus, and combined hover cases using background, foreground, bold, and underline changes. Click handling still rechecks the visible footprint against the pending blocker before answering.

The sidebar and feed divider is still painted as an actual surface when the sidebar is visible. The mouse router recognizes the recorded divider column as a SidebarFeedDivider target, while drag start still depends on the same rendered gutter. Later code has grown around the split behavior, but the resting and hovered divider affordance remains tied to the live layout column.

The vendored menu crate still exposes the hover foreground contract this sprint introduced. MenuColors has separate foreground fields for highlighted bar titles, selected or hovered dropdown items, and menu-derived modal close-button hover, plus a trait that names that public theme surface. Rendered widget tests still assert those configured foregrounds reach real menu and modal cells, including the rule that nonselectable rows do not become hover-highlighted.

The vendored mcurses-menu snapshot now contains the reconciled modal and menu behavior described in its vendoring note. The current tree keeps generic modal sizing, chrome, button rows, backdrop dimming, scrollable text, form focus mechanics, event fallthrough, examples, tests, and the vendored lockfile together. The only documented local drift is the nonpublishable package metadata, so Gantry can consume the crate without pretending host behavior lives upstream.

Gantry's theme module now fills menu hover foregrounds, dropdown selected foregrounds, and modal close-button hover foreground from the bright accent color. Menu configuration and modal configuration are built through helper functions, so callers inherit the same palette ramp instead of using widget defaults. The exact theme test still guards that modal colors and styles are drawn from Gantry's palette rather than vendored defaults.