fix(defaults): repair class attributes mangled by a class sorter

[glennmichael123]

Closes #2209.

It's 61 attributes across 23 files, not one view

The issue found blog/category.stx and noted it may already be gone upstream. It is — but the same corruption is sitting in 23 other files that are still shipped.

storage/framework/defaults/resources/ is live (frameworkPath('defaults/resources/…'), path/src/index.ts:416) and buddy new copies the repo wholesale, so all 61 reached every scaffolded app. One of them is in resources/components/InputGroup.stx — this repo's own app code.

Root cause: 9e06583afc

git log -S pins it to 9e06583afc "chore: fix lint errors" (2026-04-14, 542 files). It ran a Tailwind-style class sorter over class="..." that split on whitespace without respecting {{ }} boundaries, so {{, the expression, and }} sorted as if they were class names:

before  class="mx-auto max-w-7xl px-4 sm:px-6 lg:px-8 {{ className }}"
after   class="mx-auto px-4 sm:px-6 lg:px-8 max-w-7xl {{ }} className"

The tell is that the classes really are in sort order. stx then throws on the orphaned operators, aborting the build once the route scanner reaches the file.

Not a live regression. I verified both pickier --fix and buddy format --write leave {{ ternary }}-in-class intact today. This is committed damage.

Repaired mechanically, not by rewriting intent

A sort permutes but preserves the token multiset, so each mangled value matches exactly one pre-commit value under tokens.sort(). 61/61 matched, 0 ambiguous.

That mattered at this volume — hand-reconstructing 61 ternaries invites fresh bugs, and the nested cases are genuinely unreadable:

": : ? ? '' 'bg-blue-100 'bg-gray-100 'ring-2 {{ {{ }} }} <= == currentStep currentStep loop.index loop.index"

recovers to two separate expressions in one attribute:

"flex items-center justify-center w-8 h-8 rounded-full {{ loop.index <= currentStep ? 'bg-blue-100 text-blue-600' : 'bg-gray-100 text-gray-500' }} {{ loop.index == currentStep ? 'ring-2 ring-blue-600 ring-offset-2' : '' }}"

Deliberately untouched

ModelRecordsDashboard.stx has two {{ }} hits that are prose in comments, explaining that a placeholder in a class attribute is not reactively bound. The repair skips it, and the audit grep excludes it.

Verification

• 0 mangled attributes remain outside that comment
• 23 repaired files parse clean under lintStxStrict (0 parse errors)
• pickier clean

Follow-up

The issue's second ask — "audit for other similarly-mangled {{ … }}-in-attribute default views" — is what found these. To stop it recurring, an empty-interpolation-inside-an-attribute check belongs in buddy lint --stx (#2208), scoped to attribute values so the comment case above stays legal. I'll add it there rather than widening this PR.

🤖 Generated with Claude Code