adb-ready 0.3.4 → 0.4.0

package/CHANGELOG.md

@@ -9,6 +9,95 @@ breaking changes.
 
 ## [Unreleased]
 
+## [0.4.0] - 2026-09-15
+
+### Added
+
+- Detect explicit localhost ports in Expo `EXPO_PUBLIC_*` environment URLs,
+  include them in development-session reverse mappings and readiness checks,
+  and surface only their variable names, ports, and loaded environment-file
+  names.
+- Show a compact, preset-aware live control bar in interactive `dev` sessions
+  while preserving the framework's native stdin and keeping automation silent.
+- Attach Expo and React Native sessions to a positively identified Metro server
+  that is already running, without starting, controlling, or stopping it.
+
+### Fixed
+
+- Stop and await development-session health monitoring before intentional
+  teardown, preventing cancelled probes from creating false recovery evidence.
+- Omit a missing Android package `versionName` from structured app information
+  instead of serializing Android's `null` sentinel as a real version string.
+- Stop reporting an available host package manager as detected project
+  metadata in Flutter, Gradle, and other non-JavaScript projects, and omit the
+  irrelevant setting from generated native-project configuration.
+- Report missing Flutter and Gradle launchers as framework prerequisites with
+  the attempted launcher and actionable setup guidance instead of an
+  unspecified development-command error.
+- Preserve unrelated diagnostic text when a short numeric ADB transport ID is
+  observed; transport IDs remain operational evidence and short private
+  literals match only complete identifier tokens.
+- Parse complete Android 16 lock-screen and foreground-activity state during
+  strict readiness checks, and show actionable per-assertion failure details in
+  human session output.
+- Apply `logs --tail` after logcat filtering, and overlap snapshot-to-follow
+  handoff so a live filtered tail neither loses nor repeats setup-time records.
+- Reject contradictory log-tag include and exclude filters before accessing
+  ADB instead of allowing logcat argument order to silently override exclusion.
+- Document every supported app-install and package-list action option in the
+  focused command help, including filtering and install verification flags.
+- Make UI audits follow Android hierarchy semantics: inherit effective labels
+  through control descendants and actionable ancestors, exclude structural
+  focus and scrolling containers, and explain every finding with confidence
+  and rule rationale.
+- Make `ui scroll` directions describe content navigation—such as `down`
+  revealing content below—while keeping `ui swipe` directions as physical
+  finger gestures.
+- Reject unreadable or one-frame, zero-duration Android screen recordings
+  instead of publishing them as verified evidence, and report the measured
+  duration and frame count for valid recordings.
+- Recognize Android's separate accessibility hint when verifying `ui clear`,
+  so an empty field displaying its placeholder is not reported as a failure.
+- Let unique text and description selectors target their nearest enabled
+  actionable ancestor while reporting both the matched label and action node.
+- Keep the interactive home and focused menus inside the detected terminal
+  width, including real narrow PTYs, without implicit last-column wrapping.
+- Prevent a development session from reporting ready after its owned command
+  has already exited; distinguish passed readiness checks from the complete
+  session-ready gate and promote the first actionable child error.
+- Keep successful readiness and health polling silent in human output and out
+  of the durable session journal while retaining failures and state changes.
+- Keep Expo's automatic Android launch on the one selected ADB transport: start
+  Metro without Expo's all-device `--android` path, resolve the official launch
+  URL with an Expo 55-compatible fallback, and open it through target-scoped
+  ADB before reporting the session ready.
+- Prevent an Expo development session from reporting ready while a detected
+  localhost API is unreachable from the selected Android target.
+- Make `adb-ready help version` follow the same focused-help contract as every
+  other visible top-level command without loading project configuration or ADB.
+- Fail with a specific service conflict when Metro's configured host port is
+  occupied by another service instead of launching into an ambiguous port error.
+
+## [0.3.5] - 2026-09-12
+
+### Changed
+
+- Enforce at least 95% coverage of measurable executable lines added or
+  replaced by a pull request, in addition to the existing repository-wide
+  line and function coverage floors.
+- Keep external source maps available in local builds while excluding their
+  unreferenced payload from the published npm package.
+- Make the read-only real-ADB check report logical targets and raw transports
+  separately and fail when ADB returns an unrecognized device state.
+
+### Fixed
+
+- Preserve complete mDNS transport serials containing Bonjour collision
+  suffixes such as ` (2)`, preventing one physical device from appearing as a
+  second unknown target.
+- Classify connected `_adb-tls-connect._tcp` service transports as TLS even
+  when their mDNS serial contains a Bonjour collision suffix.
+
 ## [0.3.4] - 2026-09-12
 
 ### Added
@@ -242,7 +331,9 @@ breaking changes.
   explainable configuration precedence.
 - Human, plain, JSON, and NDJSON output across Node, Bun, and Deno entrypoints.
 
