max / makenotwork

Choose badge classes in Rust instead of interpolating status columns Thirteen templates wrote a status column straight into a class attribute (`class="badge {{ tx.status|lowercase }}"`), so the stylesheet had to mirror whatever the schema spelled. A column rename unstyled the badge silently, and a status nobody had written a rule for rendered plain: every subscription status other than `active`, and every scheduled item, was already doing that. `BadgeStatus` in src/types/badge.rs holds the charter's closed set. Each status enum maps into it with an exhaustive match, so a new variant is a compile error rather than an unstyled badge, and every status-bearing view model carries the resulting class. The raw-status CSS block phase 5 left behind goes with it. The set gains a neutral case for a terminal state nobody has to act on (Refunded, Canceled). It renders as the plain `.badge`, which already reads as neutral, so the vocabulary stays three colours wide: red would ask for an action that does not exist. Two smaller instances of the same leak: `.import-page .status-badge` was a page-scoped near-copy of `.badge` mirroring four ImportJobStatus spellings, and is now the badge it always was; `badge-role-{{ m.role }}` interpolated a role into a class no rule has ever matched, and is gone. AiTier keeps its own names, a disclosure level not being lifecycle, but sources them from `css_class()`.