Context
During continuous agent sessions, an agent can succumb to "interruption amnesia." If the human commander injects a diagnostic sub-question or testing request (e.g., "test this A2A message" or "run this node script") while the agent is midway through a ticket's lifecycle, the agent will typically resolve the sub-question and halt. It frequently drops the overarching "Definition of Done" (executing the pull-request skill) because its immediate context window was hijacked by the side-quest.
The Problem
AGENTS.md currently defines the Pull Request Mandate (Section 7), but it lacks an explicit behavioral guardrail for recovering from user-injected interruptions. Without a designated Resumption Protocol, the swarm relies on the human commander to manually remind the agent to "go back and finish the PR."
The Architectural Reality
The Agent OS relies on system prompts (AGENTS.md, AGENTS_STARTUP.md) to govern behavioral loops. The state machine of a ticket execution is fragile against prompt-injections from the user that shift the immediate goalpost.
The Fix
Introduce a formal "Resumption Protocol" clause within AGENTS.md. This clause will explicitly instruct agents to re-evaluate their ticket completion status (specifically, checking the PR Definition of Done) immediately after satisfying any user-injected diagnostic, meta-request, or side-quest.
Acceptance Criteria
Out of Scope
Implementing hard-coded, stateful tracking of ticket progress within the Node.js Orchestrator. This is strictly a behavioral protocol enhancement via the system prompt text.
Avoided Traps / Gold Standards Rejected
- Trap: Relying on the human commander to baby-sit the agent's workflow state. The agent must be autonomously resilient to interruptions.
- Trap: Adding complex SQLite state-machine tracking for "ticket progress" when a simple cognitive checkpoint in the prompt is sufficient to trigger a context re-evaluation.
Origin Session ID: 0b29a8fa-c6b0-42e2-ab3b-8015a99db2d8
Context During continuous agent sessions, an agent can succumb to "interruption amnesia." If the human commander injects a diagnostic sub-question or testing request (e.g., "test this A2A message" or "run this node script") while the agent is midway through a ticket's lifecycle, the agent will typically resolve the sub-question and halt. It frequently drops the overarching "Definition of Done" (executing the
pull-requestskill) because its immediate context window was hijacked by the side-quest.The Problem
AGENTS.mdcurrently defines the Pull Request Mandate (Section 7), but it lacks an explicit behavioral guardrail for recovering from user-injected interruptions. Without a designated Resumption Protocol, the swarm relies on the human commander to manually remind the agent to "go back and finish the PR."The Architectural Reality The Agent OS relies on system prompts (
AGENTS.md,AGENTS_STARTUP.md) to govern behavioral loops. The state machine of a ticket execution is fragile against prompt-injections from the user that shift the immediate goalpost.The Fix Introduce a formal "Resumption Protocol" clause within
AGENTS.md. This clause will explicitly instruct agents to re-evaluate their ticket completion status (specifically, checking the PR Definition of Done) immediately after satisfying any user-injected diagnostic, meta-request, or side-quest.Acceptance Criteria
AGENTS.mdis updated with a new section titled "The Resumption Protocol".pull-requestskill) after completing a human-injected side-quest.ticket-intakeskill is reviewed to ensure alignment with this new resumption behavior.Out of Scope Implementing hard-coded, stateful tracking of ticket progress within the Node.js Orchestrator. This is strictly a behavioral protocol enhancement via the system prompt text.
Avoided Traps / Gold Standards Rejected
Origin Session ID: 0b29a8fa-c6b0-42e2-ab3b-8015a99db2d8