//! Compile-fail coverage for the `Component` derive's attribute diagnostics.
//!
//! These cases fail during attribute parsing — before template resolution — so
//! they need no `.dmk` files and produce machine-independent error messages,
//! which keeps the `.stderr` snapshots portable. Template/parse error paths are
//! covered by unit tests in `damask-macros` and `damask-template`, because file
//! resolution and absolute paths do not survive trybuild's sandbox cleanly.