Fix: [DIRECT] Expose direct-bounty verifier-readiness diagnostics - #726
Open
charlieseay wants to merge 1 commit into
Open
Fix: [DIRECT] Expose direct-bounty verifier-readiness diagnostics#726charlieseay wants to merge 1 commit into
charlieseay wants to merge 1 commit into
Conversation
Resolves NSPG13#638 Generated by Talos autonomous bounty hunter. Bounty platform: github Bounty ID: 638 Quality gates passed: - meaningful: ✓ - syntax: ✓ - duplicate: ✓ - title: ✓ - tests: ✓
Owner
|
The PR is in the manual-security-review lane because it changes verifier-readiness behavior. What passed: it targets a concrete diagnostics request. What blocks main: readiness must fail closed and cannot be inferred from a planner response, comment, transaction hash, or stale row. Action: run cargo run -p cli -- docs-contract-check and focused API tests, then cover missing verifier policy, stale indexer data, malformed evidence, and confirmed ready-to-earn state. Done when each case has a deterministic expected result. Thanks for helping the community grow, and sorry for the review friction. This is not merge, bounty, or payment approval. |
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
2 participants
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.
Resolves #638
Solution
Expose verifier-readiness diagnostics via API and MCP with verifier set hash, threshold, runner identifier, and readiness status. Includes fail-closed logic that excludes unready bounties from ready-to-earn results with concise reasons. Tests cover healthy, missing-signer, stale-runner, and verifier-set-mismatch states.
Quality Checks
All pre-submission quality gates passed:
🤖 Generated by Talos | Bounty reward: $0