[UI/UX Design] Design empty and loading states for ValidationHistory page

[1nonlypiece]

[UI/UX Design] Design empty and loading states for ValidationHistory page

Description

src/pages/ValidationHistory.tsx renders the verifier store's validationHistory, but has no treatment for an empty history or loading skeleton. This issue designs an empty state encouraging the verifier to review the pending queue and a skeleton for async loading.

Requirements and context

• Must be secure, tested, and documented
• Should be efficient and easy to review
• Add an empty state linking to /verifier/queue
• Reuse a shared Skeleton component for loading rows
• Show approved/rejected status with semantic tokens and the stored notes
• Keep layout consistent with PendingValidations rows

Suggested execution

• Fork the repo and create a branch
• git checkout -b feature/validation-history-states
• Implement changes
  • Update src/pages/ValidationHistory.tsx
  • Write src/pages/__tests__/ValidationHistory.test.tsx
  • Document the state matrix in design-system/documentation
  • Verify aria-busy and empty-state heading hierarchy
• Test and commit
  • Run tests, cover edge cases
  • Include test output and notes

Example commit message

feat: empty and loading states for ValidationHistory

Guidelines

• Minimum 95 percent test coverage
• Clear documentation
• Timeframe: 96 hours