Repository navigation
fix(relay): expose agent identity separately from channel roles - #9037
Open
jpeedikayil wants to merge 2 commits into
Open
jpeedikayil wants to merge 2 commits into
jpeedikayil wants to merge 2 commits into
Conversation
Publish optional agent markers from community ownership in signed rosters. Reuse the bounded enrollment refresh for every active role while keeping permission roles and owner attribution unchanged. Co-authored-by: Codex <noreply@openai.com> Signed-off-by: Josiah Peedikayil <174502694+jpeedikayil@users.noreply.github.com>
Use the same branch base setting as GitHub CLI for stacked PRs. Fetch the target before comparing and reject unavailable or invalid bases. Keep the remaining push checks unchanged. Co-authored-by: Codex <noreply@openai.com> Signed-off-by: Josiah Peedikayil <174502694+jpeedikayil@users.noreply.github.com>
joahg
approved these changes
Nov 5, 2026
joahg
left a comment
joahg
left a comment
Member
There was a problem hiding this comment.
🤖 Agent tags are added to the roster snapshot without changing roles or exposing owners, and republish now covers every active role. Note the pre-push guard now fails when the base fetch fails, so offline pushes are blocked; the CONTRIBUTING note covers it.
This branch has not been deployed
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
Follow up on #8494 with agent identity evidence that is separate from channel permissions. Its ordinary bot label does not describe agents who hold Admin, Owner or Guest roles.
Add optional
agenttags to the relay-signed channel roster, using the community's recorded owner. Extend the existing enrollment refresh to all active roles, with the same concurrency bound and publication locks. The tags identify agents without exposing their owners or granting permissions.Document the additional identity evidence alongside verified owner attestations. Existing snapshots gain tags when republished; this change adds no upgrade backfill. The app companion consumes the tags in Members.
A separate tooling commit makes the pre-push overlap guard use GitHub CLI's configured PR base, defaulting to
main. It rejects invalid or unavailable bases and keeps the remaining checks enabled. Regression tests cover ordinary and stacked branches.Related issue
Stack Info: Stacked on #8494. This draft targets that PR's branch and contains only the follow-up. It depends on #8494 and its migration prerequisites; it will need rebasing and retargeting after that work merges. The additional display-evidence contract needs maintainer agreement before merge.
Testing
No manual testing. Human acceptance and repository-wide CI remain pending.
Generated with Codex