What problem does it solve? SAPUI5 and OpenUI5 codebases accumulate deprecated API usage, global variable references, CSP violations, and outdated manifest properties that block UI5 2.x migration. Manually auditing JavaScript, TypeScript, XML views, and manifest.json files across a project is slow and error-prone. ## Core Features & Use Cases - Static Code Analysis: Runs @ui5/linter to detect 19 rule categories including no-deprecated-api, no-globals, csp-unsafe-inline-script, and manifest modernization issues. - Autofix Guidance: Applies automatic fixes for global references, supported deprecated APIs, event handler notation, and manifest properties, with dry-run preview via UI5LINT_FIX_DRY_RUN. - CI/CD Integration: Provides templates for GitHub Actions, GitLab CI, Jenkins, Husky pre-commit hooks, and lint-staged workflows with JSON, Markdown, and HTML report formats. - Use Case: Before migrating an app to UI5 2.x, run ui5lint --details to inventory all deprecated Core and jQuery.sap calls, apply autofixes, then manually refactor the unsupported sync-to-async APIs. ## Quick Start Ask the assistant to set up the UI5 Linter in your project and run an initial lint check with detailed output.