{
  "stdout": "",
  "stderr": "\n<REPO>/tests/fixtures/antipatterns/nonrendered-text.html\n  [tiny-text] 10px body text\n    → Body text below 12px is hard to read, especially on high-DPI screens. Use at least 14px for body content, 16px is ideal.\n  [undersized-ui-text] 9px functional text \"Rendered Nav Link\" (below 11px floor)\n    → Interactive and content-bearing UI text (links, buttons, nav items, labels, table cells, meta rows, timecodes) below 11px is a legibility failure, not a style choice. WCAG sets no absolute pixel floor, but functional text under 11px is a defensible quality bar: it fails on high-DPI and small viewports and it degrades tap and read targets. The 11px floor holds even inside a footer; only non-interactive legal smallprint gets the softer 10px floor. Being ON the DESIGN.md size ramp does not exempt a value here: adding 8px to the ramp launders the token but not the legibility problem, and that is exactly the escape hatch this rule closes. Exempts sup/sub, visually-hidden (sr-only) text, and code/terminal contexts. Decorative letterspaced micro-labels are still functional and stay in scope.\n\n2 anti-patterns found.\n",
  "exit": 2,
  "signal": null,
  "files": {}
}