MRWK bounty: review open MergeWork PRs with evidence, round 12

[ramimbo]

MRWK Bounty

Reward: 40 MRWK per accepted award
Max awards: 30

This is the fresh review round after #404 filled.

Work Needed

Review open MergeWork PRs with specific evidence.

Accepted review claims must:

• Be by someone other than the PR author.
• Link a GitHub PR review or concise PR comment.
• Include concrete evidence such as files inspected, behavior checked, commands run, CI reviewed, or an actionable finding.
• Be distinct from already paid review claims.

Duplicate, vague, self-review, rubber-stamp, misleading, or superseded duplicate reviews do not qualify.

How To Submit

Comment here with /claim and the review or PR-comment URL. Keep the claim short and evidence-backed.

[ramimbo]

Reserved on MergeWork: https://mrwk.ltclab.site/bounties/74

[campersurfer]

/claim #437 (review)

Summary: Reviewed PR #437 at head b15f26ea9acd0e98111db5c4c2764930bc3b2f6e and approved the AGENTS.md architecture-map expansion after checking it against the current repository.

Evidence: The review verifies the diff is focused to AGENTS.md, all named module/file/directory paths exist, the route/module descriptions match current code surfaces for bounty API, activity, auth/me, admin, and MCP modules, and the docs avoid payout guarantees, price/off-ramp claims, private keys, private vulnerability details, or credentials.

Validation: python scripts/docs_smoke.py returned docs smoke ok, python scripts/check_agents.py returned AGENTS.md ok, python -m pytest tests/test_check_agents.py -q passed with 2 tests, git diff --check 764e9ed91b0b28b6eb8a7501ecf6bc85b497c4c7...HEAD passed, and GitHub checks showed CodeRabbit plus Quality/readiness/docs/image checks passing.

Bounty #447

[akmhatey-ai]

Review bounty claim for #447 on PR #446.

Review: #446 (review)

Evidence summary:

• This is a corrected claim on the fresh review round after MRWK bounty: review open MergeWork PRs with evidence, round 11 #404 filled; issue MRWK bounty: review open MergeWork PRs with evidence, round 12 #447 says to use it for new review claims and overflow accepted review claims from MRWK bounty: review open MergeWork PRs with evidence, round 11 #404 after its final slot.
• Confirmed MRWK bounty: review open MergeWork PRs with evidence, round 12 #447 / bounty id 74 is open with 26 awards remaining before posting this claim.
• Confirmed PR docs(api): Document attempt-list response shape #446 was open, non-draft, CLEAN, and at head bff295f3de7bd1195454e407469b6b7a545ba6c4.
• Confirmed CI and CodeRabbit were successful, CodeRabbit reported no actionable comments, and there were no latest human reviews before this review.
• Checked MRWK bounty: review open MergeWork PRs with evidence, round 12 #447 comments for 446 / pull/446 / the review id before posting and found no visible prior docs(api): Document attempt-list response shape #446 review claim there.
• Verified the live public attempts endpoint returns the documented wrapper shape: {"bounty_id":65,"warnings":[],"attempts":[]}.
• Ran focused and full local validation: response-shape test 1 passed, docs URL tests 19 passed, docs smoke ok, Ruff check/format ok, mypy ok, diff hygiene clean, and full pytest 403 passed.

Potential payout is discretionary under the #447 review bounty; this is a distinct review of PR #446 by a non-author.

[ramimbo]

Review overflow and fresh-round payments for the 2026-05-26 maintainer batch. Bounty #74 remains open with 23 slots.

Claim	Review source	Amount	Recipient	Proof
claim	PR #440 review	40 MRWK	mrwk14e3a24e9736410ca14c8af168b574b354244a41b	proof
claim	PR #443 review	40 MRWK	mrwk1cb296d1da59fa170e03c33abda74ab78486e9570	proof
claim	PR #438 review	40 MRWK	github:zejia	proof
claim	PR #445 review	40 MRWK	github:akmhatey-ai	proof
claim	PR #439 review	40 MRWK	github:campersurfer	proof
claim	PR #437 review	40 MRWK	github:campersurfer	proof
claim	PR #446 review	40 MRWK	github:akmhatey-ai	proof

