plugin-inspector v0.3.10

plugin-inspector v0.3.10

Fixed

• Accept valid mocked capture output when plugin code leaves process.exitCode dirty.

plugin-inspector v0.3.9

plugin-inspector v0.3.9

Fixed

• Follow bundled channel loadBundledEntryExportSync registration exports during mocked runtime capture.

plugin-inspector v0.3.8

plugin-inspector v0.3.8

Fixed

• Synthesize manifest config for isolated runtime capture so configured hooks can be observed without credentials.

plugin-inspector v0.3.7

plugin-inspector v0.3.7

Changed

• Downgrade registration-capture-gap to advisory severity so missing capture evidence no longer reports as a P1 plugin contract risk.

plugin-inspector v0.3.6

plugin-inspector v0.3.6

Changed

• Report import-loop RSS and CPU as baseline-adjusted plugin deltas alongside raw subprocess metrics so Crabpot dashboards do not treat harness import cost as plugin runtime cost.
• Include optional OpenClaw loader lifecycle timings for import and full activation when a capture runner provides them.

Fixed

• Accept plugin install minimum-host floors as supported package metadata.
• Flag unsupported legacy OpenClaw bundle metadata and advertised npm pack blockers.
• Reconcile runtime capture evidence and harden mocked capture paths for downstream fixture reports.

plugin-inspector v0.3.5

plugin-inspector v0.3.5

Fixed

• Add immediate/faster subprocess RSS and CPU sampling plus explicit sample counts so short import-loop reports do not silently publish fake zero-memory metrics.
• Classify createChatChannelPlugin as channel factory metadata in synthetic probe plans so channel-core plugins do not fail as unknown registrars.
• Treat createChatChannelPlugin and defineChannelPluginEntry as channel registration equivalents when validating fixture expectations.
• Label runtime profile wall-time summaries as command-median p95 and render missing sampled metrics as n/a.

plugin-inspector v0.3.4

plugin-inspector v0.3.4

Fixed

• Separate executor-covered platform portability findings from residual findings so downstream structured runners can keep reports blocking only on unhandled risks.
• Sanitize absolute target OpenClaw paths from generated report artifacts and JSON CLI output.
• Normalize the dependency-install inspector finding title to use isolated-workspace wording.
• Treat openclaw package dependencies as host-linked workspace inputs instead of isolated dependency-install blockers.

plugin-inspector v0.3.3

plugin-inspector v0.3.3

Fixed

• Classify generated kitchen-sink public registrar coverage in synthetic probe plans so new API-surface fixtures do not fail as unknown execution profiles.

plugin-inspector v0.3.2

plugin-inspector v0.3.2

Fixed

• Preserve runtime capture bindings for callback-based registrations so captured hooks and registrations can resolve their bound callback metadata.

plugin-inspector v0.3.1

plugin-inspector v0.3.1

Added

• Add grouped root facades: pluginRoot, fixtureSuites, staticInspection, reports, contracts, ci, runtime, and synthetic.
• Expose contract capture, contract coverage, CI rollup, runtime profile, ref/profile diff, import-loop, and synthetic probe helpers from the root package API.
• Add a release follow-through guard that fails when Crabpot scripts regress to the legacy advanced.js bundle.
• Add a package-contents release guard for npm tarball entrypoints, examples, and README assets.

Changed

• Move Crabpot integration scripts to the root public API while keeping Crabpot as the fixture corpus and report consumer.
• Keep generic artifact writing out of the root API; Crabpot-owned runner scripts write their own JSON outputs.
• Ship the README banner asset in the npm package so the published README does not reference a missing local image.
• Document the grouped root import path for embedding harnesses without turning the README into a full API dump.