Astryx UI/UX regression reports

Umbrella epic collecting UI/UX defects observed after the Ant Design → Astryx migration (FR-3482).

## Purpose

This epic is a **reporting bucket, not a work plan**. Every child issue is a lightweight, well-scoped observation captured while using the migrated UI. The goal is to accumulate enough concrete, reproducible context that the defects can later be triaged and fixed **in batches**, grouped by shared mechanism (theme token, wrapper component, layout primitive) rather than one-off.

Root-cause analysis is explicitly **out of scope** for the child issues. A report records what was seen, where, and what was expected. Investigation happens at fix time.

## Report categories

Every child issue is exactly one of:

- **Visual** (`astryx-visual`) — spacing, alignment, size, color, typography, border, overflow, dark-mode drift. Must name the **page** (route + menu path) and the region within it.
- **Behavioral** (`astryx-behavior`) — a component does not do what it should: no response, wrong state, broken keyboard/focus, stale value, closes/opens wrongly. Must name the **component** and at least one page where it is reachable.

## Required context in every child issue

1. Location — route + menu path (visual), or component name + host page(s) (behavioral)
1. Observed behaviour/appearance
1. Expected behaviour/appearance
1. Reproduction steps, where the defect is not simply "load the page"

Screenshots, light/dark mode, viewport and browser are recorded when the reporter has them.

## Conventions

- Child issues: type **Bug**, parent this epic, labels `astryx-report`, `frontend`, plus `astryx-visual` or `astryx-behavior`.
- Duplicates are commented on rather than re-filed; issues sharing a surface or a suspected mechanism are linked with **relates to**.
- Reports are filed through the `astryx-bug-report` skill in `lablup/webui-ai` (`.claude/skills/astryx-bug-report/`), which enforces the required context above.

## Related

- FR-3482 — the migration itself
- FR-3486 — an example of a report that outgrew this epic (structural, split out separately)

JIRA Issue: FR-3491

This is an umbrella reporting bucket rather than an implementation task. Start with .claude/skills/astryx-bug-report/ in lablup/webui-ai and review the required context for a child report; done means filing a concrete, reproducible visual or behavioral child issue, not fixing the migration defects.

Written by the indexing model from the issue text.