# Risk Register

- **API/prop stability**: Consumers depend on current prop names and `$`-prefixed styling flags; breaking changes will ripple across multiple apps.
- **Browser globals**: Helpers and components access `window`, `document`, and storage directly—unsafe for SSR/Node; changes should preserve browser-only assumptions or add guards.
- **CSS variable reliance**: Styling expects host-defined CSS vars; altering names/defaults can break theming.
- **Absence of tests**: No automated coverage; regressions in interactive components (Select, Input, Popup, Table, Upload) are likely if behavior changes.
- **State flags**: `reset`/`isForceUpdate` patterns used across components; incorrect handling could desync UI state.
- **Dependencies**: Third-party components (react-select, react-datepicker, moment-range) influence bundle size and behavior; updates may introduce breaking changes.
- **Accessibility**: Custom controls may not meet accessibility expectations (keyboard focus management limited); modifying markup requires care.
