adb-ready 0.3.0 → 0.3.1

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 CHANGED
@@ -9,6 +9,21 @@ breaking changes.
9
9
 
10
10
  ## [Unreleased]
11
11
 
12
+ ## [0.3.1] - 2026-09-11
13
+
14
+ ### Changed
15
+
16
+ - Clarify package ownership and normalize the maintainer identity used by
17
+ repository history and published package metadata.
18
+ - Reorganize the public README around six user outcomes and explicit entry
19
+ paths for coding agents, terminal users, and CI automation.
20
+ - Add copy-and-paste installation paths for npm, pnpm, Yarn, and Bun.
21
+ - Replace the simulated terminal snippet with an optimized product walkthrough
22
+ showing development startup, UI verification, and agent-driven recovery,
23
+ while keeping the marketing asset out of the installed npm package.
24
+ - Require an explicit release tag when manually dispatching the release
25
+ workflow instead of retaining a stale version default.
26
+
12
27
  ## [0.3.0] - 2026-09-11
13
28
 
14
29
  ### Added
@@ -176,7 +191,8 @@ breaking changes.
176
191
  explainable configuration precedence.
177
192
  - Human, plain, JSON, and NDJSON output across Node, Bun, and Deno entrypoints.
178
193
 
179
- [Unreleased]: https://github.com/Adam014/adb-ready/compare/v0.3.0...HEAD
194
+ [Unreleased]: https://github.com/Adam014/adb-ready/compare/v0.3.1...HEAD
195
+ [0.3.1]: https://github.com/Adam014/adb-ready/compare/v0.3.0...v0.3.1
180
196
  [0.3.0]: https://github.com/Adam014/adb-ready/compare/v0.2.0...v0.3.0
181
197
  [0.2.0]: https://github.com/Adam014/adb-ready/compare/v0.1.2...v0.2.0
182
198
  [0.1.2]: https://github.com/Adam014/adb-ready/compare/v0.1.1...v0.1.2
package/LICENSE CHANGED
@@ -1,6 +1,6 @@
1
1
  MIT License
2
2
 
3
- Copyright (c) 2026 ADB Ready contributors
3
+ Copyright (c) 2026 Adam Stádník
4
4
 
5
5
  Permission is hereby granted, free of charge, to any person obtaining a copy
6
6
  of this software and associated documentation files (the "Software"), to deal
package/README.md CHANGED
@@ -4,8 +4,8 @@
4
4
 
5
5
  **The local Android runtime for coding agents.**
6
6
 
7
- Give any MCP-capable agent a safe way to start your Android project, operate a
8
- real app, verify what happened, and bring back evidence—not guesses.
7
+ Prepare one Android target, run your project, operate the app, and return
8
+ verified evidence—for developers, agents, and CI.
9
9
 
