Skip to content

Decisions move private; docs brought up to the code; app types; Chrome and PWA checks - #91

Merged
lana-20 merged 5 commits into
mainfrom
decisions-private
Oct 1, 2026
Merged

lana-20 merged 5 commits into
mainfrom
decisions-private

Conversation

@lana-20

@lana-20 lana-20 commented Oct 1, 2026

Copy link
Copy Markdown
Contributor
  • Decision records move to the private repo. What they specified stays public: the driver protocol in examples/drivers/PROTOCOL.md, the error codes in docs/guides/cli.md §6, each and --ui in the test runner guide, the hit test in autowait.md. About 64 files that linked to docs/decisions/ carry the point inline.
  • Every page under docs/ checked against the code for currency, accuracy, completeness and ambiguity, and corrected: quickstart, guides, setup and operations, design docs, the checks README and CHALLENGES. Other tool names removed.
  • App types. The tagline is "Mobile app automation for AI agents and humans"; the README has an App types section, APP-TYPES a table of what was driven per type and where it is held, and the skill says what to do per type.
  • docs/checks/chrome.sh and docs/checks/pwa.sh, passing on a Pixel 7 AVD and two iOS simulators. They found CHALLENGES 200 (a refused tap in Chrome's web app gave a remedy that could not work) and 201 (on iOS, app_eval answered {} for any promise), both fixed. ios-webview.sh now picks Safari's page by URL.

make ci passes.

…public

docs/decisions/ is gone from the public repo. What users and driver authors
need from it is kept public: the driver protocol as
examples/drivers/PROTOCOL.md, every error code in the CLI guide, the test
UI and parameters in the test-runner guide, the hit test in the auto-wait
guide. Every reference now points at those, or keeps its reasoning inline.
On the way: the test-runner guide no longer calls --ui and recording
"not yet", the auto-wait guide no longer calls a hidden overlay the one
blind spot, and the driver guide counts five clients, not four.
A review of docs/ for currency, accuracy, completeness and ambiguity,
each finding checked against the code before it was changed.

- Quickstart: start the device with `mobium boot`, quote the real
  "pick one" errors per platform, create the project folder, anchor the
  CLI match, and fail the Go example when no row matches.
- Guides: live tool counts (71, 19 read-only), the flaky control's real
  path and its clear-data step, --config/--output, the recording's path,
  the 2s implicit wait, boot/shutdown and map --diff in the CLI guide.
- Setup and operations: boot/shutdown in SETUP and DEVELOPMENT, a real
  doctor sample, the 75s close timeout, shutdown not checking other
  daemons, Windows CI coverage stated as it is, readOnlyHint in the
  threat model.
- Design docs: the test runner done and no longer "not planned", the
  import graph and front doors in ARCHITECTURE, cookies in APP-TYPES,
  FORMFLUX's profile count and iOS test command, a swipe-an-element row,
  and RELEASE-CHECKLIST's defect count, third-party apps and newer checks.
- Checks README: phone WebViews, the mobiumdev move, a broken table row,
  device-state coverage, iPhone support where scripts have it, and usage
  guards on calculator.sh and clock-timer.sh.
- CHALLENGES: two wrong cross-references, and the environment traps'
  "neither … both" over more than two.
- No other tool named: Selenium, EarlGrey, a hub and safaridriver removed.
The tagline becomes "Mobile app automation for AI agents and humans", in
the README, the CLI's help, all five clients' descriptions, the MCP
manifests, the skill and the branding guide.

- README: an App types section — native, hybrid, mobile web and PWAs,
  React Native, and Flutter — with how each is reached and what was
  driven.
- APP-TYPES: a table of what has been driven per type and where it is
  held: checked in, measured once (Chrome's taps, Squoosh as a PWA), or
  never (Flutter, Xamarin/MAUI, Cordova, Ionic). It no longer says that
  nothing checked in drives a browser: ios-webview.sh, orientation.sh and
  shake.sh do.
- The skill: what to do per app type, including acting from NATIVE_APP
  on an iOS browser page and saying so for Flutter rather than retrying.
chrome.sh drives a page in Chrome on Android: listed by title and URL,
read through text, eval and map, a tap counted by the page, and the page's
link followed. pwa.sh installs Squoosh if its icon is absent — Chrome's
menu on Android, Safari's share sheet on iOS — launches it from the icon,
and holds it to running standalone with an active service worker and to
what a tap does on each platform. Both passed on a Pixel 7 AVD and on
iPhone 17 Pro and iPhone 17 simulators, the latter installing from scratch.

- CHALLENGES 200: Chrome's web app, opened while Chrome is running, stops
  reporting its WebView to accessibility within about five seconds. The
  refusal of a tap that then cannot be placed is right; its remedy sent
  the caller to NATIVE_APP, where Chrome's tree is empty too. It now names
  both causes and gives the remedy only for the one that has it.
- CHALLENGES 201: on iOS app_eval answered {} for any promise. WebKit's
  Runtime.evaluate has no awaitPromise; a promise is now awaited with
  Runtime.awaitPromise and anything else read back by value.
- ios-webview.sh picks Safari's page by URL rather than the first tab, and
  reads the body text after re-attaching: example.com dropped its heading.
- APP-TYPES, README, the skill, the checks README and the release checklist
  say what is now checked in, and what a PWA's taps do on Android.
@lana-20
lana-20 merged commit 7207d4c into main Oct 1, 2026
5 checks passed
@lana-20
lana-20 deleted the decisions-private branch October 1, 2026 12:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant