MRWK bounty: 200 MRWK - fix confirmed production issues from accepted reports

[ramimbo]

MergeWork status: live bounty

Reserved on MergeWork: https://mrwk.online/bounties/107

Claims are open only while the public bounty row remains open and effective award capacity remains. Use the public bounty page or API as the authoritative current status.

MRWK Bounty

Reward: 200 MRWK per accepted award
Max awards: 5

Work Needed

Open focused PRs that fix confirmed production issues from accepted or clearly useful public reports. This bounty is the implementation lane for concrete reports that are already actionable, especially after #656 filled.

Eligible source material includes:

• accepted or clearly useful reports from MRWK bounty: 75 MRWK - live verification and bug reports, round 1 #656;
• accepted proposed-work issues;
• maintainer-routed issue comments;
• queue-run findings that identify a current, reproducible production problem.

This bounty is for implementation PRs, not for posting new reports. Reporters and fixers can be different people: a useful report may be paid under a report bounty, while a separate implementation PR may be paid here.

Acceptance Criteria

Accepted PRs must:

• link this bounty issue after it becomes live;
• link the exact report, proposed-work issue, or maintainer comment being fixed;
• show the issue is still current before the fix, unless the linked report was just accepted and remains obviously current;
• make one focused fix per PR;
• include regression tests, docs smoke checks, or live/API smoke evidence appropriate to the fix;
• avoid duplicating another useful open PR for the same source report;
• avoid double-claiming another live or pending bounty for the same work.

Maintainers may reject work that is stale, duplicate, overly broad, low value, or only loosely related to the cited report.

How To Submit

After this issue becomes live, open a focused PR and include both:

• Bounty #<this issue number>
• the exact source report/comment/issue URL being fixed

If an open useful PR already addresses the same report, review that PR or choose another source issue instead of opening a duplicate.

Evidence or Tests Required

Include the evidence that fits the change:

• regression tests for route/API/MCP behavior changes;
• docs smoke checks for documentation or template changes;
• before/after command output or API examples for live-facing fixes;
• UI smoke evidence for public page changes;
• explanation of why the fix remains scoped to the cited report.

Out of Scope

• Posting new bug reports without an implementation PR.
• PR reviews, smoke reports, or proposed-work intake posts without a fix.
• Broad feature bundles that should have a dedicated bounty.
• Duplicates of open useful PRs or work already accepted under another bounty.
• Generic refactors, formatting churn, typo-only edits, or no-value AI output.
• Ledger, treasury, wallet, or security-sensitive changes unless the source report clearly scopes the work and maintainers can review it safely.
• Price, investment, exchange, liquidity, bridge, cash-out, fabricated payout, private security detail, secret, or token-value claims.

Duplicate and Stale Work Rules

Duplicate work is judged by the first useful, reviewable PR for a source report. Stale work may be rejected when the cited behavior no longer reproduces or current main already fixes it. If multiple reports describe the same root problem, maintainers may accept only one consolidated fix.

[ramimbo]

Treasury proposal: https://api.mrwk.online/api/v1/treasury/proposals/126

Status: not claimable yet. Do not submit /claim work from this issue until the proposal executes, the public bounty row exists, and the Reserved on MergeWork claims-open comment is posted.