Represent dependency-satisfied review outcomes in the delivery loop

[flyingrobots]

Claim

The delivery-loop protocol must represent review findings satisfied by producer-owned evidence in another repository without misclassifying them as stale or unreproducible and without forcing consumer-side mutation.

Acceptance criteria

• After two autonomous Code Lawyer passes, the loop escalates.
• An operator may authorize one additional disposition or remediation pass by naming the admitted findings; authorization does not reset the autonomous budget.
• SATISFIED_BY_DEPENDENCY is a first-class outcome with owning repository, issue, PR, commit, consumer-change requirement, and rationale fields.
• A disposition-only authorization cannot mutate source or documentation on the reviewed PR.
• The Echo #700 / Hello Echo Prove durable Hello Echo execution #17 closure is recorded as the motivating cross-repository example.
• The legacy prompt remains operative until the self-hosted loop replaces it.

Validation

• Markdown lint.
• git diff --check.

Non-goals

• Implementing the self-hosted loop.
• Adding a mutation or fault-injection seam.
• Reopening Hello Echo PR Prove durable Hello Echo execution #17.

[coderabbitai]

🔗 Related PRs

#6 - Establish delivery-loop hosting feasibility [merged]
#15 - Restore Pure Hello Echo as Roadmap A [merged]
#17 - Prove durable Hello Echo execution [open]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!