adb-ready 1.0.3 → 1.0.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +22 -1
- package/README.md +13 -2
- package/dist/cli.js +15274 -27198
- package/docs/dev-sessions.md +10 -1
- package/package.json +8 -7
- package/schema/agent-tools-v1.json +1 -1
- package/skills/adb-ready/SKILL.md +2 -2
package/docs/dev-sessions.md
CHANGED
|
@@ -200,7 +200,16 @@ final problem instead of briefly presenting the session as ready.
|
|
|
200
200
|
Foreground, activity, and unlocked checks parse the complete target-scoped
|
|
201
201
|
Android state returned by `dumpsys`, including current Android 16 fields. When a
|
|
202
202
|
contract does not pass, human output identifies every failed or unsupported
|
|
203
|
-
assertion with its observed detail
|
|
203
|
+
assertion with its observed detail and the selected ADB transport serial on the
|
|
204
|
+
same line. This applies to both `dev` and `run`, so a copied failure line retains
|
|
205
|
+
its target context in CI logs:
|
|
206
|
+
|
|
207
|
+
```text
|
|
208
|
+
x ui text=Welcome · failed · serial=emulator-5554 · 0 node(s) matched text=Welcome.
|
|
209
|
+
```
|
|
210
|
+
|
|
211
|
+
All unsuccessful checks from the final readiness evaluation remain visible;
|
|
212
|
+
passed checks are counted in the summary. JSON and NDJSON retain every assertion
|
|
204
213
|
result for CI and agents.
|
|
205
214
|
|
|
206
215
|
Recovery waits for a bounded stabilization period, attempts to reacquire the
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "adb-ready",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.5",
|
|
4
4
|
"description": "Agent-ready Android CLI for reliable ADB sessions, app automation, and verified evidence.",
|
|
5
5
|
"private": false,
|
|
6
6
|
"type": "module",
|
|
@@ -59,6 +59,7 @@
|
|
|
59
59
|
"url": "https://github.com/Adam014/adb-ready/issues"
|
|
60
60
|
},
|
|
61
61
|
"homepage": "https://github.com/Adam014/adb-ready#readme",
|
|
62
|
+
"funding": "https://github.com/sponsors/Adam014",
|
|
62
63
|
"author": {
|
|
63
64
|
"name": "Adam Stádník",
|
|
64
65
|
"email": "adam.stadnik@seznam.cz",
|
|
@@ -93,11 +94,11 @@
|
|
|
93
94
|
},
|
|
94
95
|
"devDependencies": {
|
|
95
96
|
"@arethetypeswrong/cli": "0.18.5",
|
|
96
|
-
"@biomejs/biome": "2.5.
|
|
97
|
+
"@biomejs/biome": "2.5.14",
|
|
97
98
|
"@types/bun": "1.4.2",
|
|
98
|
-
"@types/node": "22.20.
|
|
99
|
-
"@yarnpkg/cli-dist": "4.18.
|
|
100
|
-
"npm": "12.0
|
|
99
|
+
"@types/node": "22.20.4",
|
|
100
|
+
"@yarnpkg/cli-dist": "4.18.1",
|
|
101
|
+
"npm": "12.1.0",
|
|
101
102
|
"publint": "0.3.24",
|
|
102
103
|
"runpalette": "0.5.0",
|
|
103
104
|
"tinyexec": "1.3.1",
|
|
@@ -106,7 +107,7 @@
|
|
|
106
107
|
},
|
|
107
108
|
"dependencies": {
|
|
108
109
|
"@expo/env": "2.4.3",
|
|
109
|
-
"@modelcontextprotocol/server": "2.
|
|
110
|
-
"zod": "4.5
|
|
110
|
+
"@modelcontextprotocol/server": "2.1.0",
|
|
111
|
+
"zod": "4.6.5"
|
|
111
112
|
}
|
|
112
113
|
}
|
|
@@ -3,7 +3,7 @@ name: adb-ready
|
|
|
3
3
|
description: Prepare, automate, debug, and verify one Android target through the ADB Ready MCP server. Use for Android development sessions, app lifecycle work, UI automation, failure evidence, screenshots, and agent-driven device checks.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
|
-
<!-- Generated by adb-ready 1.0.
|
|
6
|
+
<!-- Generated by adb-ready 1.0.5; do not edit. -->
|
|
7
7
|
|
|
8
8
|
# ADB Ready
|
|
9
9
|
|
|
@@ -51,4 +51,4 @@ Use the typed `adb-ready` MCP tools. Do not replace them with generic shell or r
|
|
|
51
51
|
- `session`: 12 tools
|
|
52
52
|
- `ui`: 29 tools
|
|
53
53
|
|
|
54
|
-
Contract: ADB Ready 1.0.
|
|
54
|
+
Contract: ADB Ready 1.0.5, agent schema v1.
|