Context
During the completion of PR #10747, a commit message included a Co-authored-by footer using the GitHub noreply email address (neo-gemini-3-1-pro@users.noreply.github.com). This violates AGENTS.md §0 Critical Gate 4: "No <noreply@*> Co-Authored-By footers."
The Problem
The agent swarm (Gemini, Claude, GPT) currently defaults to using .noreply.github.com addresses when generating git footers. However, all three maintainer agents possess valid @neomjs.com email addresses (e.g., neo-gemini-3-1-pro@neomjs.com). Continuing to use noreply addresses pollutes commit logs and breaks attribution tracking.
The Architectural Reality
Agents interact directly with git via the command line and construct commit messages/PR descriptions in the pull-request skill. There is currently no strict enforcement of the exact email strings agents should use for themselves or each other beyond the negative constraint ("don't use noreply").
The Fix
- Standardize all agent email domains to
@neomjs.com in our documentation.
- Update the
pull-request skill and/or AGENTS.md to explicitly map the triad usernames to their respective @neomjs.com email addresses.
- Ensure agents utilize these valid email addresses for any
Co-authored-by footers.
Contract Ledger Matrix
| Target Surface |
Source of Authority |
Proposed Behavior |
Fallback |
Docs |
Evidence |
| Git Footers & Commits |
AGENTS.md / pull-request skill |
Swarm agents must use @neomjs.com addresses (e.g. neo-gemini-3-1-pro@neomjs.com) |
None |
Update AGENTS.md |
L2 Static Verification |
Acceptance Criteria
Out of Scope
Human user email configurations or historical commit rewrites.
Avoided Traps / Gold Standards Rejected
Ignoring the noreply default. While typical LLM assistants rely on anonymous or generic tags, the Neo Triad Swarm members are equal maintainers and require stable, professional attribution in the repository history.
Related
Origin Session ID: 16d941df-38f0-41f4-92e7-bd82aed48dfa
Context
During the completion of PR #10747, a commit message included a
Co-authored-byfooter using the GitHub noreply email address (neo-gemini-3-1-pro@users.noreply.github.com). This violatesAGENTS.md§0 Critical Gate 4: "No<noreply@*>Co-Authored-Byfooters."The Problem
The agent swarm (Gemini, Claude, GPT) currently defaults to using
.noreply.github.comaddresses when generating git footers. However, all three maintainer agents possess valid@neomjs.comemail addresses (e.g.,neo-gemini-3-1-pro@neomjs.com). Continuing to use noreply addresses pollutes commit logs and breaks attribution tracking.The Architectural Reality
Agents interact directly with git via the command line and construct commit messages/PR descriptions in the
pull-requestskill. There is currently no strict enforcement of the exact email strings agents should use for themselves or each other beyond the negative constraint ("don't use noreply").The Fix
@neomjs.comin our documentation.pull-requestskill and/orAGENTS.mdto explicitly map the triad usernames to their respective@neomjs.comemail addresses.Co-authored-byfooters.Contract Ledger Matrix
AGENTS.md/pull-requestskill@neomjs.comaddresses (e.g.neo-gemini-3-1-pro@neomjs.com)AGENTS.mdAcceptance Criteria
@neomjs.comemail mapping for all 3 maintainer agents (neo-gemini-3-1-pro,neo-opus-4-7,neo-gpt).Co-authored-bytags.Out of Scope
Human user email configurations or historical commit rewrites.
Avoided Traps / Gold Standards Rejected
Ignoring the noreply default. While typical LLM assistants rely on anonymous or generic tags, the Neo Triad Swarm members are equal maintainers and require stable, professional attribution in the repository history.
Related
Origin Session ID: 16d941df-38f0-41f4-92e7-bd82aed48dfa