mobile-debug-mcp 0.32.2 → 0.32.4

package/README.md

@@ -121,6 +121,10 @@ If you are unsure whether the environment is configured correctly, run `get_syst
 
 ## Usage
 
+For clients that support Agent Plugins, the [agent-plugin](agent-plugin/README.md)
+package installs the MCP server configuration together with the existing usage
+skill. Direct npm/MCP configuration above remains supported.
+
 Examples: 
 
 Crash fixing:
@@ -138,4 +142,4 @@ Feature building:
 
 ## License
 
-MIT
+Apache-2.0

package/agent-plugin/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/agent-plugin/README.md

@@ -0,0 +1,27 @@
+# Mobile Debug MCP agent plugin
+
+Install this directory as an Agent Plugins package in a client that supports
+both skills and stdio MCP servers. It provides the existing mobile-debug MCP
+usage skill and launches the published `mobile-debug-mcp` npm package. The
+plugin requires Node.js 18 or newer, `npx`, and the platform toolchains needed
+for the devices you want to use. The first launch may need npm registry access.
+The MCP process starts in the client-managed plugin data directory so npm does
+not resolve the source checkout as a local package when installed from this repo.
+
+The server is pinned to the published npm version in `mcp.json`. The plugin's
+`plugin.json` version advances independently for guidance-only releases; do not
+change the server pin to an unpublished npm version. The repository's
+`skills/mobile-debug-tools-usage/SKILL.md` is the
+source of the packaged skill; run `npm run sync:agent-plugin` after editing it.
+The packaged directory uses the skill's declared name, `mobile-debug-mcp`, as
+required by Agent Skills. `npm run check:agent-plugin` checks the packaged
+copies and configuration.
+
+The usage skill prefers screenshots for routine visual checks and reserves
+hierarchy reads for semantic selection and structured assertions. Assertion
+timeouts must cover a fresh tree read as well as the expected app transition.
+
+If you already configured the MCP server directly in your agent client, disable
+that separate registration when enabling this plugin to avoid duplicate tools.
+The direct npm installation remains available without this plugin. See the
+repository README for platform toolchain setup and `get_system_status` guidance.

package/agent-plugin/mcp.json

@@ -0,0 +1,11 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/mcp.schema.json",
+  "mcpServers": {
+    "mobile-debug-mcp": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["--yes", "mobile-debug-mcp@0.32.4", "server"],
+      "cwd": "${PLUGIN_DATA}"
+    }
+  }
+}

package/agent-plugin/plugin.json

@@ -0,0 +1,29 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "mobile-debug-tools",
+  "version": "0.0.1",
+  "description": "Mobile app debugging tools and usage guidance for Android and iOS agents.",
+  "repository": "https://github.com/clivejefferies/mobile-debug-tools",
+  "license": "Apache-2.0",
+  "keywords": ["mobile", "android", "ios", "debugging", "mcp"],
+  "author": {
+    "name": "mobile-debug-tools contributors"
+  },
+  "extensions": {
+    "com.openai": {
+      "interface": {
+        "displayName": "Mobile Debug Tools",
+        "shortDescription": "Inspect and debug Android and iOS apps",
+        "longDescription": "Inspect mobile apps, interact with their screens, collect debugging evidence, and verify observed behaviour on Android and iOS devices and emulators. Requires local Node.js and the relevant platform toolchains.",
+        "developerName": "mobile-debug-tools contributors",
+        "category": "Developer Tools",
+        "capabilities": ["Interactive"],
+        "defaultPrompt": [
+          "Check my mobile debugging environment and connected devices.",
+          "Inspect the current screen of my mobile app.",
+          "Help me reproduce and diagnose a bug in my mobile app."
+        ]
+      }
+    }
+  }
+}

package/agent-plugin/skills/mobile-debug-mcp/SKILL.md

@@ -0,0 +1,96 @@
+---
+name: mobile-debug-mcp
+description: Use mobile-debug MCP to inspect, interact with, and verify any Android or iOS app on a device or emulator.
+metadata:
+  author: mobile-debug-mcp contributors
+  version: "1.1"
+---
+
+# Mobile-debug MCP usage
+
+Use mobile-debug MCP when a task needs evidence from a running Android or iOS app. Identify the device and the state or behaviour to check, then choose the smallest observation or action that can establish it. A successful tool call confirms only what that tool reports; check the resulting app state before claiming an outcome.
+
+## Choose the lightest evidence that proves the claim
+
+- Prefer a screenshot for routine visual navigation, layout checks, and visible
+  outcomes that can be established from the image.
+- Use UI-tree reads and accessibility assertions such as `expect_element_visible`,
+  `expect_state`, or `wait_for_ui` when reliable element selection or a structured
+  property check is required. An image alone does not establish accessibility
+  properties such as enabled state.
+- Use a debug snapshot when an ordinary observation does not explain a failure or multiple kinds of evidence are needed together.
+- Use logs or network activity for claims about errors or requests. Correlate them with the relevant action and time window; they do not establish what the user saw.
+- Use platform shell commands only for device or system operations that the MCP tools cannot expose. Treat shell output as evidence of that operation, not of the app's visible state.
+
+Choose one observation that proves the required outcome. Avoid automatically
+reading the UI tree after a screenshot or taking a screenshot after a sufficient
+structured assertion.
+
+## Keep Android inspection APK-free
+
+Use the standard ADB path for Android inspection. It requires no helper APK.
+The normal hierarchy dump
+can take several seconds; account for this rather than treating it as a fast
+poll. Compressed dumps can omit nodes and should not be assumed faster.
+
+## Keep interaction fast
+
+Treat each MCP call as a round trip and use the fastest path that still proves
+the behaviour. For an interaction, prefer this sequence:
+
+1. Observe the current screen or wait for a uniquely identifiable target if its presence is uncertain.
+2. Perform the requested action using a stable selector or element id when available.
+3. Check the specific resulting state once it has had time to occur.
+
+Do not wait before every action when its target and current state are already
+known. Do not poll unchanged screens. Set bounded assertion timeouts that cover
+the expected app transition plus a complete fresh observation and a margin.
+For Android ADB tree reads taking 2–3 seconds, start with a 5-second timeout for
+a simple assertion; allow more when loading or repeated observations are
+required. A 2-second timeout cannot reliably accommodate a 3-second tree read.
+Adjust to measured device latency and supported tool limits. Report an
+observation timeout separately from evidence that a control is absent.
+
+Use compact responses for routine actions. If action dispatch is reliable but
+verification is slow or unavailable, dispatch with verification disabled and
+verify at meaningful checkpoints with one focused accessibility assertion or
+screenshot. Do not assume `light` verification is faster: use it only when it
+has returned useful results reliably on the current MCP version and device.
+
+Prefer a stable element selector when it is already known and valid. For a
+clearly identifiable visual target, use coordinates from a fresh screenshot
+without requiring a tree read solely to rediscover it. If the target is
+ambiguous or a semantic check is required, resolve it from the hierarchy.
+Reacquire coordinates after scrolling,
+changing orientation, switching screens, or opening a system surface.
+
+Element discovery can be the slowest part of a journey. Avoid repeated
+`find_element` calls for the same screen: resolve a control once, use the
+returned selector or coordinates while that screen is unchanged, and verify
+the resulting state before continuing. If a query fails, inspect the current
+screen once before retrying; controls represented only by icons may not have a
+matching visible text label.
+
+When the MCP offers a journey or batch action, use it only when its steps can
+express the needed observable checks and it returns enough evidence to report
+the outcome. Measure the whole journey and compare equivalent steps on the same
+device; do not infer a performance improvement from a single fast action.
+
+## Match the evidence to the claim
+
+For a state change, check the state after the action rather than inferring it
+from successful dispatch. For an asynchronous update, start a fresh observation
+after the relevant event and wait for the expected condition within a bounded
+timeout. If an accessibility tree appears stale or incomplete, use another
+appropriate observation such as a screenshot and report the discrepancy.
+
+For behaviour outside the app's foreground screen, inspect the relevant system
+surface or device state. For content that cannot be established visually, such
+as audio output, use a suitable direct check or state that it was not verified.
+
+## Report evidence precisely
+
+State the device, actions taken, observed result, evidence source, and any
+untested scope. Distinguish an observed outcome from an inference. Do not say
+a feature works solely because the build compiled or an MCP action returned
+success.

package/dist/observe/android.js

@@ -9,7 +9,6 @@ import { parsePngSize } from "../utils/image.js";
 import { deriveSnapshotMetadata } from "./snapshot-metadata.js";
 import { remainingBudget } from '../utils/operation-budget.js';
 import { createObservationMeasurement } from './performance-metrics.js';
-import { androidTreeBridgeEnabled, readAndroidTreeFromBridge } from './android-tree-bridge.js';
 const activeLogStreams = new Map();
 export class AndroidObserve {
     async getDeviceMetadata(appId, deviceId) {
@@ -47,22 +46,7 @@ export class AndroidObserve {
                         await measurement.timed('observation_wait_ms', () => delay(Math.min(remainingBudget(300 + (attempts * 100)), 300 + (attempts * 100))));
                     }
                     remainingBudget();
-                    let bridgeContent = null;
-                    if (androidTreeBridgeEnabled()) {
-                        try {
-                            bridgeContent = await measurement.physicalRead(async () => {
-                                const content = await readAndroidTreeFromBridge(deviceInfo.id);
-                                if (!content)
-                                    throw new Error('Android UI tree bridge unavailable');
-                                return content;
-                            });
-                        }
-                        catch (error) {
-                            if (error instanceof Error && (error.message === 'ACTION_TIMEOUT' || error.message.startsWith('BRIDGE_CLEANUP_UNCONFIRMED')))
-                                throw error;
-                        }
-                    }
-                    xmlContent = bridgeContent ?? await measurement.physicalRead(async () => {
+                    xmlContent = await measurement.physicalRead(async () => {
                         await execAdb(['shell', 'uiautomator', 'dump', '/sdcard/ui.xml'], deviceId);
                         const content = await execAdb(['shell', 'cat', '/sdcard/ui.xml'], deviceId);
                         if (!content || !content.trim() || content.includes('ERROR:'))
@@ -72,7 +56,7 @@ export class AndroidObserve {
                     break;
                 }
                 catch (e) {
-                    if (e instanceof Error && (e.message === 'ACTION_TIMEOUT' || e.message.startsWith('BRIDGE_CLEANUP_UNCONFIRMED')))
+                    if (e instanceof Error && e.message === 'ACTION_TIMEOUT')
                         throw e;
                     console.error(`Attempt ${attempts} failed: ${e}`);
                 }

package/dist/server-core.js

@@ -6,7 +6,7 @@ import { handleToolCall } from './server/tool-handlers.js';
 export { wrapResponse, toolDefinitions, handleToolCall };
 export const serverInfo = {
     name: 'mobile-debug-mcp',
-    version: '0.32.2'
+    version: '0.32.4'
 };
 export function createServer() {
     const server = new Server(serverInfo, {

package/docs/CHANGELOG.md

@@ -2,6 +2,9 @@
 
 All notable changes to the **Mobile Debug MCP** project will be documented in this file.
 
+## [0.32.4]
+- Removed the optional Android UI-tree bridge runtime and its APK build tooling. Android UI-tree reads use `uiautomator dump` through ADB.
+
 ## [0.32.2]
 - bug fix
 
@@ -26,7 +29,7 @@ All notable changes to the **Mobile Debug MCP** project will be documented in th
 ## [0.30.0]
 - Folded RFC 013 synchronization semantics into the main spec and aligned the interact docs with the shipped `wait_for_ui_change` behavior.
 - Updated `wait_for_ui_change` to use a 300ms stabilization default and to reset stabilization on new in-place mutations.
-- Validated the in-place UI mutation flow on the Modul8 emulator app, including a delayed state-change case.
+- Validated the in-place UI mutation flow on an Android emulator, including a delayed state-change case.
 
 ## [0.29.0]
 - Added empty resource handlers and declared the `resources` capability so Codex MCP discovery can complete the handshake against the published npm package.
@@ -57,7 +60,7 @@ All notable changes to the **Mobile Debug MCP** project will be documented in th
 - RFC-003 wait/synchronization contract with `snapshot_revision`, `captured_at_ms`, and `loading_state`
 - Added `wait_for_ui_change` for stable in-place UI mutations
 - Updated `get_ui_tree` and `capture_debug_snapshot` to surface snapshot metadata
-- Emulator-validated the new UI-change flow against the Modul8 app
+- Validated the new UI-change flow on an Android emulator
 
 ## [0.25.1]
 - Platform-native element identity metadata for UI targeting

package/docs/benchmarks/ui-tree-performance/README.md

@@ -50,9 +50,10 @@ The report commit SHAs are available locally as `codex/spec-019-baseline` and
 `codex/spec-019-candidate`; create clean, built checkouts of those refs to
 reproduce the paired measurement.
 
-For the opt-in Android bridge, run
-`LATENCY_DEVICE_ID=emulator-5554 node --import tsx test/device/automated/ui-tree-performance/bridge-probe.ts`.
-Its `bridge-probe.json` compares ten bridge and legacy reads, checks a network
+The historical `bridge-probe.json` compares ten bridge and legacy reads, checks a network
 update, and checks a timer that changes visually without emitting an
 accessibility event. The timer check catches a stale accessibility cache even
 when every bridge request calls `getRootInActiveWindow()`.
+The bridge APK source, generator, and build/install probe have been removed;
+this report is retained as historical evidence, not a runnable benchmark in
+the current checkout.

package/docs/tools/observe.md

@@ -92,8 +92,7 @@ Notes:
 - Elements may also include platform-native identity hints such as `stable_id`, `role`, `test_tag`, `selector`, and `semantic`.
 - The tree response may include `snapshot_revision`, `captured_at_ms`, and `loading_state` when a reliable signal is available.
 - Prefer `wait_for_ui` for deterministic element resolution in interactive flows.
-- Android 14+ can use the experimental persistent hierarchy reader. Build its APK with `npx tsx test/fixtures/ui-tree-bridge/build.ts`, then set `MOBILE_DEBUG_MCP_ANDROID_TREE_BRIDGE_APK` to its absolute path before starting the server. The reader clears Android's accessibility cache before every tree read, including when a screen changes without an accessibility event. Older Android versions use `uiautomator dump`.
-- If the bridge fails, the server stops it before falling back to `uiautomator dump`. While running, the bridge holds Android's UiAutomation connection, so other `uiautomator dump` clients may fail. Leave the variable unset for the default reader. To reproduce the device probe, set `LATENCY_DEVICE_ID` and run `npx tsx test/device/automated/ui-tree-performance/bridge-probe.ts`.
+- Android reads the accessibility hierarchy with `uiautomator dump` through ADB. No helper APK is installed or required.
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mobile-debug-mcp",
-  "version": "0.32.2",
+  "version": "0.32.4",
   "description": "MCP server for mobile app debugging (Android + iOS), with focus on security and reliability",
   "type": "module",
   "bin": {
@@ -19,7 +19,9 @@
     "test": "npm run test:unit",
     "lint": "eslint src test --quiet",
     "lint:fix": "eslint src test --fix",
-    "verify": "npm run lint && npm run build && npm run test:unit"
+    "sync:agent-plugin": "node scripts/agent-plugin.mjs --sync",
+    "check:agent-plugin": "node scripts/agent-plugin.mjs --check",
+    "verify": "npm run lint && npm run build && npm run test:unit && npm run check:agent-plugin"
   },
 
   "engines": {

package/scripts/agent-plugin.mjs

@@ -0,0 +1,38 @@
+import assert from 'node:assert/strict'
+import { copyFileSync, readFileSync } from 'node:fs'
+import { fileURLToPath } from 'node:url'
+import path from 'node:path'
+
+const repositoryRoot = fileURLToPath(new URL('../', import.meta.url))
+const packagedSkill = path.join(repositoryRoot, 'agent-plugin/skills/mobile-debug-mcp/SKILL.md')
+const sourceSkill = path.join(repositoryRoot, 'skills/mobile-debug-tools-usage/SKILL.md')
+const packagedLicense = path.join(repositoryRoot, 'agent-plugin/LICENSE')
+const sourceLicense = path.join(repositoryRoot, 'LICENSE')
+const packageInfo = JSON.parse(readFileSync(path.join(repositoryRoot, 'package.json'), 'utf8'))
+const plugin = JSON.parse(readFileSync(path.join(repositoryRoot, 'agent-plugin/plugin.json'), 'utf8'))
+const mcp = JSON.parse(readFileSync(path.join(repositoryRoot, 'agent-plugin/mcp.json'), 'utf8'))
+
+if (process.argv[2] === '--sync') {
+  copyFileSync(sourceSkill, packagedSkill)
+  copyFileSync(sourceLicense, packagedLicense)
+}
+else if (process.argv[2] !== '--check') throw new Error('Use --sync or --check')
+
+assert.equal(plugin.$schema, 'https://agent-plugins.org/schemas/1.0.0/plugin.schema.json')
+assert.equal(plugin.name, 'mobile-debug-tools')
+assert.match(plugin.version, /^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)$/, 'plugin releases use an independent semantic version')
+assert.equal(mcp.$schema, 'https://agent-plugins.org/schemas/1.0.0/mcp.schema.json')
+const servers = Object.entries(mcp.mcpServers)
+assert.equal(servers.length, 1, 'the plugin should expose only this MCP server')
+const [serverName, server] = servers[0]
+assert.equal(serverName, packageInfo.name)
+assert.equal(server.type, 'stdio')
+assert.equal(server.command, 'npx')
+assert.deepEqual(server.args, ['--yes', `${packageInfo.name}@${packageInfo.version}`, 'server'])
+assert.equal(server.cwd, '${PLUGIN_DATA}', 'npx must run outside the same-named source checkout')
+assert.deepEqual(readFileSync(packagedSkill), readFileSync(sourceSkill), 'packaged usage skill must match its source')
+assert.deepEqual(readFileSync(packagedLicense), readFileSync(sourceLicense), 'packaged license must match its source')
+const skillName = readFileSync(packagedSkill, 'utf8').match(/^---\r?\nname: ([a-z0-9-]+)\r?\n/)?.[1]
+assert.equal(skillName, path.basename(path.dirname(packagedSkill)), 'packaged skill directory must match its frontmatter name')
+
+console.log('Agent plugin package is in sync')

package/skills/mcp-builder/SKILL.md

@@ -64,5 +64,4 @@ Activate when an agent needs to:
 4. if install fails -> call collect-diagnostics({reason:'install failure', platform:'android'})
 
 # License
-Same as repository (MIT).
-
+Same as repository (Apache-2.0).