Always prioritize and precisely ground licensing changes

When reviewing repository changes, address license-related evidence first, even before documentation changes. Identify the exact license transition, licensors and copyright holders, use restrictions, acceptance or enforcement mechanisms, change dates, successor licenses, and consequences of noncompliance. Quote or cite exact patch text and line-level additions or removals where available, verify claims against frozen source evidence, and distinguish repository-level rules from broader vendor licensing claims. Preserve chronology for implementations, reversions, and reinstatements, and explicitly state evidence limitations when patches are incomplete or truncated.