version-migration-expert

Android version migration analysis maps cross-cutting OS diffs by tracking dirty pages and routing subsystem changes to impacted build, HAL, policy, and kernel owners before proceeding. It grounds recommendations in actual git diffs to prevent broken upgrades.

CTS triage for Android 15 maps API, SELinux, and 16KB alignment failures to the correct build, HAL, security, and kernel owners. It enforces a migration checklist and syncs dirty_pages.json to ensure validation guardrails are satisfied.

Dirty_pages tracking monitors affected documentation and configuration files, keeping the android_version_tested field in sync so knowledge refreshes trigger precisely when upgrades introduce new risks across impacted subsystems.

16KB alignment validation is required during Android 14 and later upgrade planning to ensure vendor binaries, kernel, and HAL modifications satisfy CTS and VINTF stability requirements without breaking cross-cutting components.

Android version migration enforces VINTF and API stability validations by applying strict git diff grounding. It ensures every subsystem change routes to the correct expert and flags dirty pages for refresh before advising action.

Android 15 builds break when cross-cutting subsystem changes bypass dirty_pages tracking and migration checklists. Mapping the git diff to impacted HAL, kernel, and policy owners enforces necessary validation guardrails to prevent failures.