6.2.3: chart hover during events (#137) and parallel remote log prefixes (#128)

Merged
M4
8d ago
+633-105

This PR prepares the 6.2.3 point release with two bug fixes reported by @ckrevel.

1. Keep chart metric hover active across outage bands and event pins (Refs #137)

Think of the chart hover rectangle (.chart-hit) as a pane of glass over the plot that tracks your cursor, moves the crosshair, and reads out the metric value. Previously we taped the red outage shading (.outage-band) and event pins (.ev-marker) on top of that glass with their own mouse listeners. Whenever the cursor crossed into an outage window or touched a marker column, those stickers caught the mouse event instead, freezing the crosshair and top-right live readout and hiding the actual voltage/charge/power reading.

  • Make .outage-band and .ev-marker pointer-events: none and wire .chart-hit above them on Power, Battery, and Energy charts so the crosshair, highlight dot, top-right readout, and metric value stay live across the entire plot area (and honor padR = 40 on dual-axis Energy charts so .chart-hit stops at the right-axis margin).
  • Hit-test cursor X against active outage spans and tier-1 event marker columns (5.5px radius, matching the 11px visual guide width), highlight any matched marker via .is-hover, and append the matched event and/or outage details below a .tip-sep divider inside the same floating tooltip.
  • Keep tabindex="0", role="img", aria-label, and bindTip focus/blur handlers intact on .ev-marker and .outage-band for keyboard Tab navigation.

2. Tag per-step remote shutdown logs with the server name (Refs #128)

Picture two chefs calling out "step 1 done!" and "sending final order!" from the kitchen at the same time without saying which table's ticket they're working on. During parallel remote shutdown batches (parallel: true or shared shutdown_order), the opening and closing lines named the server, while every intermediate pre-shutdown step, Sending shutdown command, and [DRY-RUN] line interleaved anonymously.

  • Prefix every per-step remote and host-loopback shutdown line in src/eneru/shutdown/remote.py with [<name>] (falling back to [<host>]), placed after the leading indent + emoji so JSONFormatter's column-0 [Group] split and all existing unit/E2E substring assertions stay intact.
  • Name the unfinished server(s) directly in _shutdown_servers_parallel's phase-timeout warning.

3. Release bump (6.2.3)

  • Bump src/eneru/version.py to 6.2.3 and move [Unreleased] into ## [6.2.3] - 2026-11-13 in docs/changelog.md.

Verification

  • Full unit suite: 4921 passed, 3 skipped, all 49 files under src/eneru/ ≥ 95% line+branch coverage (97.80% total).
  • Node-backed harness in tests/test_dashboard.py exercising real appendOutageBands, appendEventMarker, bindTip, and addChartHover (outside outage, inside outage band, over marker column, over null-valued gap sample, mouseleave, and keyboard focus/blur), plus tools/dashboard-preview.py visual audit in light and dark themes across Power, Battery, and Energy tabs.
  • eneru validate on examples/config-reference.yaml and mkdocs build --strict.
  • Independent pre-push review subagent (research subagent, inherited parent runtime model): 0 P0, 0 P1; 2 P2s (changelog wording precision and exercising real overlay builders in test_dashboard.py) and 1 P3 (.ev-hit comment alignment) addressed prior to push.

Summary by CodeRabbit

  • Bug Fixes
    • Chart tooltips now show nearby outage and event details alongside metric readings, with improved marker highlighting and keyboard focus support.
    • Remote shutdown messages identify the relevant server or host, and timeout warnings list servers that are still running.
  • Compatibility
    • Added support for Python 3.15, including required CI validation.
  • Documentation
    • Updated the release notes and dashboard testing guidance.