agentteams-openclaw

Repo	box/github.com/opencharly/layer-agentteams-openclaw:v2026.274.0610

The shared AgentTeams openclaw gateway runtime — built from the pinned upstream source commit (2026.4.14) because the matrix channel extension is NOT in the npm openclaw package and the published @openclaw/matrix npm package is broken (its openclaw.extensions entry references ./index.ts, which the tarball does not ship) — the source build is the only complete, version-matched path, and it is what the upstream manager/worker images do. Shared by the agentteams-manager and agentteams-worker images (R3: one build, two consumers). The openclaw build uses the JS pnpm (npm install -g [email protected], matching the repo’s packageManager pin) because openclaw’s scripts/pnpm-runner.mjs re-execs pnpm via node $npm_execpath — the nodejs candy’s standalone ELF pnpm would be loaded as JS and fail. The build also re-enables npm git deps (npm_config_allow_git=all): the runtime-postbuild stages the bundled plugins’ runtime deps with a bare npm install, and baileys depends on libsignal from a git URL — npm 11+ disables git deps by default (EALLOWGIT), while upstream’s NodeSource node 22 (npm 10) has no such gate.

Acceptance plan

This candy’s plan: — the runnable spec charly check executes against a live deployment. check: steps are idempotent probes; run: steps change state.

Intent	Step
run	build openclaw from the pinned upstream source commit (cached)
check	the openclaw gateway binary is installed
check	the matrix channel extension is present