connector-v0.1.28

- Injection-safe XML <context> prompt envelope (entity-escaped)
- Remote-workspace workspace.read references + note pointing at read_workspace
- New MCP tool read_workspace (read another bot's workspace under your own permission)

Compat: [update] breaks <0.1.27 configs.

connector-v0.1.27

Merge pull request #187 from haowei2000/develop

release: domain migration prep + connector self-update 0.1.27 + bridge-protocol hardening

connector-v0.1.26

Prebuilt cce-acp-connector binaries with the git dubious-ownership
recovery and read-only git-inspection security hardening from #176.

connector-v0.1.25

Merge pull request #115 from haowei2000/develop

Release: connector distribution hardening (musl builds, same-origin download, install.sh)

connector-v0.1.24

fix(connector): ship cheers-mcp-server with the connector install

The connector injects the cheers stdio MCP server into every agent
session (policy.mcp.inject_cheers), but nothing ever installed that
binary: the release only shipped cce-acp-connector and the resolver
fell back to a dev-tree path or a bare PATH lookup, so installed bots
silently lost all cheers platform tools.

- resolver: prefer a cheers-mcp-server sitting next to the connector's
  own executable (how installed deployments lay the pair out)
- release-connector.yml: build + attach cheers-mcp-server for every
  target alongside the connector
- install.sh: download the MCP server into the same bin dir as the
  connector (best-effort, with an explicit warning when unavailable)

Bump connector to 0.1.24.

connector-v0.1.23

fix(connector): install rustls CryptoProvider; derive public ws base …

connector-v0.1.22

cce-acp-connector v0.1.22