Repository navigation
ToolScope v0.2.0: portable baselines
ToolScope v0.2.0 completes the saved-baseline workflow with Import baseline.
Export definitions in one session, clear the browser baseline, and restore the file for the same catalog server identity. Imports preserve the original capture time. Replacing an existing baseline requires explicit confirmation; invalid files, cancellation, and storage errors preserve the saved reference.
The parser rejects mismatched server/tool identities, malformed definitions, duplicate JSON properties, excessive nesting, and numeric overflow. Equivalent JSON key order no longer creates false changes. File size is checked before reading, and existing incomplete-tool-list restrictions still apply to comparisons.
Verified locally: 27 affected tests, per-file coverage above the existing 90% gates, lint/format/typecheck/web build. In Chrome, a real bundled-server baseline was exported, cleared, imported, reloaded and compared successfully. Adding a synthetic tool, refreshing, and comparing reported exactly one addition. No external provider or production server was used.
The application still requires its local backend and is intended for desktop viewports of at least 1280 pixels. Comparisons identify changed definition fields; they do not prove compatibility. Imported files are not authenticated historical evidence. ToolScope adapts MCP Inspector; upstream source, licenses and notices remain. This source-release version is independent of the inherited package version.
Full CI 36335788802 passed on 3f3c916: validation, all four clients' per-file coverage, build safety/externalization gates, launcher/CLI/TUI/web smoke checks, Chromium flows and Storybook interactions. Final commit 943a0bd records that result without code changes.
The regenerated source archive matches all 1,409 files and executable modes at the final commit. SHA-256: d770bc0ea1740822f633fc089c1d2c7a863e3d47747385956c57ce2a718328f5.