React to PR review comments and remediate (requested changes / inline) #1169

Closed
opened 2026-10-27 13:39:18 +00:00 by sam · 0 comments
Owner

Archie opens a PR and never learns what was said about it. Add a PullRequestReviewReader forge surface (landed), a review-comment reaction, an owned-task guard, and a remediate workflow that fixes flagged code on the existing PR branch, pushes, and replies.

Design: docs/prds/pr-review-remediation.md, ratified 2026-09-19 (PR #871).
Parent: archie-core-7d5u event sources and typed reactions.

Sequencing is the PRD's, and the order is load-bearing: producers come last,
because a producer built before its consumer and its authorization guard
publishes into nothing and becomes an unguarded intake the moment a stream
appears. PR #859 built step 5 first and was closed unmerged.

.1 ARCHIE_REACTIONS fan-out stream
(forge read surface: landed on main)
.3 ReviewCommentEnvelope + kinded idempotency key
.2 Owned-task guard: (owner, repo, pr_number) lookup, RPC, index
.4 remediate workflow, one run per review
.5 Webhook intake
.6 Poll backstop

Close reason

Landed end to end per the mirror's close record: the ARCHIE_REACTIONS stream (forge PR), the owned-task guard (internal/infrastructure/postgres/ownership.go, verified in-tree), the review-comment envelope with kinded idempotency key, the remediate workflow, webhook intake for review and comment events, and the poll backstop with persisted cursors (internal/daemon/review_scan.go, verified in-tree). All seven child beads (.1-.7) are closed; the parent was left in progress after their landing by accident rather than by plan. Forced past the stale assignment (claim holder 'samcharles93' mirrors the same operator) because every child is closed and the landing evidence is in tree.


Imported from beads archie-core-8li9 · GitHub #813 · type feature · priority P2 · created 2026-09-09 · closed 2026-09-29

Archie opens a PR and never learns what was said about it. Add a PullRequestReviewReader forge surface (landed), a review-comment reaction, an owned-task guard, and a remediate workflow that fixes flagged code on the existing PR branch, pushes, and replies. Design: docs/prds/pr-review-remediation.md, ratified 2026-09-19 (PR #871). Parent: archie-core-7d5u event sources and typed reactions. Sequencing is the PRD's, and the order is load-bearing: producers come last, because a producer built before its consumer and its authorization guard publishes into nothing and becomes an unguarded intake the moment a stream appears. PR #859 built step 5 first and was closed unmerged. .1 ARCHIE_REACTIONS fan-out stream (forge read surface: landed on main) .3 ReviewCommentEnvelope + kinded idempotency key .2 Owned-task guard: (owner, repo, pr_number) lookup, RPC, index .4 remediate workflow, one run per review .5 Webhook intake .6 Poll backstop ### Close reason Landed end to end per the mirror's close record: the ARCHIE_REACTIONS stream (forge PR), the owned-task guard (internal/infrastructure/postgres/ownership.go, verified in-tree), the review-comment envelope with kinded idempotency key, the remediate workflow, webhook intake for review and comment events, and the poll backstop with persisted cursors (internal/daemon/review_scan.go, verified in-tree). All seven child beads (.1-.7) are closed; the parent was left in progress after their landing by accident rather than by plan. Forced past the stale assignment (claim holder 'samcharles93' mirrors the same operator) because every child is closed and the landing evidence is in tree. --- _Imported from beads `archie-core-8li9` · GitHub #813 · type feature · priority P2 · created 2026-09-09 · closed 2026-09-29_
sam added the mediumfeature labels 2026-10-27 13:39:18 +00:00
sam self-assigned this 2026-10-27 13:39:18 +00:00
sam closed this issue 2026-10-27 13:39:18 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1169