Add opt-in Android platform analysis

[mixxer]

Android platform source often refers to generated AIDL/HIDL bindings or JNI registration tables that are not directly navigable from the indexed language graph. This adds evidence queries for those boundaries while keeping the default MCP surface limited to codegraph_explore.

Scope

• Add CLI commands and opt-in MCP tools for AIDL implementations, JNI bindings, HAL interfaces, system services, permission and broadcast literals, Messenger, ContentProvider, and local sockets.
• Distinguish corroborated findings from convention-derived candidates and missing evidence. These are evidence reports, not automatic end-to-end runtime IPC traces. AIDL/HIDL declarations are read on demand rather than added as indexed language nodes.
• Improve qualified inheritance resolution and portable extraction of Java anonymous classes and Kotlin object expressions, with regression coverage for false matches and ownership boundaries.
• Document supported behavior, limitations, and public AOSP reference inputs; add contributor guidance and Linux CI for Node 22/24 plus native kernel parity.

For example, codegraph aidl-impl IPowerManager --path /path/to/android-source gathers implementation and registration candidates; codegraph jni-bridge Process --path /path/to/android-source correlates native declarations with JNI implementation and registration evidence. MCP equivalents require explicit CODEGRAPH_MCP_TOOLS configuration.

Validation

The latest complete fork CI run tested bcae921; the subsequent preparation changes only simplify the changelog and update its documentation assertion.

Check	Result
Linux portable engine, Node 22 and 24	Each: 4,581 passed, 12 failed, 192 skipped; all nine Android analysis suites passed
Linux native kernel and Android checks	1,171 passed, 7 failed
Local JNI suite after changelog preparation, macOS / Node 24 / portable engine	24 passed
git diff --check	Passed

Why this is a draft

The full suite is not green. The portable failures affect caller truncation, Next.js/server-action flows, object-literal callers, React Native pairing, and Steps views. Native failures include the Java field-initializer anonymous Stub lookup and Dart/Kotlin extraction parity. These have not been established as upstream-only failures and must be investigated before this is ready to merge.

The real-repository small/medium/large agent A/B validation required by the project guide is also outstanding. Public reference repositories and focused fixtures do not establish complete Android coverage or parity across extraction backends.

Suggested review order: the evidence contracts in docs/design/android-platform-analysis.md, the src/aosp/ analyzers and tests, the core extraction/resolution changes, then CLI/MCP wiring and CI/documentation.