You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Test 26 still targeted several retired HiClaw contracts after the hard rename: the QwenPaw provider ID, embedded controller container and data directory, Kubernetes API path, and Worker/Team apiVersion values. Align the integration test with the canonical AgentTeams runtime and API contracts so it can create resources and validate the generated workspace once CI reaches the shard.
This changes only the integration test; production behavior already uses these AgentTeams values.
Verification
extracted workspace projection check against an agentteams-gateway fixture: ok
exact static contract check for controller, token path, API group, resource declarations, and provider ID
CI attribution: all 9 translation/base/image build checks passed. I inspected the raw logs for all 10 failed integration jobs in run #1660; every matrix entry exits during install-embedded, before its test shard starts, with LLM API Key is required. This is the same base pull_request_target secret-name bootstrap regression addressed by #1026, not a failure of this focused test assertion. I am keeping this branch unchanged.
RerankerGuo
changed the title
fix(test): expect AgentTeams provider in QwenPaw projection
fix(test): align QwenPaw test with AgentTeams contracts
Jul 15, 2026
Latest-head CI attribution: all 9 translation/base/image checks passed for c5596da. I inspected the raw logs for all 10 failed matrix jobs in run #1662; each log has an empty AGENTTEAMS_LLM_API_KEY, exits from install-embedded with code 2 and LLM API Key is required, and produces no shard test output. This is the same pull_request_target base-workflow secret blocker addressed by #1026, so the locally passing QwenPaw contract patch is unchanged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
RerankerGuo
changed the title
Summary
Test 26 still targeted several retired HiClaw contracts after the hard rename: the QwenPaw provider ID, embedded controller container and data directory, Kubernetes API path, and Worker/Team
apiVersionvalues. Align the integration test with the canonical AgentTeams runtime and API contracts so it can create resources and validate the generated workspace once CI reaches the shard.This changes only the integration test; production behavior already uses these AgentTeams values.
Verification
agentteams-gatewayfixture:okbash -n tests/test-26-qwenpaw-teamharness-plugin-mode.shgo test ./api/v1beta1 ./internal/config ./internal/servicewith Go 1.25.0git diff --checkThe previous integration run stopped during
install-embeddedwith the base-workflow LLM secret issue tracked in #1026, before any test shard ran.