MRWK bounty: 50 MRWK - accepted proposed-work requests, round 2

[ramimbo]

MRWK Bounty

Status: proposed bounty. This issue is not claimable until the treasury proposal executes, the public bounty page exists, and the Reserved on MergeWork claims-open comment is posted.

Reward: 50 MRWK per accepted award
Max awards: 10

Work Needed

Open useful proposed-work issues using the proposed-work issue template. Accepted proposals should help maintainers choose, size, or reject future work without guessing.

How The Process Works

1. Open a new issue with the Proposed work template.
2. Link this bounty issue from that proposed-work issue, or comment here with the proposed-work issue URL.
3. Include the problem, current evidence, proposed work, expected value, acceptance or test notes, duplicate search, out-of-scope notes, and a suggested reference tier if useful.
4. Maintainers review the proposed-work issue. Accepted proposal posts can be paid from this bounty through a public pay_bounty proposal.
5. The proposed-work issue itself is not a live implementation bounty unless a separate create_bounty proposal later executes and adds mrwk:bounty plus Reserved on MergeWork.

Acceptance Criteria

A proposal qualifies only when it is concrete, current, non-duplicate, and useful for the project. It should include enough evidence for maintainers or agents to understand the problem, why it matters, and what accepted future work could look like.

Useful proposals usually include:

• links to the relevant docs, code, UI route, API route, issue, PR, discussion, or observed behavior
• a clear maintainer decision the proposal supports
• rough acceptance criteria or verification steps for future work
• duplicate search notes
• clear non-goals and out-of-scope work
• a suggested README reference tier when sizing guidance helps

Reference tiers are guidance only. They do not make a proposed-work issue claimable and do not promise payment for future implementation.

Evidence or Tests Required

For payment review, link the proposed-work issue and summarize why it is useful. The proposed-work issue must contain the concrete evidence, duplicate search, and scope notes above.

Out of Scope

• Vague idea lists, generic AI output, or broad rewrites without evidence.
• Duplicate proposals for the same problem or work already covered by a live or pending bounty.
• No-value typo-only posts unless they identify a real documentation failure pattern.
• Claims that a proposed-work issue is already a live bounty.
• Price, investment, exchange, liquidity, bridge, cash-out, fabricated payout, private security detail, secret, or token claims.

Duplicate and Stale Work Rules

Duplicate work is judged by the first useful, reviewable proposed-work issue that identifies the problem and gives maintainers enough evidence to act. Maintainers may reject stale, superseded, unsupported, or no-longer-relevant proposals.

[ramimbo]

Public treasury proposal created: https://api.mrwk.online/api/v1/treasury/proposals/105

Status: pending create_bounty. Earliest execution: 2026-06-01T18:46:19Z if no valid blocking challenge exists.

This issue is not claimable yet. Claims open only after proposal execution creates the public bounty row and finalizes the GitHub issue with mrwk:bounty plus the claims-open reserve comment.

[ramimbo]

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

Claims are now open for accepted work that matches this bounty's criteria.

[attaboy11]

/claim #722

Proposed-work issue: #772

Why this is useful:

• identifies a current post-finalization contradiction using live MRWK bounty: 50 MRWK - accepted proposed-work requests, round 2 #722 evidence: the issue has mrwk:bounty, a Reserved on MergeWork comment, and public bounty row https://mrwk.online/bounties/101, while the issue body still says Status: proposed bounty and not claimable;
• links public treasury proposal 105 execution evidence and the completed MRWK bounty: 50 MRWK - accepted proposed-work requests, round 1 #649 stale-body example;
• links source evidence that app/github_issue_finalization.py currently labels/comments but does not edit or annotate the issue body;
• proposes a narrow, idempotent finalization-body status block with tests, preserving the existing label/comment flow and non-blocking error behavior;
• includes duplicate-search notes against related proposed-work issues (Proposed work: add a related bounty/source field to the proposed-work template #708, Proposed work: expose structured submission mode for non-PR bounties #676, Proposed work: add bounty lifecycle and treasury discovery links to public docs #709, Proposed work: expose public deployment revision metadata for API and MCP #718) and explains why this specific body-refresh path is not already covered.

No private payout details, wallet secrets, price/exchange/liquidity/cash-out claims, or private security details are included.

[JONASXZB]

/claim #722

Proposed-work issue: #774

Why this is useful:

• identifies a current live-bounty lifecycle evidence gap on public bounty rows: they expose status/capacity and the source issue URL, but not the public create-bounty proposal or claims-open Reserved on MergeWork comment URL;
• links concrete live evidence from MRWK bounty: 50 MRWK - accepted proposed-work requests, round 2 #722, including the public treasury proposal comment and the claims-open reserve comment;
• distinguishes this from Proposed work: refresh live bounty issue status after finalization #772, which refreshes the GitHub issue body after finalization but does not add machine-readable finalization evidence to bounty API rows;
• proposes a narrow additive/read-only API serialization improvement with nullable fields for older rows, focused tests, docs guidance, and no payment, treasury, wallet, bridge, exchange, cash-out, price, private state, or secret claims.

Note: I attempted to add the proposed-work label, but GitHub label mutation requires maintainer/admin rights from this account. The issue title/body follow the proposed-work template sections and link this bounty explicitly.

[ramimbo]

Accepted claims queued as pending pay_bounty proposals. These are not paid until proposal execution creates proof links.

Source	Recipient	Proposal	Executes after
#772	github:attaboy11	https://api.mrwk.online/api/v1/treasury/proposals/121	2026-06-02T19:59:40.475521Z
#774	github:jonasxzb	https://api.mrwk.online/api/v1/treasury/proposals/122	2026-06-02T19:59:40.593915Z

[JONASXZB]

/claim #722

Proposed-work issue submitted: #778

Summary:

• Proposes rejecting whitespace-padded public account and wallet path identifiers before normalization.
• Includes live read-only evidence from account and wallet API/HTML routes showing %20-padded identifiers resolve to canonical resources with HTTP 200.
• Includes comparison with stricter ledger/proof path behavior, proposed focused scope, acceptance/verification notes, duplicate search, and out-of-scope boundaries.
• This is a proposed-work request only; it does not implement wallet mutation, payout, treasury, custody, exchange, bridge, off-ramp, or price/liquidity behavior.

[JONASXZB]

/claim #722

Proposed-work issue submitted: #779

Summary:

• Proposes consistent fail-closed handling for whitespace-padded public scalar string filters.
• Includes live evidence for bounty list, treasury proposal, activity, and wallet search filters accepting %20...%20 values with HTTP 200.
• Separates optional API-only scope from user-facing HTML search convenience so maintainers can choose a narrow implementation.
• Includes duplicate search and out-of-scope boundaries; this is distinct from Proposed work: reject whitespace-padded account and wallet path IDs #778, which covers account/wallet path identifiers.