What problem does it solve? Android developers integrating Meta smart glasses cannot trust that a Kotlin symbol mentioned in docs, AGENTS.md files, or samples actually exists in the resolved Maven artifact, and 0.9 migrations silently break camera, Display, and DatResult code. This Skill audits the public Meta Wearables Device Access Toolkit Android API surface against exact Gradle/Maven coordinates so implementation decisions rest on verified artifacts rather than prose. ## Core Features & Use Cases - Artifact-pinned API mapping: Verifies the four public artifact lanes (mwdat-core, mwdat-camera, mwdat-display, mwdat-mockdevice) and maps routes from Wearables.initialize through registration, sessions, Flows, and typed DatResult failures. - 0.9 migration auditing: Resolves Session/DeviceSession naming conflicts, camera addStream consolidation, Java-visible DatResult, Display builder changes, and DAM_ENABLED traps against the selected artifact. - Evidence-level separation: Keeps source, compile, mock, connected, physical, signed, release-channel, and production proof distinct so no claim overreaches its evidence. - Use Case: When asked to add camera streaming to an Android glasses app, produce an atlas row with the exact com.meta.wearable artifact version, confirmed Camera.stream signature, compile gate, phone fallback, and the physical-device evidence still required. ## Quick Start Audit the Meta DAT Android API surface for camera and Display support in my app targeting mwdat 0.9 and list confirmed symbols with their evidence levels.
