What problem does it solve? Verifying Android system changes on real hardware requires manually syncing source code to a build workspace, running incremental builds, pushing artifacts to a device over adb, running acceptance checks, and recording evidence. This Skill automates that entire code-to-board verification loop for Raspberry Pi 5 AOSP/kernel development, producing auditable pass/fail receipts. ## Core Features & Use Cases - End-to-End Verification Chain: Orchestrates sync, incremental build, adb push with SHA256/SELinux context verification, on-device unit tests, and acceptance checks in one chained script (ws_verify_chain.py) with per-stage timing marks. - Tag-Based Acceptance Testing: Executes declarative acceptance tags (svc:, log:, prop:, file:, cmd:, hostcmd:, boot, logfield, logfresh) from verify-cases.yaml, with three-state pass/fail/ai verdicts and automatic device clock drift correction. - Failure Forensics and Recovery: Collects bounded read-only forensics (logcat crash, dmesg, tombstones, pstore) on failure, and rescues unreachable devices through a serial-to-TCP bridge with brick-state classification (full_brick, half_brick, boot_loop). - Use Case: After modifying the LcView logging daemon in the code/ tree, trigger this Skill to sync changes into the AOSP workspace, rebuild the affected Soong modules, push them to the Raspberry Pi 5, run the lcview-liveness acceptance case, and write a timestamped receipt to data/verify-results. ## Quick Start Run the workspace-verify skill with a batch file or a target commit and case label to sync, build, push, and verify my changes on the device.
