# ``ParcelUI`` The menu bar, settings, onboarding, and window overlays. The app assembles UI models with the live engine and configuration store. Views present that state and send commands back; they do not own window placement or call AX directly. Preview and test adapters keep views usable without a running window manager. ## Settings and onboarding Settings edits go through validated TOML document updates so comments survive. Invalid edits remain visible as diagnostics rather than replacing the active configuration. Onboarding explains the Accessibility grant and can guide the reader through actions using their configured shortcuts. ## Window feedback Focus borders, drop hints, stack chips, and the hover bar are lightweight overlay panels. Keep them out of managed-window discovery. Interactive controls need keyboard access and VoiceOver labels; decorative panels must not steal focus. Route every animation through ParcelAnimation. Disabling motion or enabling system Reduce Motion removes movement, not the information a control conveys. Respect Reduce Transparency and Increase Contrast too. Experimental dimming requires verified native support and a durable recovery marker before use. ``WindowControlsController`` owns chips and hover hints independently of ``WindowLearningController``. It updates from engine snapshots, mouse/keybinding configuration, and the persisted `hoverBar.v1` preference. The tour only observes input and verified outcomes. Chip close requests go back to the app; UI never calls AX. Use String Catalogs for user-facing text. Test models with Swift Testing and exercise real focus, overlays, and input through the FixtureApp e2e harness. See for the private-beta checklist and remaining live checks.