MRWK bounty: 75 MRWK - live verification and bug reports, round 2

[ramimbo]

MergeWork status: live bounty

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

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: 75 MRWK per accepted award
Max awards: 8

Work Needed

Concrete verification reports and bug reports for current live MergeWork behavior. This round continues the useful work from #656, but should avoid repeating the same canonicalization, path-alias, filter-alias, or MCP schema reports unless the finding is clearly distinct and still reproducible.

Useful targets include:

• bounty lifecycle behavior: proposed, live, accepted, paid, closed
• treasury proposal status, execution visibility, and challenge visibility
• admin treasury/status pages and public status data
• GitHub labels and comments created by automation
• public bounty pages, activity pages, API endpoints, and MCP endpoints
• canonical mrwk.online URLs and legacy endpoint compatibility
• documentation or runbook mismatches that would mislead a maintainer or contributor

Acceptance Criteria

Accepted reports must:

• include a public evidence URL or reproducible command;
• state expected behavior, observed behavior, and why it matters;
• be current against production or current main;
• include enough detail for a maintainer to verify without guessing;
• be distinct from already accepted reports, open PRs, or merged fixes;
• avoid private security details, secrets, and unsupported MRWK value claims.

Reports can be issue comments or focused PRs. A report can be accepted even if the fix is handled separately.

How To Submit

After this issue becomes live, submit a focused report comment or focused PR that includes Bounty #<this issue number>. Link any related issue, PR, API endpoint, command output, or public page.

Do not submit work for this bounty before the public bounty row exists and the claims-open reserve comment is posted.

Evidence or Tests Required

For reports, include:

• checked URL or command;
• expected behavior;
• observed behavior;
• timestamp or current-head context when relevant;
• duplicate search notes when the finding is similar to an existing report.

For PRs, include focused tests or smoke evidence appropriate to the changed behavior.

Out of Scope

• Duplicate reports that add no new evidence or separate affected surface.
• Vague reports with no reproduction or public evidence.
• Repeating already accepted MRWK bounty: 75 MRWK - live verification and bug reports, round 1 #656 canonicalization/path/filter/MCP findings without a clearly distinct current bug.
• Speculative feature requests without a verified current problem.
• Private security exploit details, private keys, secrets, admin tokens, or wallet recovery material.
• Price, investment, exchange, liquidity, bridge, cash-out, fabricated payout, or token-value claims.

Duplicate and Stale Work Rules

Duplicate work is judged by the first useful, reviewable report or PR that matches the bounty criteria. Maintainers may reject stale reports when current production or main no longer shows the behavior. If an open PR already fixes the issue, add useful review evidence there instead of filing a duplicate report.

[ramimbo]

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

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.