fix(scoring): require solved-by-PR evidence for linked issues - #506
Merged
Conversation
|
Note Gittensory Gate skippedPR closed before full evaluation. No late first comment was created.
Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers. |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
gittensory-ui | 9865211 | Commit Preview URL Branch Preview URL |
Jun 10 2026, 08:03 AM |
JSONbored
force-pushed
the
codex/propose-fix-for-validation-bypass-issue
branch
2 times, most recently
from
June 10, 2026 07:56
ec6e662 to
1c64477
Compare
JSONbored
force-pushed
the
codex/propose-fix-for-validation-bypass-issue
branch
from
June 10, 2026 08:02
1c64477 to
9865211
Compare
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Closed
12 tasks
This was referenced Jul 2, 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.
Motivation
linkedIssueContext.status = "validated"from granting the standard linked-issue multiplier without concrete solved-by-PR evidence, which allowed forged private preview records to inflate scores.Description
src/scoring/preview.tsso a requestedstatus: "validated"is downgraded toraw/unavailableunlesssolvedByPullRequests(or an internal projection marker) provides solved-by-PR evidence and branch eligibility also passes.projectedSolvedByPullRequestValidationflag toLinkedIssueMultiplierContextand the projection helperwithValidatedLinkedIssueScenarioso scenario projections can model future solved-by-PR validation without trusting API input.test/unit/scoring.test.tsto assert that forged validated contexts without solver PR evidence remain ineligible and receive no multiplier, and adjusttest/unit/eligibility-scenarios.test.tsfixtures to include concrete solved-by-PR evidence for genuinely validated cases.Testing
npx vitest run test/unit/scoring.test.ts -t "requires solved-by-PR validation" --reporter verboseand it passed.npx vitest run test/unit/scoring.test.ts test/unit/eligibility-scenarios.test.ts --reporter verboseand all tests passed.npm run typecheckand rangit diff --checkwith no issues reported.Codex Task