Files
android-fs5/NEXT_STEPS.md
T
Jane Alesi ad6cbf5fa4 docs: end-of-day — tasks complete, learnings, next steps
- Mark all 33 tasks complete in specs/001 tasks.md (85/85 tests passing)
- Add NEXT_STEPS.md: spec 002 completion, shellcheck, README ui docs
- Add docs/learnings/2026-03-02: BATS fixtures, UIAutomator XML parsing,
  KDE Connect graceful degradation, scrcpy headless, JSON output pattern
2026-03-02 18:33:04 +01:00

1.6 KiB
Raw Blame History

Next Session Tasks

Last updated: 2026-03-02 Project: android-fs5 Status: Both specs 001 + 002 complete. 85/85 tests passing.


Priority 1 — Spec 002 Completion

  • Create specs/002-remote-control/plan.md — architecture decisions for remote control layer
  • Create specs/002-remote-control/tasks.md — formal task breakdown (T025T033 retroactively)
  • Update specs/002-remote-control/spec.md Status from DraftComplete

Priority 2 — Quality & Hardening

  • Run shellcheck fs5 lib/*.sh and fix any warnings
  • Add lib/input.sh shellcheck pass (currently used by remote control commands)
  • Consider adding --dry-run flag to push/pull for safer automation
  • Add ui tap live device integration (currently exits 1 for nonexistent elements only)

Priority 3 — Documentation

  • Update README.md with ui subcommand documentation (added in latest commit)
  • Add usage examples for ocr, sms otp, ui find to README
  • Consider a docs/ directory with architecture diagram (Mermaid)

Priority 4 — Future Features

  • fs5 record — screen recording via scrcpy (--record output.mp4)
  • fs5 sms send — send SMS via KDE Connect CLI
  • fs5 notify — read/dismiss Android notifications via KDE Connect
  • TOTP extraction from authenticator app via OCR + ui find

Notes

  • Device serial: RD51QE202392 (Samsung FS5, configured in .env)
  • KDE Connect must be paired for sms commands to work fully
  • UIAutomator XML fixture at tests/fixtures/ui_dump.xml used for offline ui tests
  • scrcpy 3.3.4 on host; tesseract required for ocr command