Skip to content

feat(persistent-worker): critic ping-pong protocol #110

@hadamrd

Description

@hadamrd

Parent

Part of #95 — persistent-worker epic. Depends on #108, #109.

What

On a critic verdict of REQUEST_CHANGES, transition AWAITING_CRITIC → REVISING and dispatch a follow-up worker session that resumes the SDK session_id with the critic comments as the next user message.

Acceptance

NOT in scope

File pointers

  • src/forge_loop/critic.py — verdict mapping
  • src/forge_loop/runner/dispatch.py — ping-pong loop integration
  • src/forge_loop/_critic_sdk.py — verdict comments threaded into next dispatch

Test matrix

  • unit: APPROVE verdict transitions to MERGED.
  • unit: REQUEST_CHANGES verdict creates a REVISING tick.
  • unit: BLOCK verdict ABANDONS with the right label.
  • unit: the next dispatch prompt includes the critic comments.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions