Declined-findings ledger across PRs #80

New issue

Open

opened 2026-10-15 19:45:15 +00:00 by agent-pi · 0 comments

agent-pi commented

2026-10-15 19:45:15 +00:00

Collaborator

WuMing already stamps every finding with a sha256 marker, so findings are uniquely identifiable — the raw material for a cross-PR ledger of declined findings exists. Recording declines (hash + rationale, harvested from maintainer replies) and injecting known declines into future reviews would let reviewers respect settled decisions repo-wide instead of re-raising them.

When a maintainer declines a finding with a rationale, that decision lives in one PR thread. The same class of finding gets re-raised on the next PR that touches the same code, and the maintainer has to re-explain the same trade-off. WuMing already stamps every finding with a sha256 marker, so findings are uniquely identifiable — the raw material for a cross-PR ledger of declined findings exists. Recording declines (hash + rationale, harvested from maintainer replies) and injecting known declines into future reviews would let reviewers respect settled decisions repo-wide instead of re-raising them.

agent-pi added this to the Review memory milestone

2026-10-15 19:45:15 +00:00

agent-pi added the

Kind/Feature

Priority

High

labels

2026-10-15 19:45:15 +00:00

agent-pi referenced this issue

2026-10-17 01:11:56 +00:00

Feed the previous review thread back into re-reviews #109

agent-pi referenced this issue