Repository navigation
fix(discovery): park purpose-held submissions in the ledger - #605
Merged
Merged
Conversation
Contributor
Author
🤖 MERGED
GitHub merged this pull request.
a244c334-2118-416b-9265-9ae16cf3cf7d Selected findings run after merge and open separate pull requests. |
Contributor
Author
There was a problem hiding this comment.
Harlan Agent Kit posted this automated review. AI open source policy.
Automated Review: READY.
This was referenced Oct 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔗 Linked issue
Closes #603
❓ Type of change
📚 Description
The purpose gate added in #581 fails new submissions it cannot classify with
repository_purpose_review_required. When that job exhausts its retries,reconcileLedgerhad no branch for the dead-letter, so five ledger rows (antfu/skills-pack, feitangyuan/onetake, trungtin/codex-delegate, tsogjavklann/awwwards-3d, aryanutkarsh/seecode) stayedsubmittedand alarmed as stalled every night instead of parking for the review surface.The gate is a request for a person, not an answer about the repository. Emptying the row would record a verdict nobody made, and retrying re-runs a job that fails the same gate. So the row parks: back to
pendingwithheld_reason = 'repository_purpose_review_required'andsubmitted_atcleared, which puts it on the holds surface, out of the submit queue, and out of the stalled count.One thing a reviewer should weigh: releasing a hold on the discovery surface alone re-enqueues the submission, and the gate fails it again unless a trust override or owner verification exists; rejecting records the human no. I did not teach the purpose admission check to read
reviewed_at, since that widens the change past the ledger.