Context
During the review and merge of PR #10747 (and PR #10750 mapping canonical @neomjs.com attribution), it was noted that while commit author headers successfully mapped to @neomjs.com, the Co-authored-by git trailers inside commit messages still used <noreply@...> mapping (e.g. Co-authored-by: neo-gemini-3-1-pro <neo-gemini-3-1-pro@users.noreply.github.com>).
The Problem
AGENTS.md §0 Invariant 4 explicitly forbids <noreply@*> Co-Authored-By footers. Currently, the agents either strip these or leave them with GitHub's default noreply mapping. Since all triad swarm agents (@neo-gemini-3-1-pro, @neo-opus-4-7, @neo-gpt) now possess valid @neomjs.com email addresses, they should use these addresses canonically across all authorship metadata (author, committer, and co-authored-by).
The Architectural Reality
- Agent GitHub profiles and
git config now reflect the @neomjs.com mapping following PR #10750.
- The Git trailers parsing / generation logic (e.g. inside
pull-request skill or agent prompt boundaries) may still default to GitHub's noreply mapping.
The Fix
- Update any workflow documentation or scripts that inject
Co-Authored-By footers to use the explicit @neomjs.com addresses for the triad swarm:
neo-gemini-3-1-pro@neomjs.comneo-opus-4-7@neomjs.comneo-gpt@neomjs.com
- Audit
pull-request skill and any git automation to ensure noreply addresses are cleanly rewritten.
Contract Ledger Matrix
| Target Surface |
Source of Authority |
Proposed Behavior |
Fallback |
Docs |
Evidence |
| Swarm Commit Footers |
AGENTS.md §0 / Git Trailers |
Commit trailers must use @neomjs.com for valid swarm identities |
Reject commit if <noreply@*> is detected |
Update AGENTS.md Invariant 4 |
N/A |
Acceptance Criteria
Out of Scope
- Modifying historical commits (only forward-looking changes).
- Changing authorship models for external contributors.
Origin Session ID
Origin Session ID: 79042442-bebc-431d-8968-8a2e7d7a1151
Context
During the review and merge of PR #10747 (and PR #10750 mapping canonical @neomjs.com attribution), it was noted that while commit author headers successfully mapped to
@neomjs.com, theCo-authored-bygit trailers inside commit messages still used<noreply@...>mapping (e.g.Co-authored-by: neo-gemini-3-1-pro <neo-gemini-3-1-pro@users.noreply.github.com>).The Problem
AGENTS.md§0 Invariant 4 explicitly forbids<noreply@*>Co-Authored-Byfooters. Currently, the agents either strip these or leave them with GitHub's default noreply mapping. Since all triad swarm agents (@neo-gemini-3-1-pro,@neo-opus-4-7,@neo-gpt) now possess valid@neomjs.comemail addresses, they should use these addresses canonically across all authorship metadata (author, committer, and co-authored-by).The Architectural Reality
git confignow reflect the@neomjs.commapping following PR #10750.pull-requestskill or agent prompt boundaries) may still default to GitHub's noreply mapping.The Fix
Co-Authored-Byfooters to use the explicit@neomjs.comaddresses for the triad swarm:neo-gemini-3-1-pro@neomjs.comneo-opus-4-7@neomjs.comneo-gpt@neomjs.compull-requestskill and any git automation to ensure noreply addresses are cleanly rewritten.Contract Ledger Matrix
AGENTS.md§0 / Git Trailers@neomjs.comfor valid swarm identities<noreply@*>is detectedAGENTS.mdInvariant 4Acceptance Criteria
pull-requestskill or relevant automation rewrites swarmCo-Authored-Byfooters to use@neomjs.com.AGENTS.md§0 Invariant 4 is updated to actively require@neomjs.comtrailers rather than just forbiddingnoreply.Out of Scope
Origin Session ID
Origin Session ID: 79042442-bebc-431d-8968-8a2e7d7a1151