Skip to content

ci: add PR-time build coverage for Dockerfile.package agent targets #1420

Description

@chaodu-agent

Description

Dockerfile.package agent targets (e.g. the Claude target with its CLAUDE_AGENT_ACP_VERSION / CLAUDE_CODE_VERSION pins and OPENAB_AGENT_COMMAND / OPENAB_AGENT_AUTH_COMMAND defaults) have no pull-request build or runtime verification. The only workflow that builds them (pre-beta-build.yml) is triggered by schedule/workflow_dispatch, so changes to the package targets are first exercised after merge while publishing images.

Raised by the review panel on #1419 (finding F3): that PR changed the package Claude target pins and runtime/auth defaults with no PR-time verification. Mitigated there by live-verifying the equivalent Dockerfile.claude content (same pins/env) as image pr1419-claude on ECS, but the gap is structural.

Use Case

A PR that edits Dockerfile.package should get the same smoke coverage as Dockerfile.claude/Dockerfile.unified targets: build the target with its bins context, then verify the agent binaries exist, pinned versions match the Dockerfile ARGs, both OPENAB_AGENT_COMMAND/OPENAB_AGENT_AUTH_COMMAND defaults are correct, and the ACP initialize handshake succeeds — mirroring the pattern in docker-smoke-test-unified.yml.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions