api-discovery

To inspect Maven artifact source code without unzipping Gradle cache JARs, run the discover script to resolve the artifact's on-disk absolute path. You can then use Grep, Read, or Glob directly against that path to check APIs and implementation details.

The fastest way to locate a Maven artifact's source path for API analysis is running the discover script with the artifact coordinates. It outputs the absolute local path to stdout, enabling immediate source inspection without slow extraction processes.

Yes, you can use Grep and Read to check type definitions in Spine sibling sources directly from the cache. The discover script resolves the absolute source path, allowing immediate file reading and pattern matching against KDoc and method signatures.

Maven artifact discovery requires a initialized shared extraction cache directory for first-run bootstrap. If the directory is missing, the discovery script provides guidance to initialize it, ensuring safe access to local sibling sources without fallback unzip workarounds.

When declared Maven artifact versions mismatch local siblings during source inspection, the discovery script detects the staleness and optionally refreshes safely. It enforces safety guardrails by blocking fallback unzip extraction workarounds when resolution fails.