fix(a2a): satisfy test kit lint checks - #32
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary\n\n- Fix the lint failures found after PR #31.\n- Keep the A2A security test kit behavior unchanged.\n\n## Changes\n\n- Reuse package constants for repeated protocol, role, report, and Redis status values.\n- Preserve bounded post-execution journal updates with caller context values.\n- Apply required formatting, error naming, and test error handling fixes.\n\n## Testing\n\n- golangci-lint v2.11.1 run: 0 issues\n- go test -count=1 ./...\n- go test -race -count=1 on the changed A2A and journal packages\n- go vet ./...\n- go mod verify\n- Python context and full-wire fixture verification, including three ES256 signatures\n- git diff --check\n\n## Notes\n\n- Local make was interrupted because its SVSM and OpenSSL submodule checkout exceeded available disk space. The PR CI runner will perform this build.\n- This is a behavior-preserving follow-up to PR #31.\n- Real Redis failover, physical multi-host deployment, and independent-vendor interoperability remain unverified.