10
10
  [![MCP](https://img.shields.io/badge/MCP-native-7c3aed)](./docs/agent-integration.md)
11
11
  [![CI](https://github.com/Adam014/adb-ready/actions/workflows/ci.yml/badge.svg)](https://github.com/Adam014/adb-ready/actions/workflows/ci.yml)
@@ -17,248 +17,218 @@ real app, verify what happened, and bring back evidence—not guesses.
17
17
  [![Capacitor](https://img.shields.io/badge/Capacitor-supported-119EFF?logo=capacitor&logoColor=white)](./docs/dev-sessions.md)
18
18
  [![Platforms](https://img.shields.io/badge/hosts-macOS_%C2%B7_Linux_%C2%B7_Windows-64748b)](./COMPATIBILITY.md)
19
19
 
20
- [Quick start](#quick-start) · [AI agents](#built-for-agentic-android-development) · [Why ADB Ready](#why-adb-ready) ·
21
- [Workflows](#find-your-workflow) · [Documentation](#documentation) ·
22
- [Compatibility](#compatibility)
20
+ [Quick start](#quick-start) · [What it does](#what-adb-ready-does) ·
21
+ [AI agents](#with-a-coding-agent) · [CI](#in-ci-and-automation) ·
22
+ [Documentation](#documentation)
23
+
24
+ <img src="https://raw.githubusercontent.com/Adam014/adb-ready/main/docs/assets/adb-ready-demo.gif" alt="ADB Ready prepares an Android development session, verifies the app UI, and lets a coding agent recover lost localhost access." width="1120" />
23
25
 
24
26
  </div>
25
27
 
28
+ ## Quick start
29
+
30
+ Install ADB Ready in the Android project your team wants to run:
31
+
32
+ **npm** · default
33
+
26
34
  ```bash
27
35
  npm install --save-dev adb-ready
28
- npx adb-ready agent setup codex
36
+ npx adb-ready dev
29
37
  ```
30
38
 
31
- Then ask your agent:
32
-
33
- > Start this Expo app on my Android phone, wait until the login screen is
34
- > actually ready, verify the change I made, and keep the failure evidence.
39
+ <details>
40
+ <summary><strong>Use pnpm, Yarn, or Bun</strong></summary>
35
41
 
36
- ```text
37
- $ adb-ready dev
42
+ #### pnpm
38
43
 
39
- ✓ Android target selected Pixel 9 · wireless
40
- Localhost ports ready 8081 → 8081
41
- ✓ Development command started pnpm run start --android
42
- ● Session healthy watching target, ports, and logs
44
+ ```bash
45
+ pnpm add --save-dev adb-ready
46
+ pnpm exec adb-ready dev
43
47
  ```
44
48
 
45
- ADB Ready handles the state around ADB that agents cannot safely guess: which
46
- device belongs to the run, whether the app is truly ready, which ports and
47
- processes it owns, and what evidence survives after a failure. It works locally
48
- with Codex, Claude Code, Cursor, VS Code/Copilot, and any MCP client—without an
49
- ADB Ready account, hosted service, or model API key.
50
-
51
- | Prepare | Operate | Prove |
52
- | --- | --- | --- |
53
- | Select one target, connect it, start the project, and keep ports healthy. | Inspect semantic UI, launch apps, act on elements, and capture the screen. | Gate tests on real readiness and return structured logs, context, and artifacts. |
49
+ #### Yarn
54
50
 
55
- ## Built for agentic Android development
51
+ ```bash
52
+ yarn add --dev adb-ready
53
+ yarn adb-ready dev
54
+ ```
56
55
 
57
- Most coding agents can edit an Android project but cannot verify the running
58
- app. ADB Ready closes that loop with a built-in local MCP server and typed tools
59
- for target readiness, development sessions, app lifecycle, semantic UI, logs,
60
- and visual evidence—without handing the model an unrestricted shell or raw ADB.
56
+ #### Bun
61
57
 
62
58
  ```bash
63
- # Connect the current project to your coding agent
64
- npx adb-ready agent setup codex
59
+ bun add --dev adb-ready
60
+ bunx adb-ready dev
65
61
  ```
66
62
 
67
- Your agent can:
68
-
69
- - find and bind one deterministic Android target;
70
- - start, check, and stop a durable development session across agent reconnects;
71
- - resolve, install, launch, restart, and inspect the project app;
72
- - find or assert semantic UI, tap by intent, type, swipe, and compare state;
73
- - capture screenshots and read bounded, redacted session evidence; and
74
- - verify actions against fresh device state instead of assuming they worked.
63
+ </details>
75
64
 
76
- Every action is bound to one verified target and checked against fresh device
77
- state. Stale UI references are rejected, destructive app removal is not exposed
78
- to agents, and every tool returns a schema-validated result. Everything stays
79
- local unless your chosen AI client sends tool results to its model provider.
65
+ ADB Ready handles the state around ADB that a person, script, or coding agent
66
+ should not guess: which device belongs to the run, whether the app is ready,
67
+ which ports and processes the session owns, and what evidence survives a
68
+ failure. It orchestrates your real ADB and framework tools; it does not replace
69
+ them or require an ADB Ready account, hosted service, or model API key.
80
70
 
81
- [Connect an AI agent in minutes →](./docs/agent-integration.md)
71
+ Running `adb-ready` without a command opens the interactive workflow home.
72
+ `adbr` is the shorter alias for the same CLI.
82
73
 
83
- ## Why ADB Ready?
74
+ ## What ADB Ready does
84
75
 
85
- ### Start once. Stay ready.
76
+ - [**Run the project**](./docs/dev-sessions.md) select one target, prepare
77
+ ports, launch the framework, and keep the session healthy.
78
+ - [**Connect the device**](./docs/targets-and-wireless.md) — discover, pair,
79
+ reconnect, and deterministically bind a physical device or emulator.
80
+ - [**Operate the app**](./docs/apps-and-evidence.md#app-lifecycle) — resolve,
81
+ install, launch, restart, deep-link, and inspect the project app.
82
+ - [**Verify the UI**](./docs/ui-automation.md) — find semantic elements, act
83
+ by intent, assert state, and capture the screen.
84
+ - [**Debug with evidence**](./docs/logs-and-context.md) — keep focused logs,
85
+ session history, screenshots, recordings, and redacted context together.
86
+ - [**Automate a real device**](./docs/automation.md#run-one-bounded-verification)
87
+ — gate a finite command on readiness and return stable results, reports, and
88
+ artifacts.
86
89
 
87
- ADB Ready finds one usable Android target, prepares its ports, launches your
88
- project with the correct `ANDROID_SERIAL`, and watches the session while you
89
- work.
90
+ ## Choose how you work
90
91
 
91
- ### Recover without the ritual.
92
+ ### With a coding agent
92
93
 
93
- When a wireless target or reverse mapping disappears, recovery is bounded,
94
- target-safe, and independently verified. It never silently restarts the shared
95
- ADB server or rewrites another tool's mapping.
94
+ Connect the current project to Codex, Claude Code, Cursor, VS Code/Copilot,
95
+ Windsurf, or another MCP client:
96
96
 
97
- ### Give agents evidence, not terminal noise.
97
+ ```bash
98
+ npx adb-ready agent setup codex
99
+ ```
98
100
 
99
- Focused logcat, structured problems, and a saved redacted timeline keep the
100
- important failure evidence together. Agents receive bounded, machine-readable
101
- context and typed actions instead of guessing from an unstructured terminal.
101
+ Then ask for the outcome you want:
102
102
 
103
- ### Keep your existing stack.
103
+ > Start this Expo app on my Android phone, wait until the login screen is
104
+ > actually ready, verify my change, and keep the failure evidence.
104
105
 
105
- ADB Ready orchestrates the real ADB, framework, and package manager you already
106
- use. It does not replace Android Studio or force your project onto Bun.
106
+ The local MCP server gives agents typed tools for target readiness, durable
107
+ development sessions, app lifecycle, semantic UI, logs, screenshots, and saved
108
+ evidence. Every result is schema-validated and checked against fresh device
109
+ state. Agents do not receive a generic shell, unrestricted raw ADB, or app
110
+ removal.
107
111
 
108
- | Projects | Package managers | CLI runtimes |
109
- | ------------------------------------- | ----------------------- | -------------------- |
110
- | Expo · React Native · Flutter · Capacitor · Gradle · custom | npm · pnpm · Yarn · Bun | Node.js · Bun · Deno |
112
+ [Connect an AI agent in minutes →](./docs/agent-integration.md)
111
113
 
112
- ## Quick start
114
+ ### From your terminal
113
115
 
114
- You need Android SDK Platform-Tools and Node.js 22 or newer for the standard npm
115
- entrypoint.
116
+ Check the host, inspect visible targets, and start the complete development
117
+ loop:
116
118
 
117
119
  ```bash
118
- # Check ADB and the host
119
120
  npx adb-ready doctor
120
-
121
- # See connected and wireless targets
122
121
  npx adb-ready devices
123
-
124
- # Start the complete development session
125
122
  npx adb-ready dev
126
123
  ```
127
124
 
128
- Add it to a project when the team should share one version:
125
+ Expo, React Native, Flutter, Capacitor, Gradle, and custom commands all run
126
+ against the same selected target through `ANDROID_SERIAL`. Add local services
127
+ with repeated `--port` flags or replace the detected command after `--`:
129
128
 
130
129
  ```bash
131
- npm install --save-dev adb-ready
132
- npx adb-ready init
133
- npx adb-ready dev
130
+ adb-ready dev --port 8081 --port 8000
131
+ adb-ready dev -- pnpm run android:local
132
+ adb-ready dev --dry-run --json
134
133
  ```
135
134
 
136
- Running `adb-ready` without a command opens the interactive workflow home.
137
- `adbr` is the shorter alias for the same CLI.
138
-
139
- [Read the five-minute setup →](./docs/getting-started.md)
140
-
141
- ## Find your workflow
142
-
143
- | I want to… | Start here |
144
- | ----------------------------------------------------------- | ----------------------------------------------------------------------------------- |
145
- | launch Expo, React Native, Flutter, Capacitor, Gradle, or my own command | [`adb-ready dev`](./docs/dev-sessions.md) |
146
- | pair or reconnect an Android device over Wi-Fi | [Targets and Wireless debugging](./docs/targets-and-wireless.md) |
147
- | choose the right device when several are connected | [Deterministic target selection](./docs/targets-and-wireless.md#explicit-selection) |
148
- | expose Metro, a local API, or a debugger to Android | [Port workflows](./docs/dev-sessions.md#port-ownership) |
149
- | install, inspect, launch, restart, or deep-link my app | [App lifecycle](./docs/apps-and-evidence.md#app-lifecycle) |
150
- | save a verified screenshot or bounded screen recording | [Evidence capture](./docs/apps-and-evidence.md#evidence-capture) |
151
- | give a developer or agent one bounded app/UI snapshot | [Structured inspection](./docs/apps-and-evidence.md#structured-inspection) |
152
- | find, read, fill, scroll, and verify the Android UI | [Safe UI automation](./docs/ui-automation.md) |
153
- | see only the Android logs that matter | [Focused logcat](./docs/logs-and-context.md#focused-logcat) |
154
- | understand why the last session failed | [Session problems](./docs/logs-and-context.md#session-history) |
155
- | prepare safe evidence for an AI assistant | [Diagnostic context](./docs/logs-and-context.md#diagnostic-context) |
156
- | connect Codex, Claude Code, Cursor, Copilot, or Windsurf | [`adb-ready agent setup`](./docs/agent-integration.md#connect-an-agent) |
157
- | share project settings without a custom shell script | [Configuration](./docs/configuration.md) |
158
- | use ADB Ready from CI or another tool | [Automation contract](./docs/automation.md) |
159
- | run one smoke test and keep its logs, result, and report | [`adb-ready run`](./docs/automation.md#run-one-bounded-verification) |
160
- | fix a known setup or target problem | [Troubleshooting](./docs/troubleshooting.md) |
161
-
162
- ## What happens in `adb-ready dev`?
135
+ [Reach your first ready session →](./docs/getting-started.md)
163
136
 
164
- ```text
165
- find or recover one target
166
-
167
- verify only the ports your project needs
168
-
169
- start the project on that same target
170
-
171
- watch target · ports · logs · child process
172
-
173
- recover safely or explain exactly what needs you
174
- ```
137
+ ### In CI and automation
175
138
 
176
- - Expo and React Native receive reverse port `8081` by default.
177
- - Add any local service with repeated `--port` flags.
178
- - Pass any command after `--`; it runs directly without an implicit shell.
179
- - Existing matching mappings are reused. Conflicts are never overwritten.
180
- - On exit, only resources created by that session are cleaned up.
181
- - The final exit code and a bounded, redacted session record are preserved.
139
+ Wait for declared readiness, execute one bounded verification command, preserve
140
+ its exit code, and clean only resources created by the run:
182
141
 
183
142
  ```bash
184
- adb-ready dev --port 8081 --port 8000
185
- adb-ready dev -- pnpm run android:local
186
- adb-ready dev --dry-run --json
143
+ npx adb-ready run -- npm run test:e2e
187
144
  ```
188
145
 
189
- ## Built for humans, agents, and automation
190
-
191
- The interactive CLI provides keyboard navigation, live state, reduced-motion
192
- support, narrow-terminal fallbacks, and clear recovery feedback. Scripts get a
193
- separate deterministic contract:
146
+ Each executed run retains a redacted evidence bundle with its result,
147
+ timeline, problems, focused logcat, AI context, JUnit XML, and GitHub step
148
+ summary. Scripts also get deterministic JSON and NDJSON contracts:
194
149
 
195
150
  ```bash
196
151
  adb-ready devices --json --non-interactive
197
152
  adb-ready logs --package com.example.app --format ndjson
198
- adb-ready context --since 5m --only problems,recovery,logs
199
153
  adb-ready sessions list --status failed --since 24h --limit 5
200
154
  ```
201
155
 
202
- - machine data on `stdout`, human diagnostics on `stderr`;
203
- - versioned JSON results and NDJSON events;
204
- - no prompt, animation, or terminal takeover in redirected/CI execution;
205
- - stable problem categories, meaningful exit codes, timeouts, and dry runs; and
206
- - explicit target, ADB path, and remote ADB server overrides.
156
+ [Build a readiness-gated device job →](./docs/automation.md)
207
157
 
208
- Local AI agents use the same contracts through a schema-validated MCP stdio
209
- server. The package includes a version-matched public tool schema, while target
210
- binding, fresh-state checks, redaction, and verification remain enforced by ADB
211
- Ready itself. [Explore the agent contract →](./docs/agent-integration.md)
158
+ ## One target. One verified loop.
212
159
 
213
- ## Documentation
160
+ ```text
161
+ find or recover one Android target
162
+
163
+ bind the complete run to that target
164
+
165
+ prepare only the ports the project needs
166
+
167
+ start the framework and wait for declared readiness
168
+
169
+ watch target · ports · logs · child process
170
+
171
+ recover safely or return bounded failure evidence
172
+ ```
214
173
 
215
- | Guide | What it answers |
216
- | ---------------------------------------------------------------- | --------------------------------------------------------------------- |
217
- | [Getting started](./docs/getting-started.md) | How do I reach my first ready session? |
218
- | [Development sessions](./docs/dev-sessions.md) | What does ADB Ready own, watch, recover, and clean up? |
219
- | [Targets and Wireless debugging](./docs/targets-and-wireless.md) | How are devices paired, connected, and selected safely? |
220
- | [Apps and evidence](./docs/apps-and-evidence.md) | How do I control one app and capture verified device evidence? |
221
- | [AI agent integration](./docs/agent-integration.md) | How do Codex, Claude Code, Cursor, or Copilot use safe Android tools? |
222
- | [Safe UI automation](./docs/ui-automation.md) | How do humans and agents act on current UI with verifiable evidence? |
223
- | [Logs and AI context](./docs/logs-and-context.md) | What is captured, redacted, saved, and exported? |
224
- | [Configuration](./docs/configuration.md) | How do projects, profiles, hooks, and precedence work? |
225
- | [Automation](./docs/automation.md) | What are the JSON, NDJSON, stdout, and exit-code contracts? |
226
- | [Threat model](./docs/threat-model.md) | Which trust boundaries, controls, and residual risks apply? |
227
- | [Troubleshooting](./docs/troubleshooting.md) | What should I do for each common failure? |
228
- | [Compatibility](./COMPATIBILITY.md) | Which hosts, runtimes, and environments are covered? |
229
- | [Example configs](./examples/README.md) | What can I copy for Expo, React Native, Flutter, Capacitor, Gradle, or custom projects? |
230
-
231
- Run `adb-ready --help` for the full command list or
232
- `adb-ready help COMMAND` for focused options.
174
+ - Existing matching port mappings are reused; conflicts are not overwritten.
175
+ - Wireless and port recovery is bounded and independently verified.
176
+ - An ADB server restart is never hidden inside recovery.
177
+ - On exit, ADB Ready cleans only resources owned by that session.
178
+ - The final exit code and a project-scoped session record are preserved.
179
+
180
+ ## Keep your existing stack
233
181
 
234
- ## Compatibility
182
+ | Projects | Package managers | CLI runtimes | Hosts |
183
+ | --- | --- | --- | --- |
184
+ | Expo · React Native · Flutter · Capacitor · Gradle · custom | npm · pnpm · Yarn · Bun | Node.js · Bun · Deno | macOS · Linux · Windows |
235
185
 
236
- ADB Ready targets macOS, Linux, and Windows, with Node.js, Bun, and Deno runtime
237
- smoke coverage. The package is architecture-neutral JavaScript with no native
238
- addon or artificial OS/CPU block. A working ADB executable remains the only
186
+ The standard npm entrypoint requires Android SDK Platform-Tools and Node.js 22
187
+ or newer. The published package is architecture-neutral JavaScript with no
188
+ native addon or artificial OS/CPU block. A working ADB executable remains the
239
189
  Android transport backend.
240
190
 
241
191
  [See tested and upstream-capable support tiers →](./COMPATIBILITY.md)
242
192
 
243
193
  ## Trust by default
244
194
 
245
- - The shared ADB server is never restarted implicitly.
246
- - Destructive or global actions are never hidden inside recovery.
195
+ - One selected target is used consistently for every operation in a session.
196
+ - Target leases prevent concurrent ADB Ready processes from mutating the same
197
+ target without an explicit takeover.
198
+ - Destructive or device-wide actions require an explicit command or
199
+ confirmation.
247
200
  - Pairing codes never enter command-line arguments.
248
- - Session data is bounded, redacted, private to the user, and never uploaded.
249
- - Package contents are allowlisted and checked before release.
250
- - npm publication is prepared for short-lived OIDC credentials and provenance.
251
- - AI clients receive typed bounded tools; raw shell/ADB and destructive app
252
- removal are not exposed through MCP.
253
- - UI references are bound to the current hierarchy digest, so stale targets are
254
- rejected before input is sent.
201
+ - Session data is bounded, redacted, private to the local user, and never
202
+ uploaded by ADB Ready.
203
+ - Stale UI references are rejected before input is sent.
204
+ - Machine data stays on `stdout`; human diagnostics stay on `stderr`.
205
+
206
+ [Review the complete threat model →](./docs/threat-model.md)
207
+
208
+ ## Documentation
209
+
210
+ | Guide | Start here when you want to… |
211
+ | --- | --- |
212
+ | [Getting started](./docs/getting-started.md) | Reach the first ready development session. |
213
+ | [Development sessions](./docs/dev-sessions.md) | Configure frameworks, commands, ports, readiness, and cleanup. |
214
+ | [Targets and Wireless debugging](./docs/targets-and-wireless.md) | Pair, connect, recover, or explicitly select a target. |
215
+ | [Apps and evidence](./docs/apps-and-evidence.md) | Control the app and capture screenshots or recordings. |
216
+ | [Safe UI automation](./docs/ui-automation.md) | Find, act on, and verify the current Android UI. |
217
+ | [Logs and AI context](./docs/logs-and-context.md) | Diagnose a failure with bounded, redacted evidence. |
218
+ | [AI agent integration](./docs/agent-integration.md) | Connect an MCP-capable coding agent. |
219
+ | [Automation](./docs/automation.md) | Use readiness, exit codes, JSON, NDJSON, JUnit, and CI artifacts. |
220
+ | [Configuration](./docs/configuration.md) | Share project presets, hooks, aliases, and policies. |
221
+ | [Troubleshooting](./docs/troubleshooting.md) | Resolve a known setup, target, UI, or session problem. |
222
+ | [Compatibility](./COMPATIBILITY.md) | Check hosts, runtimes, package managers, and support tiers. |
223
+ | [Example configs](./examples/README.md) | Copy a framework or custom-project configuration. |
224
+
225
+ Run `adb-ready --help` for the complete command list or
226
+ `adb-ready help COMMAND` for focused options.
255
227
 
256
228
  ## Project
257
229
 
258
230
  [Changelog](./CHANGELOG.md) · [Contributing](./CONTRIBUTING.md) ·
259
231
  [Security](./SECURITY.md) · [MIT License](./LICENSE)
260
232
 
261
- ADB Ready is Android-only. The current development line combines target
262
- readiness, ports, session recovery, logs, verified app lifecycle, and local
263
- evidence capture. It intentionally exposes typed workflows instead of a generic
264
- remote shell.
233
+ ADB Ready is Android-only. It exposes target-bound workflows rather than a
234
+ generic remote shell.
package/dist/cli.js CHANGED
@@ -355,7 +355,7 @@ import process13 from "node:process";
355
355
  // package.json
356
356
  var package_default = {
357
357
  name: "adb-ready",
358
- version: "0.3.0",
358
+ version: "0.3.1",
359
359
  description: "Agent-ready Android CLI for reliable ADB sessions, app automation, and verified evidence.",
360
360
  private: false,
361
361
  type: "module",
@@ -410,6 +410,11 @@ var package_default = {
410
410
  url: "https://github.com/Adam014/adb-ready/issues"
411
411
  },
412
412
  homepage: "https://github.com/Adam014/adb-ready#readme",
413
+ author: {
414
+ name: "Adam Stádník",
415
+ email: "adam.stadnik@seznam.cz",
416
+ url: "https://github.com/Adam014"
417
+ },
413
418
  keywords: [
414
419
  "adb",
415
420
  "ai-agents",
@@ -49028,4 +49033,4 @@ try {
49028
49033
  process14.removeListener("SIGTERM", abort);
49029
49034
  }
49030
49035
 
49031
- //# debugId=1B7FD726A0690DCA64756E2164756E21
49036
+ //# debugId=6E82EA8DB46AED9C64756E2164756E21