fix(mobile): reject a null device provider with INVALID_CONFIG, list the config and mobileTools errors

Merged
KA
14d ago
+24-3

What and why

  • The engine's Throws table had only the empty device list; a blank device name and a malformed device provider also fail with INVALID_CONFIG at config load.
  • mobileTools had no Throws entry: passing a non-mobile() engine fails the config load, and open_app and the other tools have failure modes the model sees.

Issue

Fixes #1629

Verified

Ran it locally: yes

  • Built CLI, e2e list with a blank device, a provider missing release, a provider without name, device: 42, and mobileTools(web()): each message and code matches its row.
  • pnpm check green; @e2e-dev/mobile tools, provider and engine unit tests pass (268).
  • Tool errors during a step not run with a model (no key); wording follows guardedTools in default-agent.ts and the unit tests in tools.test.ts.

Checklist

  • Changeset added (pnpm changeset) for any change to a published package, or the change is testbed, docs, or CI only.
  • Breaking change: title carries !, the changeset body names what breaks and what replaces it, and the deprecation warning landed a window earlier (stability policy in CONTRIBUTING.md).
  • Docs updated in the same PR: the docs/**/*.mdx page for the behavior, and skills/e2e/ if the skill describes it.
  • Contract change: emitted .d.ts reviewed, tests/types/sdk-types.ts updated; wire change edits the schema and both fixtures.
  • Engine contract change (e2e/engine): changesets for e2e, @e2e-dev/web, and @e2e-dev/mobile.