[KreutzM]

Summary

• Makes one parent Hermes session responsible for the full issue lifecycle through implementation, independent review, repair, re-review, CI and review-ready handoff.
• Makes a fresh independent reviewer leaf a required gate for substantive product-code PRs.
• Defines a bounded review/fix/re-review convergence loop and requires another review after CI-driven code changes.
• Keeps reviewer children read-only by default so the parent remains owner of the primary feature branch under worktree isolation.
• Keeps model/provider choice out of repo policy while explicitly supporting a different runtime delegation.model for reviewer children.

Issue

Closes #10

Design / Decisions

The workflow remains flat (parent -> leaf) and compatible with max_spawn_depth: 1. With delegation.worktree_isolation: true, reviewer children branch from current HEAD, so the parent commits the exact review target before dispatching review. Reviewer children report findings; the parent evaluates and applies fixes on the primary feature branch. This avoids needless child-branch integration for read-only review.

The convergence guard is three review/fix rounds. If a real blocker or semantic disagreement remains after that, the PR stays not-ready and only the unresolved decision is escalated.

Concrete model/provider IDs remain user-runtime choices, not repository architecture.

Validation

• Documentation/policy-only scope.
• Changed files: .hermes.md and docs/AGENT_OPERATING_MODEL.md.
• No product code, dependency, credential or merge-policy changes.
• Tracker Issue Agent-first development backlog and handoff tracker #4 updated separately to put Make Hermes issue work end-to-end with autonomous review loops #10 before the next product task.
• Policy preserves explicit user authorization for merging main.

No product test suite was run because this PR changes only agent workflow documentation.

Remaining / Follow-ups

• User-level runtime should pin a reviewer model via delegation.model / delegation.provider if a heterogeneous parent/reviewer workflow is desired.
• After merge, test the one-session orchestration on the next product issue without manually launching a reviewer session.

Handoff

Branch: agent/10-autonomous-review-loop

A fresh reviewer should read Issue #10, .hermes.md, docs/AGENT_OPERATING_MODEL.md, and this PR; verify the autonomous review loop is internally consistent with worktree isolation and the no-unapproved-merge boundary. Do not merge without explicit user authorization.