MRWK bounty: 40 MRWK - review open MergeWork PRs with evidence, round 17

[ramimbo]

This is a proposal-gated review bounty issue. It is not claimable yet. Do not submit /claim work from this issue until the treasury proposal executes, the public bounty page exists, and maintainers post Reserved on MergeWork.

Work needed

Review open MergeWork pull requests with concrete current-head evidence. This round exists to keep the PR queue moving while #601 is effectively almost full from pending review payout proposals.

Reward

40 MRWK per accepted review, up to 30 awards, if the treasury proposal executes.

Priority targets

• PR Automate post-execution bounty issue updates #630 first, because it simplifies post-execution bounty issue finalization.
• Clean, mergeable PRs that are close to acceptance.
• Blocker reviews on stale-looking or dirty PRs where the review gives maintainers a clear close/fix/rebase decision.

Acceptance criteria

Accepted reviews must be by non-authors and must link a GitHub PR review or concise PR comment with concrete evidence. Useful evidence includes files inspected, behavior checked, commands run, CI reviewed, mergeability checked, duplicate/overlap check, current-head SHA reviewed, or a specific actionable finding.

Out of scope

• rubber-stamp approvals
• vague comments
• stale-head reviews that do not account for current code
• duplicate reviews that add no new evidence
• self-reviews
• reviews that treat closed, exhausted, or pending-only bounty issues as live work
• reviews containing private secrets, private vulnerability details, or speculative MRWK price, exchange, bridge, liquidity, cash-out, or payout claims

Duplicate and stale review rules

Duplicate work is judged by the first useful, evidence-backed review. Stale reviews may be skipped if the PR head changes materially before acceptance. Reviews may identify blockers and still qualify if they give maintainers concrete action.

[ramimbo]

Treasury proposal created: https://api.mrwk.ltclab.site/api/v1/treasury/proposals/52

This issue is still not claimable. Do not submit /claim work from this issue until the proposal executes, the public bounty page exists, and maintainers post Reserved on MergeWork.

Earliest execution time: 2026-05-31 10:44 UTC, assuming no valid challenge blocks it.