Fixed
- OpenClaw discovery now actually finds the plugin. 0.0.2 shipped
openclaw.plugin.jsoncorrectly (manifest withid+configSchema), butpackage.jsonwas missing theopenclaw.extensionsfield. OpenClaw'sresolvePackageExtensionEntriesreadspackage.json["openclaw"].extensionsto know where the plugin entry lives — without it, discovery falls through to looking forindex.{ts,js,mjs,cjs}at the directory root, doesn't find one, and skips us silently. The gateway then warnsplugin not found: @latitude-data/openclaw-telemetry (stale config entry ignored; remove it from plugins config)even though everything else is in place. Now both the publishedpackage.jsonand the minimalpackage.jsonthe installer writes into~/.openclaw/extensions/latitude-telemetry/declare"openclaw": { "extensions": ["./dist/plugin.js"] }. After re-runninginstall, the gateway log lists@latitude-data/openclaw-telemetryin the ready-plugins line.
Added
--version/-vand--help/-htop-level flags on the CLI. Runnpx -y @latitude-data/openclaw-telemetry --versionto confirm which version is installed (or shadow-cached) on a given box.