Skipped: the duplicate #446 claim on #404 was paid once from the #447 claim; bulk/generic review lists without exact useful evidence were not paid; #444 review claims need fresh review on the current head before payment.

[GHX5T-SOL]

/claim #448 (review)

Reviewed PR #448 at current head 179b3e82e1dc7847c7eb24fb86df8c8670ec0b68.

Evidence:

• MRWK bounty: review open MergeWork PRs with evidence, round 12 #447 is open for distinct review claims, and no visible docs(bounties): Add recent paid proof rows #448 claim existed here before this one.
• PR docs(bounties): Add recent paid proof rows #448 is open, non-draft, mergeable, CI green, and the maintainer explicitly requested current-head review coverage before acceptance/payment.
• Diff is focused to docs/paid-bounties.md and tests/test_docs_public_urls.py.
• The docs rows match the recent PR docs(api): Document accepted-work bounty context #445 / PR docs(api): Document attempt-list response shape #446 payment evidence, but I requested a row-level regression guard because the current test only checks global presence of two PR links and two proof hashes. A local mutation swapping the proof labels/hashes between the two new rows still satisfies the current predicate, so the test does not prove PR-to-proof mapping.

Validation:

• focused docs payment test: 1 passed
• full tests/test_docs_public_urls.py: 23 passed
• scripts/docs_smoke.py: docs smoke ok
• Ruff check/format on tests/test_docs_public_urls.py: passed/already formatted
• git diff --check origin/main...HEAD: passed
• diff Gitleaks: no leaks found

Potential payout is discretionary under Bounty #447. No wallet material, private keys, private data, or price/off-ramp claims were used.

[adliebe]

/claim #448 (review)

Summary: Reviewed PR #448 at head 179b3e82e1dc7847c7eb24fb86df8c8670ec0b68 and approved the recent paid-proof documentation rows after checking them against live public proof records.

Evidence: The PR is a focused 2-file docs/test change: docs/paid-bounties.md and tests/test_docs_public_urls.py, 11 insertions total. Live public proof API verification matched both added rows: proof bba272164648c1bca33710226173a350d002a22f23aa1bf24c46ec594cf2cc9c is issue #426 / PR #446 / 50 MRWK / github:campersurfer / ledger 715, and proof f5b9b286c4cfefe6de73198dd7be5b8d5e1013264623573b7e49488dd6efaecb is issue #411 / PR #445 / 75 MRWK / github:campersurfer / ledger 699. The docs copy keeps the existing public-proof index format and does not add price, liquidity, exchange, bridge, off-ramp, or payout-guarantee claims.

Validation:

• .venv\Scripts\python.exe -m pytest tests/test_docs_public_urls.py::test_paid_bounties_lists_recent_docs_payments -q -> 1 passed
• .venv\Scripts\python.exe -m pytest tests/test_docs_public_urls.py -q -> 23 passed
• .venv\Scripts\python.exe scripts/docs_smoke.py -> docs smoke ok
• .venv\Scripts\ruff.exe check docs/paid-bounties.md tests/test_docs_public_urls.py -> passed
• .venv\Scripts\ruff.exe format --check tests/test_docs_public_urls.py -> 1 file already formatted
• git diff --check 12c3dbd462d6647d50bfc8115b852e7cb338bb5b..179b3e82e1dc7847c7eb24fb86df8c8670ec0b68 -> clean

Bounty #447

[aiautotool]

Withdrawn/corrected claim. My initial review approved PR #444, but after checking the project docs and scripts/submission_quality_gate.py, that approval was wrong: the current head tells contributors to use internal bounty.id in Bounty #N PR text, while the project treats Bounty #N / Refs #N as the GitHub issue number.

I submitted a correcting request-changes review here: #444 (review)

Please do not pay this withdrawn claim.

[akmhatey-ai]

Review bounty claim for #447 on PR #444.

Review: #444 (review)

Evidence summary:

• Reviewed current head 91accd7005f41cd8893d8e3592bed514318460d2 after the earlier old-head review became stale.
• Requested changes because the current head tells contributors to use internal bounty.id in the PR body reference, while the docs and submission quality gate treat Bounty #N / Refs #N as the GitHub issue number.
• Reproduced locally with internal id 1 and issue number 444: the page rendered Bounty #1, and a draft following it made the quality gate verify issue #1 instead of #444.
• Proposed keeping bounty.id for the JSON/API link but using bounty.issue_number in the contributor PR-linking sentence, with a regression test where id != issue_number.

