v1.5.0

What's Changed

Added

• Prefer a sibling <id>.yaml component definition over the twig annotation (#91).
  Transitional support for tailwind-base's incoming per-component canonical definition file
  (<id>.yaml, sibling of <id>.twig). ComponentParser now checks for it first via a new
  readComponentMetadata() helper shared by parse() and parseAll(); a malformed or missing
  <id>.yaml falls back to the existing {# … #} twig-comment parsing, unchanged. Purely
  opt-in and fallback-safe: a project with no <id>.yaml files renders exactly as before.

Changed

• HealthWarningBadge opens a native <dialog> (#89). Clicking the parser-warnings badge
  now lists every warning (file + message) in a modal — the previous console.warn-only click
  read as a dead button. Esc/backdrop/close-button dismissal comes from the native element;
  console.warn stays as a debugging side channel. New health.dialog_title/dialog_close
  i18n keys (cs/en); health.warnings_title no longer mentions the console.

Fixed

• Sidebar respects authored weight: order (#92). buildTree (prefix grouping) re-sorted
  every section alphabetically client-side, silently discarding the server's weight-sorted
  order — a weight: 1 homepage rendered after "404". Nodes now keep the incoming API order
  (weight, cs-collation name tiebreak); groups sit where their first member appears and group
  children keep authored order too. Default-weight sections look unchanged — the server
  tiebreak already produced the alphabetical order.

Pull Requests

• #90 — HealthWarningBadge: native dialog listing parser warnings (#89)
• #91 — feat: prefer sibling .yaml component definition over the twig annotation
• #92 — Sidebar respects authored weight: order — drop client re-sort in buildTree
• #93 — Release v1.5.0 — .yaml priority (#91), dialog (#89), sidebar order (#92)

Full Changelog: v1.4.0...v1.5.0