Repository navigation
Conversation
Author
|
Superseded by #6. The first failed security run remains recorded; the fresh single-parent candidate corrects the stale version fixture and enables the affected isolated Docker integration tests. No checks or history were bypassed. |
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
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.
Scope
Preserve confirmed authorization-loss terminal evidence when Proxy transport closes first. Distinguish confirmed denial from unavailable checks while keeping every non-allowed check fail closed. Freeze one terminal event and retain the existing total report budget.
Verification
Adds controlled barrier tests for proxy-first and host-first cancellation, expiry, outages, completed work and terminal retries. Local formatting and exact-tree checks pass; Go tests, race tests, security scans, package reproduction and required CodeQL must pass in the normal official workflow before merge. No production deployment or runtime patch.
Compatibility
Existing wire protocols, ordinary JWT/Full behavior, completion spool and SHA256 package checks remain unchanged. Node caller exact-version binding is updated separately.