forge-uilisted

# forge-ui: User interface ## Purpose Inspect rendered interfaces for responsive behavior, hierarchy, state clarity, consistency, and visual defects. Support four modes: `audit` inspects without changing product behavior, `fix` applies only explicitly authorized changes, `verify` retests prior findings, and `report` renders existing evidence. If no mode is supplied, use `audit`. ## Trigger conditions Use this module when a request names `forge-ui`, asks about user interface, or discovery finds an applicable boundary. Run it from the repository root after project discovery. ## When it applies - Web, mobile, or desktop interfaces - Component libraries ## When it does not apply - Headless services with no operator or user interface Do not silently skip it. Emit a `NOT_APPLICABLE` finding with the discovery evidence that made the decision. ## Inputs from project discovery - frontend applications - routes - design tokens - running-app URL when available Prefer `.forge/project-profile.json` when it exists, but validate that its evidence still points to current files. Read `../fullstack-forge/references/PROTOCOL.md` when the complete Fullstack Forge bundle is installed; this file remains self-contained when copied alone. ## Inspection procedure 1. Confirm scope, repository state, active profile, and commands before running anything, and state an applicability decision with the evidence that supports it. 2. Start or attach to the running application and enumerate repre