adb-ready 0.3.1 → 0.3.3

package/docs/RELEASING.md

@@ -21,10 +21,24 @@ The workflow does not use a long-lived npm write token.
 
 ## Prepare a release
 
-1. Complete the real-device acceptance matrix for the advertised hosts and
-   workflows.
+Release evidence has three tiers:
+
+- **Every release:** the complete fixture, unit, integration, runtime, package,
+  documentation, privacy, and release-artifact verification gate must pass.
+- **Device-behavior changes:** rerun every affected workflow on a real target
+  and record the exact host, target, Android version, and transport. A
+  documentation, metadata, or machine-output-only patch does not manufacture
+  new hardware evidence.
+- **Support expansion:** before promoting a new host, architecture, transport,
+  framework, or device class to a tested tier, complete and record its
+  dedicated acceptance matrix.
+
+Then prepare the release:
+
+1. Confirm the relevant acceptance tier above is complete and that
+   `COMPATIBILITY.md` still states the observed boundary accurately.
 2. Set the exact release version in `package.json`.
-3. Change `private` to `false` only in the release commit.
+3. Confirm the published package keeps `private: false`.
 4. Move the relevant entries from `Unreleased` into a dated
    `## [VERSION] - YYYY-MM-DD` section in `CHANGELOG.md` and update its links.
 5. Replace all prerelease installation examples and private-preview language in
@@ -110,6 +124,15 @@ bunx adb-ready@VERSION --version
 deno run -A npm:adb-ready@VERSION --version
 ```
 
+Deno 2 applies a 24-hour minimum dependency age by default. For an immediate
+post-publish verification only, override that safety delay explicitly:
+
+```bash
+deno run -A --minimum-dependency-age 0 npm:adb-ready@VERSION --version
+```
+
+Normal consumers should keep Deno's default policy and omit the override.
+
 Confirm the npm page shows the expected README, MIT license, repository,
 provenance, executable names, unpacked size, and file inventory. Then verify
 the `latest` dist-tag points to the released version.

package/docs/automation.md

@@ -25,8 +25,13 @@ agent or integration to identify the installed CLI first:
 
 ```bash
 adb-ready --json
+adb-ready --json --non-interactive
 ```
 
+Root presentation flags may appear in either order. Adding
+`--non-interactive` does not change the result shape or fall back to human
+help.
+
 Machine data is written to `stdout`. Human progress and diagnostics are written
 to `stderr`. `--quiet` hides successful human output without hiding failures.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "adb-ready",
-  "version": "0.3.1",
+  "version": "0.3.3",
   "description": "Agent-ready Android CLI for reliable ADB sessions, app automation, and verified evidence.",
   "private": false,
   "type": "module",
@@ -33,6 +33,7 @@
     "ui:playground": "bun run scripts/ui-playground.ts",
     "ui:check": "bun run scripts/ui-playground.ts --all --non-interactive",
     "test": "bun test",
+    "test:coverage": "bun test --coverage && bun run scripts/coverage-check.mjs",
     "test:commands": "bun run build && bun run scripts/command-matrix.mjs",
     "test:package-managers": "bun run build && bun run scripts/package-manager-smoke.mjs",
     "test:integration": "bun test tests/integration",

package/schema/agent-tools-v1.json

@@ -1,7 +1,7 @@
 {
   "title": "ADB Ready agent tool contract",
   "schemaVersion": 1,
-  "packageVersion": "0.3.1",
+  "packageVersion": "0.3.3",
   "protocolVersion": "2025-11-25",
   "transport": "stdio",
   "tools": [