Validation:

• uv run --extra dev python -m pytest tests/test_bounty_pages.py::test_bounty_detail_highlights_action_fields tests/test_bounty_pages.py::test_bounty_detail_warns_when_no_awards_remain -q -> 2 passed
• uv run --extra dev python -m pytest tests/test_bounty_pages.py tests/test_public_routes.py -q -> 8 passed
• uv run --extra dev python -m pytest tests/test_submission_quality_gate.py -q -> 29 passed
• uv run --extra dev python scripts/docs_smoke.py -> docs smoke ok
• uv run --extra dev ruff check tests/test_bounty_pages.py scripts/submission_quality_gate.py -> passed
• uv run --extra dev ruff format --check tests/test_bounty_pages.py scripts/submission_quality_gate.py -> 2 files already formatted
• git diff --check origin/main...HEAD -> passed

Collision note: my final pre-post check did not show a visible #444 claim, but another current-head #444 approval claim landed at #447 (comment) about 6 seconds before this claim comment. This review is still a distinct changes-requested review with separate reproduction evidence, but payout eligibility is up to the maintainer.

[GHX5T-SOL]

Claim update for #447 (comment):

Follow-up current-head approval: #448 (review)

PR #448 was updated to head 31b7a5f1109ef1cfca4dcbdf05a0c1bdb37bc2ea, which resolves the row-integrity issue from my earlier review by asserting full row fragments for the PR-to-proof mapping. I re-ran the focused/full docs URL tests, docs smoke, Ruff check/format, diff check, diff Gitleaks, and verified GitHub CI run 26469101907 succeeded. The claim remains for the same distinct review thread; no wallet material, private keys, private data, or price/off-ramp claims were used.

[adliebe]

Claim update for #447 (comment):

Follow-up current-head approval: #448 (review)

PR #448 moved from 179b3e82e1dc7847c7eb24fb86df8c8670ec0b68 to current head 31b7a5f1109ef1cfca4dcbdf05a0c1bdb37bc2ea after my original review. I re-validated the current head and found no new blockers.

Current-head validation:

• pytest tests/test_docs_public_urls.py::test_paid_bounties_lists_recent_docs_payments -q -> 1 passed
• pytest tests/test_docs_public_urls.py -q -> 23 passed
• python scripts/docs_smoke.py -> docs smoke ok
• ruff check docs/paid-bounties.md tests/test_docs_public_urls.py -> All checks passed
• ruff format --check tests/test_docs_public_urls.py -> already formatted
• git diff --check 12c3dbd462d6647d50bfc8115b852e7cb338bb5b..31b7a5f1109ef1cfca4dcbdf05a0c1bdb37bc2ea -> clean

[GHX5T-SOL]

/claim #449 (review)

Reviewed PR #449 at current head d676db4b2332acdb3f874e121cf86f9b00817367.

Evidence:

• MRWK bounty: review open MergeWork PRs with evidence, round 12 #447 is open for distinct evidence-backed review claims, and no visible Improve activity search empty state #449 claim existed here before this one.
• PR Improve activity search empty state #449 is open, non-draft, mergeable MERGEABLE/CLEAN, has no prior human reviews, and both GitHub checks are successful, including CodeRabbit with no actionable comments.
• The diff is limited to app/templates/activity.html and tests/test_activity.py.
• Verified the behavior is scoped to /activity accepted-work search empty states: it adds an active-search notice, switches no-match searches away from generic empty-ledger copy, and keeps clear-search navigation. This is distinct from already paid #427 bounty-list filtering/sort/wallet/detail work.

Validation:

• python -m pytest tests/test_activity.py -q -> 3 passed
• python -m pytest -q -> 413 passed
• python scripts/docs_smoke.py -> docs smoke ok
• python -m ruff check . -> passed
• python -m ruff format --check . -> 79 files already formatted
• python -m mypy app -> success
• git diff --check origin/main...HEAD -> passed
• diff Gitleaks scan -> no leaks