Task: Define Agent Task Protocol (Labels, Templates, Rules)

Context

As part of the "Agent Orchestration" Epic (#7914), we are moving to a hierarchical swarm model where agents coordinate asynchronously using GitHub Issues. To prevent chaos and "garbage in, garbage out," we need a strict contract (Protocol) that defines how agents communicate.

Goal

Create a comprehensive specification file ai/agents/PROTOCOL.md that serves as the "Law" for all autonomous agents in the Neo.mjs ecosystem.

Requirements

1. Label Schema

Define a strict state machine using GitHub labels.

• agent-task:pending: The task is queued and waiting for a worker agent.
• agent-task:in-progress: A worker agent has claimed the task.
• agent-task:blocked: The agent is stuck (derailed) and needs human intervention.
• agent-task:completed: The task is done (PR created or answer provided).
• agent-role:pm: Ticket assigned to a PM agent.
• agent-role:dev: Ticket assigned to a Dev agent.

2. Issue Templates (YAML Contracts)

Define the exact YAML structure that agents must use in the Issue Body.

• Epic -> Ticket Handoff: How a PM Agent describes a task for a Dev Agent.

      role: dev
  goal: "Implement feature X"
  context:
    files: ["src/foo.mjs"]
    requirements: ["Must pass test Y"]

• Ticket -> PR Handoff: How a Dev Agent reports success.

3. Lifecycle Rules

• Claiming: How an agent "locks" a ticket (e.g., assigning itself).
• Derailment: The exact conditions under which an agent must self-report as blocked (e.g., "3 failed attempts at fixing a test").
• Completion: The definition of done (e.g., "PR linked, tests passed").

Output

• A new file: ai/agents/PROTOCOL.md containing the full specification.