Skip to content

feat: define harness-agnostic agent task contract #393

@joryirving

Description

@joryirving

Parent: #392

Define the generic task envelope returned by Dispatch to any harness.

Task types: implement, followup-pr, groom, idle.

The envelope should include task id, type, agent name, lane, issue number, PR number, instructions, acceptance criteria, stop condition, allowed actions, disallowed actions, and report target.

Acceptance:

  • documented contract
  • no harness-specific assumptions
  • idle response supported
  • compatible with existing queue APIs

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or improvement.priority/p0Critical priority.status/backlogNot ready for worker pickup yet.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions