fix(mobile): reject a null device provider with INVALID_CONFIG, list the config and mobileTools errors
Merged
KA
14d ago+24+24+01234567890123456789-3-3-0123456789
What and why
- The engine's Throws table had only the empty
devicelist; a blank device name and a malformed device provider also fail withINVALID_CONFIGat config load. mobileToolshad no Throws entry: passing a non-mobile()engine fails the config load, andopen_appand the other tools have failure modes the model sees.
Issue
Fixes #1629
Verified
Ran it locally: yes
- Built CLI,
e2e listwith a blankdevice, a provider missingrelease, a provider withoutname,device: 42, andmobileTools(web()): each message and code matches its row. pnpm checkgreen;@e2e-dev/mobiletools, provider and engine unit tests pass (268).- Tool errors during a step not run with a model (no key); wording follows
guardedToolsindefault-agent.tsand the unit tests intools.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/**/*.mdxpage for the behavior, andskills/e2e/if the skill describes it. - Contract change: emitted
.d.tsreviewed,tests/types/sdk-types.tsupdated; wire change edits the schema and both fixtures. - Engine contract change (
e2e/engine): changesets fore2e,@e2e-dev/web, and@e2e-dev/mobile.