Show errors and warnings on the display (_ERROR, _WARN)

action_raise_error aborts while the macro renders, so an M117 in the same
macro never ran and errors such as the RESUME lane check only reached the
console. messages.cfg adds _ERROR (M117, then raise in a separate macro)
and _WARN (RESPOND TYPE=error + M117); all errors and warnings use them.
PAUSE shows AFC's error as the pause reason; RESUME, CANCEL_PRINT and
PRINT_WARMUP clear the display.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

CLAUDE.md

@@ -64,7 +64,12 @@ detection, `filament_error_sensitivity`), iHeater chamber heater.
   (remembered in the saved variable `nozzle_retract`); `PRINT_START` undoes
   it over the bucket with `_NOZZLE_UNRETRACT`.
 - Inside `gcode:` use `;` for comments on G-code lines; `#` lines are
-  stripped by the config parser.
+  stripped by the config parser. Never put a comment on an `M117` line:
+  M117 shows the raw rest of the line, comment included.
+- Errors and warnings go through `_ERROR` / `_WARN` (`macros/messages.cfg`),
+  not `action_raise_error` / `RESPOND TYPE=error`, so they also show on the
+  display. `action_raise_error` aborts while rendering, so an `M117` in the
+  same macro would never run. No double quotes in `MSG`/`DISPLAY`.
 - After a refactor run `python tools/effective_config.py HEAD` and check that
   only the intended sections changed.
 - Render-test macros with Jinja2 using Klipper's delimiters