adapter-sdk: MIT declared without a LICENSE file, and linked with file: so lockfiles carry no version #2

packages/adapter-sdk/package.json declares "license": "MIT", but the package has no LICENSE file and no copyright line anywhere, while the repository and the opencli-mcp package are Apache-2.0. The published opencli-mcp tarball ships packages/adapter-sdk and depends on it through file:packages/adapter-sdk.

Two problems for anyone redistributing opencli-mcp:

1. Unclear license. MIT requires the copyright notice to be reproduced, and there is none to reproduce. It is also unclear whether MIT is intended or the field was left from a template, given the rest of the repository is Apache-2.0.
2. The file: dependency has no version in consumers' lockfiles. npm records node_modules/@opencli-mcp/adapter-sdk as a link to node_modules/opencli-mcp/packages/adapter-sdk, without a version or license, so license and SBOM tooling that reads package-lock.json misses the package or has to special-case it.

Could you either:

• set "license": "Apache-2.0" if the package is meant to share the repository's license, or
• add a packages/adapter-sdk/LICENSE with the MIT text and its copyright line?

For (2), publishing @opencli-mcp/adapter-sdk to npm and depending on it by version would fix it, as would moving the SDK into opencli-mcp itself if it is not meant to be installed separately.

Context: we embed opencli-mcp 0.0.12 in Maka, whose release includes a third-party notice for every shipped package.