@agentskit/adapters@0.16.0 is uninstallable: published dependencies contain "@agentskit/core": "workspace:*"

[vectrebraun]

Summary

@agentskit/adapters@0.16.0 is published with an unreplaced pnpm workspace
specifier in its dependencies, which makes it uninstallable from the registry
with either npm or pnpm.

"dependencies": { "@agentskit/core": "workspace:*" }

workspace:* is only meaningful inside the source monorepo; it must be
substituted with a real version range at publish time. Earlier releases were
published correctly, so this looks like a regression in the 0.16.0 publish:

version	published dependencies.@agentskit/core
0.12.2	1.7.3
0.15.1	1.12.8
0.16.0	workspace:*

Reproduction

$ npm view @agentskit/adapters@0.16.0 dependencies
{ '@agentskit/core': 'workspace:*' }

npm:

$ npm install @agentskit/adapters@0.16.0
npm error code EUNSUPPORTEDPROTOCOL
npm error Unsupported URL Type "workspace:": workspace:*

pnpm (outside a workspace that happens to contain @agentskit/core):

$ pnpm add @agentskit/adapters@0.16.0
ERR_PNPM_WORKSPACE_PKG_NOT_FOUND  In : "@agentskit/core@workspace:*" is in the
dependencies but no package named "@agentskit/core" is present in the workspace

This error happened while installing the dependencies of @agentskit/adapters@0.16.0

Impact

0.16.0 is the first release to expose the ./cli subpath
(createCliAdapter, createJsonCliAdapter, createAcpCliAdapter, and the
provider-manifest registry). Every earlier version — 0.13.0 through 0.15.1 —
exports only ., ./catalog, and ./createAdapter. So adopting the new CLI
adapters currently requires taking 0.16.0, and 0.16.0 cannot be installed
cleanly.

The only workaround we found is forcing the transitive dependency past the bad
specifier, e.g. with a pnpm override:

{ "pnpm": { "overrides": { "@agentskit/adapters@0.16.0>@agentskit/core": "1.12.9" } } }

1.12.9 appears to be the intended version — it was published about two seconds
before adapters@0.16.0, so presumably it is what workspace:* resolved to in
the release. With that override the package installs and the ./cli module works
as documented.

Suggested fix

Republish @agentskit/adapters (e.g. as 0.16.1) with the workspace specifier
replaced by a concrete range such as "@agentskit/core": "1.12.9". It may be
worth adding a publish-time check that no workspace: specifier survives into a
published dependencies block, since other packages in the workspace could
regress the same way.

Environment: npm 10.x / pnpm 10.34.5, Node 22, macOS.