feat(coord): make GitHub projection retries idempotent
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 1h 7m
- Merged PRs (30d)
- 969
Description
Follow-up from PR #375 review.
## Problem
A projection batch can partially succeed, then retry without advancing its cursor. Already-successful issue comments may be emitted again.
## Expected behavior
Projection retries are idempotent per logical outbound action, using an outbox or equivalent durable idempotency key.
## Verification
Inject a partial GitHub API failure after one successful comment, retry the same batch, and assert the successful comment exists exactly once while remaining actions complete.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the review context in PR #375 and trace the projection batch retry path. Reproduce a partial GitHub API failure after one successful comment, retry the same batch, and verify that the successful comment exists exactly once while the remaining actions complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, typescript
- Domain
- api, backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100