ktc-plugins 0.2.0

Added

• diff NAME and diff --all to preview plugin updates without changing project files.
• outdated to compare locked commits with declared branches or tags without
  downloading source archives.
• remove with transactional cleanup of managed sources, declarations, registrations
  and ignore entries. Explicit --disable-in selections retain module configuration
  as comments.
• wrapper update --version to update both project launchers after verifying release
  metadata, checksums and native binary pins, while refusing local launcher edits.
• Offline, read-only validate for producer packaging, including Git ignore checks.
• Opt-in producer catalog support through catalog.file and catalog.export.
  Producer $libs.* references in plugin configuration and copied module templates
  resolve to fixed Maven coordinates from the locked producer catalog.
• Explicit library exports into the consumer catalog under ktc-<pluginId>-<alias>
  names, with alias collision checks, managed-block drift detection and preservation
  of user entries and comments.
• Lockfile catalog metadata recording the producer catalog path and digest, consumer
  catalog location and resolved exports. Catalog, source and lockfile changes share
  one transaction, including updates and removal.

Changed

• Mutation dry-runs show unified source, configuration and lockfile diffs instead of
  only paths and file counts. Binary and large-file changes show sizes and digests.
• Acceptance and runtime checks install pinned producer commits through their
  manifests without client-side path or catalog substitution.

Fixed

• Patch-application tests no longer depend on the host's Git newline conversion.
• Negative producer catalog tests preserve unrelated valid aliases and check the
  expected failure reason, preventing unrelated missing-alias errors from masking
  validation regressions.

Compatibility

• Existing manifests and lockfiles without catalogs remain supported with schema
  version 1. Older installers reject the new catalog fields; update consumer
  launchers before adopting catalog support.
• Exported libraries are catalog entries only. Consumer module dependencies remain
  explicitly managed by the user.

Downloads

Download ktc-plugins and ktc-plugins.bat into your consumer project and commit them. Unix users should run chmod +x ktc-plugins. The launchers download the matching executable and verify its pinned SHA-256.

Native binaries are provided for macOS ARM64, Linux x64, Linux ARM64, and Windows x64. SHA256SUMS covers all executables and both launchers. The installer requires curl and, inside Git projects, Git; it does not require Java. Linux binaries require glibc; Alpine/musl and Intel macOS remain unsupported.

See the README for usage and the full changelog for release history.