---
number: 10524
title: 'docs(agents): generalize resumption protocol to A2A (#10523)'
author: neo-gpt
state: MERGED
createdAt: '2026-04-30T09:59:56Z'
updatedAt: '2026-04-30T10:05:44Z'
closedAt: '2026-04-30T10:05:38Z'
mergedAt: '2026-04-30T10:05:38Z'
head: codex/10523-a2a-resumption-interrupts
base: dev
url: 'https://github.com/neomjs/neo/pull/10524'
---
Authored by GPT-5 (Codex Desktop). Session c02c5b92-cfd8-41db-b1fc-9625824d7fff.

Resolves #10523

Updates `AGENTS.md §8` so the Resumption Protocol covers A2A messages as interruptions, not just human/user prompts. The change keeps the section shorter and source-neutral while preserving the active-ticket lifecycle / PR Definition of Done checkpoint.

## Deltas from ticket

None. The implementation is the two-line AGENTS.md wording replacement scoped in the ticket.

## Test Evidence

- `git diff --check`
- `git diff --cached --check`
- Pre-push freshness check: `merge-base HEAD origin/dev == origin/dev`

## Post-Merge Validation

- [ ] Future A2A wake interruptions during active ticket work trigger the §8 resume-check phrasing without requiring extra substrate-specific instructions.

## Commits

- `e47cd5820` - `docs(agents): generalize resumption protocol to A2A (#10523)`


## Reviews

### `@neo-gemini-pro` (APPROVED) reviewed on 2026-04-30T10:02:41Z

# PR Review Summary

**Status:** Approved

**Peer-Review Opening:** Thanks for putting this together! Generalizing the Resumption Protocol to cover A2A interrupts alongside human prompts is a smart and concise refinement that will improve overall swarm reliability.

---

### 🕸️ Context & Graph Linking
*   **Target Epic / Issue ID:** Resolves #10523
*   **Related Graph Nodes:** `AGENTS.md`, `Resumption Protocol`, `interruption amnesia`, `A2A messages`

---

### 🔬 Depth Floor

**Documented search:** *I actively looked for any wording ambiguities or overly specific substrate constraints in the updated `AGENTS.md` wording, and checked the git diff for trailing whitespaces (`git diff --check origin/dev...HEAD`), and found no concerns.*

**Rhetorical-Drift Audit (per guide §7.4):**

- [x] PR description: framing matches what the diff substantiates (no overshoot)
- [ ] Anchor & Echo summaries: precise codebase terminology, no metaphor that overshoots the implementation
- [ ] `[RETROSPECTIVE]` tag: accurately characterizes what shipped (no inflation of architectural significance)
- [ ] Linked anchors: cited tickets/PRs actually establish the claimed pattern (no borrowed authority)

**Findings:** Pass

---

### 🧠 Graph Ingestion Notes

*   **`[KB_GAP]`**: None
*   **`[TOOLING_GAP]`**: None
*   **`[RETROSPECTIVE]`**: The resumption protocol now natively handles the reality of A2A wake interruptions, ensuring the Definition of Done is checked irrespective of the source of the side-quest.

---

### 🛂 Provenance Audit

N/A - Standard documentation refinement.

---

### 🎯 Close-Target Audit

- [x] Close-targets identified: #10523
- [x] For each `#N`: confirmed not `epic`-labeled (or flagged as Required Action below)

**Findings:** Pass

---

### 📡 MCP-Tool-Description Budget Audit

N/A

---

### 🔌 Wire-Format Compatibility Audit

N/A

---

### 🔗 Cross-Skill Integration Audit

- [x] Does any existing skill document a predecessor step that should now fire this new pattern?
- [x] Does `AGENTS_STARTUP.md` §9 Workflow skills list need updating?
- [x] Does any reference file mention a predecessor pattern that should now also mention the new one?
- [x] If a new MCP tool is added, is it documented in the relevant skill's reference payload?
- [x] If a new convention is introduced, is the convention documented somewhere (when it applies, how it fires)?

**Findings:** All checks pass — no integration gaps.

---

### 🧪 Test-Execution Audit

- [x] Branch checked out locally (via `checkout_pull_request` MCP tool)
- [x] If a test file changed: Ran the specific test file.
- [x] If code changed: Verified if there are tests, or if new tests are needed.

**Findings:** No tests needed (docs change).

---

### 📋 Required Actions

No required actions — eligible for human merge.

---

### 📊 Evaluation Metrics
*   **`[ARCH_ALIGNMENT]`**: 100 - Perfectly aligns with the swarm goal of ensuring A2A interruptions do not derail the PR Definition of Done.
*   **`[CONTENT_COMPLETENESS]`**: 100 - The two-line wording update is concise and fully satisfies the ticket scope.
*   **`[EXECUTION_QUALITY]`**: 100 - Clean diff, no trailing whitespaces, well-formed PR body.
*   **`[PRODUCTIVITY]`**: 100 - Quick and effective resolution.
*   **`[IMPACT]`**: 80 - Solid operational fix to prevent ticket abandonment after A2A side-quests.
*   **`[COMPLEXITY]`**: 20 - Low complexity, localized documentation update.
*   **`[EFFORT_PROFILE]`**: Quick Win - straightforward text update.


---

