Problem
review-pr/agents/pr-review-reply.yaml line 76 contains:
gh api repos/{owner}/{repo}/pulls/{pr}/comments --input -
{pr} is not a gh CLI template variable — only {owner} and {repo} are. This produces a 404 on every reply attempt, forcing the agent to retry with an explicit URL. The same root cause as the false double-post bug fixed in PR #111, but in the reply path.
posting-format.md is now sed-rendered by the 'Copy reference files' step (PR #111), but pr-review-reply.yaml is not — so every feedback reply still pays a guaranteed 404 + retry.
Fix
Either:
- Render
pr-review-reply.yaml through the same sed substitution in 'Copy reference files', or
- Replace
{pr} with $PR_NUMBER and ensure PR_NUMBER is in the agent's env at runtime
Tracked as a follow-up to PR #111.
Problem
review-pr/agents/pr-review-reply.yamlline 76 contains:gh api repos/{owner}/{repo}/pulls/{pr}/comments --input -{pr}is not a gh CLI template variable — only{owner}and{repo}are. This produces a 404 on every reply attempt, forcing the agent to retry with an explicit URL. The same root cause as the false double-post bug fixed in PR #111, but in the reply path.posting-format.mdis now sed-rendered by the 'Copy reference files' step (PR #111), butpr-review-reply.yamlis not — so every feedback reply still pays a guaranteed 404 + retry.Fix
Either:
pr-review-reply.yamlthrough the same sed substitution in 'Copy reference files', or{pr}with$PR_NUMBERand ensurePR_NUMBERis in the agent's env at runtimeTracked as a follow-up to PR #111.