[gmmcosta15]

Description

• Feature
• Bug Fix
• Code Refactor
• Documentation

After an E-stop and a reboot, the ConnectionPage now shows the reason Klipper gives instead of a generic error.

Changes

• mainWindow: pass the printer.info reply to the ConnectionPage (it was dropped at a TODO)
• ConnectionPage: handle error states with the existing shutdown-reason pipeline
• Add reasons for: MCU still halted (Can not update MCU, Command request), Unable to connect, failed MCU reset, MCU Protocol error
• Strip the Previous MCU '<name>' shutdown: and mcu '<name>': prefixes so the map keys don't depend on the MCU name
• Any other error shows Klipper's first line + "Press 'Firmware Restart' to recover."

Motivation

The MCU stays shut down across a host reboot, so Klipper boots into error. The subscription only exists once Klipper is ready, so printer.info is the only source of the message, and its reply was being dropped. The approach follows KlipperScreen state_error and Fluidd onServerInfo, which prefers the printer.info message.

Tests

• New TestErrorMessages in tests/widgets/test_connection_page.py

Future work

• Single source of Klipper state for the ConnectionPage (4 racing sources -> one (state, message) pair)