c135. Component Cleanup

Stage 1, split from c130's initial prompt on 2026-11-09. The passages below are Mark's words from ../c130.native-app/initial-prompt.md, unchanged. Program plan: ../c130.native-app/plan.md. This cycle depends on no gate.

From c130's initial prompt

• We will be using q-nuxt-layer

• Much of the past work has been rapid and organic
  • This gives us a great opportunity to clean up our components and tighten up our documentation
  • Component Cleanup
    • Look for duplicates or near cousins functionally and consider resolution strategies
    • evaluate our current catalog according to foundational principles, is the component:
      • Modular
      • Clean
      • Documented, including code annotation
      • Shaped according to component design principles
      • Have a good documentation page in ./design
        • Examples
          • We should be showing at least samples of the current flavors of implementation found in the dashboard (currently ../qcontro qdash).
          • We should have useful props and ui components for modifying those props in page (see current documnentation)

Pointers

• The catalog: ../../../q-nuxt-layer/components/ (23 groups) and ../../../q-nuxt-layer/CLAUDE.md.
• The docs: app/data/component-registry.ts, app/pages/components/_demos/ (193 demo files), the adminProps controls, the coverage system, /patterns, /layer/consolidation-gaps (c51).
• The principles: brand/component_philosophy.md, brand/design_tokens.md, CLAUDE.md "Conventions" and "Design Methodology" (the 5-question framework).
• Staged components waiting for extraction: ../../../qcontrol/crates/qdash/ui/LAYER-CANDIDATES.md, plus the c99 Opus track's 59 layer fixes (git show archive/qdash-opus-5.5:crates/qdash/apps/claude-code-opus-5.5/LAYER-CANDIDATES.md in qcontrol).

Create a plan, ask any clarifying questions, suggest patterns I may not be considering.