Every release member now declares publishConfig.access: public, so the scope no longer mixes levels: the 221 packages/*/* and apps/* manifests join the vendored framework and the native packages. check-workspace-constraints drops the per-sequence expectation and holds every release member to public, which is what stops a member from drifting back. Access is a property of the package, not of a version: the dsh packages already published as restricted become world-readable at their next publication.
acp/ — Agent Client Protocol automation
English | 中文
The ACP group exposes harness agents to programmatic clients over the Agent Client Protocol. It is an interoperability transport, not a presentation or human-interaction layer; the matching out-of-process subagent client lives in subagent/subagent-acp because it implements the subagent provider interface.
| Package | Role |
|---|---|
acp/ |
Automation-only ACP server. |
The server contract is documented in acp/README.md.