@mmerterden/multi-agent-toolkit-mcp 3.7.0 → 3.7.1

package/CHANGELOG.md

@@ -15,6 +15,30 @@ Releases before this file exists are recorded in the git tags and commit history
 
 ---
 
+## 3.7.1
+
+### Fixed
+
+- **`android_meminfo` never read the swap total on a real device.** The parser
+  was written from the documented output, which spells the line
+  `TOTAL SWAP (KB):`. An Android 35 Pixel emulator prints `TOTAL SWAP PSS:`, so
+  the regex matched nothing and `total_swap_kb` came back null on every real
+  run. Both spellings are accepted now, and the fixture is the emulator's own
+  output rather than a reconstruction.
+
+  This is the defect the 3.3.0 note predicted: that parser shipped marked "not
+  verified on a device", and the first real device broke it. Worth recording
+  plainly, because the note was right and the only thing that found the bug was
+  running it.
+
+### Note
+
+The Android checks are no longer unverified. `android_accessibility_audit` and
+`android_meminfo` were both run against a booted Android 35 emulator: the audit
+read 14 clickable elements off a real launcher, reported the reading order as
+correct with no false positive on the grid, and produced one critical and seven
+warnings; meminfo read the App Summary and, after the fix above, the swap total.
+
 ## 3.7.0
 
 ### Added

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mmerterden/multi-agent-toolkit-mcp",
-  "version": "3.7.0",
+  "version": "3.7.1",
   "description": "MCP server for iOS Simulator, Android Emulator and headless web control. 87 tools: device automation (tap/swipe/type), accessibility audits, visual diff, crash logs, App Store / Play Store pre-submission compliance. Runs standalone over stdio with any MCP client.",
   "type": "module",
   "main": "index.js",

package/tools/memory/index.js

@@ -85,11 +85,12 @@ const MEMINFO_ROWS = [
  * snapshots of the same flow is the shape a leak takes, where a single
  * absolute number says almost nothing.
  *
- * NOT VERIFIED ON A DEVICE. Written against the documented output shape on a
- * machine with adb installed but no device or emulator to run it against,
- * unlike the leaks parser above, which was
- * checked against live output. The tests below pin the shape this expects; the
- * first real run is the measurement.
+ * Verified against a real device: an Android 35 Pixel emulator, after the parser
+ * had first been written from documentation alone. That first version returned
+ * null for the swap total on every real device, because the documented shape
+ * says "TOTAL SWAP (KB):" and the device prints "TOTAL SWAP PSS:". Both are
+ * accepted now. It is the clearest argument in this file for running a parser
+ * against the thing it parses.
  *
  * @param {string} raw
  * @returns {{measurable: boolean, reason: string|null, pss: object, totalPssKb: number|null,
@@ -118,7 +119,11 @@ export function parseMeminfoOutput(raw) {
   };
   const totalPssKb = num(/TOTAL PSS:\s*(\d+)/i);
   const totalRssKb = num(/TOTAL RSS:\s*(\d+)/i);
-  const totalSwapKb = num(/TOTAL SWAP \(KB\):\s*(\d+)/i);
+  // Two spellings in the wild: "TOTAL SWAP (KB):" in the documented shape and
+  // "TOTAL SWAP PSS:" on a real Android 35 device, which is what a Pixel
+  // emulator actually printed. The first regex, written from documentation,
+  // returned null against every real device.
+  const totalSwapKb = num(/TOTAL SWAP(?: \(KB\)| PSS)?:\s*(\d+)/i);
 
   if (found === 0 && totalPssKb === null) {
     return { measurable: false, reason: "no App Summary block in the dumpsys output", pss: {}, totalPssKb: null, totalRssKb: null, totalSwapKb: null };