Android 16KB Source Doctor

An Android build can contain native .so libraries from project assets, embedded Unity packages, cached packages, or SDK archives. When a release check reports a 16 KB page‑size problem, identifying the failing file is only the first step; you still need to determine where it entered the Unity project and what evidence to send to your team or SDK vendor. Android 16KB Source Doctor brings that local evidence into a single read‑only Unity Editor workflow. It lets you inspect native‑library evidence by scanning .so files, and by inspecting entries inside AAR, ZIP, APK, and AAB containers, reviewing ABI, file size, SHA‑256, and ELF64 little‑endian PT_LOAD.p_align evidence, and keeping same‑name libraries distinct by source path and content hash. It helps you trace local origins without guessing, identifying Unity project and embedded‑package locations, reading package.json from PackageCache, retaining archive context and EDM4U dependency clues, and separating known, partial, ambiguous, and unknown origins. You can export JSON, CSV, or Markdown reports, save a scan before an SDK update and compare it with a later scan, and review added, removed, hash‑changed, or status‑changed libraries. The optional Quick Start generates synthetic ELF header examples in a temporary directory for safe review. The tool runs in the Editor with no Player code, no runtime dependency, no cloud database, no account requirement, no telemetry, no network service, and scanning does not modify input libraries; reports are written only when you choose an output location. It was tested on Windows with Unity 2022.3.62f1c1, and all 32 EditMode tests passed. The product reports local evidence only and does not repair, rebuild, replace, upgrade, download, upload, or submit binaries, and it never guarantees Google Play approval or physical‑device behavior.