A PR is never reviewed by the harness that wrote it. With `selfReview`
on, an own PR gets both roles: `land` on the head branch and `review-pr`
on a local pull/N/head checkout, which is what keeps routing unambiguous
with two sessions on one PR.
The reviewer is drawn from a configured roster of harness+model+effort
combinations, excluding the author's harness, picking among the
least-used so every combination keeps getting exercised and a new entry
goes out immediately. Each pick is appended to a JSONL ledger, which is
what makes rating them possible later.
Drafts never get a reviewer; the draft-to-ready flip spawns one.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Titles were gt-/gh-prefixed and carried the repo, which duplicates how
the sidebar is already organised. Number first so it sorts, then a slug
of the PR title.
Routing no longer looks at the title at all -- a PR title can be edited
under a running session -- and matches the worktree branch instead,
covering both the head branch and the local pull/N/head one.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The webhook allowlist never matched the "*" repo pattern, so every gitea
delivery was dropped as unwatched. Each drop returns 202, which the forge
records as a successful delivery, and only accepts and signature failures
were logged -- so a delivery that arrived and was discarded looked exactly
like no delivery at all.
Gitea also flags a PR comment with is_pull rather than nesting a
pull_request link the way github does.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Gitea sends action `synchronized` where GitHub sends `synchronize`, so
pushes to a PR branch were filtered out as noise.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
A started session waited for the next tick to get its opening prompt, and
the pending flag lived in memory, so a restart in between left it sitting
empty with nothing to do.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
A hint withheld because the session is busy left no trace, which reads
identical to no event at all.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Three bugs the first live run surfaced:
aoe reports `worktree.main_repo_path` with a trailing slash, so the
session lookup never matched and the daemon created a second session for
a PR that already had one.
The gitea token belongs to a separate bot account, so PRs opened by
agents looked like someone else's work and got `review-pr` instead of
`land`. `self` now takes a list of logins per forge.
A webhook whose signature fails logged nothing, which makes a mismatched
secret indistinguishable from no deliveries at all.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
One systemd daemon watches GitHub and Gitea and routes each PR to an aoe
session: `land` for PRs you authored, `review-pr` for everyone else's.
It reads metadata only and sends a single inert hint line, so untrusted
PR text never passes through the thing that types into agent prompts.
Routing is derived from `aoe list --json --all` by worktree branch, so
no claim files and no daemon database. Dedupe stays in the session via
`pr-<N>-seen`, which makes hints idempotent and a swallowed send
self-healing.
`land` loses its watcher machinery to the daemon and keeps the policy
and per-event handlers; `pr-common` holds what both skills share.
Review sessions run non-yolo without trusted hooks and never run the
branch's code.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
naps62-yolo
Miguel Palhas