Repository navigation
Hub: trace-forward capability claim + proxy timeout fix (Gate A dependency) - #6
Merged
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
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
Two commits that have been sitting on the
rajatbranch since 2026-08-04 with no PR.db7a992is a hard dependency of the trace-forward Gate A check in ar2#8: the node verifiescapabilities: ["trace-forward"]on the Hub JWT, and this is the commit that issues it.d1da1ab— proxy timeout fixdb7a992— issuecapabilities: ["trace-forward"]for users withrole="authority"; look forseed_geoidin the proxied payloadWhy this matters
maindoes not carry the capability claim. Deployed frommaintoday, no user is ever issuedcapabilities, so everyPOST /traceforwardfails Gate A with 403 regardless of credentials. The trace-forward feature is inoperable against hubmain.Test plan
role="authority", log in, decode the JWT, confirmcapabilities: ["trace-forward"]is presentrole="farmer", confirm the claim is absentscripts/e2e_traceforward.shfrom ar2 against this hub: the Tier 3 path returns 200, the farmer path returns 403 on Gate AMade with Cursor