Context
During the execution of the Sunset Protocol, agents are required to ping @me via the A2A mailbox. However, recent tests revealed this fails silently. Concurrently, a previous PR (#10417) failed to close its linked issue (#10217) because it embedded the magic close keyword inside a conversational sentence, violating GitHub's syntax requirements.
The Problem
MailboxService does not resolve the @me alias to the current agent identity. Because @me is not a registered node in the Native Edge Graph, GraphService.linkNodes's Foreign Key guard silently culls the SENT_TO edge, preventing message delivery.- The
pull-request skill references did not explicitly mandate the use of strict, newline-isolated magic keywords (e.g., Resolves #N), leading agents to embed them within prose, which GitHub's parser ignores.
The Architectural Reality
MailboxService.mjs: normalizeMailboxTarget(to) acts as the gatekeeper for canonicalizing addresses before passing them to the Edge Graph..agent/skills/pull-request/references/pull-request-workflow.md: The authoritative reference for agent PR construction logic.
The Fix
- Update
normalizeMailboxTarget(to, sentBy) in MailboxService.mjs to dynamically map @me to the sentBy identity node.
- Update
.agent/skills/pull-request/references/pull-request-workflow.md (Section 9: PR Body Hygiene) to add "The Syntax-Exact Keyword Mandate", strictly forbidding conversational embeds for closing keywords.
Acceptance Criteria
Out of Scope
- Modifying other Mailbox alias resolutions outside of
@me.
- Retroactively fixing previous PR bodies other than closing the stranded ticket (#10217).
Avoided Traps
- Trap: Attempting to seed a literal
@me node into the Edge Graph. Avoided: Resolving @me to the dynamic sentBy ID keeps the graph clean and correctly links the message to the actual agent identity.
Related
Origin Session ID: 49e9b05a-0581-4fb7-861f-7e4970ea4c2b
Retrieval Hint: "MailboxService @me routing fix and pull-request syntax mandate"
Context
During the execution of the Sunset Protocol, agents are required to ping
@mevia the A2A mailbox. However, recent tests revealed this fails silently. Concurrently, a previous PR (#10417) failed to close its linked issue (#10217) because it embedded the magic close keyword inside a conversational sentence, violating GitHub's syntax requirements.The Problem
MailboxServicedoes not resolve the@mealias to the current agent identity. Because@meis not a registered node in the Native Edge Graph,GraphService.linkNodes's Foreign Key guard silently culls theSENT_TOedge, preventing message delivery.pull-requestskill references did not explicitly mandate the use of strict, newline-isolated magic keywords (e.g.,Resolves #N), leading agents to embed them within prose, which GitHub's parser ignores.The Architectural Reality
MailboxService.mjs:normalizeMailboxTarget(to)acts as the gatekeeper for canonicalizing addresses before passing them to the Edge Graph..agent/skills/pull-request/references/pull-request-workflow.md: The authoritative reference for agent PR construction logic.The Fix
normalizeMailboxTarget(to, sentBy)inMailboxService.mjsto dynamically map@meto thesentByidentity node..agent/skills/pull-request/references/pull-request-workflow.md(Section 9: PR Body Hygiene) to add "The Syntax-Exact Keyword Mandate", strictly forbidding conversational embeds for closing keywords.Acceptance Criteria
MailboxServicecorrectly routes messages addressed to@meback to the sender's inbox.pull-request-workflow.mdcontains the explicit syntax mandate for magic keywords.Out of Scope
@me.Avoided Traps
@menode into the Edge Graph. Avoided: Resolving@meto the dynamicsentByID keeps the graph clean and correctly links the message to the actual agent identity.Related
Origin Session ID: 49e9b05a-0581-4fb7-861f-7e4970ea4c2b Retrieval Hint: "MailboxService @me routing fix and pull-request syntax mandate"