Project: Jakarta Agentic AI (ee4j.agentic-ai) Repo: https://github.com/jakartaee/agentic-ai Jenkins: https://ci.eclipse.org/agentic-ai/ The Jenkins release/staging pipelines for this project push release commits and tags to jakartaee/agentic-ai using the Jenkins SSH credential `github-bot-ssh`. The GitHub identity behind that credential is: login: eclipse-agentic-ai-bot id: 281679578 created: 2026-05-04 Current staging attempts fail at `git push origin HEAD:main` with: ERROR: Permission to jakartaee/agentic-ai.git denied to eclipse-agentic-ai-bot. fatal: Could not read from remote repository. The same identity also cannot update the Jenkins Git commit status on this repo — the multibranch scan log reports: Could not update commit status, please check if your scan credentials belong to a member of the organization or a collaborator of the repository. Please grant `eclipse-agentic-ai-bot` Write access to jakartaee/agentic-ai, either as a direct collaborator or via the appropriate jakartaee team (whichever matches the standard configuration used for other Jakarta EE project bots, e.g. jakartaee/faces, jakartaee/rest, jakartaee/data). Failing build for reference: https://ci.eclipse.org/agentic-ai/job/agentic-ai-staging/job/main/79/ Nexus staging repository (already receiving artifacts successfully, so only the GitHub push side is blocked): https://repo.eclipse.org/content/repositories/agentic-ai-maven2-staging/ This is blocking the 1.0.0-M1 community milestone drop. Thanks.