Repository navigation
Conversation
Signed-off-by: Kombiz Lavasany <kombiz@gmail.com>
Signed-off-by: Kombiz Lavasany <kombiz@gmail.com>
Signed-off-by: Kombiz Lavasany <kombiz@gmail.com>
Signed-off-by: Kombiz Lavasany <kombiz@gmail.com>
Signed-off-by: Kombiz Lavasany <kombiz@gmail.com>
The pinned quay.io MinIO digests now answer `unauthorized`, so every job that starts the compose fixtures fails before its tests run. Port main's docker-compose.ci.yml override (2246518) to this branch's split workflows: the desktop integration shards, backend integration, relay E2E and mesh lifecycle jobs select it through COMPOSE_FILE. Local development keeps the pinned images in docker-compose.yml. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Gateway main now refuses a shared submit that omits or mismatches the route's permission_profile and side_effect_class (agent-gateway block#30). backend=shared takes both from BUZZ_ACP_GATEWAY_PERMISSION_PROFILE and BUZZ_ACP_GATEWAY_SIDE_EFFECT_CLASS, accepts read-only values only, and sends them on every submit. The legacy backend rejects these options. A batch still refused as busy at the turn deadline was reported as an unknown outcome, although the daemon never admitted it. Once a lookup proves the submission absent, exhausting the loop now ends Failed. A gateway that never answered a lookup stays unknown, because an earlier harness process may have submitted the same event. Gate both Unix-socket clients so the Windows build compiles; on other targets every connect returns Unsupported. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Review follow-up. Like main's 2246518, run the Rust lane and the mesh lifecycle smoke when either compose file changes, and point the quickstart chart's MinIO images at the published CI image. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Review follow-up. route_session returns the route generation's latest session without checking its policy binding, so a session bound before agent-gateway block#30, or under a changed route policy, refuses every submit. The failure now tells the operator to raise the route's route_generation, which scopes route_session to a fresh session. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Review follow-up Independent review of The other red checks on this PR come from the base branch, not this change. Its private 🤖 Generated with Claude Code |
…adapter--buzz feat(buzz-acp): bridge Buzz to shared gateway sessions
|
Merge receipt, approved by the owner on 2026-10-11. Head CI at this head: 48 checks passed. Rust lint, unit tests, Windows, Relay E2E, backend integration, desktop integration, mesh smoke and security are all green. The one red check is Desktop Smoke E2E shard 4 and its roll-ups. Across 3 attempts it failed a different set of UI specs each time:
The same tree passed that shard on #3's run. These smoke tests run static 🤖 Generated with Claude Code |
58ce91e
into
task/BUZZ-ACP-0524/gateway-acp-on-v0-5-24
Backport of
main's MinIO CI fix (#5, commit 2246518) to the gateway release line that HS-46's Buzz adapter (#3) targets.Why: the pinned
quay.io/minio/*digests indocker-compose.ymlnow returnunauthorized, so every job that starts the compose fixtures fails before running any test. On #3 that is Relay E2E, Backend Integration, both Desktop E2E Integration shards and the mesh lifecycle smoke. #5 fixed this onmain, but this branch splits CI into reusable_ci-*.ymlworkflows, so the cherry-pick conflicts. This is the same change, ported by hand.What:
docker-compose.ci.yml, byte-identical tomain's, which selectsghcr.io/block/buzz-minio:latest(overridable withMINIO_CI_IMAGE). An anonymous GHCR manifest read returned HTTP 200.COMPOSE_FILE: docker-compose.yml:docker-compose.ci.ymlondesktop-e2e-integration-shard,backend-integrationandrelay-e2e(_ci-relay.yml), and onlifecycle-smoke(mesh-lifecycle.yml).docker-compose.ymlis unchanged, so local development keeps the pinned images.Checks run locally: both workflows parse as YAML, and
docker compose -f docker-compose.yml -f docker-compose.ci.yml configresolvesminioandminio-initto the GHCR image. CI on this PR exercises the relay lane, because the path filter includes.github/workflows/_ci-*.yml.Not addressed here: the Docker/GHCR image publish jobs fail on
maintoo ("installation does not exist"). That is estate-wide and separate from this branch.🤖 Generated with Claude Code