-[Unreleased]: https://github.com/Adam014/adb-ready/compare/v0.3.4...HEAD
+[Unreleased]: https://github.com/Adam014/adb-ready/compare/v0.4.0...HEAD
+[0.4.0]: https://github.com/Adam014/adb-ready/compare/v0.3.5...v0.4.0
+[0.3.5]: https://github.com/Adam014/adb-ready/compare/v0.3.4...v0.3.5
 [0.3.4]: https://github.com/Adam014/adb-ready/compare/v0.3.3...v0.3.4
 [0.3.3]: https://github.com/Adam014/adb-ready/compare/v0.3.2...v0.3.3
 [0.3.2]: https://github.com/Adam014/adb-ready/compare/v0.3.1...v0.3.2

package/README.md

@@ -71,6 +71,8 @@ them or require an ADB Ready account, hosted service, or model API key.
 
 Running `adb-ready` without a command opens the interactive workflow home.
 `adbr` is the shorter alias for the same CLI.
+The home and its focused menus adapt to the detected terminal width, including
+narrow split panes, without relying on horizontal scrolling.
 
 ## What ADB Ready does
 
@@ -81,7 +83,9 @@ Running `adb-ready` without a command opens the interactive workflow home.
 - [**Operate the app**](./docs/apps-and-evidence.md#app-lifecycle) — resolve,
   install, launch, restart, deep-link, and inspect the project app.
 - [**Verify the UI**](./docs/ui-automation.md) — find semantic elements, act
-  by intent, assert state, and capture the screen.
+  by intent—including labels inside clickable containers and content-directed
+  scrolling—assert state, audit effective accessibility labels, and capture the
+  screen.
 - [**Debug with evidence**](./docs/logs-and-context.md) — keep focused logs,
   session history, screenshots, recordings, and redacted context together.
 - [**Automate a real device**](./docs/automation.md#run-one-bounded-verification)
@@ -123,9 +127,12 @@ npx adb-ready devices
 npx adb-ready dev
 ```
 
-Expo, React Native, Flutter, Capacitor, Gradle, and custom commands all run
-against the same selected target through `ANDROID_SERIAL`. Add local services
-with repeated `--port` flags or replace the detected command after `--`:
+Expo, React Native, Flutter, Capacitor, Gradle, and custom commands all receive
+the same selected target through `ANDROID_SERIAL`. Expo sessions go further:
+ADB Ready starts Metro without Expo's all-device auto-open path, resolves the
+project deep link from the verified server, and opens it only on the selected
+ADB transport. Add local services with repeated `--port` flags or replace the
+detected command after `--`:
 
 ```bash
 adb-ready dev --port 8081 --port 8000
@@ -133,6 +140,22 @@ adb-ready dev -- pnpm run android:local
 adb-ready dev --dry-run --json
 ```
 
+For Expo projects, explicit localhost URLs in `EXPO_PUBLIC_*` environment
+variables are discovered with Expo's own development environment resolution.
+ADB Ready safely adds their ports to the selected target and verifies the host
+services before calling the session ready. Explicit port configuration always
+wins, and `--no-auto-reverse-localhost` disables discovery when required.
+
+In an interactive Expo or Flutter session, ADB Ready shows the framework's
+active reload, developer-menu, debugger, and help shortcuts as soon as the
+session is ready. Input continues directly to the framework; automation and
+redirected output stay prompt-free.
+
+If Expo or React Native Metro is already running, ADB Ready verifies its
+standard status endpoint and attaches the Android session without restarting or
+owning that server. An unrelated process on the same port is reported as a
+clear conflict instead of being mistaken for Metro.
+
 [Reach your first ready session →](./docs/getting-started.md)
 
 ### In CI and automation
@@ -173,6 +196,12 @@ recover safely or return bounded failure evidence
 ```
 
 - Existing matching port mappings are reused; conflicts are not overwritten.
+- Routine successful health polls stay silent; only failures, recovery actions,
+  and meaningful session state changes become durable output.
+- `ready` means the selected target, required services, configured checks, and
+  framework launch have all succeeded while the owned development process is
+  not already failing; a passed port check alone never produces a ready
+  session.
 - Wireless and port recovery is bounded and independently verified.
 - An ADB server restart is never hidden inside recovery.
 - On exit, ADB Ready cleans only resources owned by that session.
@@ -202,6 +231,10 @@ Android transport backend.
 - Session data is bounded, redacted, private to the local user, and never
   uploaded by ADB Ready.
 - Stale UI references are rejected before input is sent.
+- Field replacement verifies values without confusing a declared Android hint
+  for user-entered text.
+- Screen recordings require a readable MP4 and a real multi-frame timeline;
+  a filename and hash alone never count as verified video evidence.
 - Machine data stays on `stdout`; human diagnostics stay on `stderr`.
 
 [Review the complete threat model →](./docs/threat-model.md)