Android DJ Tools v0.1.3

Release date: 2026-09-18

v0.1.3 is the current first-review preview. It keeps the preparation, offline/sync, intelligence, parity, and screenshot work from the earlier previews while repairing the production launcher and packaging the real MediaStore/Media3 playback path as the primary review APK.

What changed

  • The normal debug launcher now remains the real Android DJ Tools activity; the debug dogfood harness is still compiled into debug builds but is not the launcher.
  • The release variant uses the real MediaStore library and Media3/ExoPlayer playback path rather than fixture playback.
  • The release APK is non-debuggable and currently uses Android's development signing configuration so it can be sideloaded for review.
  • CI builds and inspects both debug and release variants, rejects a release APK containing the debug harness, checks the release launcher, verifies the APK signature, and uploads the release APK as the primary artifact.

First-review gate

A host-qualified review build requires:

  1. parity-ledger integrity and provider-boundary validation;
  2. sync/fake-backend contract tests;
  3. Android JVM unit tests;
  4. Android instrumentation-source compilation;
  5. Android lint;
  6. debug and release APK assembly;
  7. APK inspection proving the real launcher is retained in both variants and the debug harness remains debug-only;
  8. a non-debuggable release APK.

The local review artifact is app/build/outputs/apk/release/app-release.apk. The debug diagnostic artifact remains app/build/outputs/apk/debug/app-debug.apk.

Evidence boundary

Host qualification does not claim real-device behavior. API-35 emulator instrumentation, screenshot rendering, TalkBack/font-scale behavior, Bluetooth/MediaSession behavior, sustained performance measurements, and Android-to-real-Sample-Lib round trips remain separate evidence tiers and must only be marked passing after those environments actually execute them.

The canonical feature/parity ledger remains under docs/parity/. A structurally valid ledger can still contain partial or blocked stories; only the explicit full-conformance gate may claim complete parity.